Difference between revisions of "Talk:RFP"

Revision as of 07:18, 18 May 2006

What is a good way to respond to this RFP? Right here?

• Yes, this works, although dialog via wiki seems awkward to me as I understand it.

To give a sense of my reaction to the RFP, I'm pretty excited seeing a way I can contribute to NVC, and also excited seeing recognition of this need for online connection. At the same time, seeing reference to Drupal, and to having a lot of functionality spelled out up front, I'm a bit anxious--while I have worked with Drupal and could implement it, I am aware of other ways to develop this site which I predict would better serve the needs of CNVC.

--Jason Felice

I'm curious what other ways you envision. What seems attractive about CivicSpace is that it's a selection of some great Drupal modules that have been pretty much tested to work together, with a fairly user-friendly front end configuration menu. We could probably have it up and ready for use within a month, and add features and modules later if desired. Are you thinking of another open source product? If so, does it have similar features and semi-automated front end?

--John W.

Hmm. As I think about this now, I'm noticing that my ideas are colored by what I was planning to do with the Practice Group Finder Idea. Maybe the same ideas don't apply to RFP.

In any case, reading "we could probably have it up and ready for use within a month, and add features and modules later if desired," it looks like ease in getting started is important to you. I was more focused on adapting quickly to needs and involving the community in the development process - so I had concluded that the agile development philosophy would be a win. I had presumed starting from scratch because of that, but I now wonder if that assumption can be usefully challenged.

The agile techniques I would incorporate would mean that the system could have very sort iterations (one or two weeks), each one showing new functionality and going "live" quickly. This enables quick responses to community and other stakeholder feedback on what works, what doesn't, and typically elicits new possibilities for value which weren't previously seen. Hence the term "agile."

Over all, this would be a shift from thinking about this as a site or software package, to thinking about this as a process for enabling and meeting community needs.

At this point, noticing that this approach is likely much different from what you were expecting, I'm feeling a little worried owing to my desire to anticipate how I'm received. Would you (and anyone else, too!) be willing to let me know what needs are met or unmet by this?

Thanks --Jason Felice

Jason, do you like to have community envolved ? And also like to be careful about providing to much functions for startup ? So that the system has the neccessary functions and easy to handle ? And the community has the chance to be part of the process and can grow with the system ?

I am interested in your thoughts and waiting for response. Probably its more effective and fast if me make an appointment in irc ?

-- Markus Pallo