This project has moved forward mostly by developers scratching their own itches. In my opinion, the most important people to open source projects are those who contribute. Projects need code, bugs, documentation, and leadership. I haven't had much time lately to actually code on this project (the iPad is looming, you know), but I'd be willing to try to pickup the torch from pieter and help keep things moving, even if i can't contribute much code right away.
Here are some of the ideas I have to tidy up the work on the project: - Let's move the website and docs into github pages - We should be able to use the github downloads feature in conjunction with gh pages to handle the sparkle feed - Tickets? Move to github? Takeover the lighthouse project? Other? - Releases. We need more of them. It might be worthwhile to take a page from textmate and have a "bleeding edge" and a "stable" feed and let users choose. There are many divergent forks. We need to do some consolidation. Should we start from pieter's master and pull in others or is there a better one? I'll nuke my master and start fresh from whichever one we decide is best. If you have work that you feel should go into the mainline, please send me a patch or a pull request. I'll create a bunch of tickets from there so we can start the discussion. thoughts? -dave (github.com/dgrijalva) On Mar 9, 2010, at 2:26 AM, Andrey Tarantsov wrote: >> - I mostly want enough git in the GitX interface that I can stop using >> the git command line for most uses. > > Same for me. I love command-line, but clicking "Push" after I commit would be > more fun. Getting some sort of a sane "pull" would be ever more fun — > currenty pulling is the biggest source of frustration I see when I try to > explain Git to someone. > > rebase -i is something I would be most happy to see in GitX. Actually I've > made a first step towards this, and find the area to be exciting enough to > continue to work on it as I have time. > >> - A lot of people have work on GitHub (Nathan Kinsinger, Morgan >> Schweers: I'm looking at you). How much of that work is ready to be >> integrated? > > I'm using my branch http://github.com/andreyvit/gitx/tree/commit-editing to > change prior commit messages from time to time. Needs better error handling > inside. Not sure if this should defer it from being included in the next > release. Maybe someone can find a bigger problem with that code upon review. > > Andrey. >
