-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/02/2012 10:21 AM, hasufell wrote:
As I was told in my recruiting process we usually don't just fix up
ebuilds of other devs unless it's trivial, very severe or something.
The usual process is nothing new: try to contact the maintainer, open
On 4 December 2012 01:18, Ben de Groot yng...@gentoo.org wrote:
On 3 December 2012 03:30, Markos Chandras hwoar...@gentoo.org wrote:
On Dec 2, 2012 6:09 PM, Rich Freeman ri...@gentoo.org wrote:
On Sun, Dec 2, 2012 at 10:21 AM, hasufell hasuf...@gentoo.org wrote:
Only question is now
On 4 December 2012 08:10, Rick Zero_Chaos Farina zeroch...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/02/2012 10:21 AM, hasufell wrote:
As I was told in my recruiting process we usually don't just fix up
ebuilds of other devs unless it's trivial, very severe or
On Tue, Dec 4, 2012 at 1:19 AM, Markos Chandras hwoar...@gentoo.org wrote:
On 4 December 2012 01:18, Ben de Groot yng...@gentoo.org wrote:
On 3 December 2012 03:30, Markos Chandras hwoar...@gentoo.org wrote:
On Dec 2, 2012 6:09 PM, Rich Freeman ri...@gentoo.org wrote:
On Sun, Dec 2, 2012
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/2012 04:23 AM, Markos Chandras wrote:
On 4 December 2012 08:10, Rick Zero_Chaos Farina zeroch...@gentoo.org
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/02/2012 10:21 AM, hasufell wrote:
As I was told in my recruiting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/2012 05:01 PM, Rick Zero_Chaos Farina wrote:
maintainer emailf...@gentoo.org/email nameMe/name
descriptionProxy maintainer, assign bugs to proxied maintainer,
cc on bugs, but feel free to just fix the bugsdescription
/maintainer
I
On 04/12/2012 08:01, Rick Zero_Chaos Farina wrote:
I feel the description field is already overloaded when there is a proxy
situation, maybe it would be best to define a field for this. Also
english isn't primary language for everyone in the world so if the
policy could actually be specific
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/2012 12:01 PM, hasufell wrote:
On 12/04/2012 05:01 PM, Rick Zero_Chaos Farina wrote:
maintainer emailf...@gentoo.org/email nameMe/name
descriptionProxy maintainer, assign bugs to proxied maintainer,
cc on bugs, but feel free to just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/2012 12:06 PM, Diego Elio Pettenò wrote:
On 04/12/2012 08:01, Rick Zero_Chaos Farina wrote:
I feel the description field is already overloaded when there is a proxy
situation, maybe it would be best to define a field for this. Also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/2012 12:32 PM, hasufell wrote:
On 12/04/2012 06:17 PM, Rick Zero_Chaos Farina wrote:
I'm sorry but isn't specific policy related to global policy? Why
yes, yes it is.
Unless they conflict, then no.
On 12/04/2012 09:10 AM, Rick
the patch has been modified to reflect Zero_Chaos suggestions:
- tell where to look for herd or maintainer notes (such as touch at
will): metadata.xml
- explicitly say to contact other devs if unsure how to handle a
situation, especially if it's a critical one
commit
On 04/12/2012 10:35, Sergey Popov wrote:
Agreed. I add description field to metadata for proxying packages, cause
i see such field in other packages' metadata. That is it. But it would
be better when this became official policy. At least - define actual
maintainer first, even if he is not
On 4 December 2012 17:28, Rick Zero_Chaos Farina zeroch...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/2012 12:06 PM, Diego Elio Pettenò wrote:
On 04/12/2012 08:01, Rick Zero_Chaos Farina wrote:
I feel the description field is already overloaded when there is a
On 4 December 2012 15:42, Alec Warner anta...@gentoo.org wrote:
On Tue, Dec 4, 2012 at 1:19 AM, Markos Chandras hwoar...@gentoo.org wrote:
On 4 December 2012 01:18, Ben de Groot yng...@gentoo.org wrote:
On 3 December 2012 03:30, Markos Chandras hwoar...@gentoo.org wrote:
On Dec 2, 2012 6:09
14 matches
Mail list logo
