I'd say: - If a package has UNMAINTAINED (perhaps also DEPRECATED?) somewhere in its title/description, don't do anything. - Otherwise if the package hasn't been updated for past 3 months, send a quarterly reminder (including the information under what conditions the reminder is sent).
2013/5/5 Doug Burke <dburke...@gmail.com> > > On May 5, 2013 7:25 AM, "Petr Pudlák" <petr....@gmail.com> wrote: > > > > Hi, > > > > on another thread there was a suggestion which perhaps went unnoticed by > most: > > > >> ---------- Forwarded message ---------- > >> From: Niklas Hambüchen <m...@nh2.me> > >> Date: 2013/5/4 > >> ... > >> I would even be happy with newhackage sending every package maintainer a > >> quarterly question "Would you still call your project X 'maintained'?" > >> for each package they maintain; Hackage could really give us better > >> indications concerning this. > > > > > > This sounds to me like a very good idea. It could be as simple as "If > you consider yourself to be the maintainer of package X please just hit > reply and send." If Hackage doesn't get an answer, it'd just would display > some red text like "This package seems to be unmaintained since D.M.Y." > > > > Best regards, > > Petr > > > > For those packages that give a repository, a query could be done > automatically to see when it was last updated. It's not the same thing as > 'being maintained', but is less annoying for those people with many > packages on hackage. > > Doug >
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
