1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Aug 16, 2005, at 12:19 PM, Grobian wrote: |
5 |
|
6 |
> |
7 |
> |
8 |
> Kito wrote: |
9 |
> |
10 |
>> On Aug 15, 2005, at 2:41 PM, Hasan Khalil wrote: |
11 |
>> Sounds like a good idea. |
12 |
>> |
13 |
> |
14 |
> Arch testers are a good idea... It's pretty much work to compile |
15 |
> packages and dive into them to test them in some decent way. |
16 |
> |
17 |
|
18 |
Great! We'll look into how the other archs run their AT's this |
19 |
weekend. We'd really like to bring Mike (shootingstar) on board -- |
20 |
he's been a great help already. |
21 |
|
22 |
>>> In terms of the elections for Gentoo for Mac OS X project leads |
23 |
>>> that we discussed in previous threads, since there have been no |
24 |
>>> other nominations, are there any objections to us taking the |
25 |
>>> positions and getting to work on the points we mentioned in our |
26 |
>>> candidacy e-mail? Please let us know one way or another. |
27 |
>>> Alternatively, if anyone wants to throw in a last-minute |
28 |
>>> candidacy pitch, please do so now! If no one objects or announces |
29 |
>>> candidacy within a week, we'll make an announcement on -dev and |
30 |
>>> change the project page as necessary. |
31 |
>>> |
32 |
>> Sounds like you guys are going to do this regardless, so why wait |
33 |
>> a week? |
34 |
|
35 |
We were hoping to give others a chance to announce candidacy. As per |
36 |
my discussion on IRC with kito, if Fabian doesn't object, we will be |
37 |
changing the election position to "Lead" and running as partners (co- |
38 |
leads) rather than staying with the traditional strategic/operational |
39 |
titles. We feel that the time commitment for the lead position would |
40 |
be better met as a team due to our existing school and work |
41 |
commitments. Kito suggested the name switch on the basis that the |
42 |
"strategic" lead isn't going to be dictating long-term goals with a |
43 |
project team as small as ours. |
44 |
|
45 |
>> |
46 |
> |
47 |
> 1) I think I missed the point why it was more suitable to wait, |
48 |
> kito can you explain (again?) |
49 |
|
50 |
My impression via our IRC conversation (and kito, please please |
51 |
correct me if I'm wrong), is that kito wanted a senior gentoo |
52 |
developer to take the project lead position. As we currently don't |
53 |
have a senior gentoo developer with the project, he felt it would be |
54 |
better to wait for one to come along. |
55 |
|
56 |
Our counterpoint here is that we want a developer that is senior to |
57 |
the Gentoo for Mac OS X (yes, we know -- name switch pending) |
58 |
project, because having seniority among other developers is useless |
59 |
if you don't know what to apply it towards. We need someone that's |
60 |
been with the Gentoo for Mac OS X project long enough to know the |
61 |
difficulties it faces and where it's come from. Things may seem |
62 |
difficult now, but relative to a year ago, we're doing excellent. |
63 |
|
64 |
> 2) Also with respect to the off-topic comment above; is it really |
65 |
> necessary to drag both of you two into this position thing? In the |
66 |
> end -- that's my impression -- your 'influence' is being controlled |
67 |
> by the amount of work you do. So I'd care for activity, not for |
68 |
> who is the real boss. gonj0n is an easy word here, but I don't |
69 |
> really think that is necessary. |
70 |
|
71 |
First of all, neither Hasan nor I feel comfortable committing to the |
72 |
time requirement the lead position requires as a single individual. |
73 |
We feel that as a team we would be able to fulfill that time |
74 |
requirement better. |
75 |
|
76 |
As for the need for the title, it is necessary for a variety of reasons: |
77 |
1) Recruitment - we can bring new devs on, but making staffing |
78 |
announcements has been a battle without the title. After much |
79 |
convincing with devrel, I got them to put up a one sentence staffing |
80 |
call for the project only because Pieter (pvdabeel) has been pretty |
81 |
publicly absent with regards to Gentoo for Mac OS X. |
82 |
|
83 |
2) Interproject relationships - There are a variety of things that |
84 |
fall under here. The first is our need to have a coherent team. There |
85 |
are a lot of people that are supposedly Gentoo for Mac OS X devs that |
86 |
have been inactive for a long time, even after being contacted and |
87 |
asked nicely to do something. We don't have the authority to do |
88 |
anything about inactive developers because pvdabeel is the project |
89 |
lead. Furthermore, this goes back to the recruiting nightmare. Why do |
90 |
we need to recruit when we already have 10-12 devs? Additionally, in |
91 |
order to be recognized as a "team" by the rest of Gentoo-dom, we |
92 |
really need to display a unified face to the rest of the community. |
93 |
We need a contact point. This isn't as severe as an issue as the |
94 |
recruiting/staffing problems, but it is starting to become a problem |
95 |
and that problem will only get worse. For instance, who does a |
96 |
package maintainer go to when they happen to own a mac and would like |
97 |
to do their own testing and keywording for the package they maintain? |
98 |
They could ask any of us, but they would almost inevitably get |
99 |
different answers, which just shows the rest of the community that |
100 |
we're sloppy and unorganized. Now, if there was a lead that directed |
101 |
conversations such as this with the rest of the community, collected |
102 |
results and formed a set policy from this, that would look a whole |
103 |
lot better. |
104 |
|
105 |
3) Public Relations: We not only need a unified face with the public |
106 |
as well, but we also need to expand our PR in may ways. Documentation |
107 |
and BugDay involvement come to mind first. As leads we have the |
108 |
ability to speak for the rest of the team with the docs team and the |
109 |
BugDay team. Without being lead, we can only speak for ourselves. |
110 |
|
111 |
> 3) can you come up with a short recap on the proposed filled in |
112 |
> functions and changes within the team, just so everyone (me) is |
113 |
> sure we talk about the same things. |
114 |
|
115 |
I'll recap the most important points. Please see our original e-mail |
116 |
post for the details. |
117 |
|
118 |
1) Recruitment/Staffing |
119 |
2) Documenting and initiating discussion on project policy |
120 |
3) Address PR - BugDay, Updated Documentation, Project Page |
121 |
|
122 |
There are other things that we talked about in our initial post, but |
123 |
I have listed only the points that require the lead position title here. |
124 |
|
125 |
Lina Pezzella && Hasan Khalil |
126 |
Ebuild & Porting Co-Leads |
127 |
Gentoo for OS X |
128 |
-----BEGIN PGP SIGNATURE----- |
129 |
Version: GnuPG v1.4.2 (Darwin) |
130 |
|
131 |
iD8DBQFDA7XTNJ9STR9DbYERAt1DAKCcKO/gVx7HKzMb/ieLwYDo9DXAhwCg6ghd |
132 |
ReqZr4xGRZJpDGlxC23Ky50= |
133 |
=IaDi |
134 |
-----END PGP SIGNATURE----- |
135 |
-- |
136 |
gentoo-osx@g.o mailing list |