Jump to: navigation, search

Difference between revisions of "Internship ideas"

m (Text replace - "__NOTOC__" to "")
(Outreach Program for Women Ideas List)
Line 5: Line 5:
 
The GNOME Foundation provides an outreach program for women. You can learn more here: https://live.gnome.org/GnomeWomen/FOSSOutreachProgram.  
 
The GNOME Foundation provides an outreach program for women. You can learn more here: https://live.gnome.org/GnomeWomen/FOSSOutreachProgram.  
  
OpenStack would like to participate as a project and has identified some mentors and three sponsorships so far, from the Foundation, from Rackspace, and from Red Hat. We also need to identify projects that would be appropriate for participants in this program. This page should collect the ideas for applicants to work on.  
+
OpenStack would like to participate as a project again. We have identified some mentors and have sponsorship from the Foundation to participate in this program. This page should collect the ideas for applicants to work on.  
  
 
They definitely emphasize that applicants may not have ever worked on FLOSS before. There are several stages to the program, but the first stage is to mentor during the application process itself. Joining mailing lists, IRC, understanding the channels of communication are good first steps. Logging bugs and fixing bugs are also good ideas.  
 
They definitely emphasize that applicants may not have ever worked on FLOSS before. There are several stages to the program, but the first stage is to mentor during the application process itself. Joining mailing lists, IRC, understanding the channels of communication are good first steps. Logging bugs and fixing bugs are also good ideas.  

Revision as of 02:23, 19 April 2013

Outreach Program for Women Ideas List

The GNOME Foundation provides an outreach program for women. You can learn more here: https://live.gnome.org/GnomeWomen/FOSSOutreachProgram.

OpenStack would like to participate as a project again. We have identified some mentors and have sponsorship from the Foundation to participate in this program. This page should collect the ideas for applicants to work on.

They definitely emphasize that applicants may not have ever worked on FLOSS before. There are several stages to the program, but the first stage is to mentor during the application process itself. Joining mailing lists, IRC, understanding the channels of communication are good first steps. Logging bugs and fixing bugs are also good ideas.

Interns are expected to spend 40 hours a week on the project.

So, feel free to list ideas here:

Documentation

API Samples

Description: Link Compute API samples so they are published to http://api.openstack.org/api-reference.html. The automation for pulling samples from one repository to another will be done by another community member, but the linking of the incoming samples is needed. This is a code-like task because you'll need to use Oxygen and edit WADLs and be able to read JSON and XML files with some understanding (guidance will be offered throughout of course!).

Blueprint (if applicable): https://blueprints.launchpad.net/openstack-manuals/+spec/api-samples-to-api-site (annegentle)

Expected results: Patchsets submitted for review that build output to the api.openstack.org site, reviewed by community members.

Knowledge Prerequisites: Understanding of XML, HTML, build automation, APIs Nice-to-have knowledge: REST API, JSON, programming, Git

Mentor: Anne Gentle

API Try-it-out Website

Description: Try it out web forms on http://api.openstack.org/api-reference.html. To make it easier for users to understand the REST API calls, we want to use a javascript library called jstack to make calls to the TryStack cloud through a web interface. There are lots of tasks within the project: web design, forms design, javascript, CSS, HTML, possibly XSLT.

Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/api-try-it-out

Expected results: Design for a web form that would enable jstack to integrate into a web page. Bonus results: A working proof-of-concept web page that uses jstack to make calls to the TryStack cloud and returns results to the web page.

Knowledge Prerequisites: Understanding of XML, HTML, build automation, APIs, javascript Nice-to-have knowledge: REST API, JSON, programming, Git

Mentor: Anne Gentle

Documentation Updating and Writing

Description: Documentation bug fixes and cleanup. Documentation for OpenStack is a code-like task because you'll need to use Github and the Gerrit review process to submit changes. A list of the bugs for admin docs built to docs.openstack.org can be found at http://bugs.launchpad.net/openstack-manuals to get an idea of how technical some of these bugs are. A list of the bugs for API docs can be found at http://bugs.launchpad.net/openstack-api-site.

Expected results: Patchsets submitted for review that build output to the api.openstack.org site, reviewed by community members.

Knowledge Prerequisites: Understanding of XML, HTML, build automation Nice-to-have knowledge: cloud operations, programming, Git

Mentor: Anne Gentle

Community

  • Build a supply-chain management system to distribute merchandising to OpenStack User Groups around the world [reed on IRC / stefano at openstack org] Details
  • Write a manual on how to start and manage user groups [reed on IRC / stefano at openstack org] Details
  • Write a mobile app for tablets to create a paperless kiosk for marketing collateral at events [reed on IRC / stefano at openstack org]

Coding

Adding features to Python Clients of Various OpenStack Projects

Description: Adding features to existing python clients for various projects of OpenStack, for example glance client(https://launchpad.net/python-glanceclient), nova client (https://launchpad.net/python-novaclient), etc. It includes finding bugs and fixing them or implementing blue prints. This will help gain an overview of various parts of OpenStack project and improve the clients.

Expected results: Patchsets submitted for review, reviewed by community members.

Knowledge Prerequisites: programming knowledge

Nice-to-have knowledge: cloud operations, python, Git

Mentor: Iccha Sethi

Consistent Transaction ID across all projects

Description: To ensure that a consistent transaction id is set for a given user requested operation and is carried forward towards all the other projects where the request might have been made. This helps tie into together requests and transaction and better analyze what went wrong where. For example, a single create server request may cause multiple requests to glance(image service), and depending on the issue, it would be great to both tie those together or investigate separately.

Listserv discussion: https://lists.launchpad.net/openstack/msg13084.html

Expected results: Patchsets submitted for review, reviewed by community members.

Knowledge Prerequisites: programming knowledge

Nice-to-have knowledge: cloud operations, python, Git

Mentor: Iccha Sethi