Skip to content

GSA/Challenge_gov

Folders and files

NameName
Last commit message
Last commit date

Latest commit

3ca1f9b · Dec 30, 2024
Jun 7, 2024
Dec 17, 2024
Jan 21, 2020
Dec 30, 2024
Feb 26, 2024
Jan 10, 2021
Jan 31, 2022
Dec 30, 2024
Nov 20, 2023
Dec 30, 2024
Dec 7, 2020
Feb 25, 2020
Feb 24, 2021
Mar 25, 2020
Mar 6, 2019
Aug 27, 2023
Mar 7, 2019
Aug 12, 2024
Jan 21, 2020
Sep 24, 2023
Jan 19, 2021
Mar 6, 2019
Sep 24, 2023
Feb 13, 2020
Nov 7, 2022
Jun 29, 2023
May 5, 2021
Jul 14, 2023
Dec 30, 2024
Dec 10, 2024
Jul 14, 2023
Jul 14, 2023
Nov 1, 2021
Nov 7, 2022

Repository files navigation

Challenge.Gov is an open source platform that accepts contributions and feedback from our customers.

Code of Conduct

Challenge.Gov is committed to building a safe, welcoming, harassment-free culture for everyone. Challenge.Gov is a part of the Technology Transformation Services (TTS) within the General Services Administration (GSA), and we expect everyone to follow the GSA TTS Code of Conduct.

We encourage you to read this platform’s DEVCONFIG, its LICENSE, and its README. If you want to read more about our open source policy or have questions, check out the GSA’s Open Source Policy (https://open.gsa.gov/oss/ or send us an email.

How you can contribute

Anyone can contribute to Challenge.Gov. Whether it's notifying us of an issue, proposing a new feature, or suggestions for content or workflow improvements, we welcome your ideas on how to improve this site.

First time contributor? We’re here to help guide you through a successful contribution. We review all contributions before merging them into Challenge.Gov. If you’re unsure about anything, just ask (mailto:[email protected]).

Before submitting a contribution, you’ll just need to create a GitHub account or sign in to your existing account.

Submitting bugs and issues

If something isn’t working the way it's supposed to:

Email (mailto:[email protected]) and document how to reproduce the bug. Before submitting a bug, try to recreate it and document the steps we can take to reproduce it. If you can, take screen shots to capture specific details about the bug. This helps us understand its context. We can only fix bugs that we're able to understand and reproduce.

To Contribute to fixing bugs, developing features and enhancements

Before submitting a contribution, you’ll just need to create a GitHub account or sign in to your existing account.

Fork this repo into your GitHub account. Read more about forking a repo on GitHub. Create a branch from production and name it in a way that lightly defines what you’re working on (for example, add-styles). Once you’re ready to submit a pull request, fill out the [pull request template (https://github.com/GSA/Challenge_gov/compare) Submit your pull request against the main branch.

If the pull request is accepted, we will merge the pull request for you.

How we prioritize

Once you’ve submitted a contribution, we'll review the code and triage it based on the following considerations:

  1. Severity: What type of functionality is impacted? Is there a workaround?
  2. Priority: Does this align with our vision and roadmap goals?
  3. Size: Can we accomplish this in a 2 week sprint or will this take longer?

Note: We prioritize issues that affect accessibility, user experience, and system security.

These considerations help us decide if and when we can work on the issue. If the issue is accepted, we will schedule them for an upcoming 2-week sprint.

Common terms

There can be a lot of jargon when discussing how you can contribute to Challenge.Gov. We’ve included some common terms we use below.