ALEX BEVILACQUA

my little corner of the interwebs

Production Timeline

| Comments

Well, it’s been a long (longer than anticipated) journey, but Redmine Plugin Extension and Development (code number 8748OS) is in the final stages of production.

Since I wanted to share a bit more detail about what went into the production of this book, I’m attaching a (slightly edited) copy of the production timeline I received from my Technial Editor.

Final Rewrites Over 50% Done

| Comments

This is just a quick post to update everyone that chapters 1, 2 and 3 of Redmine Plugin Extension and Development have been submitted to Packt with final revisions. Chapter 8 as well as the Appendix were accepted after the initial round of rewrites, so that means 4 MORE CHAPTERS TO GO!!!

Clearly I didn’t meet the target I hinted at in my last post, but it was Family Day here so I took the family away for the long weekend to go skating on the Rideau Canal in Ottawa :)

First Round of Rewrites Completed!

| Comments

This is just a quick update that I’ve finally finished the first round of rewrites for the upcoming Redmine Plugin Extension and Development book.

The issue I was struggling with was little more than a complete lack of motivation. Since I work full time and do contract development on the side (plus have a wife and kids), yet another distraction can be difficult to find time for; especially if it’s not a primary source of income.

Packt Publishing has been very patient with me though so I’m going to try to find the time in the coming week to get through the second round of revisions and rewrites and hopefully get this puppy to market ;)

My First Book: Almost Ready for Production

| Comments

For the last 4 months I’ve been working with Packt Publishing on a book about Redmine plugin extension and development.

Although it likely won’t be ready until February 2014, the book is now available for pre-order on Packt’s site.

Since the book is almost through the first stage of rewrites, I though it might be a good idea to start documenting the process.

What I’m going to write about initially are my first impressions on writing a book, as well as a few notes (which may sound like complaints) about what I did “wrong” and could improve upon in the future.

Developer Braindump: Warcraft

| Comments

In an effort to centralize some articles about how some classic games were devloped, I’ve collected the various parts of Patrick Wyatt’s blog series about the intital development of Warcraft.

Please note that this version of the series is just meant to capture the content, and not all formatting changes have been captured.

Please see the original posts for the full experience ;)

Fetching Changesets in Redmine from Heroku using Subversion

| Comments

I manage my open source and contract development projects using Redmine.

Since I’m “frugal”, I tend to try to push the free hosting envelope as far as possible. As a result, I have my Redmine deployment on Heroku, my files and attachments on Dropbox and my source on GitHub.

I also like to link to changesets in my projects, which is easy enough to do when you host the source and the Redmine server on the same machine.

Not so easy with Heroku+GitHub …. until now!

By the end of this tutorial, we will have:

  • Setup a build system using Vagrant that matches the Heroku hosting environment
  • Compiled a statically linked Subversion client
  • Added the svn client to our Redmine repository and pushed it to Heroku
  • Configured a project in Redmine to fetch changesets from GitHub using Subversion

Disable Hot Corner Hover in Linux Mint

| Comments

UPDATE For Linux Mint 16, the hotCorner settings have been moved to /usr/share/cinnamon/js/ui/hotCorner.js.

I use Synergy on all my computers to share a common mouse and keyboard, but I’ve found that with Gnome 3 based distributions, the hot corner was causing me some grief.

The beauty of using a Linux-based system though is that you can pretty much change anything you’re unhappy with, so that’s what I’m here to do.

Fixing Broken Sudo

| Comments

This is pretty much a transcription of http://www.psychocats.net/ubuntu/fixsudo, which is just such a good article I wanted to keep a copy for reference.

How does sudo work?

The way that Ubuntu has implemented sudo, the /etc/sudoers file says that users in the admin group can (after a password authentication) temporarily escalate to system-wide privileges for particular tasks. And then the /etc/groups file says which users are in the admin group.

You can read more on the community documentation about Ubuntu’s implementation of sudo.