Yves, I agree using the github wiki is optimal, general introduction and keeping the community informed and recruiting foss devs could go via wikidot. On 18 Oct 2011 20:31, "Yves Jaradin" <yves.jara...@uclouvain.be> wrote:
> Le 18/10/11 14:11, Gustavo Gutierrez a écrit : > >> >> >> 2011/10/18 stewart mackenzie <setor...@gmail.com >> <mailto:setor...@gmail.com>> >> >> Are there any German speaking volunteers who are willing to break this >> bottle neck by translating these two important mozart papers into >> English? >> >> >> I am afraid those are complete PhD thesis. Anyway, I think what we can >> do is to document the new implementation (that will keep the ideas >> described in those thesis). >> >> Regards, >> -- >> Gustavo Gutierrez >> >> > Yes, that's what I started. I made a github repo (yjaradin/mozart2) for the > new code (I want to keep it off the mozart account until it becomes minimaly > usable) and an associated wiki to document the design ideas. The nice thing > is that the wiki is also a git repo so it can be kept in sync with the code. > I like the fact that the whole development would be in one place (in this > case github) rather than spread over many websites. > > However, from what I see the wiki Stewart started on wikidot seems to > target more the Oz developpers (writing Oz programs, not the Mozart platform > itself) as a to-be replacement for mozart-oz.org and is therefore > complementary to the github one. > > Yves > > > > ______________________________**______________________________** > _____________________ > mozart-hackers mailing list > mozart-hackers@mozart-oz.org http://www.mozart-oz.org/** > mailman/listinfo/mozart-**hackers<http://www.mozart-oz.org/mailman/listinfo/mozart-hackers> >
_________________________________________________________________________________ mozart-hackers mailing list mozart-hackers@mozart-oz.org http://www.mozart-oz.org/mailman/listinfo/mozart-hackers
