Dear All,<div><br></div><div>changing the subject a bit so it is easier to track things.</div><div><br></div><div>I think for one figure (figure 2 from <a href="http://www.plosone.org/article/info%3Adoi%2F10.1371%2Fjournal.pone.0005472">http://www.plosone.org/article/info%3Adoi%2F10.1371%2Fjournal.pone.0005472</a>) we are fine - see below the extract from PLoS ONE site. It looks like we do not even need to request permission.</div>
<div><br></div><div>I will investigate the issue with chapter "GWA analysis in presence of stratification: theory" of the tutorial further (it overlaps - both in figures and text - with a a chapter of a published book, <a href="http://www.sciencedirect.com/science/article/pii/B9780123751423100094">http://www.sciencedirect.com/science/article/pii/B9780123751423100094</a>). For the moment it may be more safe to just skip it in the SVN.</div>
<div><br></div><div>YA</div><div><br></div><div>Extract from <a href="http://www.plosone.org/static/editorial">http://www.plosone.org/static/editorial</a></div><div><br></div><div><div>5. Copyright and Licensing</div><div>
<br></div><div>Open Access Agreement</div><div><br></div><div>Upon submitting an article, authors are asked to indicate their agreement to abide by an open access Creative Commons license (CC-BY). Under the terms of this license, authors retain ownership of the copyright of their articles. However, the license permits any user to download, print out, extract, reuse, archive, and distribute the article, so long as appropriate credit is given to the authors and the source of the work. The license ensures that the article will be available as widely as possible and that the article can be included in any scientific archive.</div>
<div><br></div><br><div class="gmail_quote">On Wed, Mar 13, 2013 at 9:45 AM, Yurii Aulchenko <span dir="ltr"><<a href="mailto:yurii.aulchenko@gmail.com" target="_blank">yurii.aulchenko@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I just realized there is yet another question.<div><br></div><div>What we do about figures? There are two problems with these:</div>
<div><br></div><div>1) they are binary files</div><div><br></div><div>2) some (two?) of them are coming from journals/books, and we do not have explicit copyright holder's permission - in that I would definitely be unwilling to put these in a place where we can not delete it forever (such as RForge SVN)</div>
<div><br></div><div>With 2, I probably need to contact the copyright holders - this may be or may be not a big deal; for now I can replace these parts with "void"</div><div><br></div><div>With 1 - what should we do? Put it on the server as data files?</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div></font></span><div><span class="HOEnZb"><font color="#888888">YA</font></span><div><div class="h5"><br><br><div class="gmail_quote">On Wed, Mar 13, 2013 at 9:32 AM, Yurii Aulchenko <span dir="ltr"><<a href="mailto:yurii.aulchenko@gmail.com" target="_blank">yurii.aulchenko@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
> I put the<br>
> data on the GenABEL.org site;<br>
<br>
</div>With that you mean the free/non-problematic data, I assume.<br>
<div><br></div></blockquote><div><br></div></div><div>Yes, sure</div><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>><br>
> I think I should make a new directory - say, 'tutorials' - at the same<br>
> level, as 'pkg', 'tags', 'www' and then will have a sub-directory called<br>
> 'GenABEL_general' to keep this general tutorial. What do you think?<br>
<br>
</div>I agree. That seems the most logical way. Alternatively we can put<br>
tutorials in the same directory as the respective package (e.g.<br>
pkg/GenABEL), but that will probably mess up r-forge's automatic package<br>
building even more (than it is now because of the way we need the<br>
filevector files).<br>
<br></blockquote><div><br></div></div><div>Ok. Will do that and comment on what is in. </div><span><font color="#888888"><div><br></div><div>Yurii</div></font></span></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><div class="im">-- <br>-----------------------------------------------------<br>Yurii S. Aulchenko<br><div><br></div><div>[ <a href="http://nl.linkedin.com/in/yuriiaulchenko" target="_blank">LinkedIn</a> ] [ <a href="http://twitter.com/YuriiAulchenko" target="_blank">Twitter</a> ] [ <a href="http://yurii-aulchenko.blogspot.nl/" target="_blank">Blog</a> ]</div>
</div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>-----------------------------------------------------<br>Yurii S. Aulchenko<br><div><br></div><div>[ <a href="http://nl.linkedin.com/in/yuriiaulchenko" target="_blank">LinkedIn</a> ] [ <a href="http://twitter.com/YuriiAulchenko" target="_blank">Twitter</a> ] [ <a href="http://yurii-aulchenko.blogspot.nl/" target="_blank">Blog</a> ]</div>
</div>