1 |
On Thu, August 11, 2005 06:25, Lina Pezzella wrote: |
2 |
> ... by keeping a general policy |
3 |
> page up to date from early on (I.E. now). This will also be of great |
4 |
> help to new developers and potential contributors. It might not be |
5 |
> critical now, but as we expand as a project into the future, it will |
6 |
> become more and more important. |
7 |
|
8 |
We might need our own cornerstone on the web. I used to think pull-based |
9 |
information gathering works, but not any more for me. Far too much |
10 |
sources to pull from, so please consider having a push-based email |
11 |
mechanism which I can subscribe to, to see changes whether they occur, for |
12 |
instance using a syncmail script or something else. |
13 |
|
14 |
> ... we think it might be a good idea to keep a listing of what |
15 |
> each developer is working on with regards to the project (perhaps on |
16 |
> the project page, which we all have CVS commit access to). |
17 |
|
18 |
I've been desperately in need for something like this. On the one hand I |
19 |
want to know what others are doing, but on the other, I'm submitting |
20 |
ebuilds, fix things, working on new ebuilds, etc. I'd like to have (again |
21 |
(also) push-based) mailings of what people do, whenever they think they |
22 |
have a simple line to drop like "took up package xxx-yyy/zzz a dragon to |
23 |
get it to compile". It's bad you cannot easily get CVS log messages |
24 |
(syncmail) for only the commits that I'm interested in (I guess I would |
25 |
get ALL of the commits to portage). |
26 |
|
27 |
> ... We're not looking for a list |
28 |
> of packages people are involved in porting each week; we're looking |
29 |
> to keep track of long-term goals that each developer is working |
30 |
> towards. |
31 |
|
32 |
Well, I would also be interested in the one-liners I described above. You |
33 |
can see it as a sign of life. But maybe this can be automated somehow. |
34 |
Long term goals are ok, but unlikely to change much, so less important, as |
35 |
once you know someone, you figure out what drives that person. |
36 |
|
37 |
> ... Fabian, our most |
38 |
> awesomest recent recruit, did not send us an e-mail; rather, we e- |
39 |
> mailed him after seeing some of his activity in Bugzilla. |
40 |
|
41 |
Please assure yourself that you realise that being 'asked' is much more |
42 |
motivating than actually 'asking' yourself. In Holland we say: "kids who |
43 |
ask, will be skipped". |
44 |
|
45 |
> ... we ... have been trying to promote ML |
46 |
> traffic as of late, as opposed to getting things done via IRC and |
47 |
> keeping them unannounced otherwise. |
48 |
|
49 |
This is a great thing from my perspective: |
50 |
- I'm in an impossible time zone for most of you |
51 |
- I'm a slow reader and writer, as english is not my mother tongue |
52 |
- I like to be able to re-read some things more closely, or being able to |
53 |
skip a bit for now and read it later |
54 |
- IRC -- because it has no layout in any way -- doesn't allow for easy |
55 |
visual message subtraction: you have to read all, and many garbage may |
56 |
appear inbetween. Reading an email like this looks much like a regular |
57 |
paper I read/write, which allows for instance 'skimming'. |
58 |
|
59 |
> ... it's important to keep users informed of changes ... |
60 |
|
61 |
I think (and literature is with me ;) ) that it is vital for any project |
62 |
when this background information (which may not be directly relevant to |
63 |
you) flows through, as you still can quickly relate to it when it suddenly |
64 |
becomes relevant, for instance when someone asks for your help/opinion. |
65 |
|
66 |
> ... it's better to have one unified face than to |
67 |
> have split personality disorder. We are a project, not just a group |
68 |
> of developers that occasionally talk to each other. |
69 |
|
70 |
sure thing(tm) |
71 |
|
72 |
> 4) BugDay Participation (Operations && Strategic) - BugDay is a great |
73 |
> way to meet new potential developers and to allow current developers |
74 |
> to take time off from their current blocker-problem and tackle some |
75 |
> easier stuff. |
76 |
|
77 |
It's also good to participate as a group to a general Gentoo thing. Just |
78 |
to point out we're not different or something. Bugday should also be on |
79 |
our agenda, and we should participate in it -- as group. |
80 |
|
81 |
> In regards to actually voting, what does everybody feel on this? |
82 |
> Should there be a formalized election (such as the use of 'votify'), |
83 |
> or should there just be a public vote on IRC or via e-mail? Since |
84 |
> this hasn't been done before within the Gentoo for Mac OS X project, |
85 |
> we're breaking new ground here. Please make your opinions known! |
86 |
> Also, how much time should be allowed for other developers within the |
87 |
> project to announce candidacy? |
88 |
|
89 |
Personally, I feel that within a small group you don't need anonymous |
90 |
voting schemes or something. Like you can't guess what the outcome would |
91 |
be. And if the outcome would be surprising, then that has to be cleared |
92 |
up and people will have to voice their opionions anyway. I see no problem |
93 |
in a public short discussion/voting on a proposal from you two in this |
94 |
case. We might need to have a discussion on the actual contents, but for |
95 |
now I think it's important that someone steps up, and puts his/her head |
96 |
out of the mowfield. |
97 |
|
98 |
-- |
99 |
gentoo-osx@g.o mailing list |