Adds meetup strategy definition #17
Conversation
gundalow
left a comment
gundalow
left a comment
There was a problem hiding this comment.
Thank you for this
- Please run the document through a spell checker (en_US), there are a few typos in this.
- Replace any double spaces with single space.
docs/ansible_meetup_strategy.md
Outdated
|
|
||
| ### Sustainability & Consistency | ||
|
|
||
| Establish a robust organizational structure and a clear, repeatable process (as different steps explained in the toolkit) is to ensure meetups run consistently (e.g., monthly/bi-monthly) without relying solely on a single individual. |
There was a problem hiding this comment.
| Establish a robust organizational structure and a clear, repeatable process (as different steps explained in the toolkit) is to ensure meetups run consistently (e.g., monthly/bi-monthly) without relying solely on a single individual. | |
| Establish a robust organizational structure and a clear, repeatable process (as different steps explained in the toolkit) is to ensure meetups run consistently (e.g., monthly/quarterly) without relying solely on a single individual. |
There was a problem hiding this comment.
Edited accordingly.
docs/ansible_meetup_strategy.md
Outdated
|
|
||
| 1. Code of Conduct (CoC) | ||
|
|
||
| Strict adherence to the Ansible Community Code of Conduct is mandatory for all participants (organizers, sponsors, attendees). The organizer must announce the CoC contact person at every event. |
There was a problem hiding this comment.
| Strict adherence to the Ansible Community Code of Conduct is mandatory for all participants (organizers, sponsors, attendees). The organizer must announce the CoC contact person at every event. | |
| Strict adherence to the [Ansible Code of Conduct](https://docs.ansible.com/ansible/devel/community/code_of_conduct.html) is mandatory for all participants (organizers, sponsors, attendees). The organizer MUST announce the CoC contact person at every event, for example as part of the introduction. |
There was a problem hiding this comment.
Added as suggested.
|
|
||
| 5. Deletion of the any meetup chapter | ||
|
|
||
| If an Ansible meetup group does not host a meetup, event, or workshop for X + months, Ansible or Red Hat may stop paying for the group after informing them by email (using the address on meetup.org). If a group remains inactive for X consecutive months in a calendar year, it shall be deleted. |
There was a problem hiding this comment.
| If an Ansible meetup group does not host a meetup, event, or workshop for X + months, Ansible or Red Hat may stop paying for the group after informing them by email (using the address on meetup.org). If a group remains inactive for X consecutive months in a calendar year, it shall be deleted. | |
| Red Hat reserves the right to stop paying for a Meetup group if it has been inactive for a long time, and doesn't show any signs of returning. This will only happen after the members and any organizer have been consulted. |
There was a problem hiding this comment.
I differ on the phrase of "long term". Instead of the unspecified time frame (mentioned as "long term") , we should have a specified and definite duration (as mentioned in the proposed document). This will help the community on the timeline, what to expect and the level of engagement they need to put in. Specifying the time will help us to avoid the misunderstanding and mismatch of expectation as in the future.
docs/ansible_meetup_strategy.md
Outdated
| 1. Organizer | ||
| 2. Co-Organizer | ||
| 3. Presenter/Speaker | ||
| 4. Sponsor | ||
| 5. Attendee |
There was a problem hiding this comment.
- Pro Admin: Ansible Community Team is the owner of Ansible on Meetup Pro
- Co-Organizer: Local organizers that are hosting events (not sponsors unless they are also hosting events)
- Presenter/Speaker
- Sponsor
- Members: Attendees
There was a problem hiding this comment.
Edited it accordingly.
docs/ansible_meetup_strategy.md
Outdated
|
|
||
| 6. Communication | ||
|
|
||
| Every meetup organizers shall use the regular and/common communication medium in the Ansible ecosystem, i.e Ansible Forum, Bullhorn, Ansible Community Newsletter and the dedicated (ansible social) Matrix rooam. |
There was a problem hiding this comment.
Please include links.
Let's ensure it's easy for people to take the needed actions.
Also include
The auto-generated event pages should have a reply with links to slides and discussions. That is how the organizer should inform all members of the Meetup Group after the event has taken place.
We want the event-slides tag, added. Only a Forum Admin can do that, so they will need to notify us.
There was a problem hiding this comment.
Added the links.
docs/ansible_meetup_strategy.md
Outdated
|
|
||
| Following are the basic role and and permission of the abovementioned stakeholders. | ||
|
|
||
| 1. Organizer |
There was a problem hiding this comment.
This and following section need updating since we've moved to Meetup Pro, I think we will only give co-organizer from now on.
There was a problem hiding this comment.
Does the following roles to be treated as mentioned hereunder in the light of us moving to Meetup pro?
- Organizer to be deemed as the Co-Organizer ; and
- Co-Organizer to be deemed as the Associate Organizer
There was a problem hiding this comment.
In Meetup Pro, these are the permissions:
- Network Admin
- Co-organizer
- Assistant organizer
- Event organizer
- Member
I think think we will only use the last three permissions for members
Documentation
Co-authored-by: John Barker <john@johnrbarker.com>
Co-authored-by: John Barker <john@johnrbarker.com>
Co-authored-by: John Barker <john@johnrbarker.com>
2 participants
This file explains the following :