Well the form idea is only one idea. Asking for a statement in Jira or GitHub is fine as well. Ask them enough times and they may want to sign code contribution agreement.
-- Jody Garnett On 28/05/2013, at 6:19 PM, Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> wrote: > We could make everyone agree, and make it really easy, like a web form. I > could not find an form version of the Eclipse CLA. > > On 28/05/13 14:18, Jody Garnett wrote: >> How about we write the thing up clearly in the developers guide, and we >> add a description into JIRA when they report the bug (we already have >> our own custom descriptions). We may be able to link to the correct page >> of the developers guide. >>> I am wondering if we can instead have a contributor-agreement-lite, >>> which does not require access to a printer and scanner. I think this >>> page was meant to have checkboxes and an accept button: >>> http://www.eclipse.org/legal/CLA.php >> (It says at the top that it is a reference copy, to actually fill it in >> you login to the eclipse website and they have a checkbox or form thing >> you can fill in). >>> Anyone have experience with other open source projects that >>> have addressed this issue? >> Here is an example from webkit >> http://www.webkit.org/coding/contributing.html >> >> The phrase they use is: /If you make substantive changes to a file, you >> may wish to add a copyright line for yourself or for the company on >> whose behalf you work. / >> / >> / >> This kind of brings us full circle - what is a "substantive" change? In >> a sense it does not really matter as long as we are clear… >> >> Story could go something like: >> >> * Fill in code contribution agreement … when introducing a new method? >> >> Downside is we actually like new methods introduced for clarity, and do >> not want to encourage super long methods. >> >> * Fill in agreement when new public or protected method? >> >> That is a bit safer, as changing API = code contribution agreement. >> Downside is we like to encourage creation of tests with each patch. >> >> * Fill in code contribution agreement when creating a new file. >> >> (original recommendation) >> >> It makes sense as have a new "item" to track copyright on, and the >> header needs to be filled in anyways (so it is not out of our way to >> think about copyright). >> >> >> Jody > > -- > Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> > Software Engineer > CSIRO Earth Science and Resource Engineering > Australian Resources Research Centre ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
