Worksheets and Accomplishment

As I mentioned in my previous blog post: “Questhub, quests and CPAN”, sense of accomplishment is a very fulfilling feeling. Gamification is a technique, which can be used to obtain that particularly feeling, but often play on other psychological aspects of the human mind.

I am often very satisfied, with the sense of connecting the dots or clearing the table. Therefor I mostly identify everything as tasks and organize tasks into releases or work packages, so when everything is ticked off I am one happy camper.

Tasks are like the key component. The key concept is that tasks should be viewed as either closed or open, not half-done or similar. Clusters of tasks as releases or work packages can of course be half-done, but every task should be easily identifiable, break down to sub-tasks if this is not possible.

Tools like Best Practicals Request Tracker and Atlassians Jira are very interesting to me, because they often support the process and workflow I use and not only for professional work, but also for hobby projects were picking up work can sometimes be with somewhat extended intervals and these tools, which are sort of advanced TODO files let me organize and manipulate tasks easily and I can easily identify where I am and where I want to go, even though projects have laid dormant for some time.

Since some issues I need to address are spread across several CPAN distributions, Meaning they will influence several different software packages and therefor require inclusion in several road maps and release plans. Here I use a very nifty feature in Jira and Confluence, the two products from Atlassian.

By tagging the issues with a special tag I can create a worksheet with all of the tasks cross, releases and distributions, so I then can create sort of a work package.

First time I did this was for an issue with the best practice of Makefile generation for Module::Build. I had to change a lot of distribution build files for a lot of projects. So I simply created all the tasks in the different projects with the same tag to let a Confluence report provide me with an overview.

This technique could again be used when I could see that almost all of my Changes files where either missing or malformed according to the proposed standard.

So I created a new tag and a Confluence report. The report gave me a quick overview of the tasks related to the quest I had created at Questhub.

Questhub and it’s quests are also a magnificent combination of gamification and task organization.

The report visualized a problem with my quest. I have planned to do 20 releases, but the overview visualized that I have 18 distributions under version control in Jira and one on SourceForge.

The problem is simply because one of the issues is for a distribution, which is no longer being maintained. It changed name and implementation from: Bundle::JONASBN to Task::BeLike::JONASBN, so I might have to make a rogue release using a branch from an old release under the early name or alternatively via GitPAN.

It seems that to every issue there is a solution, so now I just need to get on with the tasks at hand.

Worksheets and Accomplishment

Questhub, quests and CPAN

I fell over this blog post “Make me do some work, via Questhub!” by Neil Bowers via Twitter on some quests he had undertaken using Questhub.

The idea of Questhub is quite fun and summertime projects are always fun (see my previous post), IMHO the Summer of Code concept existed long before Google branded it.

Neil Bowers have set up a quest to get 1% of CPAN distributions to conform with a certain layout for Changes files, described as the CPAN::Changes::Spec and Brian Cassidy has implemented a service which check changes files named CPAN::Changes Kwalitee service.

Anyway I poked around the service and found out that my CPAN distributions apparently do not do quite well. Out of 31 distributions I have 2 passes and 29 fails (overall 6% success). Gamification is always good and sense of accomplishment is always very fulfilling, so I decided to play.

The 29 failing distributions are:

  • Bundle-JONASBN 0.05
  • Business-DK-CPR 0.08
  • Business-DK-CVR 0.06
  • Business-DK-FI 0.04
  • Business-DK-PO 0.05
  • Business-DK-Phonenumber 0.05
  • Business-DK-Postalcode 0.05
  • Business-OnlinePayment-CashCow 0.09
  • Date-Holidays 0.15
  • Date-Holidays-Abstract 0.05
  • Date-Holidays-Super 0.03
  • Date-Pregnancy 0.03
  • Games-Bingo 0.15
  • Games-Bingo-Bot 0.01
  • Games-Bingo-Print 0.04
  • Module-Build-Bundle 0.11
  • Module-Info-File 0.11
  • Perl-Critic-Policy-logicLAB-ProhibitShellDispatch 0.01
  • Perl-Critic-Policy-logicLAB-ProhibitUseLib 0.01
  • Perl-Critic-Policy-logicLAB-RequireSheBang 0.03
  • Perl-Critic-Policy-logicLAB-RequireVersionFormat 0.03
  • Perl-Critic-logicLAB 0.05
  • Task-BeLike-JONASBN 1.04
  • Task-Jenkins 0.01
  • Test-Timer 0.05
  • WWW-DanDomain 0.05
  • WWW-Nike-NikePlus-Public 0.01
  • Workflow 1.38
  • XML-Conf 0.04

Of all of these distributions the most should be fixable quite easily, the others are part of another summer project of migration version control system, before I can move on with these. These are the ones, which I will have to ignore for now.

  • Date-Holidays 0.15
  • Date-Holidays-Abstract 0.05
  • Date-Holidays-Super 0.03
  • Date-Pregnancy 0.03
  • Games-Bingo 0.15
  • Games-Bingo-Bot 0.01
  • Games-Bingo-Print 0.04
  • Module-Info-File 0.11
  • XML-Conf 0.04

So out of 29 fails I can address 20 imminently.

The two passes are modules I currently do not pay much attention to, but I will have a look at their Changes files just for understanding why they pass.

  • Module-Template-Setup 0.03
  • Tie-Tools 1.06

I have created an account with Questhub and I am setting up a quest to get my 6% to as close to 100% as I possibly can by addressing issues with 20 of the 29 distributions.

Have fun,

jonasbn

Questhub, quests and CPAN

Summer releases: Workflow 1.36 and Business::DK::Postalcode 0.04

I normally find the time to catch up on some of my open source projects over the summer.

My summer holiday have only just started and I have nothing planned for coding, not that I lack projects, but I would much rather do some blogging.

Anyway, I managed to get two releases done.

Just before I left for holiday Oliver Welter punked me with an issue in Workflow, I had forgotten about. So Workflow 1.36 has been released to CPAN.

My monitor of PostDanmark notified me with a change to the danish postal codes, so a new release of Business::DK::Postalcode (0.04) has also been released to CPAN.

I hope to be able to do some more coding over the summer, since I have both the projects and the bugs to address, but I had sort of planned to do more blogging, researching and reading.

Have a nice summer – I know I will,

jonasbn, Silkeborg

Summer releases: Workflow 1.36 and Business::DK::Postalcode 0.04