1 |
Nicolas Sebrecht wrote: |
2 |
> hasufell wrote: |
3 |
> > You can use the command line too. |
4 |
> > |
5 |
> > www-client/pybugz |
6 |
> |
7 |
> I know this tool. I did try it. At that time it was buggy and did not |
8 |
> work for me. Though, this would still be a busy process as this is just |
9 |
> another interface og the bugzilla thing. |
10 |
|
11 |
It's another command to run, just like git. As others have pointed out, the use of |
12 |
a bug-tracker is important in terms of managing the process. That still stands. |
13 |
|
14 |
> > Git workflow has been on the todo list for a long time, as well as |
15 |
> > review systems such as gerrit. |
16 |
> > |
17 |
> > It is non trivial to implement |
18 |
> |
19 |
> Other than the git repository size requiring a huge initial clone, it's |
20 |
> very easy to do. And yes, I've read all the headaches on the Gentoo |
21 |
> mailing lists about the git migration. |
22 |
|
23 |
Using git and accepting patches on a mailing-list wouldn't change the process you |
24 |
discuss: it would just make everything harder to manage, and require more work on |
25 |
the part of maintainers. And there are no people working full-time on Gentoo ebuilds, |
26 |
in contrast to Linux kernel development. |
27 |
|
28 |
So aiming for that as a model, is simply a bad idea: the circumstances and the time |
29 |
available are radically different. As is the product. |
30 |
|
31 |
> Also, Gentoo organization has two heads making ambitious dicisions hard |
32 |
> to take. And AFAIKS, to decision process in Gentoo is not helping at |
33 |
> all. We are far from how it worked at the genesis/beginning of Gentoo. |
34 |
|
35 |
I don't agree: Gentoo is much stronger now. But more importantly I don't see this |
36 |
as relevant in the slightest. You appear to be whinging basically, that you weren't |
37 |
welcomed with open arms on the strength of your email to the list, so you emailed |
38 |
again and "no-one cared." And going from there to drawing wider conclusions on a |
39 |
the whole setup, as if that's the reason you were snubbed *sniffle*. Total non- |
40 |
sequitur imo. |
41 |
|
42 |
> > It is non trivial to implement and none of it is an excuse for not |
43 |
> > contributing IMO ;) |
44 |
> > |
45 |
> > Those are enhancements and we are already working on it. Get your hands |
46 |
> > dirty. |
47 |
> |
48 |
> Oh, yes. Pass the recruitement process to enhance the recruitement process, |
49 |
> workflow and decision process (not possible to change, IMO). Funny! :-) |
50 |
|
51 |
No: just contribute. |
52 |
|
53 |
> Again, I proposed myself to the dev list two times in the past. Nobody |
54 |
> cared and I had no answers. |
55 |
|
56 |
Because that has never been the process: anyone can post to the mailing-list, it |
57 |
doesn't mean anything. While I agree it would have been good if recruiters had |
58 |
followed it up with you, if you're so new to Gentoo that you think the ML is how |
59 |
to start, then I can see why people might feel you needed to learn more, perhaps |
60 |
by reviewing the documentation. And if that's too much to ask, then perhaps you're |
61 |
not cut out to be a Gentoo developer: ime you need to be more of a self-starter |
62 |
just to use the distro. |
63 |
|
64 |
Please don't get me wrong: I think the recruitment process could be improved, in |
65 |
particular by having more developers working on it. And that does take a cultural |
66 |
shift, in terms of seeing recruitment as important, and a desirable thing to work |
67 |
on, as well as in terms of being more proactive and welcoming to newcomers, and to |
68 |
external perspectives. |
69 |
|
70 |
Neither of those change the fact that you don't join a team just by sending them |
71 |
an email. Like it or not, there are social factors involved, or it wouldn't be |
72 |
a team of people, however loosely associated. |
73 |
|
74 |
And if you cba to review the basics, stuff most users know, or can find out easily, |
75 |
what makes you think you're cut out to be a developer? |
76 |
|
77 |
Please note I'm not discussing any technical ability you may or may not have with |
78 |
bash, ebuilds or upstream sources. Just your ability to find out the basics, which |
79 |
is much less difficult than installing Gentoo in the first place. |
80 |
|
81 |
If you want/ed to be a developer, my advice would always be: show you're useful, not |
82 |
that you need hand-holding and ego-stroking from the get-go. |
83 |
|
84 |
-- |
85 |
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-) |