May 5, 2008
We’re going to meet twice this week. Wednesday we’ll do another mini-sprint at Backspace (downtown on NW 5th), starting at noon. Come have lunch and work on bugs. Then on Saturday, we’ll meet at CubeSpace for our regularly scheduled code sprint at 10AM. We need to get the duplicate-entry management tools polished and ready for public use, and start importing and updating events on a recurring basis so users spend less time manually importing everything.
As a reminder, our meetings are open to everyone. Programmers (at any level of Ruby experience) and web designers are especially needed, but anyone can test the site, write documentation, and work on figuring out what’s left to do so we’re importing all calendar events for groups in the Portland tech community.
January 20, 2008
You can RSVP on the wiki. Instructions for logging in to modify the wiki are on the front page of the site.
We’ll be working on Calagator, and all are welcome to join. The coders are using Rails for the development environment. If you’d like to code, please come with current versions of Ruby (1.8.6), Rails (2.0.2), and RSpec (1.1.2) installed.
If you’d like to work on research, documentation, UI design or graphical work, just bring yourself. If you have notecards for jotting down tasks and sharing with everyone, those are always useful!
January 19, 2008
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 Biels, Paige Saez, Daniel Etra, Anselm Hook, and Bill Burcham.
We spent the first part of our gathering discussing our goals for the project. We focused on our reasons for creating a new calendar system, and the user communities we intend for this to serve. We determined that many existing calendar services have barriers to entry such as required registration that limit usage in our community. Current calendars can also lack the quality of details we would like to provide. We felt that creating a model for aggregating events around a specific interest area is important, and something that existing calendars only partially succeed at.
Read the rest of this entry »