As of this morning - 09 December 2009 - web2project v1.2 is live!

While there is not a huge amount of new user-facing functionality, the sheer number of fixes and amount of cleanup is staggering.  Since the v1.1 release in September:

If you were paying attention a few months ago, you know that for php|tek 2009, MTA put together a free webcast series. We had great turnout, feedback, and success with them, so we're doing it again:

We have the FREE CodeWorks 2009 Webcast Series!

It works basically the same as last time around.  About every other Friday over the next three months, we'll have a ~30 presentation starting at 1pm Eastern Time.  We tend to start on time, so don't be late.  But if you have to miss it or are running late, the video and slides will be posted afterwards.  Where?  We're not sure yet, stay tuned.

It's been 23 days since the first Release Candidate for web2project v1.0 was released.

In the time, we've had 17 bugs reported by a total of eight different users. Combined with the four issues we had before, we briefly reached a peak of 17 open issues. As of 6pm Eastern on 06 May, the current triage is:

It's been 16 days since the first Release Candidate for web2project v1.0 was released.

In the time, we've had 13 bugs reported by a total of five different users.  Combined with the four issues we had before, we briefly reached a peak of 17 issues.  As of 7pm Eastern today, the current triage is:

The last week week - since theweb2project v1.0 Release Candidate - has been very quiet.  It's not entirely out of choice, it's partially due to the effort involved in rolling a Release... even if it's just a candidate.  And in addition, it makes sense to give everyone a bit of time to play with the system, collect their notes, submit their bugs, and generally provide useful feedback.

On that note, we have 13 open issues.  Most are high priority and require a definite response and update before Release, but there's one where we need some help.

We could us assistance on Issue #112 - related to Translation Management.  Most of the people/groups that I know of using web2project are predominantly English-speaking so their usage of translations is minimal at best.  Therefore, if you're a web2project user and use translations, please let me know so we can collaborate and make sure this is handled appropriately.

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.

Well, I have good news and bad news.

The Good News: php|tek 2009 will have an Unconference!

The Bad News: I'm in charge.

(cue mad scientist laughter)

Let's be clear right off the bat:  All [name]Camps (Bar or otherwise) are unconferences but not all unconferences are [name]Camps.  The distinction - and this seems to be widely accepted - is that [name]Camp sessions should be selected day of and everyone needs to participate in some manner. Uncons can have the above but don't really have to... which is how it works at these Uncons which are attached to conferences.

Therefore, here's the (estmated) format for this con/uncon combination:

• Normal sessions start at the beginning of the day and the three tracks run until about 4 or 5pm;
• At that point, we take over and get full access to the rooms, projectors, network, and anything else not nailed down;
• We're slated to have three sessions in each room each evening, giving us a total of 18 sessions.

So here's your mission: