1 |
> what research? It doesn't matter how nice you and your teammates |
2 |
> are if the project has no ability to deliver the product. Keep in mind |
3 |
> I never questioned you or your ability or your projects or your teammates. |
4 |
> I asked how you planned on getting this to work and you reacted |
5 |
> in a very emotional and defensive way. I suggest you evaluate the |
6 |
> goals of the project and your ability to contribute to Gentoo with it. |
7 |
> We will be more than happy to facilitate your project and it's contributions |
8 |
> but you must take the initiative to talk to developers who can help you. |
9 |
> |
10 |
|
11 |
Okay, our guidelines clearly state that when a fixed ebuild has been |
12 |
confirmed by two other people as working, we submit it to bugzilla. All |
13 |
the ebuild janitors do is make sure that the ebuilds use the USE flags |
14 |
to the maximum of their potential, and of course generally clean them up |
15 |
as there's a lot of stuff in some older ebuilds that is no longer valid. |
16 |
Your mail clearly showed that you had not read those guidelines.. |
17 |
|
18 |
The plan is NOT to fork portage, the plan is NOT to stage a coup, the |
19 |
plan is NOT to start a pissing contest with the developers... the plan |
20 |
is quite simple, to make portage even better. |
21 |
|
22 |
How to make it work, it's simple, fix ebuilds, make sure they work, |
23 |
submit to bugzilla. |
24 |
|
25 |
Should we be so unlucky as to hit a major problem that we can't handle |
26 |
within the project, we will of course take contact to the person in |
27 |
charge, or mail gentoo-dev for input depending on the situation. |
28 |
|
29 |
We have already hit some cases that could be viewed as imperfections in |
30 |
the way flags are handled in Portage, and we have yet to receive any |
31 |
technical feedback on these issues. |
32 |
|
33 |
- Lovechild |
34 |
|
35 |
|
36 |
-- |
37 |
gentoo-dev@g.o mailing list |