<div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><em>In publications you would just cite the Web site, or, down the road,<br>whatever publication(s) announced the core modules.
</em></blockquote>
<div> </div>
<div>Who then would be the authors of such a publication, surely it would have to contain the names of very person that committed code to "core modules", otherwise it wouldnt be fair. </div>
<div>
<p>You guys program this and that, we ll write the paper and future references will be to our paper. </p>
<p>If anyone is interested and wants to contribute to any set of core modules in your spare time (like I m interested/planning on doing) then I do want to have some small measure of credit for it and not really be adding to someones publication count. Im sure this must of been an issue at some other point in another project/idea like this before, does anyone know how this was resolved?
</p>
<p><em>I honestly don't expect to see significant bodies of code hitting the<br>community Web site in the form of tutorials. I think a license for core<br>library modules that go beyond simple code or interface spec can be
<br>discussed if and when we actually have some code up for review ;).<br></em><br>Speaking of tutorials what sort of topics would be good tutorials for the community site? </p>
<p>You mentioned last week (I think) that you were planning for having a basic core spec ready soon, any information/timelines on that?</p>
<p>Nathan<br></p></div></div>