This year I helped the Gentoo GSoC project as a mentor for the first time! I mentored Jauhien Piatlicki, that worked on the g-sorcery project, that is a framework for automated ebuild generators. It is meant to replace g-octave and some of the other Gentoo automated ebuild generators in the future.
For those who don't know, Google Summer of Code is a Google program that pays a student to work during 3 months on an open source project.
I have been using Scrum at work for some time already, and asked Jauhien about trying to use it in our project. We agreed on using it wherever it made sense for our workflow. In other words, we adapted Scrum to our workflow, instead of adapt our workflow to Scrum. That's because none of us was a Scrum expert, and because we needed to follow Gentoo/Google guidelines and timeline during all the project, making it hard to apply some aspects of the Scrum methodologies.
We had sprints of 2 weeks, starting on monday, after a quick planning on IRC. We had a private IRC channel at Freenode, where we discussed stuff, had meetings, etc.
Warning: This post relies on unreleased blohg features. You will need to install blohg from the Mercurial repository or use the live ebuild (=www-apps/blohg-9999), if you are a Gentoo user. Please ignore this warning after blohg-1.0 release.
Tumblelogs are old stuff, but services like Tumblr popularized them a lot recently. Thumblelogs are a quick and simple way to share random content with readers. They can be used to share a link, a photo, a video, a quote, a chat log, etc.
blohg is a good blogging engine, we know, but what about tumblelogs?!
You can already share videos from Youtube and Vimeo, and can share most of the other stuff manually, but it is boring, and diverges from the main objective of the tumblelogs: simplicity.
After having lots of problems with people that can't use g-octave properly, sometimes because they don't seems to be able to read documentation, elog messages and/or just ask, and after a suggestion of Sebastien Fabbro (bicatali), I write down some simple scripts to update the g-octave package database and an overlay using g-octave and a cronjob.
I built a virtual machine on my own server and set up a weekly cronjob, that will hopefully keep the packages up-to-date.
The overlay is available on Github:
To install it, follow the instrunctions available on the README file. The overlay is available on layman, named octave.
Packages with unresolvable dependencies, e.g. packages with dependencies unavailable on gentoo-x86, aren't available in the overlay. If you find some package that is supposed to work and isn't available on the overlay please open an issue on Github, and I'll take a look ASAP.
As a bonus, g-octave code itself was moved to Github:
Feel free to submit pull requests if you think that something is broken and you know how to fix it.
And as another bonus, the g-octave website (http://g-octave.org/) is now running on the Read the Docs service, that is way more reliable than my own server. This should avoid the recent documentation downtimes.
Create a homepage and documentation for a project is a boring task. I have a few projects that were not released yet due to lack of time and motivation to create a simple webpage and write down some Sphinx-based documentation.
To fix this issue I did a quick hack based on my favorite pieces of software: Flask, docutils and Mercurial. It is a single file web application that creates homepages automatically for my projects, using data gathered from my Mercurial repositories. It uses the tags, the README file, and a few variables declared on the repository's .hgrc file to build an interesting homepage for each project. I just need to improve my READMEs! :)
It works similarly to the PyPI Package Index, but accepts any project hosted on a Mercurial repository, including my non-Python and Gentoo-only projects.
My instance of the application lives here:
The application is highly tied to my workflow, e.g. the way I handle tags and the directory structure of my repositories on my server, but the code is available in a Mercurial repository:
Most of my projects aren't listed yet, and I'll start enabling them as soon as I fix their READMEs.
- ← Newer
- Older →