Restructure FOSS Community NSBM
Work through the forum. (Issue a badge according to their contributions)
Through replying threads and contributing to the foss, Mozilla projects,
They can build up their profile as a Volunteer, Moderator, Coordinator, and Core Member.
As the open-source constitution should open every event detail and its’ process.
As the event details, we can include that how many volunteers are there and their contributions’ screenshots.
Sahould create a Complain Suggestion Form for 24 hours publicly.
Monthly Meetup - As the next step we should inform about this monthly meetup by Sending an email like Newsletters.
Privacy is the most important, according to Mozillians.
Print no photography badge for the physical event. (if there is a no photography badge anyone can’t take a photo without permission)
So, therefore, we should make a privacy team.
- OWASP Community - should build a website as “hack.fossnsbm.org”. There is a dashboard with an update of whether our services are working or not.
The Privacy team’s duty is protecting our services from cyber-attacks.
If someone changes some settings regarding the fossnsbm.org, It should inform the Privacy team.
Should create a unique template for the Foss Blog.
We have to make a digital marketing team.
Should verify a stable platform for the conference calls of Foss Community.
Use auth0 for user managing.
Suggestions of the Privacy team should come up through the voting from other volunteers.
Thumbnail template for the blog.
Create a post-approval system for the blog.
Should plan an event from Devoke Community.
Use open collective to make budget publicity.
All suggestions are welcome