-
Notifications
You must be signed in to change notification settings - Fork 12
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
Requesting R/W access to directory #5
Comments
Jumping in here, more from a "corporate" perspective; I'm not a developer on this project. The general workflow that we try to encourage for collaborators outside of MITRE (including former MITRE employees) is to use the standard GitHub collaboration pattern: fork, develop, issue pull requests. Can that be used in this case rather than giving R/W access? |
Reasonable to start that way. Considering we are co-authors (lead designers + engineers to be precise) on this project and have RW access to several other active corporate M projects, it's practical we get RW access over time (assuming we're actually contributing). |
Okay, well, let's let @babraham33 weigh in also (who I know is associated with this project). Someone on the MITRE side needs to be engaged with this project and paying attention to incoming PRs. Otherwise this model will fail. @babraham33 : are you content with this approach for now? Circle back with me on Slack if you want to discuss further. |
@jsonin Totally understand where you're coming from and agree your team should continue leading the development of this tool. For now, let's start with the approach that @sbowman-mitre has laid out. |
Ok. What's the process then (or gates or...), on the Corporate M side, in order to garner trust to get RW? |
Oh, I'd say there is no official process, nor any hoops to jump through. AFAIK, it's up to the MITRE POCs for each project make the decision on when & how this is done. Happy developing! |
Pull request for a document that's part of this project... |
Daniel Reeves, Craig McGinley, Sharon Lee, and I designed + engineered this project. Requesting R/W access to keep evolving it.
The text was updated successfully, but these errors were encountered: