git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <chriscool@tuxfamily.org>
To: git@vger.kernel.org
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	Junio C Hamano <gitster@pobox.com>,
	Scott Chacon <schacon@gmail.com>,
	Sam Vilain <sam.vilain@catalyst.net.nz>,
	Petr Baudis <pasky@suse.cz>
Subject: GitTogether topics status (4th of October)
Date: Sat, 4 Oct 2008 18:16:40 +0200	[thread overview]
Message-ID: <200810041816.41026.chriscool@tuxfamily.org> (raw)

Hi,

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

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

the planned speakers/topics changed a lot during the last weeks and are now:

- Johannes Schindelin (Google Tech Talk, 1 hour):
	Contributing with Git (or: all your rebase are belong to us)

- Shawn O. Pearce (Talk + Brainstorm, 1 hour):
	Introduce the secret bundle project

- Shawn O. Pearce (Talk + Debate, 0.5 hour):
	JGit, where is it going?

- Shawn O. Pearce (Talk + Plan Hacking, 1 hour):
	Pack v4, what's stopping you?

- Sam Vilain (?):
	GitTorrent, Git as a DB backend, perl.git conversion

- Junio C Hamano (Talk, 1 hour):
	Git Chronicle, Recent Additions to Git

- Scott Chacon (Talk/Discussion, 1 hour):
	Linkable library, Scriptability

- Scott Chacon (Hack Session(proposed)):
	Architecting / Building a usable linkable library

- Scott Chacon (Lightning Talk, 10 min):
	iGitHub - git daemon and repository browser on the iPhone

- Tom Preston-Werner (Talk/Discussion, 1 hour)
	Git ideas from GitHub

- ? (Talk/Discussion, 1 hour):
	New git homepage hammering out

- ? (Talk/Discussion, 1 hour):
	Git GUI that even a designer would use

There are still many things that are not clear or undecided. So more input 
is welcome.

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 vadis?
 * 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)
 * perl.git - the joy of grokking Perforce metadata using Postgres, and 
writing a transactional git-fastimport exporter SamV
 * Linkable library for basic object access (libification or new library)
 * Scriptability, using git in other languages (using interfaces vs calling 
plumbing vs reimplementting) 
 * Git GUI that even a designer could use (GitCheetah, AKA TortoiseGit?) (UI 
session?)
 * Git integration with IDE, RAD, and editors (UI session?)
 * New Git Homepage hammering-out (UI session?)
 * Shawn's current bundle related secret project
 * TopGit introduction/design/integration(?)
 * Pasky's current pickaxe related "secret project" (if tangible by then)
 * Extending Git with volatile metadata database (see 
[http://mid.gmane.org/20080910164045.GL10360@machine.or.cz 
20080910164045.GL10360@machine.or.cz])
 * Git improvement ideas gleaned from creating and running Git``Hub as a 
social layer on top of Git
 * 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".

Thanks,
Christian.

             reply	other threads:[~2008-10-04 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-04 16:16 Christian Couder [this message]
2008-10-07  3:15 ` GitTogether topics status (4th of October) Jeff King
2008-10-07  3:46   ` Nicolas Pitre
2008-10-07 14:38     ` Shawn O. Pearce
2008-10-07 14:46   ` Shawn O. Pearce
2008-10-17 19:18 ` René Scharfe

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=200810041816.41026.chriscool@tuxfamily.org \
    --to=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pasky@suse.cz \
    --cc=sam.vilain@catalyst.net.nz \
    --cc=schacon@gmail.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).