-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I wanted to spur discussion about part of this, specifically:
On 10-03-07 10:41 AM, Mike.lifeguard wrote:
Because Progit (
progit.org) is not freely licensed
(the license
forbids commercial use), and contributing to it is unnecessarily
difficult, I have begun working on a textbook about Git on Wikibooks
Progit is a textbook about git, which is hosted in a git repository on
GitHub. This means that if you want to fix errors or translate, you can
fork the repository, make your changes, and the author can incorporate
them if they want to.
This gives the illusion of being able to contribute, when really your
edits are held hostage by one person. Not only are they a bottleneck,
but they can also refuse to accept your changes. More to the point, in
this case, they don't seem keen on accepting anything that isn't simply
fixing errata, or translating the English text.
Have other folks encountered other seemingly-open textbook-writing
efforts that aren't really open upon further inspection? How can we
capitalize on the frustration that might arise when people are unable to
contribute in practice (or doing so is more difficult than on Wikibooks)?
More to the point, I'm concerned (you may have seen my recent posts to
foundation-l) that using Flagged Revisions is killing Wikibooks because
it is taking us towards this seemingly-open-but-not-really model of
editing, which is contrary to the spirit of openness which got us this
far. I'd be interested to hear whether people think it is time to
abandon the extension, revamp the configuration, or something else.
Thanks,
- -Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkuTv2UACgkQst0AR/DaKHtprQCfcP+2fOt7ZNvQjoqKED7Q/zbS
ITsAniwLP/HmIL0wJ1qd6KUza8ZSe7G8
=bB3S
-----END PGP SIGNATURE-----