The Time-Tracker helps teams and individual developers to log the time they spent working on specific GitHub issues. It is designed to integrate seamlessly into your development process, by hooking directly into GitHub issues. You and your team have the ability to log your working hours and keep track of your monthly progress.
How it works
- Login with your GitHub account
- Add the repositories you want to track
- Start logging your work by clicking on the injected Log time link in GitHub
- Get an overview of your logged times. If you are an admin of a GitHub repository you can see the logged work of your whole team.
So, why did we make this?
Last year we decided to get rid of our proprietary issue tracking software and switched to GitHub issues.
- Better integration in our development process. We had been using Github for code anyway.
- Simpler workflows. Pull requests ftw
- Comfortable to use. It’s just fun to browse code on GitHub
- Good integration with CI software
Unfortunately, there is no time tracking integrated in GitHub. So we made our own time tracking software because we couldn’t find a good solution out there. Now we open sourced it and host it for free.
The frontend is a single page webapp, built with Backbone and Marionette. Thanks to Bootstrap it looks good and is responsive. For the Scala backend we used the Play2 framework with MongoDB for persistence. Thanks to GitHub Webhooks, the server gets notified when a user generates a new issue. Thereafter, the Time-Tracker injects a link to the issue description, which can be used to log time. Everything is pretty much straight forward from there. If you want to know more, don’t hesitate to contact us. We are happy to help you.
I built a web app to train sheet reading skills with a real piano. The web app renders random music sheets and the user has to play the notes on his piano. The communication between piano and browser is implemented with the help of the Web MIDI API.
This week all major industry players joined forces to come up with a common standard format for Linux containers. This is great news because imho containers will play a major role in deployments. They are the key enabler of the DevOps methodology and will drive IT efficiency improvements in many organizations.
Topic models are great to categorize WHAT a text is about. It is pretty easy as well: Get an off-the-shelf LDA, train it on your corpus and you are set to go. But there are even more insights you can get about your texts. Modifying your corpus in a certain way (mostly removing everything but verb phrases) allows you to gather a deeper understanding about WHY a certain text was written.