[dms-discuss] January Meeting

[Steve Edberg]

I'd vote for using a wiki; I haven't played with the internal wiki much,
but I use dokuwiki a lot for such purposes. Git is probably overkill for
this, and there's more of a learning curve. I've seen strange things
happen to Office formats (MS/LibOf/OpenOf/...) when passed among different
suites/OSes/versions, so I'd avoid that. Most wikis have enough formatting
to take care of things, there's inherent versioning, and (at least in
dokuwiki's case) there are PDF/text/other export options when needed.

Or, we could just do things in TeX (http://tug.org/)...no learning curve
there at all :)

   steve

On Thu, January 2, 2014 10:53 am, James R Holliday wrote:
>> I noticed that during the email discussion
>> of the key policy, the document was reformatted at least once, possibly
>> twice.  It would be good if we could agree on a suitable document format
>> for future discussions that allowed strike-outs and tracked revisions.
>
> Gotcha.  This is a great point/observation.
>
>
> Just throwing out some ideas for discussion...
>
>
> * For readability, mildly formatted/marked-up text is king.  Something
> like markdown is probably a good idea.
>
> * MS Word / LibreOffice has internal versioning.  That might lead to
> interoperability issues, however.
>
> * We could leverage github for revisioning.  We could also better
> utilize our internal wiki.
>
> -J
>
>
> _______________________________________________
> Davis Makerspace Discuss mailing list
> Discuss at lists.davismakerspace.org
> http://lists.davismakerspace.org/listinfo/discuss
>
>