git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@inf.ethz.ch>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: "Jeff King" <peff@peff.net>,
	git@vger.kernel.org, "Shawn Pearce" <spearce@spearce.org>,
	"Jakub Narebski" <jnareb@gmail.com>,
	"Christian Couder" <christian.couder@gmail.com>,
	"Pat Thoyts" <patthoyts@users.sourceforge.net>,
	"Paul Mackerras" <paulus@samba.org>,
	"Carlos Martín Nieto" <cmn@elego.de>,
	"Thomas Gummerer" <t.gummerer@gmail.com>,
	"David Barr" <b@rr-dav.id.au>,
	"Jens Lehmann" <Jens.Lehmann@web.de>,
	"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
Subject: Re: Google Summer of Code 2013 (GSoC13)
Date: Mon, 18 Feb 2013 21:03:50 +0100	[thread overview]
Message-ID: <878v6lwfrt.fsf@pctrast.inf.ethz.ch> (raw)
In-Reply-To: <CALkWK0kFYP4k5=237PZ3XHhxkzF-RWwwe=3+Thb_xU2Jw5tg2g@mail.gmail.com> (Ramkumar Ramachandra's message of "Tue, 19 Feb 2013 01:15:49 +0530")

Ramkumar Ramachandra <artagnon@gmail.com> writes:

[...]
>>> On a related note, I don't like our Wiki.  It's down half the time,
>>> and it's very badly maintained.  I want to write content for our Wiki
>>> from the comfort of my editor, with version control aiding me.  And I
>>> can't stand archaic WikiText.
>>
>> Agreed on all of those points. Putting the Wiki on GitHub fixes that.
>> But it means contributors need to have a GitHub account. On the other
>> hand, I think kernel.org wiki contributors need an account these days?
>> And GitHub is putting some active effort into finding and killing spammy
>> accounts, which might keep wiki spam down (I do not pay too much
>> attention to those efforts, but on kernel.org, it is mostly up to the
>> Git community to do it ourselves).
>
> No, I'm against using the GitHub Wiki for neutrality reasons.  There
> is one easy way to fight spam: don't expose a web-based editing
> interface at all.  It's mainly going to be maintained by the
> community, and we're all much more comfortable in our editors and git.
>  We can give the regulars direct commit access and ask the rest to
> submit pull requests.  Make it cost pennies, so any of us can easily
> afford it: just a cheap domain, DNS, and static HTML hosting.

I suppose since github's wiki system (gollum) is open source [1] it
wouldn't be too hard to set up another instance somewhere.  Bonus points
for importing all the old data in mediawiki format first, which is also
apparently supported.

But that just shifts the point of failure from the entire github team to
one or two people who end up administering the server.

Perhaps a better solution would be to ask Scott or Peff to create a
gollum instance under git-scm.com, which they're already hosting?  (It
seems people got over *that* neutrality issue quickly enough.)  Push
rights could be given to interested regulars.  It would then at least be
independent in name.


Footnotes: 
[1]  https://github.com/github/gollum

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  parent reply	other threads:[~2013-02-18 20:04 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 17:23 Google Summer of Code 2013 (GSoC13) Thomas Rast
2013-02-18 17:42 ` Jeff King
2013-02-18 18:44   ` Ramkumar Ramachandra
2013-02-18 18:58     ` Jeff King
2013-02-18 19:45       ` Ramkumar Ramachandra
2013-02-18 19:57         ` Jonathan Nieder
2013-02-18 20:03         ` Thomas Rast [this message]
2013-02-19  7:51           ` Ramkumar Ramachandra
2013-02-18 21:13         ` Jeff King
2013-02-19  9:00           ` Ramkumar Ramachandra
2013-02-18 19:45     ` Thomas Rast
2013-02-18 20:01       ` Jens Lehmann
2013-02-18 22:32     ` Junio C Hamano
2013-02-19  7:08       ` Ramkumar Ramachandra
2013-02-19  7:25         ` Jonathan Nieder
2013-02-19  8:12           ` Ramkumar Ramachandra
2013-02-19  8:41             ` Thomas Rast
2013-02-19 16:29               ` Junio C Hamano
2013-02-19 16:39                 ` Thomas Rast
2013-02-19  7:31         ` Junio C Hamano
2013-02-19  8:22           ` Ramkumar Ramachandra
2013-02-19 16:32             ` Junio C Hamano
2013-02-18 19:34   ` Jonathan Nieder
2013-02-18 20:02     ` Jens Lehmann
2013-02-20  6:17       ` Christian Couder
2013-02-18 20:44     ` Ramkumar Ramachandra
2013-02-18 21:07       ` Jeff King
2013-02-18 22:37         ` Junio C Hamano
2013-02-18 21:11       ` Potential GSoC13 projects (Re: Google Summer of Code 2013 (GSoC13)) Jonathan Nieder
2013-02-19  1:23         ` Duy Nguyen
2013-02-18 20:55     ` Google Summer of Code 2013 (GSoC13) Jeff King
2013-02-18 23:03       ` Jonathan Nieder
2013-02-20  6:50   ` Shawn Pearce
2013-02-20 12:07     ` Christian Couder
2013-02-20 12:26       ` Matthieu Moy
2013-02-21 15:41     ` Thomas Rast
2013-02-20 19:48   ` Michael Schubert
2013-02-21 14:29     ` Carlos Martín Nieto
2013-02-25  9:12   ` Florian Achleitner
2013-02-25 17:44     ` Junio C Hamano
2013-02-18 17:46 ` Thomas Rast
2013-02-18 18:02   ` Ronan Keryell
2013-02-18 19:48     ` Thomas Rast
2013-02-18 18:13   ` Ramkumar Ramachandra
2013-02-18 19:53     ` Thomas Rast
2013-02-19  1:17 ` Duy Nguyen
2013-02-26  4:59 ` Jaseem Abid

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878v6lwfrt.fsf@pctrast.inf.ethz.ch \
    --to=trast@inf.ethz.ch \
    --cc=Jens.Lehmann@web.de \
    --cc=artagnon@gmail.com \
    --cc=b@rr-dav.id.au \
    --cc=christian.couder@gmail.com \
    --cc=cmn@elego.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=patthoyts@users.sourceforge.net \
    --cc=paulus@samba.org \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    --cc=spearce@spearce.org \
    --cc=t.gummerer@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).