[Rfc-markdown] Fwd: [Paul White] [eclipse.org-membership-at-large] Proposal to establish the AsciiDoc Working Group

Carsten Bormann <cabo@tzi.org> Fri, 14 February 2020 08:09 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 76AA7120043 for <rfc-markdown@ietfa.amsl.com>; Fri, 14 Feb 2020 00:09:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id lxMzW93wpewL for <rfc-markdown@ietfa.amsl.com>; Fri, 14 Feb 2020 00:09:38 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2866120045 for <rfc-markdown@ietf.org>; Fri, 14 Feb 2020 00:09:37 -0800 (PST)
Received: from sev.informatik.uni-bremen.de (sev.informatik.uni-bremen.de []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 48JmHz6d56z10pf; Fri, 14 Feb 2020 09:09:35 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8744DF58-3C73-4FEC-9683-69DDC3C55ECB"
X-Mao-Original-Outgoing-Id: 603360575.7753201-846321580918f0d2213d9debec485cbb
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.\))
Date: Fri, 14 Feb 2020 09:09:35 +0100
Message-Id: <2303DFD7-0EF6-4C3F-8100-35AEA041D6F4@tzi.org>
References: <87imk9iq8h.fsf@wangari>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/LKi7Ew2jFSwGL4nlRBrdGsqC8-4>
Subject: [Rfc-markdown] Fwd: [Paul White] [eclipse.org-membership-at-large] Proposal to establish the AsciiDoc Working Group
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2020 08:09:42 -0000

While this may not yet tip the scales from markdown to asciidoc, this is an interesting development.

Grüße, Carsten

> From: Paul White <paul.white@eclipse-foundation.org>
> Subject: [eclipse.org-membership-at-large] Proposal to establish the AsciiDoc Working Group
> Date: 2020-02-13 at 21:56:03 CET
> To: eclipse.org-membership-at-large@eclipse.org
> All,
> A proposal has been made to establish the AsciiDoc Working Group [1].
> The aim of the working group is to drive the standardization, adoption, and evolution of the AsciiDoc language. This effort will include tools to comprehend, analyze, and transform this language for use in creating technical communication encoded in AsciiDoc. The ultimate goal is to support the development, deployment, management, and usage of software documentation, applications, and services that use AsciiDoc.
> The working group will:
> 	• Foster the design and development of the AsciiDoc language specification, which includes the syntax, rules, built-in attributes, Abstract Semantic Graph (ASG), DOM (Document Object Model), API and options, conversion model, referencing system, extension SPI, and runtime-agnostic technology compatibility kit (TCK), all to ensure interoperability and portability of information encoded in AsciiDoc.
> 	• Collaborate with Working Group members, contributors, subject matter experts, and community members from multiple domains to select and define capabilities, terminology, and syntax for AsciiDoc based on tangible and emerging use cases, requirements, and important external developments.
> 	• Support the development of associated technical specifications, compatible implementations, tools, and software libraries.
> 	• Encourage an extensible architecture, pattern reuse, interface consistency, ease of use and customization, enterprise-level frontend and backend performance, and secure programmatic practices.
> The proposed charter [1]  for this working group is available for review.   If you have any comments or feedback on the proposed charter, please send them to the working group mailing list [2], or feel free to contact me directly.  
> All Members of the Eclipse Foundation are invited to join and participate in this working group. If you are interested, please send an email to the mailing list [2].  Based on the feedback and level of interest, the working group will be officially created later this quarter. 
> You can find a list of all of the Eclipse Foundation’s Working Groups here [3]. 
> [1] https://www.eclipse.org/org/workinggroups/asciidoc-charter.php  
> [2] https://accounts.eclipse.org/mailing-list/asciidoc-wg
> [3] https://www.eclipse.org/org/workinggroups/explore.php
> Regards,
> Paul
> Paul White
> VP, Member Services | Eclipse Foundation, Inc.
> paul.white@eclipse-foundation.org
> +1.613.224.9461
> _______________________________________________
> eclipse.org-membership-at-large mailing list
> eclipse.org-membership-at-large@eclipse.org
> https://www.eclipse.org/mailman/listinfo/eclipse.org-membership-at-large
> IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@eclipse.org to request removal.