git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Scott Chacon <schacon@gmail.com>, git@vger.kernel.org
Subject: Re: Google Summer of Code 2012... and git wiki
Date: Thu, 1 Mar 2012 19:56:39 -0500	[thread overview]
Message-ID: <20120302005638.GC21835@sigill.intra.peff.net> (raw)
In-Reply-To: <201203020027.41016.jnareb@gmail.com>

On Fri, Mar 02, 2012 at 12:27:40AM +0100, Jakub Narebski wrote:

> Google Summer of Code 2012 has started.  The Git Development Community 
> has time till March 9 to submit organization application.
> 
> The problem (beside finding volunteer for the position of GSoC 
> administrator) is that both GSoC application and ideas for GSoC 
> projects were hosted on Git Wiki... but Git Wiki is still only parially 
> functional, available only as static pages under changed URLs.

I can be GSoC administrator again if nobody else wants to do it (and
probably Shawn as co-admin again). On my todo list for tonight is
actually starting and posting a draft application.

I'm perfectly happy if somebody else wants to take over the position.
It's mostly boring, and aside from coordinating the proposal ranking
process, not even all that much work (the real work is done by the
mentors).

> I guess we can get by without having fully functional wiki for creating 
> application (if we decide to apply), but it would need a forum to send 
> ideas for GSoC projects and some place to publish them.  Editable wiki 
> can work as both, though git mailing list and some static page (perhaps 
> home pages for git project on GitHub?) could also work.

My plan was to just solicit feedback from the mailing list. Though I
think I may throw the work into a repo or even a GitHub wiki to make
small edits simpler for people who want to contribute. If last year is
any indication, about 3-4 people will come up with comments. So just
taking patches or incorporating their suggestions manually would
probably be acceptable.

> I don't know what are ETA on bringing Git Wiki fully up, but I doubt it 
> would be possible at http://git.wiki.kernel.org -- it is more than two 
> months since the event and wiki is not functional yet.  Perhaps it 
> could be hosted at git-scm.com somewhere -  but it really should be 
> true wiki, editable without need to use git.

FWIW, I really like the GitHub wikis, because they are backed by git. So
you can choose whether to use the web interface or not. And you can
write in a variety of markup languages, including mediawiki, though when
I tried importing the old git wiki many moons ago, I noticed that the
formatting of many of the pages was not quite right.

-Peff

  parent reply	other threads:[~2012-03-02  0:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 23:27 Google Summer of Code 2012... and git wiki Jakub Narebski
2012-03-01 23:33 ` Scott Chacon
2012-03-02  0:26   ` Andrew Ardill
2012-03-02  0:56 ` Jeff King [this message]
2012-03-02  4:06   ` David Barr

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=20120302005638.GC21835@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=schacon@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).