Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IDEA: "Adopt a Framework" Campaign #88

Open
mattaereal opened this issue Jan 5, 2025 · 2 comments
Open

IDEA: "Adopt a Framework" Campaign #88

mattaereal opened this issue Jan 5, 2025 · 2 comments
Assignees
Labels
help wanted Extra attention is needed question Further information is requested

Comments

@mattaereal
Copy link
Collaborator

So, Devcon has passed, with it, the official introduction of SEAL's Frameworks to the community. The amount of positive feedback I (and many of the other pinnipeds) have received for this initiative is impressive. I have even been told that many organizations have started to follow it (which worries me because it's still in a very early stage).

We can get to the next level of improvement quickly, but we're still low on collaboration. Not only do we get a few interested in collaborating (despite the apparent interest), but only a fraction of them follow up on this commitment. This is probably a direct consequence of the nature of this project, writing documents.

If you're reading this and identify with what's written above, feedback on how to improve collaboration is more than welcome, particularly right here.

Now, back to the main topic. I have been considering strategies to delegate a portion of the responsibilities to the community. One of the first ones that comes to mind is something like "Adopt a Framework" Campaign.

The concept is similar to an ambassador program, where contributors act as "champions" or "stewards" of the framework. Their role would involve recruiting collaborators to enhance their framework, with each GitHub issue related to that framework falling under their realm, and the rest of the core team will be there to assist. By distributing this type of work among peers, tasks become more focused and specific, rather than overly broad. This approach allows minds to work more effectively, resulting in fewer distractions and greater concentration.

I'm going to pitch it to the rest of SEAL and the rest of the core team of Frameworks to hear their opinions, and we can later discuss how to properly execute it. I also devise a future where we get articles written on our blog by one of each of the champions to spread visibility on best practices of each of the frameworks. I think one per month is doable.

Communication:
"Be the voice of [Framework Name]" or "Join the Framework Advocacy Movement."
Titles/badges like Framework Stewards or Security Framework Ambassadors.

Benefits:
There should be some, at least symbolic. Small monetary incentives, tickets to conferences, or invitations to private SEAL events.

@mattaereal mattaereal added help wanted Extra attention is needed question Further information is requested labels Jan 5, 2025
@mattaereal mattaereal self-assigned this Jan 5, 2025
@devtooligan
Copy link

I think it's a cool idea. I think that's a great way to divide up the responsibility.

Some people may want to help but not feel confident to take on any framework. We can also request "General Volunteers" that can just help in general with triaging tickets, reviewing prs, and participating in discussions. Of course, anyone is free to do that now but people are more likely to get involved if they are given a title or a badge.

@Robert-MacWha
Copy link
Contributor

Sub-issue: #88

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants