https://bugzilla.wikimedia.org/show_bug.cgi?id=49313

Luis Villa <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #2 from Luis Villa <[email protected]> ---
I think it makes sense to:

1. Copy https://git.wikimedia.org/blob/mediawiki%2Fcore.git/HEAD/COPYING into
https://git.wikimedia.org/tree/qa%2Fbrowsertests (Please rename it LICENSE
instead of COPYING - that's not traditional, but it is more clear.)

2. Create a CREDITS file; suggest that anyone who has made a significant
contribution put their name/handle there.

3. Use a brief header, instead of the traditional full GPL header; something
like:

----
This file is subject to the license terms in the LICENSE file found in the
browsertests top-level directory of and at
https://git.wikimedia.org/tree/qa%2Fbrowsertests/HEAD/LICENSE. No part of
browsertests, including this file, may be copied, modified, propagated, or
distributed except according to the terms contained in the LICENSE file.

Copyright 2013 by the Mediawiki developers. See the CREDITS file in the
browsertests top-level directory and at
https://git.wikimedia.org/tree/qa%2Fbrowsertests/HEAD/CREDITS.
----

This approach will keep the headers smaller (particularly nice for something
like this) and means there is less to update should we ever need to clarify
something.

FYI, these recommendations are mostly based on
https://www.softwarefreedom.org/resources/2012/ManagingCopyrightInformation.html
(We should probably consider working in that direction across all new projects,
but that's a long-term project - no hurry.)

I'd love to make the patch myself, but I'm swamped for the next few weeks...

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to