On 21/12/2010, at 6:51 AM, Morgan Hall wrote: > Funny, > > I just had this conversation with Max. I wanted to help contribute and > jokingly said "Please tell me you aren't using LaTex." > > I of course found out that Tex is the base for the documentation and I have > less than fond memories of using Tex, despite the very nice and consistent > output that it is capable of creating. > > I know how hard it can be to find contributors so limiting that volunteer > base even further by requiring GIT and Tex understanding and capability will > really minimize the number of people providing input. Maybe a chief editor > that collects input from contributors and edits the Tex document is a way to > maintain consistency of the documentation while gathering input from multiple > contributors. Good luck finding that volunteer leader though. > > I would probably prefer a wiki approach, but it clearly needs some structure, > boundaries and an Editor/Owner to help keep things consistent. > > Morgan
Hi Morgan et al. Yes I know what you mean about LaTex being love hate relationship :-) I do like the idea of Wiki, even if we use Tex in the wiki. One of the advantages is that any text based system allows for easy merging etc. If we can find some way to do easy online editing in some format or another, that can then be pulled together for the doc, we can then use the same technique we do for code, which is to (using git metaphores here) pull peoples changes. That way, like Max keeps an eye across the code, I (or someone) can keep an eye across the documentation. Allowing best of both worlds. There are a few online editors, but they are basically just text editors with a compile button to view your code. What it comes down to is the list of people offering to do documentation. If we can get at least 3 of us together, we can choose ourselves the best choice. One solution that may work well, depending on the individuals, is to use http://www.scribtex.com/ - although it would cost us $10/month - but perhaps only for a few months while we get things going. Either way, not a huge expense. Could you please email me those who are happy to help put content into the documentation. I will give people a few days, then I will email those people and come up with a plan. If we keep with Tex, I can then contribute those changes back into GIT for long term storage. If not, then we will still keep copies/backups in our Git repository for transparency and long life. I can easily split all the sections into separate files to make it easier to edit them, no matter what form of editor we use. Scott ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
