Adium needs your help

[Chris Forsythe]

Folks,

Summary

Adium needs your help. If Adium is to continue as a project it's going to need some active developers again. The transition to GitHub last year hopefully makes this a bit easier for people to get re-engaged in the project.

Details

As of right now there is enough to be done where it will take a few people to get things into a shippable state. If you have the ability to help or know someone who would be interested in doing so please either join the irc channel, or make a comment on an issue you will work on.

Asher is in the process of writing up issues which apply to 1.6 and a subsequent 1.7 release.

1.6 - https://github.com/adium/adium/milestone/1
1.7 - https://github.com/adium/adium/milestone/2

Any other issues are being marked as part of the Future Stuff milestone currently. Priority is with the two named release milestones listed above.

Thank you for your time.
Chris

[Robert Vehse]

Hi,

> […] Asher is in the process of writing up issues which apply to 1.6 and a subsequent 1.7 release.

Adium Trac’s list of tickets scheduled for the 1.6 milestone covered pretty much all known issues. Do we have a Trac backup we could look at? Jordan?

Cheers,
Robbie

[Jordan]

We do have a backup from cPanel with these two files:

adium_adiumnewtrac.tar

adium_adiumtrac.tar

Located at /var/www/vhosts/adium.im/trac_db_backups/psql

Postgres is not on the current VPS and largely probably won't be needed -- does anyone have a postgres installation that adium_adiumnewtrac.tar could be imported into to go diving?

Another perspective: there's likely a *lot* to wade through in that Trac database dump... perhaps starting fresh isn't a bad idea to clear everyone's heads ;)

Jordan