Repository navigation
Discuss move to TAP group #60
Description
The current TAP copyrights are 'wrong' and wouldn't be binding in any court of law due to the work having been done by far more contributors than is in the list and actually even Larry Wall should have some part of the copyright also.
Copyright 2003-2007 by Michael G Schwern schwern@pobox.com, Andy Lester andy@petdance.com, Andy Armstrong andy@hexten.net. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See http://www.perl.com/perl/misc/artistic.html.
I suggest a move to:
- Assign the rights to a group which has governing power over the TAP specifications
- or make it a copyleft with the agreement
- Make a separate acknowledgement page for (authors, acknowledgements and copyright) which needs mention to old contributors and perhaps automated from github for new contributions.
This would obviously need agreement etc but ensures future development can drive forward with more people acknowledged.
/cc @isaacs
Activity
jonathanKingston commentedon Dec 15, 2015
Also the domain testanything.org is owned by @AndyA this would be better under group ownership etc.
isaacs commentedon Dec 15, 2015
I think this is a fine idea. I'd meant to try to orchestrate something like this when you tagged me in last summer, but then startup management happened and we shipped the first version of a major npm SaaS product line since then.
TAP seems like it's pretty much a collection of mostly-stable-and-working-fine implementations at this point. I don't think fast moving specification churn serves anyone, and would have a hard time taking off anyway. But it would be nice to have things in a more organized format, and a spec for what we all already support.
jonathanKingston commentedon Dec 15, 2015
@isaacs that's fine things have been busy for me also and I agree even further than before that it should be fast paced etc now however it would be nice to create something much neater to at least be the updated spec and nice documentation with that I think honouring all the contributors on a dedicated page and resolving the issues above is important (a GitHub graph isn't important just a way of resolving who gets their name on etc).