URGENT REQUEST, Sahana Disaster Management System, Haiti Earthquake

Posted November 30, 2011 by tshrinivasan
Categories: python

Tags: , ,

Job Description:This is an urgent call for experienced Python programmers to help in the Sahana Disaster Management System immediately – knowledge of Web2Py platform would be best. The Sahana Disaster Management System is used to coordinate relief efforts. Please recruit any available programmers for the Haiti effort as quickly as possible and have them contact me immediately so that I can put them in touch with the correct people. Thank you kindly and I do hope that we can quickly identify some contributors for this monumental effort – they are needed ASAP.

http://sahanapy.org/ is the developer site and the demo is http://demo.sahanapy.org/


mincemeat.py need contribution

Posted November 30, 2011 by tshrinivasan
Categories: python

Tags: , , ,



mincemeat.py is a Python implementation of the MapReduce distributed computing framework.

mincemeat.py is:

  • Lightweight – All of the code is contained in a single Python file (currently weighing in at <13kB) that depends only on the Python Standard Library. Any computer with Python and mincemeat.py can be a part of your cluster.
  • Fault tolerant – Workers (clients) can join and leave the cluster at any time without affecting the entire process. (Master checkpointing coming in future versions)
  • Secure – mincemeat.py authenticates both ends of every connection, ensuring that only authorized code is executed. (TLS support coming in future versions)
  • Open source – mincemeat.py is distributed under the MIT License, and consequently is free for all use, including commercial, personal, and academic, and can be modified and redistributed without restriction.


  • Just mincemeat.py (v 0.1.2)
  • The full 0.1.2 release (includes documentation and examples)
  • Clone the git repository
    git clone http://mincemeatpy.com/git/mincemeatpy.git



The following features will be included in mincemeat.py by version 1.0:

  • On disk storage of worker data
  • Worker-to-worker transfer of the intermediate data
  • Master checkpointing
  • TLS


Get in touch with me at michaelfairley @ gmail.com.

Patches are welcome, especially for the roadmapped features. It’s best to contact me to make sure that your potential work fits the goals of the project and has not already been started.


Source: http://remembersaurus.com/mincemeatpy/

Ubuntu IRC Bots Junior Tasks

Posted April 26, 2010 by tshrinivasan
Categories: python, ubuntu

The Ubuntu IRC Bots team is looking for volunteers who know python, or are interested in learning python to help out with development of the Ubuntu IRC bots. They recently created a tag called Junior Tasks for people who are interested in getting started with the Ubuntu IRC Bots team. If you are interested in helping out, join in at #ubuntu-bots-devel on freenode and visit the ubuntu-bots project on launchpad. We look forward to seeing you there!

Fedora Graphics Test Week : This Week

Posted April 13, 2010 by tshrinivasan
Categories: fedora

The Fedora project announces that this week is Graphics Test Week.

This is the highlight of the Fedora 13 Test Day cycle, with Test Days
for NVIDIA, ATI/AMD and Intel graphics all falling this week. Tuesday
13th is NVIDIA Test Day [1], Wednesday April 14th is ATI/AMD Test Day
[2], and Thursday April 15th is Intel graphics Test Day [3].

Although these are Fedora events, the results will ultimately benefit
almost all distributions: Fedora tends to use the latest versions of
graphics-related components and sends all its changes upstream, so the
fixes that result from these events will end up in all major
distributions. Even if you’re not a Fedora user, you can help Linux as
a whole by contributing your test results.

The testing can be done using a live image, so there’s no need to
install Fedora onto your system to contribute to the testing: just
download a live image, write it to a CD or USB stick, boot it, and run
through the tests. Comprehensive test instructions are available on
the Wiki pages, and you
enter your results into a table on the Wiki page; there’s no need to
have a Fedora wiki account to do this.

QA team members and developers will be available on the IRC channels
throughout each event to help with testing and triage, and to work on
some of the problems immediately. The more results we get and the more
bugs we expose, the better it is for everyone, so if you have time,
please check out the Wiki pages and join the IRC channel –
#fedora-test-day on the Freenode network – to help out!
You can use WebIRC [4] if you’re not a regular IRC user – just click
that link and you’re in the chat.

[1] https://fedoraproject.org/wiki/Test_Day:2010-04-13_Nouveau
[2] https://fedoraproject.org/wiki/Test_Day:2010-04-14_Radeon
[3] https://fedoraproject.org/wiki/Test_Day:2010-04-15_Intel
[4] http://webchat.freenode.net/?channels=fedora-test-day

PyJunior: Call For Documentation Help!

Posted April 13, 2010 by tshrinivasan
Categories: python, ubuntu

Just a quick note: the PyJunior code is up on Launchpad. Please remember: I wrote this in about two hours and haven’t had any time to clean it up. So, expect warts and all. :-)

The Open Sourcerer pointed me at Snake Wrangling for Kids as a great kid-friendly guide for learning Python. My dream now is that when a kid clicks the big Help button in PyJunior, that the book pops up in native GNOME help format. Problem is: I have absolutely no idea how to convert Snake Wrangling for Kids (which is available in LaTeX and PDF format) into this help format, and don’t really have any time to contribute to this either.

So, I am looking for help. PyJunior provides a simple and effective of way of playing with Python for kids, but we really need the documentation to make this story rock. Is there anyone out there who would like to work on this and make clicking that Help button a fantastic experience for kids interested in learning programming? I really hope so: this could be a wonderful learning tool for ankle-biters everywhere. :-)

If you are interested in helping, do let me know in the comments on this blog entry and we can talk more. If you just want to crack on and make the docs love happen, do feel free to go ahead and submit a merge proposal when you have something.

To do those who help, thanks so much in advance! :-)


The Ubuntu Manual Project needs you!

Posted March 22, 2010 by tshrinivasan
Categories: ubuntu

We’ll do all the hard work going through your reports and triaging them, then submitting them as bugs in Launchpad and subsequently fixing them before the 31st. We want to make it easy for you lads and ladettes to get involved and have your say, because our project cares about community input and well, let’s be honest. We really like you guys.
All you have to do is download the latest revision of the manual by clicking this button:

Then you’ll need to read through the manual and look for:

  • Spelling and grammar mistakes
  • Factual errors
  • Missing references
  • Formatting errors
  • Sentences that don’t make sense
  • Inconsistencies in wording
  • Somewhere where you think a screenshot is needed and there isn’t a placeholder already
Start at a random place in the manual and work backwards or forwards. We don’t want everyone starting at the prologue and getting a tonne of bugs about the prologue but none for Chapter 9, for example.

Each time you find any of the above, jump on over to http://ubuntu-manual.org/?bugs and fill out the form. It’s as easy as that!

You get to have a small input in the final product, and we get to make sure our manual is super high quality and error-free!

Oh and please remember, this is still the alpha version of the manual!

Check us out on these exciting social sites:

Nominate your favorite Ubuntu Server Papercuts

Posted March 22, 2010 by tshrinivasan
Categories: ubuntu

An Ubuntu Server LTS release stays around for 5 years, so during the
development cycle there is an increased focus in QA, bugfixing and
stability. During Lucid UDS in Dallas, we discussed of various ways of
translating that effort into clear actions. One of those discussions was
geared towards improving the Ubuntu Server user (sysadmin) experience:
we could focus on fixing lots of minor annoyances, low-hanging-fruit
bugs that traditionally get less attention than others. On the footsteps
of the excellent One hundred papercuts project (from the User experience
team), this project was named Server papercuts.

This project is led by the Ubuntu Server community, for the Ubuntu
Server community. We discussed the implementation details during our
weekly IRC meetings, a specific Launchpad project was created, together
with a team to triage the candidates (with a cool badge).

Now it’s time to nominate your personal pet bug, your favorite minor
annoyance, your preferred PITA ! Here is the process to follow:

1. If the papercut isn’t already filed as an Ubuntu bug in Launchpad,
file a bug against the affected Ubuntu package
2. Look up the bug you want to nominate as a Server papercut, then click
on “Also affects project”
3. Click “Choose another project” and type in “server-papercuts”, click
4. Click on “Add to Bug report”

That’s it ! Your bug will now show up on the Server papercuts buglist
and we’ll Confirm or Invalid-ate it soon, when we start getting a good list.

Here are a few guidelines on what makes a good Server papercut:

* Bug affects a server package
* Bug has an obvious and easy fix
* Bug makes the life of the sysadmin more miserable

Here are a few guidelines on what doesn’t make a good Server papercut:

* New features
* Large-scale improvements that affect multiple packages
* Your solution is likely to result in a new papercut for someone else

For more details, complete acceptation criteria is described in the
project spec. https://wiki.ubuntu.com/ServerPapercutsSpec