Use Advanced Search to search the entire archive.
[jsr363-experts] Re: Fwd: JSR 363 Specifica... - Should this be in a separate document...
- From: Werner Keil <
>
- To: "
" <
>
- Subject: [jsr363-experts] Re: Fwd: JSR 363 Specifica... - Should this be in a separate document...
- Date: Wed, 26 Aug 2015 11:09:09 +0200
Dear experts,
Please find the RI User Guide for JRS 363:
https://github.com/unitsofmeasurement/unit-ri-userguide
I actually managed to trick GitBook into accepting an organization
repository (when you add a new book it only shows your personal repos, but
"link" allows to specify any repository you own or have necessary grants
to;-)
Started to pull out the first chapters from the Spec. Eventually everything
under "Implementation" as Chris suggested will go to the new RI guide.
EG Members and Content Developers (those in this team, a java.net analogy)
are permitted to update this book. Please feel free to work on it. Ideally
with a GitBook account, but pushing directly to the GitHub files should
also work if you don't have a GitBook user.
Regards,
Werner
On Mon, Aug 17, 2015 at 6:33 PM, Werner Keil
<
>
wrote:
>
Hi,
>
>
As there were no other votes, I guess we'll go for GitBook.
>
>
It has one major advantage which is a separate repository independent of
>
the actual RI, so non EG Members can help docment or simply translate to
>
another language more easily.
>
>
Regards,
>
Werner
>
>
On Wed, Aug 5, 2015 at 12:53 PM, Werner Keil
>
<
>
>
wrote:
>
>
> Especially Gitbook uses Markdown, almost the same as in README or others
>
> you may use in GitHub, too.
>
>
>
>
>
>
>
> On Wed, Aug 5, 2015 at 12:24 PM, Martin Desruisseaux <
>
>
>
>
> wrote:
>
>
>
>> Le 05/08/15 11:55, Werner Keil a écrit :
>
>>
>
>> Just a quick reminder if you have a preference towards format of a "RI
>
>> guide"?
>
>>
>
>> As of now, we have
>
>>
>
>> - 3 votes for Gitbook
>
>> - 2 votes for Asciidoc
>
>>
>
>>
>
>> No preference between those two on my side.
>
>>
>
>> In the past I have used extensively Maven APT, Docbook, Markdown and
>
>> others, and came to the conclusion that it was better to write directly in
>
>> HTML 5 for our documentation. But not all documentation have the same
>
>> needs.
>
>>
>
>> Martin
>
>>
>
>>
>
>
>