On Fri, Apr 27, 2012 at 4:05 PM, Chris Steipp <csteipp(a)wikimedia.org> wrote:
If you have an OAuth use case / user story, please
I'd like to second this ^^^ Support for OAuth is not a binary thing,
and so we'll need these user stories to start in earnest on this.
Here's how I see the process of building this feature working. Chris
is available to lead all of this, but if someone wants to volunteer to
do any of this, we don't want to get in the way:
Phase 1: User story gathering. User stories seem to be the most
sensible way of doing requirements gathering in a collaborative way,
since it's easier to prioritize a big list of user stories than it is
to prioritize abstract requirements.
Phase 2: User story prioritization and requirements distillation.
Once the user stories stop trickling in, then we can do rough
prioritization on the stories (high, medium, low). This is going to
be guided by a combination of community input and technical
feasibility. We'll need to distill the requirements from the user
stories to find common functionality between various stories.
Phase 3: Making the backlog - we'll then construct the initial backlog
based on some number of the higher priority user stories.
Phase 4: Implementation - start chipping away at the backlog
We have some smaller security projects that we'd like Chris to code on
before starting in on this, so it'll be a while before Chris starts in
on phase 4. However, he's available to start this process now, so if
there's an experienced volunteer developer that can pair with Chris
now, we could make this happen a lot faster.