We're slowly making progress with making Corvalligator a reality in
Corvallis and I wanted to just introduce some of you since some of you
don't know each other.
Bryan Stearns (@bryanstearns): PDX ruby guy that has offered to help
us code in his free time
Jillian Burrows (@jburrows) : Corvallis coder getting paid to work on
corvalligator for a special program
Sheri Dover (@sheri_dover): Corvallis Artistians Market lead
Lance Albertson (@ramereth) : Well, you all know me :)
I pasted the email I originally sent to Bryan months ago here [1]
detailing some of the important features we need to get this going
initially. I plan to get my hosting sorted out by the end of this
week/weekend so that we have something online to at least see. I'd
rather not publicly announce this until we've gotten most of the
bugs/etc worked out but I don't mind a trail run. It'd be nice to get
a logo or something created too.
Jillian: I recommend you subscribe to the calgator development mailing
list [2] and check the archives if you encounter any issues.
Additionally, you should look over the documentation they have online
[3] and if you can create a login to github [4] and create a fork of
the main calagator tree that will make pushing fixes to upstream a lot
easier. If you need help understanding github, just let me know but I
think the calagator project has more details on how to setup github.
Add me as a friend on github (my username is ramereth) that way I can
watch your commits easier and pull those changes into production
eventually.
I imagine they will have a code sprint in Portland in the next month
or so, we should try to make a trip up there when they do that. If you
have any more questions, please use this list as a primary means to
communicate updates/etc!
Cheers!
-Lance
[1] http://groups.google.com/group/corvalligator/web/corvalligator-features-todo
[2] http://groups.google.com/group/calagator-development
[3] http://code.google.com/p/calagator/
[4] http://github.com/