<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<p>Hi all!<br>
<br>
</p>
<p>I'm slightly burned out and bored with certain areas of Zope 2 Zwiki
development. I think the product will provide some value for a while
yet, and it's not too late to shake things up and make a bigger splash.
If we don't do this during the period of Zwiki & Zope 2's
relevance, our good work will bring less benefit than it might have. So
I'm putting out a call for help. I'd really like to see more people
take on development of Zwiki.
</p>
<p>What are the roadblocks - of my making, and otherwise - to a more
active Zwiki developer community ?
For one thing I needed to nail down some copyright/license issues more
explicitly, to make contributing and accepting contributions more of a
no-brainer. Here's my latest thinking:</p>
<p>LICENSE</p>
<p>Much Zope code uses the ZPL. We want to maximize code sharing and
participation with the whole Zope community. Much of the rest of the
FOSS world uses the GPL, and the same goes for them. Dual GPL/ZPL
licensing may seem a good option, but I'm convinced it's not worth the
added complexity, legal uncertainty and fragmentation; either straight
GPL or straight ZPL is preferable.
GPL is the mainstream license for the future IMHO, I think it's still
the best option, and I have no plan to leave it. Also I think we
should adopt GPLv3<a class="new visualNoPrint"
href="http://zwiki.org/PolicyAnnouncementDraft/createform?page=GPLv3"
title="create this page">?</a> when it's ready. That said, there's now
clear policy allowing non-GPL code to be added
to Zwiki if necessary (below). Also I remain open to license
exemption requests from Zope developers.</p>
<p>COPYRIGHT</p>
<p>I no longer think the single copyright holder policy is best for
this
project, and I'm going to drop it. I am changing the main repo's
policy to multiple copyright holders (& allowing multiple
licenses),
with the simple condition that the overall project manager is assigned
the right to relicense to newer license versions. The powerful darcs
revision control system (together with new CONTRIBUTORS list) should
help us to keep track of copyright & licensing status and even
remove
problematic commits later if needed.</p>
<p>CONTRIBUTOR'S AGREEMENT</p>
<p>To ensure that everyone gets proper credit for their work; a clear
audit trail and legal status for the project; and that the project can
remain license-compatible with other free & open-source software in
future, I have added a very simple contributor agreement/contributor
list: <a href="http://zwiki.org/repos/ZWiki/CONTRIBUTORS.txt">http://zwiki.org/repos/ZWiki/CONTRIBUTORS.txt</a>
. All Zwiki contributors should read and consider signing this file, to
help us meet these goals. You can follow this easy procedure to add
your name to the glorious list:
</p>
<pre> (install darcs if needed, see <a class="moz-txt-link-freetext" href="http://darcs.net/DarcsWiki/CategoryBinaries">http://darcs.net/DarcsWiki/CategoryBinaries</a>)
darcs get --partial <a class="moz-txt-link-freetext" href="http://zwiki.org/repos/ZWiki">http://zwiki.org/repos/ZWiki</a>
cd ZWiki
echo "- Your Name <your@email>" >>CONTRIBUTORS.txt
darcs record -a -m"signed it" CONTRIBUTORS.txt
(enter your name & email address again)
darcs send
</pre>
<p>
</p>
This will become the authoritative list of code committers (at least),
and I'll be working to make sure all of you are listed properly. Many
have donated their time and creativity over the years - this list will
make that clearer.<br>
<br>
All comments, help and other ideas welcome. And I hope to see some of
you online or off. Happy holidays, and thanks <br>
<br>
-Simon<br>
</body>
</html>