[aur-general] Proposed rules for packages entering [community]

[Firmicus]

Mikko Seppälä a écrit :
> Firmicus wrote:
>> <...>
>>
>> I have examined the repos extra, community and unsupported quite 
>> carefully, and as a result I do not think there are that many 
>> packages in unsupported that really deserve being in community! 
>> Possible candidates are
>>
>> yaourt, etc: but only if wain would become a TU AND if we think it is 
>> a good idea to support that very popular tool (not sure personally – 
>> also it is only a script, so easy to install).
>> aurup
>> nspluginwrapper-flash + dependencies > well, these are no longer 
>> required I believe
>> splashy
>> wine-doors
>> songbird
>> <enemy-territory, warsow, openarena etc. : if TUs are interested>
>> uswsusp
>> customizepkg
>> pactools
>> archassistant
>> vlc-plugin
>> fbsplash
>>
>> Otherwise, I would rather VERY MUCH encourage TUs to have a look at 
>> the packages in EXTRA that are currently orphaned, and to contact the 
>> devs if you are interested to maintain some of them in community. 
>> There are many more important packages there that would deserve to be 
>> maintained in community than being orphaned in extra.
>>
>> That's it for now.
>>
>> F
>>
> Little thing here:
> Never add 32bit binaries into 64bit system on community front 
> (nspluginwrapper above), libs are kinda ok.
> Atleast I strongly disagree on adding them.
>
> - Neverth
>

I totally agree. I simply gave a list of packages with a large number of 
votes or high pkgstats numbers, so that we might consider them as 
potential candidates for community. My point was simply that I don't 
think there is more than a dozen of packages currently in unsupported 
that deserve to be moved to community. I may err though.

But as I wrote, there are more important packages in extra that are 
orphaned and would be suitable for community.

F