Calagator code sprint! [Cross post from pdx-tech-calendar]

7 views

Skip to first unread message

Shawna Scott

unread,

Jul 21, 2014, 8:55:36 PM7/21/14

to pdx...@googlegroups.com, pdxruby-...@googlegroups.com

Reid posted this to pdx-tech-calendar, but I thought the Rubyists might want to know about it directly. Sorry if you get this twice. Come contribute to an open source Portland Ruby project!

-Shawna

-------------------------

We're holding a Calagator Code Sprint on Saturday, July 26! You can find the details at: http://calagator.org/events/1250466635

We'll be meeting from 1–5pm at Portland Code School to talk about the state of the project, review issues, and write some code. There's been an upswing in Calagator development in the last few months, with a bunch of new contributors jumping in that we'd love to get to know a bit more. :)

Some folks have been discussing this over on the calagator-development list, but I wanted to make sure that anyone who was only following the GitHub issues also found out about it. If you're following issues here and want to keep up with low-traffic discussion about the project, I recommend joining that list.

Some possible topics include:

What were our goals when Calagator started? What does the Portland community need now?
How can we make Calagator's UI friendly, responsive, and modern. I'm updating some mockups of my ideas and would welcome discussion and ideas.
Some very-useful enhancements exist in divergent forks of Calagator. How can we best integrate these changes?
How do we make Calagator easy to customize while also keeping things as easy as possible for new contributors?
What is the current state of the knowledge that a new contributor is likely to have when approaching the project.