git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / Atom feed
* Git representative on AsciiDoc Working Group
@ 2020-02-12  0:21 brian m. carlson
  2020-02-14  6:23 ` Jeff King
  0 siblings, 1 reply; 4+ messages in thread
From: brian m. carlson @ 2020-02-12  0:21 UTC (permalink / raw)
  To: git

[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]

I've had folks from OpenDevise reach out to me and let me know that they're
launching a standardization initiative for AsciiDoc under the Eclipe
Foundation's open standardization process.  The goal is to standardize the
language, ensure compatibility across implementations, and provide a reference
implementation, with input from implementers, users, and others.

They'd like to extend an invitation for the Git project to send a
representative, since we're a significant user of AsciiDoc.  I'm sending out
this email to see what the project thinks and if anyone would be interested in
fulfulling that role.

Here's a bit of a summary on what will be involved:

  As a Working Group member, the Git project will have the opportunity to:

  - Influence the scope and roadmap of the AsciiDoc standardization effort
  - Help define the AsciiDoc specification, including terminology, syntax,
  document model, behavior, and extension points
  - Establish compatibility rules that ensure portability and
  interoperability of content and language extensions

  To learn more about the AsciiDoc Working Group and how it works, please
  refer to the welcome messages on the mailing list:

  - https://www.eclipse.org/lists/asciidoc-wg/msg00001.html
  - https://www.eclipse.org/lists/asciidoc-wg/msg00002.html

If anyone has any questions, I'll do my best to answer them, or to pull in folks
who can if I can't.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Git representative on AsciiDoc Working Group
  2020-02-12  0:21 Git representative on AsciiDoc Working Group brian m. carlson
@ 2020-02-14  6:23 ` Jeff King
  2020-02-14 12:07   ` Johannes Schindelin
  0 siblings, 1 reply; 4+ messages in thread
From: Jeff King @ 2020-02-14  6:23 UTC (permalink / raw)
  To: brian m. carlson; +Cc: git

On Wed, Feb 12, 2020 at 12:21:29AM +0000, brian m. carlson wrote:

> I've had folks from OpenDevise reach out to me and let me know that they're
> launching a standardization initiative for AsciiDoc under the Eclipe
> Foundation's open standardization process.  The goal is to standardize the
> language, ensure compatibility across implementations, and provide a reference
> implementation, with input from implementers, users, and others.
> 
> They'd like to extend an invitation for the Git project to send a
> representative, since we're a significant user of AsciiDoc.  I'm sending out
> this email to see what the project thinks and if anyone would be interested in
> fulfulling that role.

It certainly would be nice for somebody with Git's interests in mind to
keep an eye on the proceedings, just to make sure nothing too disruptive
is decided on.

But I don't know that we have a particular wishlist of things we'd
_like_ to see. The lack of semantic markup in asciidoc (e.g., being able
to mark a command-line parameter as such, rather than just a literal) is
sometimes a pain, but I think that's also what makes the source
documents so readable and generally non-painful to write.

As far as choosing a representative from the project, I'd probably
nominate you. ;)

-Peff

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Git representative on AsciiDoc Working Group
  2020-02-14  6:23 ` Jeff King
@ 2020-02-14 12:07   ` Johannes Schindelin
  2020-02-14 21:05     ` brian m. carlson
  0 siblings, 1 reply; 4+ messages in thread
From: Johannes Schindelin @ 2020-02-14 12:07 UTC (permalink / raw)
  To: Jeff King; +Cc: brian m. carlson, git

Hi,

On Fri, 14 Feb 2020, Jeff King wrote:

> On Wed, Feb 12, 2020 at 12:21:29AM +0000, brian m. carlson wrote:
>
> > I've had folks from OpenDevise reach out to me and let me know that they're
> > launching a standardization initiative for AsciiDoc under the Eclipe
> > Foundation's open standardization process.  The goal is to standardize the
> > language, ensure compatibility across implementations, and provide a reference
> > implementation, with input from implementers, users, and others.
> >
> > They'd like to extend an invitation for the Git project to send a
> > representative, since we're a significant user of AsciiDoc.  I'm sending out
> > this email to see what the project thinks and if anyone would be interested in
> > fulfulling that role.
>
> [...]
> As far as choosing a representative from the project, I'd probably
> nominate you. ;)

I'd probably second this. ;-)

Ciao,
Dscho

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Git representative on AsciiDoc Working Group
  2020-02-14 12:07   ` Johannes Schindelin
@ 2020-02-14 21:05     ` brian m. carlson
  0 siblings, 0 replies; 4+ messages in thread
From: brian m. carlson @ 2020-02-14 21:05 UTC (permalink / raw)
  To: Johannes Schindelin; +Cc: Jeff King, git

[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]

On 2020-02-14 at 12:07:00, Johannes Schindelin wrote:
> Hi,
> 
> On Fri, 14 Feb 2020, Jeff King wrote:
> 
> > On Wed, Feb 12, 2020 at 12:21:29AM +0000, brian m. carlson wrote:
> >
> > > I've had folks from OpenDevise reach out to me and let me know that they're
> > > launching a standardization initiative for AsciiDoc under the Eclipe
> > > Foundation's open standardization process.  The goal is to standardize the
> > > language, ensure compatibility across implementations, and provide a reference
> > > implementation, with input from implementers, users, and others.
> > >
> > > They'd like to extend an invitation for the Git project to send a
> > > representative, since we're a significant user of AsciiDoc.  I'm sending out
> > > this email to see what the project thinks and if anyone would be interested in
> > > fulfulling that role.
> >
> > [...]
> > As far as choosing a representative from the project, I'd probably
> > nominate you. ;)
> 
> I'd probably second this. ;-)

I'm happy to fill this role if the project would like.  The main
interest for me when representing the Git project would be a focus on
compatibility between implementations, which has historically been a
minor pain point for us.  That, of course, is the whole point of
standardization.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-12  0:21 Git representative on AsciiDoc Working Group brian m. carlson
2020-02-14  6:23 ` Jeff King
2020-02-14 12:07   ` Johannes Schindelin
2020-02-14 21:05     ` brian m. carlson

git@vger.kernel.org list mirror (unofficial, one of many)

Archives are clonable:
	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Example config snippet for mirrors

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.io/gmane.comp.version-control.git

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git