Systers Development Branch

Before You Sprint

• 426849 - The oldlist bug (oldval = oldval[0] listindex out of range) - In testing
• 414166 - definition of dynamic sublists needs to exist outside developer docmention
• 386133 - Image/Attachment filtering happens before conversation unsubscribe
• 314519 - List Archives constantly prompting for login
• 324406 - Message held when unsubscribing to a conversation without leaving subject line blank
• 406372 - errors in the archieves for dlists

Save the Systers Sign-up Essays

Problem: Right now application essays are only held until a member is approved or rejected.

Solution: Store the application essays along with additional member information in the database.

Skills: Some Python and Sql

I'd love to work on this (add your name):

• Lavanya, email address

Problem: Presently we manually generate testing checklists from a template whenever we release new code. This is very time-consuming and tedious. Additionally, as we add new features we need to add new tests to the template. Again very tedious to do this manually. Review the current testing process here: tests.

Solution: Design a small web-app that automatically generates new test checklists and allows the template to be easily updated.

Skills: You can write this in any language you like except C++, anything .NET, C or Lisp/Haskell something obscure that would be hard to manage. We'd prefer Python or PHP, but would also be willing to use Ruby if you'd be willing to help out with installation and maintenance documentation. Perl is probably a no-go as well – unless someone really, really, really wants to write the app in Perl and will make it exceptionally awesome.

I'd love to work on this (add your name):

• Jessica Stringham, jstringham@hmc.edu

Progress: See the project page below for progress.

• Checklist Web-App

• Creating Searchable Archives - Everyone knows how hard it is to search the default Mailman Archives. Let's start designing a solution!
• Ideas for a Systers Virtual Community Platform - How do we expand Systers beyond a Mailing List. What sort of technology would facilitate the most functionality and how will we build the platform?

• Upgrading to a new a version of Mailman is very difficult since the Systers customizations are not yet in MM upstream. What can we start working on to integrate Systers functionality with MM 3.0.

• Systers currently uses Dokuwiki and in the interim of our platform upgrade it would be nice to have a more attractive theme.

Skills: Some php, css and html - How to Create Dokuwiki Templates

Launchpad offers a lot of functionality for controlling and documenting the software release cycle. We need help with release management! Design and document a good release strategy that fully utilizes the power of distributed development.

• How to use irc - DONE - Thanks Jessie
• More notes on distributed development
• Quick Python tutorial
• How to make a screencast/podcast - DONE - Thanks Ann-Marie Horcher!!

Problem: Dokuwiki is good for fast and dirty documentation (hey at least now we have some documentation!), however we'd really like to have a robust wiki for Systers to use for collaboration. It would be great if the Mediawiki skin was branded for Systers – or maybe we have a couple skins for Systers to choose from.

Solution: Design a Mediawiki skin specifically for Systers. Skin development instructions may be found here: Manual:Skins

Skills: Some PHP, CSS, an interest in UI Design

I'd love to work on this (add your name):

• name, email address

Problem: The Systers FAQ really needs to be updated for readability and to reflect some changes in the community.

Solution: Let's work on rewriting the Systers FAQ!

Skills: Some html and CSS

I'd love to work on this (add your name):

• name, email address