Sounds good to me, I have been woring on a couple of new views for GitX. On Sep 10, 2010, at 11:25 , Michael Dippery wrote:
>> Thanks for the hint. However, this patch shows why we should integrate >> and release something soon (or else every new patch stands the chance of >> being pointless because already included): While this might be true for >> stable and for Andre Berg's branches, this is fixed in Nathan's >> experimental branch. > > Yeah, it's fixed in my fork as well [1]. > > I think this brings up a question I've had: What exactly is the status of > this project? I appreciate all the work pieter did on GitX, but it seems like > he's not terribly active on the project anymore? Is it time to re-organize > the project under new development leadership, set up a new "canonical" repo, > and get working on this? > > GPGMail development was similarly stagnant as a couple months ago, but a few > developers stepped up and refocused the project. They set up a main repo on > GitHub, granted a few devs write access, relaunched the webpage, and have > been moving the project along pretty well. Should we do something similar? > Set up a "gitx" organization on GitHub, push in the "latest" common repo, > give some devs write access and let them push their experimental changes and > whatnot into the repo? That way, we'd have a set of core developers and a > repo from which other collaborators could easily get changes. > > > ---- > Michael Dippery > [email protected] | www.monkey-robot.com > > > [1] > http://github.com/mdippery/gitx/commit/c1d89d6858290f630eab745faaa2c03d2ad6d6a8
