251
edits
Community Workshops: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
*Process: | *Process: | ||
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop | **Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop | ||
**Assess overall technical knowledge for each workshop lead | **Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community based on interest and fit within the organization | ||
**Create an internal Engineering Committee to assist with the development of those workshops | **Create an internal Engineering Committee to assist with the development of those workshops | ||
**Bring guidance to the community and clear milestones to keep the community engaged afterward | **Bring guidance to the community and clear milestones to keep the community engaged afterward | ||
| Line 18: | Line 18: | ||
**Jetpack & add-on development | **Jetpack & add-on development | ||
**Engineering (FFx and Platform) | **Engineering (FFx and Platform) | ||
*Tools and Support | |||
**Have a clear channel of distribution and one central location for community members to have easy access to resources | |||
**Build an Engineering Committee | |||
**Series of Tutorial videos (Rainer) | |||
**Provide clear documentation | |||
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible. | |||
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall) | |||