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

[no bug] Relaunch and redo the web bug bounty program #4777

Merged
merged 1 commit into from May 3, 2017

Conversation

craigcook
Copy link
Member

Description

Started by @april who did all the real work in #4744, I've only tidied up a few odds and ends and squashed commits.

This completely relaunches the Mozilla web bug bounty program.

It includes:

Updated site lists
Revamped navigation
Completely rewritten documentation
Specific payouts

Bugzilla link

Testing

Checklist

  • Requires l10n changes.
  • Related functional & integration tests passing.

@jeffbryner
Copy link

Thanks @craigcook !

@april
Copy link
Contributor

april commented Apr 20, 2017

Thanks so much, @craigcook! I have a couple other tweaks I might make, but they can wait until after this is pushed so as to make things cleaner. :)

Copy link

@floatingatoll floatingatoll left a comment

Choose a reason for hiding this comment

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

drive-by f+ with some notes for @april

<p>Yes, as long as the bug otherwise meets the published bug bounty
program guidelines. Bugs found in Aurora and Beta releases of Firefox and
program guidelines. Bugs found in Developer Edition and Beta releases of Firefox and
Firefox for Android, EarlyBird and Beta releases of Thunderbird are eligible as
long the bug is reproducible in the latest nightly mozilla-central build and has

Choose a reason for hiding this comment

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

"in the nightly mozilla-central build at the time that the bug is reported", theoretically.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm fine with changing this, but I'd rather it was done in a different bug since it's unrelated to the web bug bounty stuff.

<h4>Bedrock (www)</h4>
<ul>
<li>www.firefox.com</li>
<li>www.getfirefox.com</li>

Choose a reason for hiding this comment

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

Tiny whitespace nitpick: the two lines above are indented differently than the two below.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure what you mean? <li> is supposed to be indented differently, since it's under <ul>.

Copy link
Member Author

Choose a reason for hiding this comment

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

These are indented two spaces, the two items below are indented one space. It is indeed a tiny nitpick but I'll fix it.

</ul>
<p>
<strong>Please do not use automated scanners, create, or modify bugs when testing Bugzilla.</strong>
<br><br>Instead, install your own local copy for testing from <a href="https://github.com/mozilla/webtools-bmo-bugzilla">webtools-bmo-bugzilla</a> or use our <a href="https://bugzilla-dev.allizom.org/">development instance</a>.

Choose a reason for hiding this comment

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

@dylanwh Would you like to add a bit about the vagrantfile here, for "no seriously it's that easy" opportunity?


<h4>Source Control</h4>
<ul>
<li>hg.mozilla.org (excludes website)</li>

Choose a reason for hiding this comment

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

Can this say '(except website, see below)'? I initially interpreted it as a flat denial for https://hg and didn't think "oh, they re-include that later on" at first read.

Copy link
Contributor

Choose a reason for hiding this comment

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

Works for me


<h4>Source Control</h4>
<ul>
<li>hg.mozilla.org (website)</li>

Choose a reason for hiding this comment

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

"(website only)", paired with the prior note.

@@ -28,7 +29,7 @@ <h1 itemprop="name" class="title-shadow-box">Web And Services Bug Bounty Hall of

<p>On behalf of the Mozilla and the millions of people who visit our sites, use Firefox and our other products we would like to thank them for their hard work in helping to make us more secure.</p>

<p>As of this date, we have paid out almost <b>$1,000,000</b> across all of our bounties. Congratulations to everybody who has participated!</p>
<p>As of this date, we have paid out over <b>$1,600,000</b> across all of our bounties. Congratulations to everybody who has participated!</p>

Choose a reason for hiding this comment

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

As of what date?

Copy link
Contributor

Choose a reason for hiding this comment

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

It will always be true as of the present.

Copy link
Contributor

Choose a reason for hiding this comment

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

Not including a date always it to always be accurate and also reduces the number of updates we need to do.

@@ -37,7 +37,7 @@ <h1 itemprop="name" class="title-shadow-box">Client Bug Bounty Program</h1>

<p>Mozilla will pay a bounty for client and security bugs as detailed below. All security bugs must follow the following general criteria to be eligible:</p>

<p> Eligible security bugs may be present in any of the current main development or released versions of Firefox, Thunderbird, Firefox for Android, or FirefoxOS as released by Mozilla Corporation (e.g. Nightly mozilla-central, Firefox Developer Edition, or Beta test versions, as well as the final release product versions)</p>
<p> Eligible security bugs may be present in any of the current main development or released versions of Firefox or Firefox for Android as released by Mozilla Corporation (e.g. Nightly mozilla-central or Beta test versions, as well as the final release product versions)</p>

Choose a reason for hiding this comment

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

One Thunderbird removal occurs here, but this isn't reflected in many other occurrences of Thunderbird elsewhere in the document.

Copy link
Contributor

Choose a reason for hiding this comment

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

As above, I'd like to clean up the client stuff in a different commit, unless it's really necessary right now.

@floatingatoll
Copy link

floatingatoll commented Apr 21, 2017

uh, i'm sorry, i didn't intend to exercise some sort of formal merge approval on this pull request. please don't treat whatever github just decided about my commentary as any sort of "approval to merge" by the project.

@floatingatoll
Copy link

floatingatoll commented Apr 24, 2017 via email

@jpetto jpetto self-assigned this Apr 27, 2017
@jpetto
Copy link
Contributor

jpetto commented May 1, 2017

Code looks good, but a couple pages need a little CSS help:

screen shot 2017-05-01 at 4 33 09 pm
screen shot 2017-05-01 at 4 33 16 pm

@craigcook
Copy link
Member Author

Pesky floats... should rebuild the whole thing with grids...

Fix bug 1357380: Remove Aurora mention from Bug Bounty FAQ page
@jpetto
Copy link
Contributor

jpetto commented May 3, 2017

LGTM!

@jpetto jpetto merged commit f8a2ee5 into mozilla:master May 3, 2017
@craigcook craigcook deleted the bug-bounty-relaunch branch May 3, 2017 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants