Most of our teams are using github wikis or google docs at this point for sharing notes, and github issues for tickets/work tracking. Would ideally like to keep to these so that we're not spread across too many different tools.

In terms of chat we've got slack setup. Happy to invite anyone that need access.

-Ilan

On Wed, Aug 10, 2016 at 4:46 PM, Lan Dang via Scale-planning < scale-planning@lists.linuxfests.org> wrote:

---

Scale-planning mailing list Scale-planning@lists.linuxfests.org https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning

---------- Forwarded message ---------- From: Lan Dang l.dang@ymail.com To: SCALE Planning List scale-planning@lists.linuxfests.org Cc: Date: Wed, 10 Aug 2016 23:46:11 +0000 (UTC) Subject: Collaboration tools

A comment came up earlier in the OSSIE thread about getting access to a wiki or some kind of folder.

I know there is a SCALE wiki, but I tended to use that more as a reference than something I wanted to contribute to. Not everyone on my team would have access to the wiki, and there really isn't a reason they should; we have many day-of volunteers.

With the A/V team, we have been using a combination of GitHub wiki, GitHub issues, and Google Drive to keep track of things. (I also use the GitHub repo to serve up a website to onboard our volunteers.) Our repos are public and part of the socallinuxexpo org.

https://github.com/socallinuxexpo/scale-av-web

We store files in the Google Drive, as well as meeting notes, and I run surveys using Google Forms to capture comments and feedback that we use in next year's planning.

We use Google Hangouts to hold virtual meetings, and I'll take notes in a Google doc, that I can share with everyone.

I use Slack at work, and I've used it for SCALE as well.

I think of it as a more user-friendly IRC that maintains the history of the channel, so everyone can get the context of the conversation, even if they just joined. It's also nice that we can stay plugged in via mobile app or desktop app.

We can start any number of private or public channels and invite others to them. Even when only two members of the team are conversing, the rest of the team can see the conversation and stay looped in. And you can copy and paste the history and use it as the start of documentation on a wiki.

Just food for thought. I'd be happy to learn of other ways folks have collaborated. I think it's important to have the information stored in an organized fashion so anyone can take the lead and it's easy to on-ramp new people.

Lan