Agenda for panel workshop at DrupalCon Boston about the d.o redesign efforts:
http://boston2008.drupalcon.org/session/drupalorg-redesign-panel
Panel presenters
Angela Byron
Tiffany Farriss
Kieran Lal
Daniel Zhou
Nedjo Rogers
Derek Wright
Revised agenda
Here is a revised agenda based on Tuesday evening's discussions with the modification that Kieran will be there. We'll leave the previous draft below because it contains useful details.
- Aims and leadup – Nedjo Rogers, Drupal Association
- Scoping – Tiffany Farriss, Palantir
- Progress so far – Angela Byron, DA
- Identified pieces
* Aiding module evaluation with pivots, Daniel
* Improving developer toolsets, Derek Wright
5. Fundraising – Kieran Lal, DA
6. Getting involved
Welcome and introduction [Angela] (5 minutes)
- Goals of session
- Engage the community in the redesign of drupal.org.
- Identify remaining work for and potential contributors to a RFP for a site redesign.
- Help promote a fund raising campaign.
- Drupal Association role
- Existing redesign team
Design goals for d.o [Nedjo] (15 minutes)
- Goals for drupal.org
- Increase Drupal adoption and market share
- Increase the capacity and quality of Drupal development, both core and contributed
- Produce a revenue stream to support Drupal Association work
- Existing site: strengths and
- Identified priorities
- Increase searchability of sites
- Ease identification of resources, e.g., modules
- Improve documentation
- Questions needing further information and analysis
- How best can we meet the needs of prospective Drupal adopters?
- What will best facilitate a revenue stream?
Addressing priority Drupal user and developer needs [Angela and Derek] (25 - 30 minutes)
- Identified personas (A)
- Possible subsites design for identified user groups (A)
- Specific objectives and proposed approaches
- Documentation improvements (A)
- Improve the ease of finding modules (D)
- Additional tools for developers (D)
Redesign process [Tiffany] (15 minutes)
What does a project this size look like?
- RFP prerequisites
- Scope
- Management and oversight needs
- Stages
- Pieces and separate solution providers
- new theme
- specific new functionality, e.g., module browsing
- design, navigation structure
Funding the effort [Kieran] (10 minutes)
- Budgeting needs
- Potential funding sources
Helping people find modules [Daniel] (10 minutes)
- The concepts of "pivots", and how they can be used in d.o. to help people find modules.
- A short live demo.
Discussion, Q/A [All, Nedjo to facilitate] (15-20 minutes)
- Questions for feedback
- How well have we identified the overall goals?
- What needs have we missed?
- Identifying resources and volunteers for completing the RFP and beyond
Information in preparation for the session is being pulled together here: http://groups.drupal.org/node/9034
Comments
Some questions
Thanks for putting together this outline, Derek.
Last week Tiffany and I met while I was in Chicago and discussed the session. We wanted to start with an understanding of what we're trying to achieve with the session. Is the session intended to communicate information about the plan and process? Is it to gather community input? Do we have specific questions and needs going into this?
We came up a set of questions and background info that would be useful to prepare for the session. I'm aware that most or all of these questions have been discussed and that information exists on this site. Still, it would be useful to draw information together in accessible forms and also to seek clear direction from the Association.
Here are my notes from our conversation:
Information needs:
The session
The redesign project
drupal.org current setup
-- handbook
-- forums
--issues, etc.
Constraints of project, if any
Current usage of site
Current feature set: do we have user analysis/input?
Redesign process outputs
What are our target users? Do we have personas defined?
Possible user groups:
-- complete newbs
-- beginner: one to three sites
-- intermediate: 4 – 9
-- advanced: 10+
-- zealot: too many to count
Good questions
Many of these questions are already answered in the posts in this group and the marketing group. If you could make this into a wiki page we could summarize this data and get it into the RFP.
Here's the plan.
1) Convince the association that it's number one priority is drupal.org redesign.
a) http://buytaert.net/drupal-association-2008-wishlist so the community has agreed.
b) http://buytaert.net/drupal-org-wishlist the president of the association has agreed
c) http://buytaert.net/recruiting-for-the-drupal-association the president of the association has requested a board member to fulfill this position. Despite over 60 candidates for the association, the association failed to recruit and elect a board member to fulfill this role.
d) The association needs to budget for the redesign.
2) The information architecture, interaction design, visual design, graphic design, user experience design should not be a brain dead design by committee or design by lowest common denominator process. Community input is important, but you can't grease squeeky wheels and expect a good outcome. Iterative processes, community input, analytics, and user research should all be used. But let's recognize we have a few hundred, if not a few thousand people who do this all day every day professionally. We can collectively come to a good process.
3) We need to get an estimate of the costs of the design portions of the redesign. A Request For Proposals process has begun and a draft of an RFP is available for review.
4) We need to raise money through fund raising and revenue opportunities with Drupal.org to pay for the design aspects to be done. The current Drupalcon is on track to raise $225 000 for 500-600 attendees. Drupal.org supports millions of visitors. We can raise and earn money in a fair, open, and useful way, to support the payment for a redesign.
5) A parallel effort by the community to tackle many aspects of the redesign is certainly welcome. This group contains a lot of thoughtful work and there's very good work going on behind the scenes on the RFP, Fundraising for the redesign, Recommendation systems. The community can and should play a huge role in the redesign of the site, but a truly great design will need dedicated attention to the design goals the community can execute.
6) Once a central design is done, and the design iterations are begun, the community can certainly rally to help in the operations and execution of the design.
Please read every single comment in this group. Please read every post. There's really very good work being done so far, and all we ask is that it be acknowledged.
DON'T MISS EARTH'S LARGEST GATHERING OF DRUPAL PROFESSIONALS!
Drupalcon Boston 2008 · March 3-6, 2008
Learn more at http://boston2008.drupalcon.org
Affordable sponsorship packages available
Lots of answers
here: http://groups.drupal.org/node/9034.
helping people find modules
Per discussion with Kieran, I'd like to give a short presentation on our "pivots" work. It will generate modules recommendations and help people find the modules that meet their needs.
I have updated the timeslot in the wiki.
Revised outline, some slides
I've added a revised outline and put up some initial slides.
Have I mentioned lately how much you ROCK?
I was just sitting down to do this, and it's already done. :D
Adding some slides for my part now...
EDIT: Done. ;)