We're at that time of year where everyone wants to start something new. We have a flood of articles and blog posts about "what I'm going to do differently this year" and everyone wants to [choose: lose weight, read more, get out of debt, get that new job, etc, etc]. If they're lazy, this urge will last about a week.. aka it's probably done by now. Alternatively, if they're motivated, they might make it to February.

At the end of the day, it doesn't happen because starting something new is HARD.

Alternatively, in software development, we're spoiled. We can write a single line of code and do some interesting things. If we add a framework, that single line of code is backed up by thousands.. and can do even more impressive things. At Twilio, it's cool watching someone get excited that their three lines of code just made their phone ring. Unfortunately, we can take this too far..

This is the sixth of my weekly updates for web2project. For newcomers, feel free to subscribe to my web2project newsfeed here.

I could talk about commits, issue counts, etc, but that's actually the least important part...

As of early morning EST on 13 April 2009, the web2project Release Candidate is live:

web2project-v1.0-rc1.tar.gz

To be clear, we know this is not a perfect package.  If we thought it was 100% bug free, it'd be called a Release and not a Release Candidate.  Towards that goal, if you find bugs, please report them to our Issue Tracker as soon as possible.

This is the fifth in my weekly web2project updates.  For those of you just joining us, feel free to subscribe to my web2project-only newsfeed here.

We've had six commits this past week.  Some have been small - borderline trivial - but there are a couple that are huge and covered later in this post.

Next, we have thirteen open bugs.  While this seems like a bad thing, I don't consider it that.  Lots of bugs is often a sign that the software is in bad shape.  In some cases, this is true... I don't believe it is here.  Instead, I see this as an opportunity to catch issues pre-Release before they become support issues and fill the forums with plantive cries of "omg!!!111 help me!"  Resolving these problems now will save everyone time and stress... and probably save team credibility.

But there's something more subtle here...

Another week, another bit of fun... This is the fourth weekly update on the status of web2project development. If you're interested in staying up to date, check out the web2project newsfeed.

First, we've had five commits in the last week.  All five commits closed bugs - two from the issue tracker, two from the forums, and one via email.  Four of those issues were from the community and not core team members.  As always, bug reports are one of the best ways a community can help a project.  A useful bug report is an amazing contribution that almost anyone can make.  After all, no one can fix your issue if the rest of the community doesn't know about it.

This is the third weekly update on the status of web2project development. Don't worry, these should only come out on Tuesdays which works well since I do most of my review, updates, and development on Sundays. I have a few goals in doing this: First, it should help the community stay up to date. Second, it will let people know the project exists and some interesting details about it. Finally, it will apply a bit of friendly peer pressure to make sure I have something to talk about. These will all be tagged with the category "web2project" and the corresponding feed is available here

Between attending SXSW and other chaos, I've been remiss the past ten days or so in not getting updates out as planned... so away we go.

This is the first of a series of weekly updates that I plan to give on the status of web2project development. Don't worry, these should only come out on Tuesdays which works well since I do most of my review, updates, and development on Sundays. I have a few goals in doing this: First, it should help the community stay up to date. Second, it will let people know the project exists and some interesting details about it. Finally, it will apply a bit of friendly peer pressure to make sure I have something to talk about. These will all be tagged with the category "web2project" and the corresponding feed is available here.