You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Participants interested in joining can be added to a contact list (similar to our current framework developer meetings).
Notifications:
1 week prior
24 hours prior
1 hour prior
Communication method: Email
Documentation Meetings
Schedule could be per major release.
Follows the notification process mentioned above.
Developer Meetings
Module Developer Meetings
Periodic meetings addressing module-specific concerns. These could be held on the flip side of the day so to speak or after monthly framework meetings and/or every other meeting for example and discuss more openly things like the Marketplace module developing, etc.
Workshops lasting 1 hour for skill enhancement and knowledge sharing.
Follows the notification process mentioned above.
Framework Meetings
Our current monthly meetings addressing framework-specific concerns.
Follows the notification process mentioned above.
Administrative Workshops
Workshops for understanding and contributing to administration aspects.
These could be to help educate those having to administrate applications built on Oqtane.
Can help give insights to developers looking to contribute.
Follows the notification process mentioned above.
Vendors Showcase Events
Organize events for vendors to showcase products and innovations.
Encourage interaction and collaboration between vendors and developers.
This communication plan aims to create a more inclusive and informed developer community, fostering a collaborative environment for learning, sharing, and showcasing advancements within the framework. Participants can choose their preferred types of meetings and receive timely notifications to ensure engagement.
Additional Notes:
Different members of the community could host these events.
These can all be co-hosted at times as well to help lighten the load of a meeting between more than one community member.
For example Vendors would maybe share an event as a chance to showcase their latest releases along with demonstrations of how to use their product. Events vendors can sign up for, we keep a thread going here on the Oqtane GitHub Discussions to let community members know about each type of meeting. One of the vendors can be the "host" of the event if not someone dedicated.
Another example is the documentation meeting event can be hosted by whomever is handling that project and as the example @iJungleboy could host these meetings or someone else willing. This way @sbwalker is not as needed to be so involved in so many meetings and can focus primarily on the developer related meetings. He can more less help the community out of snags in the other areas when issues arrive from the other meetings.
Administrative workshops could be held by any community member that administrates a lot of Oqtane. Touch on things like creating profile properties, tenants, adding/removing/moving modules and other related administrative tasks for advanced and for the less technical Oqtane application users.
Some types of meetings will be more fun and less technical like vendor showcasing and administration while others will be dealing with some more serious and technical topics such as the developer framework and module meetings.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Enhanced Communication and Collaboration Plan
Scheduled Meetings
Documentation Meetings
Developer Meetings
Module Developer Meetings
Framework Meetings
Administrative Workshops
Vendors Showcase Events
This communication plan aims to create a more inclusive and informed developer community, fostering a collaborative environment for learning, sharing, and showcasing advancements within the framework. Participants can choose their preferred types of meetings and receive timely notifications to ensure engagement.
Additional Notes:
Different members of the community could host these events.
These can all be co-hosted at times as well to help lighten the load of a meeting between more than one community member.
For example Vendors would maybe share an event as a chance to showcase their latest releases along with demonstrations of how to use their product. Events vendors can sign up for, we keep a thread going here on the Oqtane GitHub Discussions to let community members know about each type of meeting. One of the vendors can be the "host" of the event if not someone dedicated.
Another example is the documentation meeting event can be hosted by whomever is handling that project and as the example @iJungleboy could host these meetings or someone else willing. This way @sbwalker is not as needed to be so involved in so many meetings and can focus primarily on the developer related meetings. He can more less help the community out of snags in the other areas when issues arrive from the other meetings.
Administrative workshops could be held by any community member that administrates a lot of Oqtane. Touch on things like creating profile properties, tenants, adding/removing/moving modules and other related administrative tasks for advanced and for the less technical Oqtane application users.
Some types of meetings will be more fun and less technical like vendor showcasing and administration while others will be dealing with some more serious and technical topics such as the developer framework and module meetings.
Beta Was this translation helpful? Give feedback.
All reactions