Based on IRC discussions, our idea is to start off with the Github issue tracker and wiki and see how it works for us. If it is workable, then we're happy. If not, then at least we know what it's missing and that will help us figure out what we *do* want.
What have your experiences been like using Github issues/wiki for AO3? You sound less than delighted so I presume it doesn't do everything you'd like? I'd love to hear about it, since so far we haven't found anyone working on a comparable project who's had relevant experience to share.
With regard to commitment, XP suggests that no story should be larger than can be completed in one iteration (3 weeks). If it's larger, then you split it. That means that if someone wants to take on a large (by our standards) task, they're only signing on for 3 weeks, and after that they can back out if they don't want to keep going. Continuous integration and making sure that we have a working feature at the end of each iteration means that we shouldn't get ourselves into that situation where someone bites off a task that's larger they can chew, and winds up going off for months at a time working on a huge feature set. And hopefully our refactoring, pairing, etc will mean that if someone does have to drop out for whatever reason, others will be able to pick up where they left off without too much trouble.
Hope that answers your question... if I didn't cover something you wanted me to, let me know.
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
ninetydegrees
no subject
on 2012-08-04 11:37 am (UTC)What have your experiences been like using Github issues/wiki for AO3? You sound less than delighted so I presume it doesn't do everything you'd like? I'd love to hear about it, since so far we haven't found anyone working on a comparable project who's had relevant experience to share.
With regard to commitment, XP suggests that no story should be larger than can be completed in one iteration (3 weeks). If it's larger, then you split it. That means that if someone wants to take on a large (by our standards) task, they're only signing on for 3 weeks, and after that they can back out if they don't want to keep going. Continuous integration and making sure that we have a working feature at the end of each iteration means that we shouldn't get ourselves into that situation where someone bites off a task that's larger they can chew, and winds up going off for months at a time working on a huge feature set. And hopefully our refactoring, pairing, etc will mean that if someone does have to drop out for whatever reason, others will be able to pick up where they left off without too much trouble.
Hope that answers your question... if I didn't cover something you wanted me to, let me know.