That's definitely better than what we do currently, but it still requires keeping that file up to date. There are a lot of contributors, and it's really difficult to get the list right. The problem you run into is that someone gets left out and feels bad because their contributions aren't acknowledged. Many times, people contribute patches without updating the copyright notice on the file being patched (although, technically, you're supposed to do that every time you modify something.) Some people are using "Copyright TigerVNC Team", which is pretty meaningless, because TigerVNC Team is not a legal entity, the set of developers is not really fixed, and three of the four principal developers work for companies (Red Hat and Cendio) who own their contributions.
It would maybe be good to study what other projects do. I'll take that as an action item. On 6/24/11 5:20 PM, Conan Kudo (ニール・ゴンパ) wrote: > There needs to be a notice of some kind in order for people who just > grab a tarball know who contributed. A CONTRIBUTORS.txt file could work > instead. A simple statement could be used in each program "Copyright (C) > 1999-2011, Copyright owners listed in CONTRIBUTORS.txt" or something of > the sort. > > On Fri, Jun 24, 2011 at 5:16 PM, DRC <dcomman...@users.sourceforge.net > <mailto:dcomman...@users.sourceforge.net>> wrote: > > Currently, whenever you launch Xvnc or the legacy Unix or new FLTK > viewers, they print an outdated copyright acknowledgment: > > Copyright (C) 2002-2005 RealVNC Ltd. > Copyright (C) 2000-2006 TightVNC Group > Copyright (C) 2004-2009 Peter Astrand for Cendio AB > > This needs to be changed or updated. The problem is that the actual > copyright history is about a mile long (see the new README.txt I just > added in the top-level source directory.) Thus, I think we really need > to replace the run-time copyright message with something more generic. > > It's been the convention of the Windows viewer and server for a while to > say: > > Copyright (C) 1999-2011 [many holders] > > That seems somewhat unsatisfying to me, but I can't come up with > anything better. Just trying to eliminate the need to maintain a list > of the copyrights in multiple places. I question whether it's even > important to maintain that list in the README files, since it's likely > to get out of date as well. If people really want to know who wrote the > code, they can grep the source. > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense.. > http://p.sf.net/sfu/splunk-d2d-c1 > _______________________________________________ > Tigervnc-devel mailing list > Tigervnc-devel@lists.sourceforge.net > <mailto:Tigervnc-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/tigervnc-devel > > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
