MeetUp Change Efforts

[luccacabra]

This issue is meant to serve as the main tracking mechanism for all work on the Austin DevOps MeetUp re-org/enhancement/whatever-buzzword-floats-your-boat effort.

I've just jotted down some thoughts/structure that were top of mind. I'll continue to enhance this list/make sub-issues, but please everyone feel free to contribute to the issue in the mean time!

---

Chat Client

In order to reduce noise, increase discoverability, support a SIG structure, and encourage more community interactions, we want to switch to a chat solution that has a organization/channel structure.

Requirements

• Free
• Unlimited Chat History
  • How concerned are we with unlimited message history?
  • Why are we concerned with unlimited message history?
    • Can we address these concerns through another means? (archiving message history periodically, etc)
• Ability for all users to create new channels

  Tasks

  1. • [ ] Define list of must haves and nice to haves for a chat client
  2. • [ ] investigate chat client technologies
     • • [ ] chanty
     • Beta
     • Unlimited message history for free
     • • [ ] rocket.chat
     • Self Hosted
     • Free unlimited everything (whatever your hosting solution can support)
     • • [ ] ryver
     • free tier includes unlimited members/messages/storage
     • integrations use requires paid plan
     • • [ ] slack
     • 10k message history for free
     • • [ ] freenode
  3. • [ ] setup the chat client
  4. • [ ] surface chat client via website/meetup
  5. • [ ] publicize chat client to members
  6. • [ ] add /remind action to #atxdevops with link to new chat client

Website

Tasks

• [ ] Decide on Hosting Solution
• [ ] Landing page
• [ ] SIGs
• [ ] CoC
• [ ] Organizers
• [ ] Formal Contact Forms
  • [ ] Request to Sponsor
  • [ ] Request to Speak
  • [ ] Contact Organizers

Remote Sharing

Tasks

[jjasghar]

My vote will always be for freenode, but i understand that's a limiting our community.

I would like to say that as we figure out what we want to do, we can use the /remind action for a "weekly/every other week" announcement in the #atxdevops channel to announce where we have moved.

[jjasghar]

We should verify https://github.com/Austin-Devops/austin-devops/issues/5 as part of this overarching plan.

[luccacabra]

@jjasghar 👍 to the /remind action in #atxdevops. Would also be nice to implement a similar feature in the new client that acts as a reminder for upcoming meetups.

[moutons]

going to close this since it's been dormant since 2018