On Fri, Apr 17, 2015 at 09:57:41AM +1000, Jeff Fearn wrote:
On 04/15/2015 11:40 AM, Pete Travis wrote:
> A wiki was discussed, probably more than once. The general
> feeling, as I recall, is that it would pose a quality control
> problem. We already have a pretty good demonstration of what
> happens to a wiki in the long term.
You have an example of what happens to un-curated content in the
long term, to mistake the absence of curation as a flaw in the
technology is unfortunate.
The only way git and CI help you curate is by keeping the number of
contributors low, if you had hundreds of people committing it
wouldn't help you curate their contributions.
This is why I suggested a stand alone docs wiki, you need to be able
to control publishing to address the real reason wikis fail,
curation.
I think I agree with Jeff here -- a Fedora wiki for *contributors* and
a Fedora wiki for *users to find docs* don't have to be the same
thing. The latter could be curated without taking on the virtually
endless problem of dealing with the former.
> Also, infra wants a static site, ie no database backends, to
allow
> scaling out with proxies; that rules out a lot of solutions.
IMHO this is your real fight and where you should spend most of your
energy.
Docs has to engage with the community and has make contributing
easy, git and CI will not do neither of those things, in fact they
actively work against these two goals.
Hmm, can you link to this policy? Or to where it's been
communicated?
Also... this sounds like a challenge for the infrastructure team. Is
this a problem that's unique to Fedora? If not, how do other projects
or communities solve it?
--
Paul W. Frields
http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - -
http://pfrields.fedorapeople.org/
The open source story continues to grow:
http://opensource.com