> Was there some reason we weren't doing that before? :-) Mostly lack of demand. Everyone who has expressed any interest in contributing to the documentation effort is granted access to the markdown. All files are hosted on dropbox, and it would be a trivial effort to make the folder public. To me its really just a matter of deciding to manage a (hopefully) larger number of contributors to the documentation.
On Feb 27, 2014, at 11:28, Karl Fogel <kfo...@opentechstrategies.com> wrote: > "dwuthr...@fargeo.com" <dwuthr...@fargeo.com> writes: >> All Leanpub does is read Markdown files. There's nothing stopping us >> from making the Markdown files publicly available, thereby allowing >> anyone to access and edit. The arches project website might be a good >> place to allow people access to the files. Of course, there will need >> to be some kind of vetting of edits that are contributed. > > Yup -- just the same as with program source code changes. > >> In any case, we can choose to use these publicly edited documentation >> files as the input to Leanpub to generate new documentation. All in >> all, I don't think the problem is a technical one; rather its simply >> deciding to allow open access to the documentation files and begin >> managing the community-driven editing process. > > Was there some reason we weren't doing that before? :-) -- -- To post, send email to archesproject@googlegroups.com. To unsubscribe, send email to archesproject+unsubscr...@googlegroups.com. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to archesproject+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
