![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
Iteration 0 is in progress!
Aug. 10th, 2012 10:07 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
alexbayleafThanks everyone for signing up in the team signup post the other day. The current list of participants in this iteration is:
Customers:skud, inkstone, azurelunatic, japester, ilyena_sylph, Seegwen
Design:commodorified, Seegwen, algeh, aquaprofunda (via other channels), randomling
Communication:skud, amianym, commodorified, japester (primarily technical/project stuff), shadowspar, algeh (available but less interested)
Coding:skud, amianym, shadowspar, seegwen, cesy, algeh, randomling
Sysadmin/devops:japester, shadowspar, Seegwen
Please subscribe to the mailing list! If you want to actively participate in this iteration and you're not currently subscribed to the mailing list, you probably should be. We'll be posting highlights and important stuff here to the DW community, but a lot of the conversation will be happening there. Subscribe here.
Meanwhile, we've started roughing out some stories (remember, that's the Extreme Programming term for "requirements document") that we might want to work on in this iteration or in an upcoming one. Here are some links:
Placeholder website
Dev website
Community guidelines
Twitter account icon
(The previous ones have been added to the issue tracker, while the following ones have been posted to the mailing list but haven't made it to the issue tracker yet. The process is that stories are first raised on the mailing list, then once the iteration coach(es) have validated them as being decent stories (i.e. they're written from a customer perspective, and so on) then they get added to the issue tracker. So the following ones are less solid at this point.)
Signup/login
Profile page
My garden
Profile privacy
Firehose
(You can see discussion threads about some of these stories in the mailing list archives, too.)
---
Our next step is to start breaking down these tasks and talking about what steps are needed to complete them, what skills those involve, who wants to do them, and how long it will take. From that we'll come up with a list of tasks we'll aim to complete in this iteration, with two people assigned to each one, and then -- very soon now -- we'll start work.
One of the things I'm concerned about with this iteration is that we've had a lot of people sign up to take part (thank you!) but I'm not sure we have tasks for them all, as the early stuff seems to not be easily parallelisable. If you have suggestions regarding this -- of other things we can do in parallel, or of ways for everyone to get involved in the few tasks we already know of -- then I'd love to hear them!
Customers:
skud, inkstone, azurelunatic, japester, ilyena_sylph, SeegwenDesign:
commodorified, Seegwen, algeh, aquaprofunda (via other channels), randomlingCommunication:
skud, amianym, commodorified, japester (primarily technical/project stuff), shadowspar, algeh (available but less interested)Coding:
skud, amianym, shadowspar, seegwen, cesy, algeh, randomlingSysadmin/devops:
japester, shadowspar, SeegwenPlease subscribe to the mailing list! If you want to actively participate in this iteration and you're not currently subscribed to the mailing list, you probably should be. We'll be posting highlights and important stuff here to the DW community, but a lot of the conversation will be happening there. Subscribe here.
Meanwhile, we've started roughing out some stories (remember, that's the Extreme Programming term for "requirements document") that we might want to work on in this iteration or in an upcoming one. Here are some links:
Placeholder website
Dev website
Community guidelines
Twitter account icon
(The previous ones have been added to the issue tracker, while the following ones have been posted to the mailing list but haven't made it to the issue tracker yet. The process is that stories are first raised on the mailing list, then once the iteration coach(es) have validated them as being decent stories (i.e. they're written from a customer perspective, and so on) then they get added to the issue tracker. So the following ones are less solid at this point.)
Signup/login
Profile page
My garden
Profile privacy
Firehose
(You can see discussion threads about some of these stories in the mailing list archives, too.)
---
Our next step is to start breaking down these tasks and talking about what steps are needed to complete them, what skills those involve, who wants to do them, and how long it will take. From that we'll come up with a list of tasks we'll aim to complete in this iteration, with two people assigned to each one, and then -- very soon now -- we'll start work.
One of the things I'm concerned about with this iteration is that we've had a lot of people sign up to take part (thank you!) but I'm not sure we have tasks for them all, as the early stuff seems to not be easily parallelisable. If you have suggestions regarding this -- of other things we can do in parallel, or of ways for everyone to get involved in the few tasks we already know of -- then I'd love to hear them!
