Hi Oliver,
> Yes, copyright assignment is required to be assigned to me
Okay. Do you have a copyright assignment agreement that needs to be signed?
--steve
> I can help out here. Yes, copyright assignment is required to be assigned to
> me. This goes way back to when I wanted to change the licensing from GPL to
> LGPL. To do this properly was difficult due to the copyright issue. Luckily
> at the time the project was small and it could be worked around. I also had
> issues when I wanted to change the license of Chainsaw to contribute to the
> Log4J project, when one of the contributors would not change the license for
> their code.
>
> From that point on I have required that copyright assignment is required to
> be assigned to me. Imagine in the future it becomes advantageous to move to
> the GP{Lv3 license, then this move is possible because of the copyright
> assignment. Without it, I would never even consider it.
>
> I hope this helps.
>
> Regards.
> Oliver
>
> On 9/19/07, Steve McKay☄ <smckay@xxxxxxxxxx> wrote:
> > Hi Lars,
> >
> > It looks like the checks for the checkstyle project as configured in
> > checkstyle_checks.xml require copy right assignment via the Header
> > check on line 39, but the "Contributing" page
> > (http://checkstyle.sourceforge.net/contributing.html)
> doesn't mention
> > this. Can you help me understand if a copyright assignment is required
> > as part of a code contribution?
> >
> > Thanks.
> >
> > --steve
> >
> > On 9/12/07, Steve McKay☄ <smckay@xxxxxxxxxx> wrote:
> > > Hi Lars,
> > >
> > > > Sounds interesting. While I don't see why you would want to allow
> > > > silly names in new code I can see the value of this feature in code
> > > > cleanup efforts for existing code, where you would tackle the public
> > > > API of a module first. Is that the intended use case?
> > >
> > > I think our need emerged from the now abandoned practice of prefixing
> > > (or was it suffixing) private members with underscores.
> > >
> > > > Yes, please submit three individual patches and make sure that they
> > > > follow the guidelines in our "contributing" document.
> > >
> > > Excellent. I'll get them to you soon. Thanks for the feedback.
> > >
> > > --
> > > Steve McKay < smckay@xxxxxxxxxx>
> > >
> >
> >
> > --
> > Steve McKay <smckay@xxxxxxxxxx>
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Checkstyle-devel mailing list
> > Checkstyle-devel@xxxxxxxxxxxxxxxxxxxxx
> >
> https://lists.sourceforge.net/lists/listinfo/checkstyle-devel
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Checkstyle-devel mailing list
> Checkstyle-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/checkstyle-devel
>
>
--
Steve McKay <smckay@xxxxxxxxxx>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Checkstyle-devel mailing list
Checkstyle-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/checkstyle-devel
|