Ok, great, I think this is the way to go.<div><br></div><div>Will make an account of private/public files, will push things to SVN (hopefully some time next week), and see what we can do :)</div><div><br></div><div>best wishes,</div>
<div>Yurii<br><br><div class="gmail_quote">On Thu, Mar 7, 2013 at 8:12 PM, L.C. Karssen <span dir="ltr"><<a href="mailto:lennart@karssen.org" target="_blank">lennart@karssen.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Yurii,<br>
<div class="im"><br>
<br>
On 24/02/13 17:27, Yurii Aulchenko wrote:<br>
><br>
> But I think we do not need to choose. We could keep both the "full old<br>
> PDF" together with "incomplete new" on the <a href="http://genabel.org" target="_blank">genabel.org</a><br>
</div>> <<a href="http://genabel.org" target="_blank">http://genabel.org</a>>'s tutorial section. Next, I am going to try to<br>
<div class="im">> construct a smarter Makefile, which could build both 'private' and<br>
> 'public' version depending on the availability of data files. Then we<br>
> could combine both solutions :)<br>
<br>
</div>I think that's the best solution for now. It also allows other people to<br>
help thinking about or even generate the open data sets.<br>
<div class="im"><br>
><br>
> I think the next steps are 1) for me to look up how many chapters in the<br>
> GenA tutorial become crap when I remove these datasets 2) try to do<br>
> smart Makefile - hopefully with your help<br>
<br>
</div>Sure! I have some experience writing Makefiles for LaTeX (the biggest<br>
one being for my PhD thesis, which also took care of image conversion to<br>
PDF and the like). I've also played around with rubber<br>
(<a href="https://launchpad.net/rubber/" target="_blank">https://launchpad.net/rubber/</a>) a bit and it seems to be a nice tool.<br>
However, for most smaller project usually do stuff by hand (or actually<br>
Emacs' AucTeX keybindings). But I'm digressing...<br>
Building a Makefile (-like?) solution for this sounds like a fun challenge.<br>
<br>
<br>
Lennart.<br>
<div class="im"><br>
><br>
> Let me know what you think, and I will keep you updated<br>
><br>
> best wishes,<br>
> Yurii<br>
><br>
> On Wed, Feb 20, 2013 at 10:40 PM, Maarten Kooyman <<a href="mailto:kooyman@gmail.com">kooyman@gmail.com</a><br>
</div><div><div class="h5">> <mailto:<a href="mailto:kooyman@gmail.com">kooyman@gmail.com</a>>> wrote:<br>
><br>
> Dear All,<br>
><br>
> I think on the long run replacing the data is the best thing to do.<br>
> (although it will take quite some effort).<br>
><br>
> As an temporary solution we could use a build server with jenkins<br>
> (<a href="http://jenkins-ci.org/" target="_blank">http://jenkins-ci.org/</a>), that recreates the document after each<br>
> alteration on svn and publish this on a public place(by coping it to<br>
> a webserver). On this build server the datasets are secure in a<br>
> trusted environment and the results are visible to the outer world.<br>
> I use Jenkins also for monitoring Probabel, but the goal is the<br>
> same: keep the quality of the code in check.<br>
><br>
> This solution prevent coping binary files to svn and this can be<br>
> done in a completely automated way.<br>
><br>
> Kind regards,<br>
><br>
> Maarten<br>
><br>
><br>
><br>
> On 02/20/2013 06:54 PM, L.C. Karssen wrote:<br>
><br>
> Dear Yurii,<br>
><br>
> Great idea. I'm all for putting the tutorials in SVN. They are<br>
> already<br>
> of high quality and together with our community we can make them<br>
> even<br>
> better.<br>
> I do see the problem with the data sets, of course.<br>
><br>
> You are using Sweave, right? I'm wondering how much not having<br>
> the data<br>
> will impact the possibility to tweak the document. Fixing small<br>
> typos<br>
> will be alright, but before you know it a typo can mess up the<br>
> LaTeX or<br>
> R code and since you can't compile the document to check it this may<br>
> lead to a lot of bug hunting for you, once you recompile it again.<br>
> That's the only potential problem I see.<br>
><br>
> How about also including the latest PDF version of the tutorial<br>
> (I know,<br>
> this is against SVN's principles) each time you compile a<br>
> version? This<br>
> way people who don't have the data know what it is supposed to<br>
> look like<br>
> and could even help creating replacement data sets.<br>
><br>
><br>
> Best,<br>
><br>
> Lennart.<br>
><br>
> On 02/20/2013 04:35 PM, Yurii Aulchenko wrote:<br>
><br>
> Dear All,<br>
><br>
> For long time I was thinking that GenABEL tutorial(s) should<br>
> be a part of<br>
> the project - the same logic as with the code, with the same<br>
> idea that in<br>
> such case people can easily contribute by submitting patches<br>
> and new<br>
> pieces.<br>
><br>
> The problem was (and still is) that the tutorial uses some<br>
> data sets, which<br>
> are not public domain, and it is quite awkward if we as the<br>
> project start<br>
> re-distributing them. Little by little I am trying to switch<br>
> the whole<br>
> thing to the use of only public and simulated data, but this<br>
> is a lengthy<br>
> process.<br>
><br>
> So I thought that may be a good solution is to put the code<br>
> of tutorials on<br>
> our SVN; and put the data only if these are either public or<br>
> simulated. Of<br>
> cause in this way the tutorials will not be really<br>
> "functional" (e.g. they<br>
> would not compile right away), but this may become a<br>
> starting point for<br>
> others to build up something new and really<br>
</div></div>> free-for-all-to-use-and-__contribute.<br>
<div class="im">><br>
> Let me know what you think,<br>
> best regards,<br>
> Yurii<br>
><br>
><br>
><br>
> _________________________________________________<br>
><br>
><br>
</div>> _________________________________________________<br>
> genabel-devel mailing list<br>
> <a href="mailto:genabel-devel@lists.r-forge.r-__project.org">genabel-devel@lists.r-forge.r-__project.org</a><br>
> <mailto:<a href="mailto:genabel-devel@lists.r-forge.r-project.org">genabel-devel@lists.r-forge.r-project.org</a>><br>
> <a href="https://lists.r-forge.r-__project.org/cgi-bin/mailman/__listinfo/genabel-devel" target="_blank">https://lists.r-forge.r-__project.org/cgi-bin/mailman/__listinfo/genabel-devel</a><br>
> <<a href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel" target="_blank">https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel</a>><br>
<div class="im HOEnZb">><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> genabel-devel mailing list<br>
> <a href="mailto:genabel-devel@lists.r-forge.r-project.org">genabel-devel@lists.r-forge.r-project.org</a><br>
> <a href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel" target="_blank">https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel</a><br>
><br>
<br>
</div><div class="HOEnZb"><div class="h5">--<br>
-----------------------------------------------------------------<br>
L.C. Karssen<br>
Utrecht<br>
The Netherlands<br>
<br>
<a href="mailto:lennart@karssen.org">lennart@karssen.org</a><br>
<a href="http://blog.karssen.org" target="_blank">http://blog.karssen.org</a><br>
<br>
Stuur mij aub geen Word of Powerpoint bestanden!<br>
Zie <a href="http://www.gnu.org/philosophy/no-word-attachments.nl.html" target="_blank">http://www.gnu.org/philosophy/no-word-attachments.nl.html</a><br>
------------------------------------------------------------------<br>
<br>
</div></div><br>_______________________________________________<br>
genabel-devel mailing list<br>
<a href="mailto:genabel-devel@lists.r-forge.r-project.org">genabel-devel@lists.r-forge.r-project.org</a><br>
<a href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel" target="_blank">https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel</a><br></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>