DrupalCon is seeking a partner to enhance the current DrupalCon website to prepare for the growth of DrupalCon events. Integration and development will use the existing code base as a foundation for adding or enhancing features as outlined in the RFP.
First held in 2005 in Antwerp, Belgium DrupalCon has grown to host over 3,100 Drupal developers, themers, users, business owners, and decision makers from all over the world. The DrupalCon website is the central point for the DrupalCon community to meet, discuss, and plan the next DrupalCon. The community is heavily involved in the planning of the conference including submitting and selecting sessions and voting on the conference direction. The website is a pivotal tool in the planning, organization, and execution of the conference.
With over five years of planning experience the next generation of the DrupalCon website will be built upon the expertise, code, and architecture of the previous DrupalCon websites. All of which have been built by some of the greatest Drupal development teams in the world. DrupalCon is seeking a strong partner to help us implement and integrate the best features of our past websites into a single site with the ability to host multiples simultaneous conferences. As the integration and development partner you will be teamed with past development teams to learn from their expertise and code. This will dramatically reduce your planning and code development allowing you to focus on integration and feature enhancement.
Come and be a part of the DrupalCon team!
Interested? Review the RFP and get in touch!
| Attachment | Size |
|---|---|
 DrupalCon-RFP.pdf | 140.38 KB |
Comments
Diff?
Since the website relies on the existing code base, is it possible to specify what in the RFP is actually new, and what already exists in the code base?
This will allow better responses to the RFP, IMHO.
This depends
We are looking for the best use of the existing code base and the most appropriate configuration for the conference website. This may be that the entire code base is used or that the code base is simply used as a guideline. For this reason we have not stated what should or must be reused. We can, however, help you to understood what is available, which is basically the entire site.
Feel free to contact me so that I can help you understand what exactly we are looking for and what resources are already available to pull from.
http://drupal.org/project/cod
http://drupal.org/project/cod is worth consideration
It is under consideration
Those folks have been contacted and we are actively considering it as an option.
deadlines
The RFP has the following deadlines:
RFP Process closes on September 1st.
The site must be ready to accept ticket sales on October 1st, 2010.
When do you plan to select a vendor?
Having my hands dirty with a
Having my hands dirty with a couple of builds using cod_support, cod, and the helluva helpful contrib modules (features, context, boxes, panels, fivestar, action, workflow, signup, you_name_it ...) -- I am quite sure this can be done in sprints.
However, while site-building might be easy... design-integration plus capturing & implementing use-cases would be the hard part.
I'm wondering if this can be a community project of sorts? I'm sure a lot of people would be able to contribute.
Cheers,
Marc C.