User Tools

Site Tools


Systers OSD 2014 Projects

Our Systers has a long history with open source day at GHC and in fact, was instrumental in starting OSD at GHC in Atlanta GHC 2010. It is tradition that we participate in GHC OSD and this year is no exception. We will have several projects for our participants.

Skills Needed

No worries, we're here to help you get exposed to open source, technologies and a great community of women in computing. You can have NO programming experience to advance programming experience. We have something for everyone.

In fact, we need participants who want to help us define/design/code/etc …

  • user interface (also CSS and templates)
  • Database
  • Architects
  • Developers/Coders
  • Business Analysts
  • Functional Requirements
  • Testers/Quality Assurance
  • Configuration Managers (GitHub)
  • And everything else


Systers Peace Corps


Note: We do not have mentors available, but if you have experience in mobile development for Android and iOS, you are welcome to work on this project during OSD.

Mobile App Control Center

Language Translation


Systers Projects

We do have 2 other open source projects where 1 is in beta. If you would like to work on one of these projects, that would be great. There won't be anyone from the project team, but Her Systers Keeper will be available to give some background information.

Portal project is in beta right now and currently utilized by our community leaders. Be sure to visit the repo on GitHub for more information.

Volunteer Management System (VMS) has also made great progress. One of our GSoC (Google Summer of Code) students has taken lead and continuously working on the project this semester as part of one of her class.

OSD Development Process

As you are developing your code, we want you to do

  1. Coding
  2. Unit Testing
  3. Documentation

The following sections will help

1.1. Coding

Be sure you are documenting your code. Usual name, GitHub username, date is needed, but simple additional information is always useful. For example, if you defining a new function, what does function do, what are the parameters, what does it return? Another example, if you are using existing module from a framework, which one, and how you are referencing that module. Should not add too much time, but descriptive enough.

# This is an example of commenting your code.
# Date: 8 October 2014
# Contributer: @github-username or email address or First name Initial last name (Rose R.).
# Description: This does what.

e.g. Online programming line #This is also a comment.

Each project has it's own VM that you can download and install. This prevents anyone stepping on anyone's code. Please read each project's README file on Systers GitHub Repo.

Systers repos »

1.2 GitHub

1.2.1 Be sure you're in Systers repo

Because we are working on Peace Corps projects, Systers manage development and code reviews before pushing to Peace Corps repo.

Systers repos »

You can review our code review process here »

1.2.2 Create New Branch

For our new open source projects, we use GitHub for our code repository. Before checking in your work, please create a branch on your repository named “GHC14”. This will help admins later on to review your code and help in configuration management.

If you are new to GitHub, please consider the following tutorials. Don't worry, there will be folks who are familiar with GitHub that will be able to help you.

1.3 Documentation

Before you wrap up the day at GHC OSD, we would really appreciate it if you would document your work and check it in to each repo you worked on. We hope that you will want to continue the work you began at OSD, but we do understand this is not always the case. However, development must continue so documentation is always critical for other developers to jump right in particularly in open source environments.

Aspects your documentation should contain.
[1] Your approach to your design. (e.g. why you are using a certain package/module?)
[2] Touch points (If your application interacts with another application or framework, it's necessary to document these requirements. e.g. API specifications, etc.)
[3] Derived types and function, flags/error definition, database models

Keep it basic but informative. We understand the bulk of your work is in the coding, but Documentation is critical to maintain project momentum.

Systers OSD Schedule

Below is an tentative schedule and there is some flexibility with the times. The start and end times are strict however.

Time Activity
12:30pm Begin with General announcements
1:00pm Systers announcements
1:10pm Ensure your environment is setup
1:20pm Q&A about your projects
1:30pm Coding
5:30pm Wrapup Coding and complete documentation
6:00pm General announcements wrap up
6:30pm End

OSD Assignments

After reviewing the projects above, please sign up for one of the projects you would like to work on during OSD on Wednesday. Then, definitely install your VM (for web projects only).

Name GitHub Username Project
Rose Robinson @rosariorobinson All projects
Jamie Yu Language Translation

If you don't have a GitHub username account, don't worry, you can still work on our projects. If you do have a GitHub account, please add link to your GitHub page.

See you at GHC!

ghc14systers.txt · Last modified: 2014/10/08 19:14 by rosariorobinson