This is a list of books currently on my To Read shelf... literally. I do not suggest or anti-suggest any of them at this time as I haven't read them yet.
This is not the home of dotProject or web2project. It is the home of CaseySoftware, LLC. Any dotProject support questions should be referred to their support forums.
When we spec'd out the Web2project Desktop Client, the Vision was to build a simple client that would retrieve a user's list of tasks, allow them to log time against any or all of them, and update the server with the time and comments. While the vast majority of the time the user would be online, there are times - either by choice or necessity - when the user may not be able to connect to their server. Therefore, we needed a simple local datastore.
While I could attempt to have mysql installed locally, that's a huge dependency that will scare away non-developers. Alternatively, some file-based XML monstrousity might work but then I'd have the fun of dealing with XML. Without a doubt, SQLite was the only logical choice, especially once I found out Flex has support built in.
If you've only worked with a "normal" database engine like MySQL or SQL Server, then you'll quickly realize that SQLite is whole other beast..
For those of you just tuning into the WordPress/Thesis battle, here is the current - as of 19 July 2010 - state of things:
Update: To be fair, a great deal of inspiration for this post came from Ed "Funkatron" Finkler and his session at phpWorks 2008 Picachu pitch-at-ya peek-at-you lightning talk called "Users are Assholes" and later by Matthew Weier O'Phinney's lightning talk called "How to get kicked off my Project." Thanks for the fodder guys!
On all sides of software development, there are annoyances. Some of them go beyond annoyances and into pet peeves. Some of them go beyond pet peeves and incite open war within projects and communities. After witnessing a number of these rants - from developers and non-developers - and even sharing a few myself, I thought maybe I could make the situation better.
Therefore, I present here for comment:
The Ten Commandments of Open Source Software.
As of 29 June 2010, web2project v2.0 is officially released! You can download it from SourceForge now.
Although this release had lots of bug fixes, the primary focus was on a few specific new features and major pieces of functionality. You can read the full v2.0 Release Notes, but in my opinion, the six most important items are:
Over a year and a half ago, I caught one of Travis Swicegood's sessions on "Getting Git." At the time, I didn't but it had interesting implications, so I bought his book "Pragmatic Version Control Using Git" and promptly forgot about it.
Fast forward a year and I found myself buried under web2project patches. At the time, all of them had to go through a few of us to make it into the core Sourceforge repository and the diffs started piling up. Needing a new approach where I could handle patches faster and easier, I decided to spend some time and actually explore Git.
It's been a week since tekX completed and there are a number of other tekX writeups to read but I thought I'd share one last one from a different point of view. To add some context, I'm not the guy that signs the contracts, approves the expenses, schedules the sessions, arranges the speakers, or anything useful. Due to other project commitments, I basically served as backup for some of those things and then as social chair for the evening events.
First off, I'm proud of our first time tekX speakers. Easily half of the speakers had never spoken at a tek before, off the top of my head that includes - Bill Karwin, David Strauss, Jason Austin, Josh Holmes, Kanwalijeet Singla, Kristina Chodorow, Matt Schmidt, Matt Turland, Ryan Stewart, Sumit Chawla, and myself. Since tek is the Community Conference and it tends to be incredibly technical, it takes a different mindset than many of the other conferences. Even better, a few of those people were first or second time conference speakers period.