1 |
On 05/16/2012 02:29 PM, Dirkjan Ochtman wrote: |
2 |
> On Wed, May 16, 2012 at 2:26 PM, Kacper Kowalik <xarthisius@g.o> wrote: |
3 |
>> I'd like to propose that we create and maintain overlay for Python |
4 |
>> project. As I envision it, it would mostly oriented towards the users |
5 |
>> (read new developers). We could encourage people to push new version |
6 |
>> bumps there, keep packages not-yet-ready for tree (alphas,betas,rc) etc. |
7 |
> |
8 |
> Can you say something about what/how this would make things better |
9 |
> (either for users/almost-developer holdouts or for us)? |
10 |
|
11 |
Taking vesion bump as an example: |
12 |
|
13 |
1) Current workflow - user attaches ebuild/diff to bugzi, you `bugz |
14 |
attachment` it, do all fixes, commit to tree or reject entirely, leaving |
15 |
a comment on bugzilla. Sometimes it's possible to interact via IRC. |
16 |
|
17 |
2) Overlay workflow - user issues a PR, you can comment on per-line |
18 |
basis that stays with the code (and can for example later serve for |
19 |
creating "common mistakes made in ebuilds"), you can patch ebuild on-the |
20 |
spot and request user to take it back and test it, etc. The history of |
21 |
changes stays behind in an easy accessible place. |
22 |
|
23 |
I'd compare 1) as doing vcs as adding current date to filename, and 2) |
24 |
as doing vcs with vcs :) |
25 |
Additionally 2) gives you nice web UI and some users find it appealing. |
26 |
|
27 |
Cheers, |
28 |
Kacper |