Today several of us met during the Code Sprint gathering at CubeSpace to talk and work on the calendar.
Participants: Audrey Eschright, Selena Deckelmann, Igal Koshevoy, Reid Beels, Paige Saez, Daniel Etra, Anselm Hook, and Bill Burcham.
I was a little slow on the uptake. But a few days later, I managed to crank out a post about the “Portland Tech Calendar” project, highlighting:
Last Saturday, the Portland Tech Calendar group dove headlong into a code sprint around the problem of aggregating all of the tech calendars for Portland, Oregon, and the surrounding areas. The result? Calagator.
The group made a great deal of progress during the code sprint. A full recap is available via Google Groups. Highlights are available on the Calagator blog. (That’s right, they have the beginnings of code and a blog. These guys have accomplished more in a weekend than I’ve accomplished in the last six months.)
What came out of that initial meeting was more than code, and more than an app. Much more.
Calagator remains one of my favorite examples of Portland ingenuity, Open-Source teamwork, and the underlying culture of Portland’s Web tech community. And I sincerely hope that they continue doing the same kinds of things they’ve managed to do over the past year.
Happy Birthday, Calagator. And thank you. Not only for aggregating the Portland tech calendar, but for providing a shining example of that which this community is capable.
Portland’s favorite calendar aggregator, Calagator, continues to improve, code sprint after code sprint.
And it’s drawing ever nearer to its 1.0 milestone.
But before Calagator gets there, it’s time for a different kind of sprint, as Audrey Eschright shares:
We’ll be meeting tomorrow starting at 10am at CubeSpace, to kick off the Calagator documentation sprint. I really encourage anyone who has been involved in the development of this project, on any level (including lurking on the mailing list) to stop by, even if you only have an hour or two free. We’ll be working on the Calagator User Guide, and talking about what’s next for the project after we reach our 1.0 milestone.
More details, time, and location for the Calagator documentation sprint can be found, well, on Calagator, of course.
Calagator is an all-volunteer effort to provide a unified calendar for technical communities and user groups in Portland, Oregon. Anyone can contribute information by importing, creating, and editing entries.
I was going to write a post about the next Calagator code sprint which is going to be held tomorrow, March 15, from 10 AM until 5 PM at CubeSpace. But I’ll be darned if Igal Koshevoy’s note didn’t put that write up to shame.
So, I’m just going to quote liberally from that note.
Calagator is an all-volunteer, open-source project to develop a calendar aggregation system for the Portland technical community. We’re making lots of progress, so please join us in the effort.
Where does the code sprint take place?
We’ll doing another code sprint to work on the project this Saturday, 10am to 6pm at CubeSpace. We usually meet in the FlexSpace (also the place where the Ruby Brigade meetings usually are), but the friendly front desk staff will tell you where to go if you’re not sure.
I’m not much of a “coder,” is there anything I can do to help?
Everyone is welcome to participate, even if you haven’t attended a code sprint before. Experience with Ruby on Rails and agile development is helpful, but you’re welcome to come even if you’re new to these because this is a great way to learn. You do not have to come to the entire event, so swing by if you have time.
I’m standing here at CubeSpace and you guys are nowhere to be found.
If you drop in and we’re not there, you’ll probably find us eating lunch at the “Side Door” bar/restaurant a few blocks away.