[geeklog-devel] Credits to ourselves?
geeklog at langfamily.ca
Tue Mar 30 10:03:01 EST 2004
Dirk, are you thinking there would be a 1 line comment added to the changed
file header documenting the change and author?
I agree that a comment standard with the develper name is a good idea.
The question is do we want to really add this to the header of each file - I
My changes are mostly noted in the history doc and I have not had a problem
with the current method.
----- Original Message -----
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Sent: Monday, March 29, 2004 3:20 PM
Subject: [geeklog-devel] Credits to ourselves?
> With the addition of Vinny, there are now four people with CVS access
> contributing code on a (more or less) regular basis. Which brings up the
> issue of proper credits.
> I've always tried to properly credit code, fixes, and other things
> contributed by people outside of the core team. But what about the four
> of us now? Should we start putting our names after each change
> description? The PHP team does it like this, for example:
> Fixed getopt() so it works without $_SERVER (Rasmus, bfrance)
> Personally, I don't care. I can always get the information I need (who
> made a change a when) from CVS. But I don't want to downplay anybody's
> role in this project or pocket someone's credits.
> So, do we add our names to docs/history or do we stick with the rule that
> changes without credits were made by an (unnamed) team member?
> bye, Dirk
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
More information about the geeklog-devel