0.11.10

This is the list of things I'd like to see in the October OpenHatch release.

There are two sections: The basically can't live without it items are the ones that are most crucial that we ship during October. The non-urgent ones would be amazing, but if we don't get to them in October, we'll deal.

As of 2011-10-03, there are 0 bugs more stale than two days. This is good news.

We need to watch it day by day to make sure that bugs successfully refresh themselves. If they don't, then I (Asheesh) can identify the problems and fix them.

Owner: Asheesh

Ship a redesigned front page (even if it's not on the main site)[edit]

We keep meaning to clean up the front page; we set goals like, "Integrate events with the front page."

Let's step back a moment and make a list of the things we want people to be able to find when they hit the front page. Once we have that list, we can go through the front page and make sure those items are easy to find.

Owners: Karen + Asheesh

What the heck is this OpenHatch thing about, anyway? Why are people who are looking at our website here?

Provide a list of upcoming events on the front page of OpenHatch[edit]

OpenHatch is actively pursuing events. I think we should:

Get upcoming events data out of events.oh.o

Create a module on the front page that lists upcoming events

Link to information from the front page about why events are exciting

Owner: Asheesh, unless someone else wants it.

Skills needed: Django templates, plus CSS and a willingness to modify our templates and to accept feedback. The exact styling will likely be dependent on the redesign, but it's better that someone gets the functionality working in the old design (which we can then reskin as needed).

Recently on the Events mailing list, Asheesh said he wanted to run more on-campus events to teach students how to get involved with free software. In addition, he said he'd organize an online version of the event before the on-campus ones start.

Let's publish a timeline of when this will happen. That way, we can "show our work" and people can easy see the planned timeline.

A new, under-publicized feature of the project pages (e.g. https://openhatch.org/+projects/OpenHatch ) is the "buildhelper," a set of steps a new contributor would take that sets up a usable build environment.

Right now, we have a working (and simple) frontend and backend for the buildhelper. However, there is no way to edit a buildhelper document except from the Django admin interface.

I think we should:

Write code that converts the models to a text-based representation that looks like MediaWiki markup

Provide a textarea that lets people edit this MediaWiki markup

On save, render that markup into HTML, and then parse the HTML into buildhelper step objects for the database

Owner: ?

Initial implementation of handler for people who've clicked "I want to help"[edit]

Right now, when visitors to OpenHatch click a button on a project page indicating they want to help, we add them to a list. We have repeatedly received feedback that project maintainers want the ability to manage this as a queue.

(Recently, we've used the short-hand "IWH handler" to describe this -- "I Want to Help" handler.)