[tur-users] Public announcement

[Varun Acharya]

Eric Belanger wrote:
> I also think that a lot of these orphans had very few votes when they were
> initially added to community.  For this reason, we should be careful and
> try not to put low votes packages in community because once they get
> orphaned, it's very hard to find another TU interested in them.
>
>
> Eric
++1 totally agree. But there isn't any rule enforcing this as of now is 
there? If a TU likes a package he can move it to
community even with 0 votes. I feel that this is ok if the package he 
needs is a dep for another package (which the community
might have voted significantly for). But don't you think some sort of 
guideline is required for a TU to bring a new package and
its blanket of dependencies into community? My suggestions:

1). Minimal voting system : a minimum of 5 votes perhaps?
2). A TU could ask another TU to agree to 'co-maintain' a particular 
package. In such cases a TU wanting to move a relatively unknown
package to community could do so if another TU agress to be 
co-maintainer for the package. So if a TU is going on a long holiday or 
stepping
down altogether then the co-maintainer could take over for him, till a 
new maintainer is found at least. Co-maintainer's name should of course
be added to the PKGBUILD.

Any other suggestions?

Whatever we implement, will make community have less orphans/outdated 
packages, which is a very good thing IMHO.

Varun