Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [asciidoc-wg] AsciiDoc Tooling Overview / Awesome list

Since you are a Working Group through the Eclipse Foundation, I think the default position is that anything you are doing should be viewed through that, leveraging the Eclipse Development Process where appropriate.  I don't claim to be authoritative on this specific topic in terms of this user supplied documentation, but before moving forward I highly suggest you expand on it, clearly stating what you are looking to achieve and pass it through emo@xxxxxxxxxxx as a sanity check.

I don't know what specific agreement you made with Eclipse regarding asciidoc repositories, nor what your intended future use of them will be.  However I find it mildly concerning, enough so to send this response, that you are talking about leveraging non-EPL licenses and short circuiting the ECA process.  I think in the short term the intention should be that as much as possible your community should be encouraged to sign ECA's and participate in the eclipse ecosystem in a proper fashion, in this situation through PRs that committers then approve and merge. If you have specific issues with that process, bring them up with the Architecture Council which I am a member of and would be happy to discuss/champion.

In summary, this may all be fine, I only know enough details to say something seems hinky. My caveat is that most of my experience with Eclipse has been project related and not Working Group related in these sorts of details?

cheers,
Jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx


On Fri, Apr 9, 2021 at 9:00 AM Alexander Schwartz <alexander.schwartz@xxxxxxx> wrote:

Hi,

at the previous steering group meeting I proposed an AsciiDoc awesome list to provide a community edited list of tools in the AsciiDoc ecosystem - see https://github.com/sindresorhus/awesome for examples.

As the AsciiDoc WG it allows us to list and promote tools that support AsciiDoc. These lists are usually maintained on GitHub repos in the README.

This post is about where to host a Git repo for this, and which license to choose.

While the AsciiDoc WG has a strong interest in this, I propose to host it not as an Eclipse project, but as as a simple GitHub repo unter https://github.com/asciidoc

Future versions of this list might be rendered as nice HTML on the asciidoc.org.

Please comment if you think this is possible/advisable.

Something to be discussed in the future: We (as the AsciiDoc WG) might end up with a list of things that have the name AsciiDoc in their name, but not necessarily be AsciiDoc TCK compliant (once there is a language specification).

These lists have usually a very liberal license. A quick survey revealed mostly licenses like "Creative Commons Zero v1.0 Universal" aka "CC0", others used MIT License.

Some thoughts on this: CC-licenses fit better here, as this is about documentation. As the AsciiDoc Lang documentation will be licensed CC-BY-4.0, this would also be an option. Following it to the letter, it would require everyone copying a link and one-line-of-text from the Awesomelist to add a link to the AsciiDoc Awesome list. Using CC-BY-4.0 is tempting to promote the list, but probably not the spirit of Awesome lists.

I therefore propose:

  • to adopt a license of CC0
  • no requirement of signing a eclipse contributor's agreement

Again, please comment if you think this is possible/advisable.

Best regards,
Alexander


--
Alexander Schwartz (alexander.schwartz@xxxxxxx)
https://www.ahus1.de
_______________________________________________
asciidoc-wg mailing list
asciidoc-wg@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/asciidoc-wg

Back to the top