[aur-general] Should TU put in [community] packages they use?

[Grigorios Bouzakis]

On Fri, Jan 18, 2008 at 02:50:31PM +0100, bardo wrote:
> This came to my mind reading the discussion about Sergej, but after
> some thinking I couldn't make up a clear opinion about it, so this
> thread just brings up the question.
> 
> There's a few packages I maintain in unsupported that almost nobody
> voted, so I never moved them to [community]. But what if I use them in
> my daily activities? I'm interested in having an up-to-date package,
> so I'd maintain, build and test it anyway... should I share it with
> its (small) user base?
> 
> 
> Corrado

As i had also stated in my previous illiterate mail (sorry for that),
IMHO yes, TU's should upload to community only packages that have high
demand by users.
This is also the case now for developers about uploading packages in 
extra too.
I think i am one of the few people who dont use community anymore and
that fact is one of the main reasons.
The community repo has gone very big, with many high demand packages
staying in unsupported, while many of the packages in community have low
usage, are old projects with almost no updates for years and build in a
couple of secs. Even though the later isnt a reason for them to not be
in community.
If TU's want to upload to community packages they use before adding them to
unsupported they should instead consider creating a custom local
repo just like everyone else. You guys arent TU's to only help yourself
but mostly help other community members and the distro itself.

Greg