git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Zawirski <marek.zawirski@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, Sam Vilain <sam@vilain.net>,
	Joshua Roys <roysjosh@gmail.com>,
	Sverre Rabbelier <alturin@gmail.com>,
	Sverre Rabbelier <sverre@rabbelier.nl>,
	David Symonds <dsymonds@gmail.com>,
	Lea Wiemann <LeWiemann@gmail.com>,
	John Hawley <warthog19@eaglescrag.net>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Miklos Vajna <vmiklos@frugalware.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Stephan Beyer <s-beyer@gmx.net>,
	Christian Couder <chriscool@tuxfamily.org>,
	Daniel Barkalow <barkalow@iabervon.org>,
	Junio Hamano <gitster@pobox.com>
Subject: Re: [GSoC] Git projects for Google Summer of Code 2008 final evaluation
Date: Mon, 08 Sep 2008 19:46:21 +0200	[thread overview]
Message-ID: <48C564ED.7050402@gmail.com> (raw)
In-Reply-To: <200809042315.58898.jnareb@gmail.com>

Regarding...
> 4. Eclipse plugin push support
>
> Student: Marek Zawirski
> Mentor: Shawn O. Pearce


Jakub Narebski wrote:
> So students and mentors, please write what do you think current status 
> of project is: is it done, is it ready, is it perhaps already merged 
> in, or can be merged in at any time.  Please write also what wasn't 
> done, or what should be done different way (hindsight and all that).

Project is done, it's merged to master of egit, as Shawn pointed. I also
consider it successful, for sake of my experience too!

I was hoping to do some optional task after push GUI (2nd part of GSoC),
but instead I was designing/polishing the new GUI and existing clone
wizard. Created code was also base for later added (after GSoC) fetch GUI.

The downside is that there was not enough time for even starting stuff
like binary delta (re)implementation. This became huge task, as there
are serious libxdiff related license-issues. So it probably needs to be
implemented from scratch basing on existing research and pack file
format knowledge, but not the code.

> Students, could you please tell us if you plan to work on git further, 
> and in what range (how much time can you get to work on git). 

I enjoyed coding here, so I except to keep on working on egit. As you
may see (looking on my activity on the list) I'm pretty busy last time -
doing overdue exams, getting credits or having vacations (that's
especially hard labor...). So I won't work on egit next weeks for sure.
Later, I'm back to university again, so my activity may vary/be limited
during some periods. But I except to take some missing feature and work
on that in free time.

> What do you think about git development community?

Folks that I don't know how spend that much time on Git producing
portions of nice code...

Actually, I learned here what community in open source projects means.
Even if Git is not considered user-friendly, its community definitely is.

> What have you learned from participating in GSoC?

Among other things, I learned here using Git ;), doing development in
more open source way (e.g. where patches review/comments is natural
process), and somewhat doing development of product that is intended to
be highly reusable and effective.

(...)
> Thank you all very much for your work on Git projects on this Google 
> Summer of Code.

Thanks too!

-- 
Marek Zawirski [zawir]
marek.zawirski@gmail.com

  parent reply	other threads:[~2008-09-08 17:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04 21:15 [GSoC] Git projects for Google Summer of Code 2008 final evaluation Jakub Narebski
2008-09-04 22:10 ` Daniel Barkalow
2008-09-04 22:22 ` Joshua Roys
2008-09-04 22:36 ` Stephan Beyer
2008-09-04 22:44 ` Sverre Rabbelier
2008-09-04 22:55 ` Miklos Vajna
2008-09-04 23:04 ` Shawn O. Pearce
2008-09-08 17:46 ` Marek Zawirski [this message]
2008-09-09 14:52 ` Johannes Schindelin
2008-09-15 12:13 ` Jakub Narebski
2008-09-15 12:40   ` Johannes Schindelin
2008-09-15 14:08     ` Shawn O. Pearce

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=48C564ED.7050402@gmail.com \
    --to=marek.zawirski@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=LeWiemann@gmail.com \
    --cc=alturin@gmail.com \
    --cc=barkalow@iabervon.org \
    --cc=chriscool@tuxfamily.org \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=roysjosh@gmail.com \
    --cc=s-beyer@gmx.net \
    --cc=sam@vilain.net \
    --cc=spearce@spearce.org \
    --cc=sverre@rabbelier.nl \
    --cc=vmiklos@frugalware.org \
    --cc=warthog19@eaglescrag.net \
    /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).