Enrico Weigelt wrote:
The gentoo devs currently do much of the upstream's work.
Fixing bugs or even adding new stuff which does not directly have to
do w/ gentoo should be done exlusively by the upstream.
This is not really a problem. Fixing bugs is what I enjoy after all, this is the
Luis Francisco Araujo wrote:
The 'modus-operandi' would go like this:
1 - We setup a mailing list (yes, yet another one, but this one is gonna
be useful!) , call it , [EMAIL PROTECTED] , or [EMAIL PROTECTED]
2 - Developers interested to serve as a proxy , subscribe to the list.
3 - Users ask
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Hill wrote:
So far the only difference between this and doing a query on b.g.o for
maintainer-wanted is that it's on mailing list.
Which (as a side note), increase the flow of communication between
developers and users, giving an alternative
Luis Francisco Araujo wrote:
3 - Users ask on this mailing list if there exist any developer
interested to include X, or Y ebuild into the tree. (Probably we could
create a template for this?)
The user should send the ebuild changes together with the mail. Make it look
like on LKML including
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Schweizer wrote:
Luis Francisco Araujo wrote:
3 - Users ask on this mailing list if there exist any developer
interested to include X, or Y ebuild into the tree. (Probably we could
create a template for this?)
The user should send the
* Luis Francisco Araujo [EMAIL PROTECTED] schrieb:
Hi,
Well, my idea is more focused on getting closer the developer with the
user, in the sense that they would be like a team (as i already said) ,
where the developer is the official figure in the group. So, at some
so far okay, but we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Enrico Weigelt wrote:
The gentoo devs currently do much of the upstream's work.
Fixing bugs or even adding new stuff which does not directly have to
do w/ gentoo should be done exlusively by the upstream.
Not true at all.
We (as developers)
