From: Jakub Narebski <jnareb@gmail.com>
To: Miguel de Icaza <miguel@ximian.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Andreas Ericsson <ae@op5.se>,
Git Mailing List <git@vger.kernel.org>,
Shawn Pearce <spearce@spearce.org>,
monodevelop-list@lists.ximian.com,
Michael Hutchinson <m.j.hutchinson@gmail.com>
Subject: Re: [MonoDevelop] git integration with monodevelop
Date: Fri, 14 Nov 2008 18:55:47 +0100 [thread overview]
Message-ID: <200811141855.48131.jnareb@gmail.com> (raw)
In-Reply-To: <1226683698.4483.265.camel@erandi.site>
On Fri, 14 Nov 2008, Miguel de Icaza wrote:
Please, try to not lose the attribution
> Johannes Schindelin wrote:
> > May I suggest respectfully, that the next time communication channels
> > between the Mono-mentor and at least one knowledgable Git guy are
> > established early in the project? IIRC there was a GSoC project to
> > reimplement Git in C# last year, too, which failed, too.
>
> The first year effort failed because the student never started, he got a
> job before the official SoC start.
>
> This year one of the students vanished before the SoC started, the other
> one did some minimal work, probably because the work was above his
> comfort zone.
I think that it might also be that 'Git# implementation' is just too
big a project for single Google Summer of Code, even for two students.
JGit/EGit is developed for much longer than a single summer, with
larger number of developers than one or two students, and it is not
yet complete Git implementation. The JGit GSoC 2008 project was simply
"Eclipse plugin push support", and that size of project worked
wonderfully (see http://git.or.cz/gitwiki/SoC2008Projects page).
So for the future I think it would be better to a) define smaller sized
projects with definite (and reachable) goals; b) maintain better contact
with Git Development Community (git mailing list, #git IRC channel).
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-11-14 17:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 10:22 git integration with monodevelop Andreas Ericsson
2008-11-12 10:31 ` Andreas Ericsson
2008-11-13 0:00 ` Govind Salinas
2008-11-12 19:48 ` [MonoDevelop] " Miguel de Icaza
2008-11-12 22:19 ` Jakub Narebski
2008-11-13 1:42 ` Miguel de Icaza
2008-11-14 13:26 ` [MonoDevelop] " Johannes Schindelin
2008-11-14 17:28 ` Miguel de Icaza
2008-11-14 17:55 ` Jakub Narebski [this message]
2008-11-14 17:53 ` "Andrés G. Aragoneses"
2008-11-12 23:56 ` Michael Hutchinson
2008-11-13 7:55 ` Andreas Ericsson
2008-11-13 9:28 ` Christian Hergert
2008-11-13 11:01 ` [MonoDevelop] " Andreas Ericsson
2008-11-13 16:10 ` Lluis Sanchez Gual
[not found] ` <491AF20D.4070600@kde.ru>
[not found] ` <491AF768.3010607@op5.se>
[not found] ` <491B02FF.2060204@kde.ru>
2008-11-13 7:20 ` Andreas Ericsson
2008-11-14 13:30 ` Johannes Schindelin
2008-11-14 13:53 ` Andreas Ericsson
2008-11-14 14:55 ` Johannes Schindelin
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=200811141855.48131.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=m.j.hutchinson@gmail.com \
--cc=miguel@ximian.com \
--cc=monodevelop-list@lists.ximian.com \
--cc=spearce@spearce.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).