On Thu, 13 Feb 2003 13:19:09 -0800 (PST) "Ben Rockwood" <[EMAIL PROTECTED]>
babbled:
>
> Hello All.
>
> I'm planning a complete re-vamp of the team page soon to remove all the
> old non-active people from that page. The hope is to encourage new
> people to join the effort who may look at that page now and think we
> have plenty of people, and to make sure that credit goes to those who
> really deserve it here and now.
> Before I do this, I'd like to ask that any owners of code, or
> contributers to various codebases make sure that their due credit has
> been noted in the AUTHORS files of each project and the ChangeLog of
> each codebase if applicable. If old contributers have worked on the
> code you are resposable for please note the individuals if you can.
> Thank You.
i think that maybe we should make an official way of doing this? how about
something like:
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 will mean we maintain an active developer list. all people who send patches
and would want to be listed as an active developer... should ask to get a
sourceforge account and be added to e's developer list on sourceforge, then
commit their fixes via cvs instead of via patches in e-mail.
this will then make it easy to track where what came from :)
another idea is to do cvs annotate on all files in each project and match
login/user names to people names on sourceforge and then atuo-generate AUTHORS
files from that (or use this list to double check). this at least gets the
exisiting lines of code/doc/Makefile/configure.in etc. and who was responsible.
#!/bin/sh
DEVELOPERS=""
for F in `find e17/ -print`; do
pushd `dirname $F`
FL=`basename $F`
A=`cvs annotate $FL | awk '{printf("%s\n", $2);}' | tr -d "(" | sort | uniq`
DEVELOPERS=$DEVELOPERS$A
popd
done
D=`echo $DEVELOPERS | sort | uniq`
echo "Developers:"
$D
disclaimer: above script written in e-mail client and unstested :) will take
forever to complete, but will have a list of unique developer logins on
sourceforge for the current source for the given directory in cvs.
--
--------------- 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
