For Github, we found that the issues tracker didn't let us do complex searches, and didn't have as much flexibility for permissions compared to Google Code, so we're sticking with GCode's issue tracker for now.
Wiki-wise, the most difficult thing has been that you can't watch a page, and can't get email notifications that it's changed, which severely inhibits asynchronous collaborative editing, and leaves us with a lot less protection against malicious edits.
I think that makes sense for the rest. So if someone who's been around for a while takes a break and then wants to come back in, they have to either synchronise with an iteration, or pick something small enough for them to do in the amount of time that's left in the iteration?
![[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 01:13 pm (UTC)Wiki-wise, the most difficult thing has been that you can't watch a page, and can't get email notifications that it's changed, which severely inhibits asynchronous collaborative editing, and leaves us with a lot less protection against malicious edits.
I think that makes sense for the rest. So if someone who's been around for a while takes a break and then wants to come back in, they have to either synchronise with an iteration, or pick something small enough for them to do in the amount of time that's left in the iteration?