On 10/09/10 14:25, Michael Dippery wrote: > 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?
Hi Michael, thanks for your mail. Having been inactive the last few months as well, I started looking at GitX again a few days ago. Right now the project is completely stalled: No commits (in the official repo), no responses to the issues on Lighthouse, no ML-traffic here. The worst part in my opinion is that there now are a lot of forks on GitHub, some carrying far-reaching branches with quite a lot of good features, which are a nightmare to reintegrate all at the same time. I know, I tried to combine branches from Nathan and Andre Berg plus some private patches today. So, here is what I personally think would be the best jump-start for GitX (correct me if you disagree): - Find a consensus about an OK-branch of one of the developers (I'd prefer Nathans 'experimental' branch) - Fix the worst bugs, if any. Accept a few bugs in order to release fast and _not_ get into stall-mode again. - Release as fast as possible and get everyone to (re)base their patches on this new master. - _After_ the release: Close invalid bug-reports, try to solve open bugs, bring documentation up to speed, try to reach people with promising branches on GitHub. The part about releasing something ASAP is the most important one imho. It enables people who don't work on core-features (like me) to reply to bug-reports with definitve statements and try to fix bugs without having to worry which branch will eventually get nominated. I don't think Pieter would mind if this moved forward, even if someone else took charge. The only technical problem at the moment is that a new release of GitX would have to be signed using Pieter's private key in order to be auto-updatable from the current stable GitX, which is what most people are probably running. Or we could branch of to a different website, release something like 0.8 cold and use Sparke for the new website in the future. Greetings, Jojo -- Johannes Gilger <[email protected]> http://heipei.net GPG-Key: 0xD47A7FFC GPG-Fingerprint: 5441 D425 6D4A BD33 B580 618C 3CDC C4D0 D47A 7FFC
