josephhenryblack wrote: > André Pouliot wrote: > >> josephhenryblack wrote: >> >> >>> André Pouliot wrote: >>> >>> >>>> Also if there is multiple person who work on the code we better use >>>> some >>>> guideline on signal denomination and file name convention. Also the >>>> structure of directory used. It's some boring consideration to do >>>> right >>>> now but if we don't in a few month we are going to wish we did. >>>> >>> >>> This is where the wiki can help. Especially if we add it as we go. If >>> someone wants a small task - add the info that has already been said >>> about software. We can always fix the formatting in the wiki later, >>> but getting in on the page is the important part. snip >> >> I did <snip> a first rough >> draft >> http://wiki.duskglow.com/tiki-index.php?page=Contributing+Code >> >> André > > apouliot and PeterBrett have made nice work of the contributing code > page. Make sure you have a read and keep those great ideas rolling in. > Here is one: Perhaps in the headers we should include the info about > the dual license of GPL and Traversal. > > 1. Do we want to use this agreement that Mark found > http://www.xaraxtreme.org/images/pdf/16-01-06/contributor_agreement.pdf > (with OGP and traversal inserted) when people submit code. > 2. How should we refer to it in the headers? > jb > For point 2 : what we could do is write 2 line in the header one to name the license and the other to give a link to the complete text of the license. Else if we add the full license text in the header it will be hell to go trought all of it to see the code finally.
For point 1 : I didn't fully read the license but it seem troublesome to have to send it by snail mail. Just writing in the header the code is under the dual licensing should be enough. If it's not then we cannot accept the code. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
