There is a monthly Hcoop volunteer day where we get together on IRC and work on Hcoop tasks. A good place to start is the category Needs Work. Below there's some tasks that are not directly related to the wiki.

The next Hcoop volunteer day is (tentatively): March 9th

• It would be nice if the new website had a better member url and location directory. The member url directory / location map are generated from DaemonAdmin/Portal using a shell script. You'll need to either update the portal code that spits these out, or come up with another solution (they are easy database queries and could be done in most any language)

  • Bonus points for the first person to use an open street maps widget for the member location summary
  • We also need to make members aware of the url directory again

• Volunteeer to be a system admin

  • In particular, anyone who knows exim or dovecot could help us quite a bit

• Check out CategoryNeedsWork and revise/clean up wiki pages that have been neglected.

• Tag pages CategoryNeedsWork if they clearly need work

• We need someone with Windows 7 and/or Windows 8 to update the guide to mounting your afs directory since the process is different, and you have to use OpenAFS 1.7.x.

• Screenshots showing how to whitelist hcoop announcements on gmail would be helpful on MemberManual/GettingStarted/AccountCreated

• Mailing list moderators for -discuss, -help, and -sysadmin are needed (right now ClintonEbadi is doing all moderation, and not very regularly)

  • Workload is light: when you receive a moderation message either kill it or approve it. Can usually be done once per day or less, especially when multiple people are moderating the lists simultaneously.

• DomTool does not have command line help and instead refers users to the wiki docs. A basic overview of available commands for each tool would increase discoverability

  • It would be straightforward: modify domtool's src/main-FOO.sml drivers to spit out useful help on badArgs. Ideally help would be integrated with command processing (domtool just does a case over the command line arguments, a type for storing command line arguments would be nice). No real knowledge of domtool is needed, and you can test it without needing to install a virtual hcoop.

• DomTool could produce "human readable" type errors

  • E.g. "Expected type [Vhost], actual type [Vhost] {Foo}" should hint to the member they need to set the Foo domtool environment variable

• Someone should write a Thunderbird auto configuration file.

• We are using MeetBot running on Debian's servers to log our meeting minutes because RichardDarst added us. Since he is no longer with the coop, we should run our own copy of MeetBot since we have no guarantee Debian will continue to allow us to use their bot. MeetBot is a pretty simple Python IRC bot so effort for this is low.

  • Bonus points for implementing hcoop specific commands (for voting, roll call, etc.)

• Recreate the hcoop website logo as an svg (using LogoDiscussion sources) with layers etc. Changing "A web hosting cooperative" to "Internet Hosting Cooperative" would be nice.