On Mon, 2006-09-25 at 17:41 +0200, Jörn Nettingsmeier wrote: > Thorsten Scherler wrote: > > On Fri, 2006-09-22 at 22:11 +0000, [EMAIL PROTECTED] wrote: > >> Author: nettings > >> Date: Fri Sep 22 15:11:10 2006 > >> New Revision: 449107 > >> > >> URL: http://svn.apache.org/viewvc?view=rev&rev=449107 > >> Log: > >> added experimental tinymce module. this is work in progress. > >> see the README and TODO files for details. > > > > ... > >> Added: lenya/trunk/src/modules/tinymce/README > >> URL: > >> http://svn.apache.org/viewvc/lenya/trunk/src/modules/tinymce/README?view=auto&rev=449107 > >> ============================================================================== > >> --- lenya/trunk/src/modules/tinymce/README (added) > >> +++ lenya/trunk/src/modules/tinymce/README Fri Sep 22 15:11:10 2006 > >> @@ -0,0 +1,36 @@ > >> +TinyMCE Editor integration for Lenya 1.4 > >> + > >> + > >> +Loosely based on a module written by Wyona (http://wyona.com). > >> +Thanks to Bob Harner, Renaud Richardet and Tim Hannigan for > >> +documentation and code examples. > >> + > >> +Lenya 1.4 integration and some extra bells and whistles > >> +by Jörn Nettingsmeier <[EMAIL PROTECTED]>. > >> + > > > > > > Actually we agreed a while ago that we do not want to keep this notes. > > sorry, i was not aware of a strict policy against such notes.
We should add it to our guidelines. > > > The most important thing to learn in this project is that the code > > belongs to the community and is normally not the work of a single > > entity. > > you should not read this as a claim to ownership. of course everyone is > free to work with the code as they please. i dropped my name in mostly > so that people know who to blame or direct bug reports to if they are > not on the lists and do not have access to the svn log. This is exactly why we do not want that. All communication about the Lenya code (since your commit, it belongs to the ASF) should be on the mailing lists from lenya! We do not want direct communication with committer. That is why we removed most of the author tags in our documentation. If people cannot subscribe to the ml but directly contact one of us committer then we need to refer to this list for discussion and bug reports. Here we have a community helping with problems not a single committer and the answers get archived for public research. > > > Further people like Simon how worked as well on the code get singled > > out. > > that was unintentional. the only credit i found in the module was > "wyona", so that's what i put in. Yeah, but see down. > > > The question is were do we draw the line which contribution is > > worth mentioning and which not. > > > > Therefore not a single entity should be mentioned as author nor do we > > want a big list of thanks. A thanks to the Apache Lenya community is > > enough. > > well, in all my open source work so far, i have found that it is better > to give too much credit than too little. especially for code that > originated outside the lenya community or donated code from corporate > entities. > Hmm, I understand that corporate entities would like special credits but there is only one form for crediting and this is giving the *person* who is committed Commit access. If this person further s helping with project management then she is likely candidate for PMC membership. That is the way we credit here on the ASF. > as i demonstrated earlier, credits are not the primary source of > repository bloat ;-) Well, licenses are very important and we must be very careful to be legally on the save side. I would hate seeing a law suite because we not added some lines. Like I stated before, please discuss this on legal if you do not want so many lines for the copyright notice. Please try to understand the line of argumentation why credits can be harmful to this project. > > > Please remove this. > > ok. > Thanks salu2 -- Thorsten Scherler COO Spain Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
