This is a great idea for our first application. It's something that is usable right from the start.<br><br>We will need someone who will volunteer managing the progress, perhaps a basecamp for this? or some other tools we have access too for collaboration and project outlining.
<br><br>Any ideas? When do we start?<br><br><br><br><div><span class="gmail_quote">On 8/14/07, <b class="gmail_sendername">Chad Fowler</b> <<a href="mailto:chad@chadfowler.com">chad@chadfowler.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On 8/14/07, Michael D. Ivey <<a href="mailto:ivey@gweezlebur.com">ivey@gweezlebur.com</a>
> wrote:<br>> What about building some reusable components that would be useful for<br>> multiple non-profits? A NPO/NGO plugin/gem collection, perhaps.<br><br><br>I think this is a good idea, but I'd like to start on something more
<br>concrete and less infrastrcturey at first. Partially because I'd like<br>to extract such components (frameworks) from real application work.<br><br>That being said, one obvious application we could get started on would
<br>be a hosted app/place for matching volunteers with projects and/or<br>their regions. Perhaps a non-profit could come intot he site and look<br>for a local developer that could help lead an open-source<br>charity-based project as part of the Ruby For Change umbrella. What
<br>do you all think about that as something to start hacking?<br><br>Chad<br>_______________________________________________<br>Rubyforchange-talk mailing list<br><a href="mailto:Rubyforchange-talk@rubyforge.org">Rubyforchange-talk@rubyforge.org
</a><br><a href="http://rubyforge.org/mailman/listinfo/rubyforchange-talk">http://rubyforge.org/mailman/listinfo/rubyforchange-talk</a><br></blockquote></div><br>