As i already mentioned a longer time ago, i'd recommend a method and/or 
possibility to disown packages, if someone forgot about them.

Some packages keep outdated, the authors are just not around any longer, and 
did never orphan the package. So like "author request a package".
The author gets informed about this, and if a longer time the request wasn't 
accepted or rejected, the package moves to orphan.

I dont know if this is already included by the current disown / adobt package 
systems. I know this request has been around some time, but i never tried to 
disown any package having an owner again.

That's maybe a point for some more brainstorming. I'll take some time to think 
about what i could think being implemented in aur2, i'm sure some people will 
have nice feature requests - though, i'm quite happy with the current aur. 
Was a real big improvement to the "i-post-in-the-forum" system, which was 
quite annoying.

Kind regards,
Georg

On Monday 25 December 2006 19:38, Simo Leone wrote:
> Hi everyone,
>
> I'd like to get moving with AUR2 code sometime in the near future.
> However, before that can happen, we need to know what we're coding 8)
> (and I deliberately say "we"... I want your help!)
>
> That's where you come in, I've set up an AUR2 wiki page at
> http://wiki.archlinux.org/index.php/AUR_2 , where anyone and everyone is
> welcome to share some thoughts. I've posted some initial questions you
> might want to consider, but don't feel limited to answering them. The
> wiki page also gives some idea of the direction I'd like to take with
> this project.
>
> So have at it! Let's hear some good ideas! Oh, and merry christmas :)
>
> -S

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to