PyCon sprint 2014: Difference between revisions

From OpenHatch wiki
Content added Content deleted
imported>Shauna
imported>Shauna
Line 10: Line 10:


* Improve the user experience in the volunteer opportunity finder
* Improve the user experience in the volunteer opportunity finder
** [Insert links to specific user experience bugs/enhancement requests on issue tracker.]
** [Insert links to specific user experience bugs/enhancement requests on issue tracker. If only if it were easy to find links on the issue tracker. See below.]

* Move issue tracker to Github
** Base goal: Come up with a plan for how to get issues from openhatch.org/bugs to a github issue tracker
*** [Insert specifics of how to come up with the plan.]
** Stretch goal: Implement plan


* Fix security issues with the OpenHatch site
* Fix security issues with the OpenHatch site


* Clean out issue tracker
* Clean out issue tracker
** Possible dependency: moving issues.
** Base goal: Go through tracker and label issues by what type of “cleaning” they need. Does a bug need to be verified? Does a patch need to be tested? Does the feature request need to be attached to a milestone?
** Base goal: Go through tracker and label issues by what type of “cleaning” they need. Does a bug need to be verified? Does a patch need to be tested? Does the feature request need to be attached to a milestone?
** Stretch goal: Use the labels as a guide to “clean” each issue. Verify bugs, test patches, etc.
** Stretch goal: Use the labels as a guide to “clean” each issue. Verify bugs, test patches, etc.

* Move issue tracker to Github
** Base goal: Come up with a plan for how to get issues from openhatch.org/bugs to a github issue tracker
*** [Insert specifics of how to come up with the plan.]
** Stretch goal: Implement plan


* Provide code review & merge some outstanding pull requests
* Provide code review & merge some outstanding pull requests

Revision as of 20:19, 13 April 2014

OpenHatch is an open source web app for helping people get involved in open source projects. We do that through web-based interactive tutorials called "training missions;" a browsing tool for bitesize bugs in open source projects called the "volunteer opportunity finder"; and an online mentor/mentee matching tool.

OpenHatch is written in Django and we welcome people of any level to contribute! We also need CSS and Javascript help.

Goal of the OpenHatch project

OpenHatch’s goal is to make the free software/open source community more welcoming to newcomers. To do this, we provide curricula and logistical support for running “Intro to Open Source” workshops, a website with open source tools, “training missions” and a volunteer opportunity finder, and several other projects in progress.

Goals for this sprint

  • Improve the user experience in the volunteer opportunity finder
    • [Insert links to specific user experience bugs/enhancement requests on issue tracker. If only if it were easy to find links on the issue tracker. See below.]
  • Move issue tracker to Github
    • Base goal: Come up with a plan for how to get issues from openhatch.org/bugs to a github issue tracker
      • [Insert specifics of how to come up with the plan.]
    • Stretch goal: Implement plan
  • Fix security issues with the OpenHatch site
  • Clean out issue tracker
    • Possible dependency: moving issues.
    • Base goal: Go through tracker and label issues by what type of “cleaning” they need. Does a bug need to be verified? Does a patch need to be tested? Does the feature request need to be attached to a milestone?
    • Stretch goal: Use the labels as a guide to “clean” each issue. Verify bugs, test patches, etc.
  • Provide code review & merge some outstanding pull requests
  • Improve our developer experience
    • Move the OpenHatch bug importers to scrapinghub
  • Set up a MediaGoblin instance? (If AL thinks that maintenance would be reasonable.)
  • Make a new training mission
    • Base goal: Pick a skill to create a new training mission around, and design what the mission will look like. Create a mock-up of the mission.
    • Stretch goal: Implement the mock-up, and user test it on volunteers from the event.

Project setup

http://openhatch.readthedocs.org/en/latest/getting_started/installation.html

How to find the community

Sprints will be in rooms 518A-C, 519A/B, 520A-F and 524A-C on the 5th level of the Convention Center. We'll be in one of those rooms, not sure which yet.

We'll also be using the #openhatch IRC channel. See http://openhatch.readthedocs.org/en/latest/getting_started/getting_started.html for info about that.

We'll also be using the http://lists.openhatch.org/mailman/listinfo/devel email list. Consider joining.

We'll also be using https://openhatch.org/bugs/ . To use that site, you need to have an openhatch.org account. (You can make one easily.)

We'll also be using GitHub for some things -- feel free to make an account there.