[geeklog-devel] Credits to ourselves?

Simon Lord slord at marelina.com
Mon Mar 29 23:15:30 EST 2004

I'm not even contributing to CVS other than the glpro theme, but it 
seems to me that you guys need to stick your names in there.  If 
nothing else, it's a great resume piece down the road.

GL is not some hack cms, you guys have some crazy classes in there etc 
that may prove you're the right man for the job at your next interview. 
  But if your names are not in CVS you'll have a hell of a time 
convincing them you wrote a file uploader class etc.  I'm sure if I was 
a contributor to SAMBA I'd want my name in there.

Cripes, here's a great free CMS system.  The least *all* of us can do 
is allow the major contributors to stamp their names in there 
somewhere.  Module developers can stick their names into their modules 
and theme developers can stick theirs into the css file... ;)

My two cents.

On Mar 29, 2004, at 3:20 PM, Dirk Haun wrote:

> 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
> -- 
> http://www.haun-online.de/
> http://mypod.de/
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://lists.geeklog.net/listinfo/geeklog-devel

More information about the geeklog-devel mailing list