Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



nobody here is screwing others work

teh topic is how about to find out AUTOMATICALLY which are
they doing the work and which things are orphaned without
finding it out the hard way in the running release cycle

and if you need to find out things automatically you need
any flag to measure - this would be FAS login

Am 04.11.2012 08:37, schrieb Aleksandar Kurtakov:
> How does it sound? Really like the right way to build community by excluding people? Think about this more before trying to screw others work? Your feature might mean nothing for someone else if you want to see it happen step in and do your part and don't tell people that there work should be removed.
> P.S. My words would have been a lot more harsh if sending from personal email!!
> 
> Alexander Kurtakov
> Red Hat Eclipse team
> 
> ----- Original Message -----
>> From: "Aleksandar Kurtakov" <akurtako@xxxxxxxxxx>
>> To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx>
>> Sent: Sunday, November 4, 2012 9:30:49 AM
>> Subject: Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how	to install into a LVM partitions (or
>> RAID))
>>
>> Hmm, actually I have new proposal.
>> Policy about active/inactive maintainers should be decided only by
>> actual maintainers. In the true meritocracy way - if you don't
>> maintain anything you don't have a say.
>>
>> Alexander Kurtakov
>> Red Hat Eclipse team
>>
>> ----- Original Message -----
>>> From: "Reindl Harald" <h.reindl@xxxxxxxxxxxxx>
>>> To: devel@xxxxxxxxxxxxxxxxxxxxxxx
>>> Sent: Saturday, November 3, 2012 4:47:57 PM
>>> Subject: Re: Anaconda is totally trashing the F18 schedule (was Re:
>>> f18: how	to install into a LVM partitions (or
>>> RAID))
>>>
>>>
>>>
>>> Am 03.11.2012 15:38, schrieb Emmanuel Seyman:
>>>> * "Jóhann B. Guðmundsson" [02/11/2012 20:34] :
>>>>>
>>>>> That package would hardly be un-maintained if it has
>>>>> co-maintainers
>>>>> now does it...
>>>>
>>>> Absolutely. Hence my request that any process we put in place be
>>>> package-focused rather than maintainer-focused
>>>
>>> why?
>>> how will you do this?
>>> if there is nothing to change on a apckage it is at it is
>>>
>>> if any maintainer not login he is INACTIVE
>>> if a package has more maintainers it is no problem retire the
>>> inactive maintainer
>>> if a package has only one maintainer and he is gone away the
>>> package has to be retired

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux