> 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.
A giant +1 from me on getting this going again. I'd second Nathan's branch as an excellent choice. > 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. 100%. I'm in the same boat. > 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. I think we should do whatever has the lowest chance of blocking forward progress, and from what I've heard, that sounds like a cold release. Cheers, Josh
