GitTogether topics status

GitTogether topics status

[Christian Couder]

Hi,

As can be seen on the GitTogether page on the wiki: 

http://git.or.cz/gitwiki/GitTogether

we may have the following speakers/topics:

* Shawn O. Pearce:
	- bundle related secret project,
	- JGit,
	- PackV4,

* Sam Vilain:
	- GitTorrent (current state, security considerations, future direction),
	- Git as a DB backend,

* Junio C Hamano:
	- TBD,

Some people are not yet decided and others have not yet be contacted. So the 
list of possible speakers may grow. By the way if you want to talk or 
introduce a discussion/workshop/haxession please contact us (Shawn and 
myself).

The topics suggested on the wiki are:

	- GitTorrent: current state, security considerations, future direction
	- Submodules: how to make a UI for this important feature that is intuitive 
and complete
	- PackV4
	- JGit, quo vadis1?
	- Using Git for everything but source (Git as a backup tool, how to handle 
large blobs, using as a DB back-end, etc)
	- How to make Git more attractive to the Google Code folks?
	- Success/War stories (big wanking session for Gits)
	- Linkable library for basic object access (libification or new library)
	- Git GUI that even a designer could use (GitCheetah, AKA TortoiseGit?)
	- Shawn's current bundle related secret project
	- TopGit introduction/design/integration(?)
	- Pasky's current pickaxe related "secret project" (if tangible by then)
	- New Git Homepage hammering-out
	- Extending Git with volatile metadata database (see 
20080910164045.GL10360@machine.or.cz)
	- Git Survey 2008 results and discussion
	- Free form "We tried to use git in our project this way, didn't work very 
well" session, where participants are not allowed to say "Your workflow is 
broken".

More topics/ideas are welcome.

Thanks,
Christian.

Re: GitTogether topics status

[Jakub Narebski]

Christian Couder <chriscool@tuxfamily.org> writes:

> The topics suggested on the wiki are:
[...]
> More topics/ideas are welcome.

Perhaps a good idea would be to take advantage of whiteboards and
meeting face to face, and talk for example about ideas for perfect GUI
for git, or for editor/IDE/RAD integration interface, designing
mockups of UI.  This could aldo help with improving git homepage (the
original one, I guess).

What also might be interesting to talk about scriptability, having
defined API, libification (I see that there is planned), interfaces to
other programming languages versus calling git plumbing versus
reimplementing git in other languages (e.g. JGit vs JavaGit, Grit vs
Ruby/Git, GitPython vs PyGit, Git.pm vs Git::Repo), but I guess this
discussion could be had on git mailing list.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

Re: GitTogether topics status

[Christian Couder]

Le jeudi 18 septembre 2008, Jakub Narebski a écrit :
> Christian Couder <chriscool@tuxfamily.org> writes:
> > The topics suggested on the wiki are:
>
> [...]
>
> > More topics/ideas are welcome.
>
> Perhaps a good idea would be to take advantage of whiteboards and
> meeting face to face, and talk for example about ideas for perfect GUI
> for git, or for editor/IDE/RAD integration interface, designing
> mockups of UI.  This could aldo help with improving git homepage (the
> original one, I guess).

Ok. There are now the following topics together on the wiki:

 * Git GUI that even a designer could use (Git``Cheetah, AKA Tortoise``Git?) 
(UI session?)
 * Git integration with IDE, RAD, and editors (UI session?)
 * New Git Homepage hammering-out (UI session?)

The second one is new. And "(UI session?)" was added at the end of each of 
them.

> What also might be interesting to talk about scriptability, having
> defined API, libification (I see that there is planned), interfaces to
> other programming languages versus calling git plumbing versus
> reimplementing git in other languages (e.g. JGit vs JavaGit, Grit vs
> Ruby/Git, GitPython vs PyGit, Git.pm vs Git::Repo), but I guess this
> discussion could be had on git mailing list.

The following topics are now together on the wiki:

 * Linkable library for basic object access (libification or new library) 
 * Scriptability, using git in other languages (using interfaces vs calling 
plumbing vs reimplementting)

The second one is new.

If we want these topics to be discussed during the GitTogether, we need 
someone who wants to talk about or at least introduce these subjects 
though. (Hint, hint.)

Thanks,
Christian.

Re: GitTogether topics status

[Scott Chacon]

Hi,

On Thu, Sep 18, 2008 at 10:03 PM, Christian Couder
<chriscool@tuxfamily.org> wrote:
> Le jeudi 18 septembre 2008, Jakub Narebski a écrit :
>> Christian Couder <chriscool@tuxfamily.org> writes:
>> > The topics suggested on the wiki are:
>>
>> [...]
>>
>> > More topics/ideas are welcome.
>>
>> Perhaps a good idea would be to take advantage of whiteboards and
>> meeting face to face, and talk for example about ideas for perfect GUI
>> for git, or for editor/IDE/RAD integration interface, designing
>> mockups of UI.  This could aldo help with improving git homepage (the
>> original one, I guess).
>
> Ok. There are now the following topics together on the wiki:
>
>  * Git GUI that even a designer could use (Git``Cheetah, AKA Tortoise``Git?)
> (UI session?)
>  * Git integration with IDE, RAD, and editors (UI session?)
>  * New Git Homepage hammering-out (UI session?)
>
> The second one is new. And "(UI session?)" was added at the end of each of
> them.
>
>> What also might be interesting to talk about scriptability, having
>> defined API, libification (I see that there is planned), interfaces to
>> other programming languages versus calling git plumbing versus
>> reimplementing git in other languages (e.g. JGit vs JavaGit, Grit vs
>> Ruby/Git, GitPython vs PyGit, Git.pm vs Git::Repo), but I guess this
>> discussion could be had on git mailing list.
>
> The following topics are now together on the wiki:
>
>  * Linkable library for basic object access (libification or new library)
>  * Scriptability, using git in other languages (using interfaces vs calling
> plumbing vs reimplementting)
>
> The second one is new.
>
> If we want these topics to be discussed during the GitTogether, we need
> someone who wants to talk about or at least introduce these subjects
> though. (Hint, hint.)

I would be happy to talk about / introduce at least the second one,
since I've done most of the work on the pure-ruby implementation of
git in the Grit project, which is one of the more popular of the
re-implementations out there (and runs the GitHub site).  I would also
be happy to help with a discussion on the first one, since I added it
to the wiki in the first place and it is heavily connected to the
second topic.  I very much want to see a library that provides basic
Git object access that we can use to write proper bindings in
Ruby/Python/Perl.  If the current Git code is too difficult to libify
properly, then perhaps an alternate C implementation that is built
only for that purpose is preferable to having a re-implementation in
_every_ language.  Looking forward to the discussion.

Scott

>
> Thanks,
> Christian.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: GitTogether topics status

[Christian Couder]

Le vendredi 19 septembre 2008, Scott Chacon a écrit :
> Hi,
>
> On Thu, Sep 18, 2008 at 10:03 PM, Christian Couder
>
> <chriscool@tuxfamily.org> wrote:
> > Le jeudi 18 septembre 2008, Jakub Narebski a écrit :
> >
> >> What also might be interesting to talk about scriptability, having
> >> defined API, libification (I see that there is planned), interfaces to
> >> other programming languages versus calling git plumbing versus
> >> reimplementing git in other languages (e.g. JGit vs JavaGit, Grit vs
> >> Ruby/Git, GitPython vs PyGit, Git.pm vs Git::Repo), but I guess this
> >> discussion could be had on git mailing list.
> >
> > The following topics are now together on the wiki:
> >
> >  * Linkable library for basic object access (libification or new
> > library) * Scriptability, using git in other languages (using
> > interfaces vs calling plumbing vs reimplementting)
> >
> > The second one is new.
> >
> > If we want these topics to be discussed during the GitTogether, we need
> > someone who wants to talk about or at least introduce these subjects
> > though. (Hint, hint.)
>
> I would be happy to talk about / introduce at least the second one,
> since I've done most of the work on the pure-ruby implementation of
> git in the Grit project, which is one of the more popular of the
> re-implementations out there (and runs the GitHub site).  I would also
> be happy to help with a discussion on the first one, since I added it
> to the wiki in the first place and it is heavily connected to the
> second topic.  I very much want to see a library that provides basic
> Git object access that we can use to write proper bindings in
> Ruby/Python/Perl.  If the current Git code is too difficult to libify
> properly, then perhaps an alternate C implementation that is built
> only for that purpose is preferable to having a re-implementation in
> _every_ language.  Looking forward to the discussion.

Great! You are now in the "Possible speakers" list on the wiki.

Thanks,
Christian.  

Re: GitTogether topics status

[Johannes Schindelin]

Hi,

On Thu, 18 Sep 2008, Scott Chacon wrote:

> I very much want to see a library that provides basic Git object access 
> that we can use to write proper bindings in Ruby/Python/Perl.  If the 
> current Git code is too difficult to libify properly, then perhaps an 
> alternate C implementation that is built only for that purpose is 
> preferable to having a re-implementation in _every_ language.  Looking 
> forward to the discussion.

libgit-thin.  What is missing is somebody taking this forward (and this 
includes making it more public on the Git mailing list).

Hth,
Dscho