Since there are so few of us currently developing and contributing to foresight, and given that most of the core developers wear multiple hats, perhaps it would be good to consolidate the communications (and perhaps the teams?), at least while we huddle up and do this spring cleaning sprint.
I propose that we also take the time to make a list of the google groups and mailing lists that we have and take stock of whether to keep or delete them.
Finally, I propose that
- We use foresight-devel for calls for participation and discussions on this particular sprint (like we've done so far),
- That we hold sprint related meetings in irc.freenode.org#foresight-qa (like we've done so far)
- That we document the resolutions here and link to relevant drafts, policies and HOWTO on the wiki (where?)