Project: Keeping Track of your GitHub Open Issues in Real Time

The need

Since my team started working more and more on open-source projects, which are publicly shared on GitHub, I faced a need to have an easy way to follow up whenever new issues (GitHub's euphemism of bugs) were submitted by users.

There is a way to keep track by "watching" repositories of your choice, for which you get email notifications, but those emails are not limited just to newly submitted issues, but also to every pull/push request and comments. Also, for some reason, although I have clearly unsubscribed ("unwatched") specific repositories on my list, GitHub continues to notify me about them (which seems to be an issue in itself).

Thus, I decided (as always) to take things to my own lazy hands, and spent ~2 days building my very own GitHub Issues Notifier.

Get it on GitHub!

Babylon-based dictionaries on Kindle - Round 2

My post "Using Babylon-based dictionaries on your Kindle" seems to have gotten relatively wide attention. Currently the statistics show that 2595 users have seen it, 31 of them commented, 2 more via Facebook and a number of emails I've received from readers.
People's interest in pre-built dictionaries which they can run on their Kindle devices (specifically English-Hebrew dictionaries, but not just) is understandable. There are some issues with the BabylonToHtml conversion tool I've put together.

Due to lack of time for resolving the known issues with the project, or for production of pre-built dictionaries, I've decided to share BabylonToHtml publicly as an open-source project, for anyone who wishes to update/improve it.

Pre-Built Dictionaries in this post!

I'm sharing some pre-built dictionaries in this post. Some were produced by me and some by others. They are shared here so that they can be freely downloaded and used by anyone.
This section will be updated with dictionaries which the readers share with me over time.
 Jump to the pre-built dictionaries section!

Setting Up Subversion Source-Control with Assembla and TortoiseSVN

Why Source-Control?

When working on sufficiently-large projects, it's good to be able to keep track of changes with a source-control system (sometimes referred to as "revision control system" or "version-control system" or VCS. Personally I prefer the old term "source-control"). The advantages of using such a system:

• Keeping track of changes:
  Know who made the changes and when.
  Record changes with appropriate comments ("..hmmm.. why did I make this change..?").
• Reverting and obtaining previous versions.
• Managing versions and labels of your code in various history points.
• Potentially sharing the project with other developers ,working together making tracked changes.
• Some source-control systems allow tracking bugs and tasks, while associating them to changes made in files.

Many enterprises use commercial source-control systems. Since the majority of my enterprise projects have been on Microsoft environments, in the early days I was using Visual Source Safe (VSS), in later years it's been Team Foundation Server (TFS). Both consist of a source server and client applications which integrate with the Windows domain users and with Visual Studio IDE.

On home projects I prefer to use a more modest source control system, preferably one which I can store online for backups and doesn't require a server running all the time.

Article Level:

Reasonably moderate