--
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/120f7910-9555-40f5-bf85-3cd35e197164%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
+1 for Asciidoc
It can do everything Markdown can, plus a bit more. There’s also a great toolchain for creating PDFs that Dan Allen maintains. The MicroProfile.io website content is also in Asciidoc, so anything we create is instantly publishable there (regardless of what repo it lives in, the code that builds the site can pull and publish asciidoc from any git repo).
On Jun 7, 2017, at 2:09 PM, Ken Finnigan <k...@kenfinnigan.me> wrote:
I know I prefer adoc because of its features.But I don't know if we need to "pick one", though it would make it easier for contributions if we were consistent.Ken
On Wednesday, June 7, 2017 at 5:06:47 PM UTC-4, Kevin Sutter wrote:Have we decided on whether we're using md or adoc for our common files (README, CONTRIBUTING, etc)? Our evolution-process seems to be using md. But, I noticed that many of our component repos are using adoc... Should we focus on just one? Or, doesn't anybody care?
This came up because I was just initializing my new repo for the "bill of materials"... By default, Eclipse uses md (README.md), which is consistent with the component proposal I just completed for MP 1.1. But, I noticed that Config is using adoc (README.adoc).
Thanks, Kevin--
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile+unsubscribe@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/120f7910-9555-40f5-bf85-3cd35e197164%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "MicroProfile" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/microprofile/wuF8zAr1rnk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to microprofile+unsubscribe@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/B75229D4-4EFA-4A24-A5C6-42DED46F7C52%40tomitribe.com.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/CABH8erk3ECDHY4qUzapnf7J7UO_n5nQycaBdEh3_%3DZR7W0jF3A%40mail.gmail.com.
I prefer adoc.
It's much more powerful than MD.
For simple documents it doesn't matter but it makes sense to avoid mixing 2 formats. The evolution repo is one of the oldest and I guess MD was chosen just because the author knew it better or the original content was already in MD. With revising the evolution process, I would convert it to adoc.
--Ondro
+1 for Asciidoc
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/120f7910-9555-40f5-bf85-3cd35e197164%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "MicroProfile" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/microprofile/wuF8zAr1rnk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to microprofile...@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/B75229D4-4EFA-4A24-A5C6-42DED46F7C52%40tomitribe.com.
Just a small example why adoc is better – md doesn't support nested lists while adoc supports multilevel nested lists. And much more.
Ondro
+1 for Asciidoc
It can do everything Markdown can, plus a bit more. There’s also a great toolchain for creating PDFs that Dan Allen maintains. The MicroProfile.io website content is also in Asciidoc, so anything we create is instantly publishable there (regardless of what repo it lives in, the code that builds the site can pull and publish asciidoc from any git repo).
On Jun 7, 2017, at 2:09 PM, Ken Finnigan <k...@kenfinnigan.me> wrote:
I know I prefer adoc because of its features.But I don't know if we need to "pick one", though it would make it easier for contributions if we were consistent.Ken
On Wednesday, June 7, 2017 at 5:06:47 PM UTC-4, Kevin Sutter wrote:Have we decided on whether we're using md or adoc for our common files (README, CONTRIBUTING, etc)? Our evolution-process seems to be using md. But, I noticed that many of our component repos are using adoc... Should we focus on just one? Or, doesn't anybody care?
This came up because I was just initializing my new repo for the "bill of materials"... By default, Eclipse uses md (README.md), which is consistent with the component proposal I just completed for MP 1.1. But, I noticed that Config is using adoc (README.adoc).
Thanks, Kevin--
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile+unsubscribe@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/0dc6d48f-dde9-43e4-8900-1e08cad53f77%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/0dc6d48f-dde9-43e4-8900-1e08cad53f77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile+unsubscribe@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/AEEEC19D-481B-4B0F-A65C-F65BD639EE6F%40gmail.com.
For reading it doesn’t matter, for authoring md is still more widely understood, so likely has a lower barrier of entry. I quite like asciidoc though.
On Jun 7, 2017, at 5:36 PM, Kevin Sutter <kwsu...@gmail.com> wrote:
I'm not an expert with either one, so I don't really have a preference. But, I do think that consistency would be good for our own sanity as well as future contributions.Let's leave this conversation going for a bit, but it's leaning towards adoc... Ondrej or Heiko? Since the evolution-process is slanted towards md...-- Kevin
On Wed, Jun 7, 2017 at 4:33 PM, David Blevins <dble...@tomitribe.com> wrote:
+1 for Asciidoc
It can do everything Markdown can, plus a bit more. There’s also a great toolchain for creating PDFs that Dan Allen maintains. The MicroProfile.io website content is also in Asciidoc, so anything we create is instantly publishable there (regardless of what repo it lives in, the code that builds the site can pull and publish asciidoc from any git repo).
On Jun 7, 2017, at 2:09 PM, Ken Finnigan <k...@kenfinnigan.me> wrote:
I know I prefer adoc because of its features.But I don't know if we need to "pick one", though it would make it easier for contributions if we were consistent.Ken
On Wednesday, June 7, 2017 at 5:06:47 PM UTC-4, Kevin Sutter wrote:Have we decided on whether we're using md or adoc for our common files (README, CONTRIBUTING, etc)? Our evolution-process seems to be using md. But, I noticed that many of our component repos are using adoc... Should we focus on just one? Or, doesn't anybody care?
This came up because I was just initializing my new repo for the "bill of materials"... By default, Eclipse uses md (README.md), which is consistent with the component proposal I just completed for MP 1.1. But, I noticed that Config is using adoc (README.adoc).
Thanks, Kevin--
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/120f7910-9555-40f5-bf85-3cd35e197164%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "MicroProfile" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/microprofile/wuF8zAr1rnk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to microprofile...@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/B75229D4-4EFA-4A24-A5C6-42DED46F7C52%40tomitribe.com.
--
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/fcc56ab3-f72a-4307-a6be-6280b96b5295%40googlegroups.com.
+1 for adoc: richer and more versatile format without complexity addition (compared to md)
Antoine
--+1 for adoc.Alasdair already mentioned the slightly higher friction for new users of Asciidoc, but I've found it's worth it. The pain of later finding out that MD isn't good enough and converting to Asciidoc is *large*. There's support in lots of editors, AsciidocFX and Atom will both give live rendered previews, or there are are browser plugins which would work very well for Vi/Vim users ;-)
http://asciidoctor.org/docs/editing-asciidoc-with-live-preview
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile+unsubscribe@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/fcc56ab3-f72a-4307-a6be-6280b96b5295%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "MicroProfile" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/microprofile/wuF8zAr1rnk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to microprofile+unsubscribe@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/6ef009c2-6586-491d-9113-cb4d9a3bf161%40Spark.
Okay, I think I've left this vote/discussion open long enough... AsciiDoc is the clear winner. Please ensure that your documentation (proposals, readmes, specs, etc) are all in AsciiDoc (.adoc) format. As previously discussed, there are several tools to help you out . Personally, I use the AsciiDoc plugin for Atom and it works quite nice to preview the updates real time.
Thanks!
Kevin
On Thursday, June 8, 2017 at 10:49:41 AM UTC-5, Kevin Sutter wrote:
I'll leave this "vote" open for at least 24 hours, but it's looking like asciidoc is the clear winner... Thanks!-- Kevin
On Thu, Jun 8, 2017 at 7:21 AM, 'Antoine Sabot-Durand' via MicroProfile <microp...@googlegroups.com> wrote:
+1 for adoc: richer and more versatile format without complexity addition (compared to md)
Antoine
--+1 for adoc.Alasdair already mentioned the slightly higher friction for new users of Asciidoc, but I've found it's worth it. The pain of later finding out that MD isn't good enough and converting to Asciidoc is *large*. There's support in lots of editors, AsciidocFX and Atom will both give live rendered previews, or there are are browser plugins which would work very well for Vi/Vim users ;-)
http://asciidoctor.org/docs/editing-asciidoc-with-live-preview
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/fcc56ab3-f72a-4307-a6be-6280b96b5295%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "MicroProfile" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/microprofile/wuF8zAr1rnk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to microprofile...@googlegroups.com.