scribe-tool license?

[BigBlueHat]

scribe-tool license?

[gkellogg]

Actually, it’s Manu’s tool that I’ve tweeked a bit. Takes some handholding, but has some nice features.

[gkellogg]

@msporny, care to opine?

[gkellogg]

Perhaps the W3C Software and Document License would cover it:

All documents in this Repository are licensed by contributors under the W3C Software and Document License.

It was copied from https://github.com/opencreds/minutes/blob/master/LICENSE, so that may be the one to use. It's @msporny's creation, so he decides.

[msporny]

It was/is CC-0... 3-clause BSD is fine as well. I'd rather not do W3C SDL.

If either of you don't like CC-0, let's do 3-clause BSD.

[BigBlueHat]

@msporny does/did it have it's own repo? It'd be nice to just pull the tool in via package.json (vs. maintaining code with the archives)--and obviously I'd tweak the code to use templates per-the local repo or some such. 😄

License choices are of course fine, though I'm curious (tangentially) why not the W3C SDL (but totally fine if this code is not under that license).

[BigBlueHat]

And, if we get scrawl it's own repo, I'll make PRs to this one and opencreds to get them using a package.json originated scrawl command line thingie.

Cheers!
🎩

[msporny]

@msporny does/did it have it's own repo?

Yes, it has 3! (note that the W3C CCG also uses the tool)

It'd be nice to just pull the tool in via package.json (vs. maintaining code with the archives)--and obviously I'd tweak the code to use templates per-the local repo or some such.

Yeah, that'd be nice. It has been a constant work in progress over the past decade or so. Note instructions on using it:

https://github.com/w3c-ccg/w3c-ccg.github.io/blob/master/irc_ref.md#publishing-the-minutes

It's a part of a larger system... :)

Also note that there is live editor here where you can drop an IRC log into, clean it up, and see live changes as you make changes:

https://w3c-ccg.github.io/meetings/scribe-tool/

For example, drop the text of this IRC log into the text box at the link above:

https://w3c-ccg.github.io/meetings/2018-03-20/irc.log

License choices are of course fine, though I'm curious (tangentially) why not the W3C SDL (but totally fine if this code is not under that license).

My expectation is that developers don't know CC-0 and W3C SDL well enough to feel comfortable with it, thus will feel more comfortable contributing to the 3-clause BSD license.

[BigBlueHat]

@msporny works for me!