[OH-Dev] Ideas for new training missions

[Shauna Gordon-McKeon]

I'm enthusiastic about this.  Asheesh and I were talking about the training
missions earlier today. There are a couple of other missions I want to
make, and I think Cindy was interested in working on the IRC mission.  The
major obstacle is that we don't have a set process for making new missions
- we're in limbo between the old process, which uses Django, and the new
process, using Oppia.

Maybe it makes sense to have a training mission sprint - a virtual get
together on a weeknight or weekend day?


On Sat, Jun 28, 2014 at 11:39 AM, Eeshan Garg <jerryguitarist at gmail.com>
wrote:

> Hi everyone!
>
> I have some ideas for new training missions that I would like to get some
> feedback on. I noticed that a large part of projects listed on OpenHatch
> are Python projects. I think it would be cool to have a section on the
> training missions page titled "Python development tools" with the following
> or similar training missions:
>
> A virtualenv and virtualenvwrapper mission that describes the purpose of
> using isolated Python environments and the basics of how to work with them.
>
> A pip mission that describes how to install and remove packages using the
> pip package management system.
>
> These ideas interested me because I personally would have found it helpful
> if OpenHatch had training missions for the above mentioned tools at the
> time when I got started with these tools.
>
> I would really appreciate it if someone could give me some feedback and
> guidance on whether these ideas are good or not. And also, if you think
> they are good, I would love to work on them. :)
>
> Thanks & regards,
> Eeshan Garg
> <https://github.com/eeshangarg>
> <https://twitter.com/eeshangarg>
>
>
>
> _______________________________________________
> Devel mailing list
> Devel at lists.openhatch.org
> http://lists.openhatch.org/mailman/listinfo/devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/devel/attachments/20140701/eec9a797/attachment.html>