| 2012-08-17 01:42:46 |
Tudor Holton |
bug |
|
|
added bug |
| 2012-08-17 01:46:24 |
Tudor Holton |
description |
I apologise if this bug has already been reported. I have searched, but my knowledge of the terminology in this area is a bit hazy.
Currently, the visual display of code contributions is limited to branches and versions.
Frequently, multiple programmers are making separate contributions to different forks in bazaar. Without pull each fork's logs (and sometimes code) separately and analysing the differences, it is difficult to determine if it's worth merging that fork (to simplify merges in either direction later with a main branch)
Github solves this problem by providing a fork map that shows (among other things) when each fork was contributed to, the log summary, and links to the code changes in a visual way. It is scrollable so that it's easy to follow a fork back to see when that fork began, and at what point that fork was merged with other forks.
While many of these tasks can be performed with a combination of bzr commands and UI tools, having on the lp site allows both coders and non-coders alike to see what's being worked on and why.
For example, currently I'm trying to convince a manager that one contributor should not be pandered to because he has been hoarding contributions and hasn't actually commit for almost a year. This would be easy to prove on github, since my manager has an account and can therefore see everything that's going on on every fork, but on launchpad it is painful due to the reliance on command-line tools.
Please consider implementing a interactive fork map tree. |
I apologise if this bug has already been reported. I have searched, but my knowledge of the terminology in this area is a bit hazy.
Currently, the visual display of code contributions is limited to branches and versions.
Frequently, multiple programmers are making separate contributions to different forks in bazaar. Without pulling each fork's logs (and sometimes code) separately and analysing the differences, it is difficult to determine if it's worth merging that fork (to simplify merges in either direction later with a main branch).
Github solves this problem by providing a fork map that shows (among other things) when each fork was contributed to, the log summary, and links to the code changes in a visual way. It is scrollable so that it's easy to follow a fork back to see when that fork began, and at what point that fork was merged with other forks.
In a recent project, I had around a dozen programmers contributing code several times a day on one project. I found myself referring to the interactive fork map sometimes several times a day.
While many of these tasks can be performed with a combination of bzr commands and UI tools, having on the lp site allows both coders and non-coders alike to see what's being worked on and why.
For example, currently I'm trying to convince a manager that one contributor should not be pandered to because he has been hoarding contributions and hasn't actually commit for almost a year. This would be easy to prove on github, since my manager has an account and can therefore see everything that's going on on every fork, but on launchpad it is painful due to the reliance on command-line tools.
Please consider implementing a interactive fork map tree. |
|
| 2012-08-17 01:47:00 |
Tudor Holton |
description |
I apologise if this bug has already been reported. I have searched, but my knowledge of the terminology in this area is a bit hazy.
Currently, the visual display of code contributions is limited to branches and versions.
Frequently, multiple programmers are making separate contributions to different forks in bazaar. Without pulling each fork's logs (and sometimes code) separately and analysing the differences, it is difficult to determine if it's worth merging that fork (to simplify merges in either direction later with a main branch).
Github solves this problem by providing a fork map that shows (among other things) when each fork was contributed to, the log summary, and links to the code changes in a visual way. It is scrollable so that it's easy to follow a fork back to see when that fork began, and at what point that fork was merged with other forks.
In a recent project, I had around a dozen programmers contributing code several times a day on one project. I found myself referring to the interactive fork map sometimes several times a day.
While many of these tasks can be performed with a combination of bzr commands and UI tools, having on the lp site allows both coders and non-coders alike to see what's being worked on and why.
For example, currently I'm trying to convince a manager that one contributor should not be pandered to because he has been hoarding contributions and hasn't actually commit for almost a year. This would be easy to prove on github, since my manager has an account and can therefore see everything that's going on on every fork, but on launchpad it is painful due to the reliance on command-line tools.
Please consider implementing a interactive fork map tree. |
I apologise if this bug has already been reported. I have searched, but my knowledge of the terminology in this area is a bit hazy.
Currently, the visual display of code contributions is limited to branches and versions.
Frequently, multiple programmers are making separate contributions to different forks in bazaar. Without pulling each fork's logs (and sometimes code) separately and analysing the differences, it is difficult to determine if it's worth merging that fork (to simplify merges in either direction later with a main branch).
Github solves this problem by providing a fork map that shows (among other things) when each fork was contributed to, the log summary, and links to the code changes in a visual way. It is scrollable so that it's easy to follow a fork back to see when that fork began, and at what point that fork was merged with other forks.
In a recent project, I had around a dozen programmers contributing code several times a day on one project. I found myself referring to the interactive fork map sometimes several times a day.
While many of these tasks can be performed with a combination of bzr commands and UI tools, having on the lp site allows both coders and non-coders alike to see what's being worked on and why.
For example, currently I'm trying to convince a manager that one contributor should not be pandered to because he has been hoarding contributions and hasn't actually commit for almost a year. This would be easy to prove on github, since my manager has an account and can therefore see everything that's going on on every fork, but on launchpad it is painful due to the reliance on command-line tools.
Please consider implementing an interactive fork map tree. |
|
| 2012-08-17 02:04:21 |
Tudor Holton |
description |
I apologise if this bug has already been reported. I have searched, but my knowledge of the terminology in this area is a bit hazy.
Currently, the visual display of code contributions is limited to branches and versions.
Frequently, multiple programmers are making separate contributions to different forks in bazaar. Without pulling each fork's logs (and sometimes code) separately and analysing the differences, it is difficult to determine if it's worth merging that fork (to simplify merges in either direction later with a main branch).
Github solves this problem by providing a fork map that shows (among other things) when each fork was contributed to, the log summary, and links to the code changes in a visual way. It is scrollable so that it's easy to follow a fork back to see when that fork began, and at what point that fork was merged with other forks.
In a recent project, I had around a dozen programmers contributing code several times a day on one project. I found myself referring to the interactive fork map sometimes several times a day.
While many of these tasks can be performed with a combination of bzr commands and UI tools, having on the lp site allows both coders and non-coders alike to see what's being worked on and why.
For example, currently I'm trying to convince a manager that one contributor should not be pandered to because he has been hoarding contributions and hasn't actually commit for almost a year. This would be easy to prove on github, since my manager has an account and can therefore see everything that's going on on every fork, but on launchpad it is painful due to the reliance on command-line tools.
Please consider implementing an interactive fork map tree. |
I apologise if this bug has already been reported. I have searched, but my knowledge of the terminology in this area is a bit hazy.
Currently, the visual display of code contributions is limited to branches and versions.
Frequently, multiple programmers are making separate contributions to different forks of the same project (and usually the most current version) in bazaar. Without pulling each fork's logs (and sometimes code) separately and analysing the differences, it is difficult to determine if it's worth merging that fork (to simplify merges in either direction later with a main branch).
Github solves this problem by providing a fork map that shows (among other things) when each fork was contributed to, the log summary, and links to the code changes in a visual way. It is scrollable so that it's easy to follow a fork back to see when that fork began, and at what point that fork was merged with other forks.
In a recent project, I had around a dozen programmers contributing code several times a day on one project. I found myself referring to the interactive fork map sometimes several times a day.
While many of these tasks can be performed with a combination of bzr commands and UI tools, having on the lp site allows both coders and non-coders alike to see what's being worked on and why.
For example, currently I'm trying to convince a manager that one contributor should not be pandered to because he has been hoarding contributions and hasn't actually commit for almost a year. This would be easy to prove on github, since my manager has an account and can therefore see everything that's going on on every fork, but on launchpad it is painful due to the reliance on command-line tools.
Please consider implementing an interactive fork map tree. |
|
| 2012-08-17 02:05:24 |
Tudor Holton |
description |
I apologise if this bug has already been reported. I have searched, but my knowledge of the terminology in this area is a bit hazy.
Currently, the visual display of code contributions is limited to branches and versions.
Frequently, multiple programmers are making separate contributions to different forks of the same project (and usually the most current version) in bazaar. Without pulling each fork's logs (and sometimes code) separately and analysing the differences, it is difficult to determine if it's worth merging that fork (to simplify merges in either direction later with a main branch).
Github solves this problem by providing a fork map that shows (among other things) when each fork was contributed to, the log summary, and links to the code changes in a visual way. It is scrollable so that it's easy to follow a fork back to see when that fork began, and at what point that fork was merged with other forks.
In a recent project, I had around a dozen programmers contributing code several times a day on one project. I found myself referring to the interactive fork map sometimes several times a day.
While many of these tasks can be performed with a combination of bzr commands and UI tools, having on the lp site allows both coders and non-coders alike to see what's being worked on and why.
For example, currently I'm trying to convince a manager that one contributor should not be pandered to because he has been hoarding contributions and hasn't actually commit for almost a year. This would be easy to prove on github, since my manager has an account and can therefore see everything that's going on on every fork, but on launchpad it is painful due to the reliance on command-line tools.
Please consider implementing an interactive fork map tree. |
I apologise if this bug has already been reported. I have searched, but my knowledge of the terminology in this area is a bit hazy.
Currently, the visual display of code contributions is limited to branches and versions.
Frequently, multiple programmers are making separate contributions to different forks of the same project (and usually the most current version) in bazaar. Without pulling each fork's logs (and sometimes code) separately and analysing the differences, it is difficult to determine if it's worth merging that fork (to simplify merges in either direction later with a main branch).
Github solves this problem by providing a fork map that shows (among other things) when each fork was contributed to, the log summary, and links to the code changes in a visual way. It is scrollable so that it's easy to follow a fork back to see when that fork began, and at what point that fork was merged with other forks.
In a recent project, I had around a dozen programmers contributing code several times a day on one project. I found myself referring to the interactive fork map sometimes several times a day.
While many of these tasks can be performed with a combination of bzr commands and UI tools, having on the lp site allows both coders and non-coders alike to see what's being worked on and why.
For example, currently I'm trying to convince a manager that one contributor should not be pandered to because he has been hoarding contributions and hasn't actually commit for almost a year. This would be easy to prove on github, since my manager has an account and can therefore see everything that's going on on every fork, but on launchpad it is painful due to the reliance on command-line tools.
Please consider implementing an interactive fork map tree.
Also, if this is bug is unclear, please suggest ways to improve it. |
|
| 2012-08-17 02:09:12 |
Tudor Holton |
description |
I apologise if this bug has already been reported. I have searched, but my knowledge of the terminology in this area is a bit hazy.
Currently, the visual display of code contributions is limited to branches and versions.
Frequently, multiple programmers are making separate contributions to different forks of the same project (and usually the most current version) in bazaar. Without pulling each fork's logs (and sometimes code) separately and analysing the differences, it is difficult to determine if it's worth merging that fork (to simplify merges in either direction later with a main branch).
Github solves this problem by providing a fork map that shows (among other things) when each fork was contributed to, the log summary, and links to the code changes in a visual way. It is scrollable so that it's easy to follow a fork back to see when that fork began, and at what point that fork was merged with other forks.
In a recent project, I had around a dozen programmers contributing code several times a day on one project. I found myself referring to the interactive fork map sometimes several times a day.
While many of these tasks can be performed with a combination of bzr commands and UI tools, having on the lp site allows both coders and non-coders alike to see what's being worked on and why.
For example, currently I'm trying to convince a manager that one contributor should not be pandered to because he has been hoarding contributions and hasn't actually commit for almost a year. This would be easy to prove on github, since my manager has an account and can therefore see everything that's going on on every fork, but on launchpad it is painful due to the reliance on command-line tools.
Please consider implementing an interactive fork map tree.
Also, if this is bug is unclear, please suggest ways to improve it. |
I apologise if this bug has already been reported. I have searched, but my knowledge of the terminology in this area is a bit hazy.
Currently, the visual display of code contributions is limited to branches and versions.
Frequently, multiple programmers are making separate contributions to different forks of the same project (and usually the most current version) in bazaar. Without pulling each fork's logs (and sometimes code) separately and analysing the differences, it is difficult to determine if it's worth merging that fork (to simplify merges in either direction later with a main branch).
Github solves this problem by providing a fork map that shows (among other things) when each fork was contributed to, the log summary, and links to the code changes in a visual way. It is scrollable so that it's easy to follow a fork back to see when that fork began, and at what point that fork was merged with other forks.
In a recent project, I had around a dozen programmers contributing code several times a day on one project. I found myself referring to the interactive fork map sometimes several times a day.
While many of these tasks can be performed with a combination of bzr commands and UI tools, having on the lp site allows both coders and non-coders alike to see what's being worked on and why.
For example, currently I'm trying to convince a manager that one contributor should not be pandered to because he has been hoarding contributions and hasn't actually commit for almost a year. This would be easy to prove on github, since my manager has an account and can therefore see everything that's going on on every fork, but on launchpad it is painful due to the reliance on command-line tools.
Please consider implementing an interactive fork map.
Also, if this is bug is unclear, please suggest ways to improve it. |
|
| 2012-08-17 07:02:24 |
Laura Czajkowski |
launchpad: status |
New |
Triaged |
|
| 2012-08-17 07:02:28 |
Laura Czajkowski |
launchpad: importance |
Undecided |
Low |
|
| 2012-08-17 07:02:47 |
Laura Czajkowski |
tags |
|
bzr ui |
|
| 2012-08-17 14:02:26 |
Curtis Hovey |
tags |
bzr ui |
bzr feature ui |
|
| 2012-08-17 14:02:37 |
Curtis Hovey |
tags |
bzr feature ui |
bzr feature lp-code ui |
|
