On Thu, Feb 17, 2011 at 11:46 AM, Ivan Hamer <tic...@gmail.com> wrote:
> > Hi Richard, > > I looked at the agreement form, and it is pretty all-encompassing. Since > my company integrates fossil into its product, the agreement seems to imply > that all of that work would then belong to Hwaci. I am pretty sure your > intent was to get the release on the contributions only, but the wording in > clause 1 does not mention that. > I don't read it that way. Clause 1 explicitly applies to Fossil only, not to your product. Now if you have your own private extensions to Fossil, I can see how you might interpret clause 1 as saying you are giving up the rights to those private extensions. You are correct in inferring that is not the intent. I think that the best course of action there, though, it to simply declare the extensions/enhancements are part of your product and not part of Fossil so that clause 1 does not apply. Meanwhile, I see if I can't come up with alternative wording for clause 1. > Also, do you want a hard copy of the signed form? > Yes. > > On Tue, Feb 8, 2011 at 11:29 AM, Richard Hipp <d...@sqlite.org> wrote: > >> >> >> On Sun, Feb 6, 2011 at 10:11 PM, Ivan Hamer <tic...@gmail.com> wrote: >> >>> >>> I would like to be able to send in some contributions, but couldn't >>> find much information on the topic. There is a ticket on adding this info to >>> the FAQ (http://fossil-scm.org/index.html/tktview?name=15dfbde729) >>> Do what are the guidelines on how to contribute to fossil? >>> >>> Specifically, I am interested in: >>> >>> 1. Which branch to work on? >>> 2. What to do with changes? >>> (How to test? Do I create a patch? Where to send the patch?...) >>> >>> I am volunteering to create a wiki/faq/documentation page on this >>> topic. >>> >> >> I've been thinking I need to write all of this up. It has simply been >> crazy lately and I've had to focus on other priorities. >> >> In order to maintain clear title, I ask that all contributors sign a >> copyright release prior to getting check-in privilege. After receiving >> check-in privilege, new contributors are asked to store on branches only - >> at least until such time as I can evaluate their work. And, experimental >> changes always go on a branch. We desire to keep the trunk working and >> ready-to-use at all times. >> >> I need to work up checklists for coding style and design rules. I started >> on a testing checklist which you can see at >> http://www.fossil-scm.org/fossil/doc/trunk/test/release-checklist.wikibut it >> needs a lot of work yet. >> >> A lot of this I'll need to do since I'm the only one with the knowledge to >> do it. But I'd still appreciate any help and/or advice. >> >> >>> >>> _______________________________________________ >>> fossil-users mailing list >>> >>> fossil-users@lists.fossil-scm.org >>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >>> >>> >> >> >> -- >> D. Richard Hipp >> d...@sqlite.org >> >> _______________________________________________ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> >> > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users