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

Changing BugHunt/ Bug Hunt to Bug Bounty #3873

Draft
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

tsu-ki
Copy link
Contributor

@tsu-ki tsu-ki commented Mar 8, 2025

User description

Closes: #3869


PR Type

Enhancement, Documentation


Description

  • Replaced "Bug Hunt/Bughunt" with "Bug Bounty" across templates.

  • Updated translations in multiple locales for consistency.

  • Revised documentation to reflect terminology changes.

  • Enhanced clarity and alignment with updated terminology.


Changes walkthrough 📝

Relevant files
Enhancement
3 files
about.html
Updated terminology to "Bug Bounty" in about page template
+1/-1     
bug_summary.html
Updated email template to use "Bug Bounty Hunters"             
+1/-1     
mobile_about.html
Updated terminology to "Bug Bounty" in mobile about page template
+1/-1     
Documentation
7 files
django.po
Updated German translations for "Bug Bounty" terminology 
+8/-8     
django.po
Updated French translations for "Bug Bounty" terminology 
+1/-1     
django.po
Updated Japanese translations for "Bug Bounty" terminology
+1/-1     
django.po
Updated Chinese translations for "Bug Bounty" terminology
+3/-3     
BltCompanyDashboard.md
Updated documentation to reflect "Bug Bounty" terminology
+2/-2     
BltDetailsFromOwasp.md
Updated details document to use "Bug Bounty" terminology 
+1/-1     
BltStartaBughunt.md
Updated "Start a Bughunt" document to "Bug Bounty"             
+3/-3     

Need help?
  • Type /help how to ... in the comments thread for any questions about PR-Agent usage.
  • Check out the documentation for more information.
  • Copy link
    Contributor

    github-actions bot commented Mar 8, 2025

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    🎫 Ticket compliance analysis 🔶

    3869 - Partially compliant

    Compliant requirements:

    • Replace all instances of "Bug Hunt/Bughunt" with "Bug Bounty" across templates.
    • Update translations in multiple locales for consistency.
    • Revise documentation to reflect terminology changes.
    • Ensure clarity and alignment with updated terminology.

    Non-compliant requirements:

    []

    Requires further human verification:

    []

    ⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ Recommended focus areas for review

    Possible Translation Consistency Issue

    Ensure that the updated terminology "Bug Bounty" is consistently translated across all locales and templates.

    {% env 'PROJECT_NAME' %} {% trans "is a 100% free to use, open-source, non-commercial and non-profit initiative dedicated to improving software security through community-driven bug reporting. Every reward goes directly to the security researchers(bug bounty hunters) who find and report vulnerabilities." %}
    Documentation Clarity

    Verify that the updated documentation reflects the intended changes and maintains clarity in describing the "Bug Bounty" process.

    The "Start a Bughunt" UI component is designed to allow users to initiate a bug hunt within the OWASP Bug Logging Tool (BLT) application. Its primary functionalities include capturing details about the bug hunt, such as the name, URL, file uploads, and setting the prize amount for the bug bounty hunters. This component is crucial for organizations and individuals looking to find and fix bugs in their software by incentivizing external testers.
    
    #### 2. **User Interaction**
    Users interact with this component by filling out a form to start a new bug hunt. The steps involved are as follows:
    1. Enter the name of the bug hunt.
    2. Provide the URL or application name or GPS location related to the issue.
    3. Upload relevant files that may help in identifying or describing the bug.
    4. Optionally, add further descriptions.
    5. Select a subscription plan if applicable.
    6. Set the prize amount for the successful bug bounty hunter using a slider.
    7. Click the "Start Bughunt!" button to submit the form and initiate the bug hunt.
    
    #### 3. **Key Elements**
    - **Name of the Bughunt Field**: An input field where users enter the name of the bug hunt.
    - **URL Field**: An input field for the URL or app name.
    - **File Upload Button**: A button that allows users to upload files relevant to the bug hunt.
    - **Description Field**: A text area for users to provide additional details about the bug hunt.
    - **Subscription Plan Dropdown**: A dropdown menu for selecting the subscription plan.
    - **Prize Amount Slider**: A slider to set the amount of prize money awarded to the successful bug bounty hunter.
    - **Start Bughunt Button**: A button to submit the form and start the bug hunt.

    Copy link
    Contributor

    github-actions bot commented Mar 8, 2025

    PR Code Suggestions ✨

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    Globally replace "Bug Hunt / Bughunt" with "Bug Bounty"
    1 participant