On 08/11/2017 02:45 PM, Nicolas Pace wrote:
> The downside of the github wiki is that it can only be editted by
> collaborators of the repository.
Github wiki for lime-packages is editable by everyone (having a Github
account).
https://help.github.com/articles/changing-access- permissions-for-wikis/
On 08/13/2017 01:42 AM, Patricio Gibbs wrote:
> right now we're in the phase of looking at
> software options for translation management. While we could use a
> dedicated translation platform, such as
> https://translatewiki.net
> or
> http://zanata.org
Sounds good :)
> another option is to create a multilingual platform that serves as:
> - the multilingual community wiki,
> - the home for multilingual documentation,
> - the platform for coordinating translation of software interfaces and
> documentation.
>
> One way to do that would be to copy the infrastructure of
> www.translatewiki.net. Another way might be an appropriately
> configured
> CMS instance (Drupal, Tiki, Wiki Suite, Cyclope?, etc.).
I would avoid setting up on our servers something needing a periodic
maintaining effort. Unless we really need it.
> I have not looked at the GitHub Wiki, but it almost certainly doesn't
> have an advanced translation interface (let me know if it does). Using
> a
> mono-lingual platform seems to me like a sub-optimal way forward given
> the diversity of languages in the LibreRouter project.
Gollum (Github wiki engine) doesn't support multilingual, but clearly
you can make a directory for each language.
> Pro "Hosted by someone else":
> - The TranslateWiki platform has users who enjoy translating
> free/libre
> software interfaces, and they're more likely to translate LibreMesh
> stuff that's on their server, so using their server might result in
> more
> translations of higher quality in more languages.
> - The complexity of maintaining the server is handled by someone else,
> so we can focus on what we're already doing.
These are both great points.
A good thing of Github wikis is that they support writing in Asciidoc
(which is the same way we write the pages for our website), for example:
https://github.com/powerman/asciidoc-cheatsheet/wiki
so contents could be easily fetched and included in our website.
Another good thing of it is that's basically a git repository, you can
clone, pull and push contents from a Github wiki.
https://help.github.com/articles/adding-and-editing- wiki-pages-locally/
So, the solution I like the most is:
* use Github wiki (Gollum hosted by Github)
* move the whole lime-web/docs directory content (which is the
documentation) or even all the *.txt files from lime-web (all the
contents from the website) to the wiki of lime-packages repository
* continue using asciidoc syntax also for wiki
* keep the repository open for write to everyone
* fetch contents from the wiki and include them in our static website
built with Jekyll, this would be painless
* use directories for separating different languages on the Github wiki
(sub-optimal but easy), while on our website the multilingual stuff
is already implemented (I checked: Jekyll finds the files even when
moved to another directory)
_______________________________________________
lime-users mailing list
lime-users@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users