git/list[1] front-page[2] threads[3] people[4] search[5] about
 

GitTogether topics status (4th of October)

From
Christian Couder <chriscool@tuxfamily.org>
Date
Oct 4, 2008, 16:16 UTC
Message-ID
<200810041816.41026.chriscool@tuxfamily.org>
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.

Next: Jeff King
Message 1 of 6 in “GitTogether topics status (4th of October)”
  1. Christian CouderOct 4, 2008
  2. Jeff KingOct 7, 2008
  3. Nicolas PitreOct 7, 2008
  4. Shawn O. PearceOct 7, 2008
  5. Shawn O. PearceOct 7, 2008
  6. René ScharfeOct 17, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.