On 12/09/10 09:46, Josh Bleecher Snyder wrote:
> I'd be happy to help. Not sure where I'd be the most use (what is the
> list of tasks you have in mind?), but I could e.g. systematically
> close out bugs / feature requests against a selected branch.

Hi Josh,

hopefully we will have a preview in the next few days (or even today,
depends on Nathan ;). With this specific point in development we can try
to reproduce all the bugs in Lighthouse (which is what I've been doing
all day, always referring to GitX 0.8 if it were indeed be based on
Nathan's branch), and assign them to the 0.8 milestone.

If you want privileges on the Issue tracker just contact me.

Furthermore what I would really appreciate is general consolidation of
issues and documentation. We should try to limit ourselves to
Lighthouse, that means closing / transfering tickets from the GitHub
trackers and the annoying GitHub-wiki. Anything redudant should be
deleted as quickly as possible ;). If you're running forks of GitX on
Github make sure to only publish the branches that actually contain
changes. I have just one branch 'bugfixes' on GitHub, since pushing out
Pieter's (or Nathan's) branches to my repo would have no benefit and
only complicate things.

If you're a fan of that you could also try to update the GitX
documentation with screenshots from the soon-to-be-released preview. The
source-code for the GitX-website is in the Gitx repo in the subdir
'Site'. There is noone working on that right now, so don't be afraid
that your commits could clash with something else.

That obviously goes for everyone around. Thankfully we have excellent
Cocoa-programmers like Pieter, Nathan, Dave (etc.), but a fair amount of
grunt-work is needed as well ;)

Greetings,
Jojo

-- 
Johannes Gilger <[email protected]>
http://heipei.net
GPG-Key: 0xD47A7FFC
GPG-Fingerprint: 5441 D425 6D4A BD33 B580  618C 3CDC C4D0 D47A 7FFC

Reply via email to