On 14 Feb 2003 12:10:40 +1000 Ben Martin <[EMAIL PROTECTED]> babbled:
> On Fri, 2003-02-14 at 08:35, Carsten Haitzler wrote: > > > > > 1. collect all names from AUTHORS files. list all of them. (this will assume > > the step of making sure they are up-to-date has been done) i REPEAT it is > > the responsibility of the contributors to make sure their patches include > > patches to AUTHORS as the maintainer is not likely to know what real > > name/email to include for that contributor (and is often too busy to go > > hunting it down too). So if you CARE - check out cvs and the AUTHORS files. > > Append your name or send in a patch to append it. > > 2. match author names with sourceforge login names/accounts > > 3. all developers who have not committed code in 12 months go onto a > > contributors list. all authors who have committed code in the last 12 months > > get on the current developers list ? does 12 months sound good? > > > > This does leave a big gap in some cases, for example efsd and gevas2 > where cvs commits are not as frequent. I think for some projects the > maintainer/major author just needs to be listed on the page if the > project itself is mentioned. If we start adding automated scripts to > drop people off after 12 months then I suspect we might start seeing > little README commits every 11 to stop the automation :) though automation will catch 1. unmaintained software, 2. inactive software and let people know those programs can be listed as "authors: X maintainers: <empty>" based on commits. yes i'd atually prefer a README comit every 11 months by he author/maintainer just to let people know "hey" i'm still here" :) > I think surely if folks see a major component like efsd and only a few > names next to it then they will jump in if they want to hack it. > > Maybe we can add a list of which projects should get the new love, so > that folks dont start hacking on something like ebits1 etc? This way > they know what is for hacking and that those projects need love no > matter how many names are attached. definitely a good idea? shall we build a list? start listing every cvs project (app and lib) list who's currently working on it, if it is "table and done except for minor bug fixes as bugs are found" or "active development" or "earmarked for a refactoring", or "works, needs more features ?& code - needs maintainers" etc. ? > -- > Patches talk and bullshit walks. > http://witme.sourceforge.net/libferris.web/ > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > enlightenment-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] [EMAIL PROTECTED] Mobile Phone: +61 (0)413 451 899 Home Phone: 02 9698 8615 ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
