Core Drupal Product DevelopmentWho Am I?

1. douggreen2. coder, views fastsearch (now

d6 core search), and dozens of other modules that I no longer maintain

3. CivicActions for 3 years4. NowPublic.com since 10/2009

Core Drupal Product DevelopmentWho needs Management?

1. Product Manager2. Developer Roles 3. Release Cycle4. Fast Track Bug Fixes5. Upgrade Paths, Backwards

compatibility

Core Drupal Product DevelopmentProduct Manager

1. Agile: timeboxed, best features with limited resources

2. Core committers work for the Product Manager, not the other way around

3. Keeps an eye on balance between killer features and business costs

4. Responsible delivery schedule5. Responsible for business

impact (i.e., low cost upgrades)

Drupal Product DevelopmentDeveloper Roles

1. Inventors, work closer with Product Manager and have schedules to meet or feature slips

2. Fixers, have leeway to commit fixes to dev branch, and fast track backport

3. Lobbyists / Politicians,4. Managers, arbitrate issues

and make final decisions 5. Some people will have

multiple roles, d.o. can enforce these rules in issue q

Drupal Product DevelopmentRelease Cycle

1. 2007 Barcelona survey 65% want 1 year release cycle

2. Discuss now and agree3. Publish the hard date, make

the deadline4. Businesses could plan around

the date5. We need to make it less costly

for business with major investments, to stay current and upgrade

6. This will be harder for inventors (most of us in this room)

Drupal Product DevelopmentFast Track Bug Fixes

1. I don't have know the solution2. I no longer "politic" my bug

fixes, I just write them, apply them to my project, and nudge to them into core ... this can't be good, but I don't have time to "game" the current system.

3. More people with "fixer" role who can commit simple fixes to dev branch. Reputation based, they can be fired.

4. Backport of fixes needs to be simpler, so they too can be fast-tracked

Drupal Product DevelopmentUpgrade Paths

1. Business invests hundreds of thousands of dollars, and are obsolete in 1-2 years, we can't keep this up

2. We need easier upgrade paths!

3. Coder and Deadwood attempt to solve this, but not good enough tech solution, we need a business solution too

4. When is core good enough?5. Can we stop all the

backwards breaking?

Drupal Product DevelopmentDiscussion

1. release cycle, 1 year? 18 months? 2 years?