From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Eric Wong <normalperson@yhbt.net>,
Jakub Narebski <jnareb@gmail.com>,
Nicolas Pitre <nico@fluxnic.net>,
Paul Mackerras <paulus@samba.org>, Johannes Sixt <j6t@kdbg.org>,
Robin Rosenberg <robin.rosenberg@dewire.com>
Subject: Re: git as an sfc member project
Date: Fri, 26 Feb 2010 07:59:16 -0500 [thread overview]
Message-ID: <20100226125916.GA12650@coredump.intra.peff.net> (raw)
In-Reply-To: <20100224154452.GA25872@coredump.intra.peff.net>
On Wed, Feb 24, 2010 at 10:44:52AM -0500, Jeff King wrote:
> A while back I mentioned that we had some leftover GSoC money, and
> suggested joining the Software Freedom Conservancy as a member project:
Thanks for all of the feedback so far. Here is round 2 of the
application, which I hope is close to done. I am cc'ing all of the
people under the "Key Developers" list; if you have affiliations you
feel should be disclosed, please let me know. And of course any other
suggestions or corrections are welcome.
-- >8 --
> * Detailed description of the project.
Git is a free & open source, distributed version control system
designed to handle everything from small to very large projects with
speed and efficiency.
Every Git clone is a full-fledged repository with complete history and
full revision tracking capabilities, not dependent on network access or
a central server. Branching and merging are fast and easy to do.
Projects using git include the Linux kernel, X.org, Perl, Gnome, Ruby on
Rails, Wine, Android, and more.
> * FLOSS License(s) used by the project
The core git code is licensed under GPLv2.
The JGit code, a pure-Java implementation of git, is licensed under
the Eclipse Distribution License, which is a new-style BSD
license.
> * Roadmap for future development.
Git is a stable, widely-used version control system. The majority
of the key functionality is already implemented. Consequently the
project does not maintain a formal roadmap, but instead accepts
a wide range of relevant enhancements and fixes directly from
the user community.
Based on prior history, major new releases occur about every 18
months, minor releases about every 2-3 months, and maintenance
releases every few weeks. Development is highly distributed,
with over 280 individual contributors during the past 12 months,
and over 730 contributors since the project's inception.
> * link to the website.
http://git-scm.org
http://www.eclipse.org/jgit/
> * Link to the code repository.
http://git.kernel.org/?p=git/git.git
http://repo.or.cz/w/jgit.git
> * Have you ever had funds held by the project, or by any individual
> on behalf of the projects? How and for what did you spend those
> funds?
Yes. We received funds from participating in the Google Summer of Code
in 2008 and 2009. Those funds were disbursed to individual project
members, and used for transportation and lodging of members attending
the GSoC mentor summit and the GitTogether, our annual mini-conference
for developers. The remainder of the funds were sent to the SFC.
> * Brief history of the project, including past governance decisions.
Git was started by Linus Torvalds in April of 2005. In July of 2005,
Junio C Hamano became the maintainer. Junio maintains sole control of
the codebase, accepting changes from other developers (both frequent
contributers and one-time patch submitters). For participation in the
Google Summer of Code, Shawn Pearce has served as the project
administrator.
JGit was started in 2006 by Shawn Pearce to provide an efficient,
portable implementation of Git for Java based applications. The
project moved to the Eclipse Foundation in late 2009, but remains a
standalone component and is widely embedded in non-Eclipse software.
> * Existing for-profit or non-profit affiliations, funding
> relationships, or other agreements that the project or its leaders
> have with other organizations.
Git has participated in the Google Summer of Code.
JGit is hosted by the Eclipse Foundation, and is run in accordance
with the foundation's development processes.
> * Names, email addresses, and affiliations of key developers, past and
> present.
Junio C Hamano <gitster@pobox.com>
(Part of Junio's git time used to be funded jointly by his employer and
NEC, but the latter is not anymore.)
Shawn O. Pearce <spearce@spearce.org>
(Google employee, Eclipse Foundation project committer, Apache Software
Foundation project committer)
Linus Torvalds <torvalds@linux-foundation.org>
[Linux Foundation?]
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Eric Wong <normalperson@yhbt.net>
Jeff King <peff@peff.net>
Jakub Narebski <jnareb@gmail.com>
Nicolas Pitre <nico@fluxnic.net>
Paul Mackerras <paulus@samba.org>
Johannes Sixt <j6t@kdbg.org>
Robin Rosenberg <robin.rosenberg@dewire.com>
[I'm still not happy with this list. For example, Pasky was certainly a
key person (and while he is not too active lately, it does say "past and
present"). But this list is already getting long, and if they really
care they can run shortlog themselves. I am tempted to cut it off after
Dscho, where there is a big jump in the number of commits:
$ git shortlog -ns v1.7.0
7689 Junio C Hamano
1356 Shawn O. Pearce
1092 Linus Torvalds
710 Johannes Schindelin
459 Eric Wong
432 Jeff King
395 Jakub Narebski
327 Nicolas Pitre
322 Paul Mackerras
272 Johannes Sixt
Maybe a note saying the development is very distributed and that they
should look at the repo for full details?]
> * Information about any past for-profit or non-profit organizational
> affiliations the project has had.
None.
next prev parent reply other threads:[~2010-02-26 12:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 15:44 git as an sfc member project Jeff King
2010-02-24 16:07 ` Jakub Narebski
2010-02-26 12:39 ` Jeff King
2010-02-26 15:56 ` Jakub Narebski
2010-03-01 10:58 ` Jeff King
2010-02-24 16:22 ` Shawn O. Pearce
2010-02-26 12:49 ` Jeff King
2010-02-24 17:44 ` Christian Couder
2010-02-26 12:25 ` Jeff King
2010-02-24 18:12 ` Junio C Hamano
2010-02-26 12:29 ` Jeff King
2010-02-26 12:37 ` Jeff King
2010-02-26 12:59 ` Jeff King [this message]
2010-02-26 13:14 ` Julian Phillips
2010-03-01 10:53 ` Jeff King
2010-02-27 6:35 ` Eric Wong
-- strict thread matches above, loose matches on Subject: below --
2010-10-22 18:30 Jeff King
2010-10-22 19:19 ` Shawn Pearce
2010-10-22 19:35 ` Jeff King
2010-10-22 20:06 ` Shawn Pearce
2010-10-22 20:59 ` Sverre Rabbelier
2010-10-22 21:48 ` Junio C Hamano
2010-10-22 22:59 ` Junio C Hamano
2010-10-22 23:18 ` Jeff King
2010-10-22 23:21 ` Brandon Casey
2010-10-22 23:26 ` Junio C Hamano
[not found] ` <hh0bQq8TcM0saDTuJo6qVdOMgn-14aysvhF_S70syB678Of7zQOsY9jLajG2WpeGXid8jtG4kVA@cipher.nrlssc.navy.mil>
2010-10-23 0:09 ` Brandon Casey
2010-10-23 1:30 ` Brandon Casey
2010-10-23 22:48 ` Brandon Casey
2010-10-22 23:22 ` Junio C Hamano
2010-10-23 11:52 ` Ævar Arnfjörð Bjarmason
2010-10-23 13:39 ` Jeff King
2010-10-23 16:03 ` A Large Angry SCM
2010-10-26 22:39 ` Jeff King
2010-10-27 7:03 ` Tait
2010-10-27 11:08 ` Jeff King
2010-11-02 23:03 ` Bradley M. Kuhn
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=20100226125916.GA12650@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=jnareb@gmail.com \
--cc=nico@fluxnic.net \
--cc=normalperson@yhbt.net \
--cc=paulus@samba.org \
--cc=robin.rosenberg@dewire.com \
--cc=spearce@spearce.org \
--cc=torvalds@linux-foundation.org \
/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).