1 |
Daniel Armyr wrote: |
2 |
|
3 |
> I need to know what ideas are being |
4 |
> tossed around so that I feel my work is in line with where the distro is |
5 |
> going. |
6 |
> |
7 |
|
8 |
That is what -dev is for, mostly. Big changes in policy do not happen |
9 |
overnight, so dont worry that one day we use ebuilds and the next day we |
10 |
use RPMs. |
11 |
|
12 |
> What is for example the point of me rewriting all of qpkg to python if |
13 |
> portage is to be remodeled? |
14 |
|
15 |
Such questions would be best asked to the portage maintainers directly, |
16 |
afaik there is an IRC channel for portage alone. |
17 |
|
18 |
|
19 |
> I feel quite sure no info on this has been |
20 |
> posted to any place where I can actually read it. |
21 |
|
22 |
Cause it hasn't been discussed for a long time and i think part of it |
23 |
went on -dev back then (or anyway, some public ml). This was before i |
24 |
became a dev and i know about it (it's also on the website i think). |
25 |
|
26 |
> That, my friends, is |
27 |
> what we non-developers need. |
28 |
|
29 |
I think -core looks a lot more interesting from the outside then when |
30 |
you are actually on it. I'd say the best way to keep informed is to hang |
31 |
around the dev irc channel, you pick up most (even -core) stuff there. |
32 |
|
33 |
> If you devs feel a need to discuss your |
34 |
> intermarriages on the list, feel free, but if this means you can't |
35 |
> publish what you write, it doesn't exactly help the community. |
36 |
|
37 |
It doesn't impair the community either. And if you feel a need to be on |
38 |
it, do your best. Help us close some bugs and such and you will be |
39 |
recognized and picked up as a dev. |
40 |
|
41 |
- foser |
42 |
|
43 |
|
44 |
-- |
45 |
gentoo-dev@g.o mailing list |