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

docs(processes): bug bounty program #532

Merged
merged 12 commits into from
Jun 28, 2019
Merged

Conversation

lirantal
Copy link
Member

Addresses #503 and #525 for a list of module criteria for monetary rewards in the bug bounty program

@lirantal lirantal added the process processes and documentation label May 13, 2019
@lirantal lirantal self-assigned this May 13, 2019
@lirantal
Copy link
Member Author

I would also like us to capture and finalize the bounty rates so we can actually kick it off.

Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, generally looks good but @Trott's comments should be addressed and I also made a few suggestions.

Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, generally looks good. We should incorporate @Trott's suggestions and I made a couple of suggestions as well.

@lirantal
Copy link
Member Author

Cool thanks for the feedback @Trott & @mhdawson ❤️
Will hopefully be able to get to it in a couple of days while in between travels.

lirantal and others added 4 commits May 18, 2019 15:00
Co-Authored-By: Rich Trott <rtrott@gmail.com>
Co-Authored-By: Rich Trott <rtrott@gmail.com>
Co-Authored-By: Rich Trott <rtrott@gmail.com>
@lirantal
Copy link
Member Author

I think we're at a good point here to land so will wait till we talk it out in the monthly agenda call before merging.

@sam-github
Copy link
Contributor

Discussed at #541 , removing from agenda (but please add back if it should be discussed again).

@lirantal
Copy link
Member Author

We currently have the PR mentioning the actual modules:

## Modules list 

 The following is a list of modules which are eligible in the monetary reward due to their maintainers
explicitly confirming to collaborate with the working group and security researchers to receive and 
resolve security reports.

 * lodash
* jQuery
* node-red
* hapi (all packages under the GH org)
* Koajs (all packages under the GH org)
* Webpack
* ESLint
* socket.io

So before landing this PR we need to get agreement from their maintainers.
How do we go about reaching out to them? for bigger projects like webpack/lodash there is mostly a team than a BDFL

@sam-github
Copy link
Contributor

I'd suggest opening an issue on their repo and ask if they want to participate. That should reach the right people, or get a response about who the right people are.

@lirantal
Copy link
Member Author

Cool. We've already got a few I'll proceed with contacting some of those in the WIP

* Koajs (all packages under the GH org)
* Webpack
* ESLint
* socket.io
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably include links to the github organizations.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree although I'd be ok with the links being added in a follow on PR.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added links to the github repos

@lirantal lirantal merged commit 94a63fa into master Jun 28, 2019
@lirantal lirantal deleted the lirantal-processes-bug-bounty branch June 28, 2019 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
process processes and documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants