Skip to content

Commit 93c0035

Browse files
authored
chore: Update community files and workflows for org migration (#387)
1 parent f66dc23 commit 93c0035

12 files changed

+148
-100
lines changed

.github/CODEOWNERS

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
#####################
2+
# Main global owner #
3+
#####################
4+
5+
*

.github/ISSUE_TEMPLATE/bug_report.md

-41
This file was deleted.

.github/ISSUE_TEMPLATE/bug_report.yml

+70
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
---
2+
name: 🐛 Bug report
3+
description: Create a report to help us improve
4+
labels:
5+
- bug
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
Thanks for taking the time to fill out this bug report!
11+
12+
Before you continue filling out this report, please take a moment to check that your bug has not been [already reported on GitHub][issue search] 🙌
13+
14+
Remember to redact any sensitive information such as authentication credentials and/or license keys!
15+
16+
**Note:** If you are seeking community support or have a question, please consider starting a new thread via [GitHub discussions][discussions] or the [NGINX Community forum][forum].
17+
18+
[issue search]: https://github.com/nginx/nginx-s3-gateway/issues
19+
[discussions]: https://github.com/nginx/nginx-s3-gateway/discussions
20+
[forum]: https://community.nginx.org
21+
22+
- type: textarea
23+
id: overview
24+
attributes:
25+
label: Bug Overview
26+
description: A clear and concise overview of the bug.
27+
placeholder: When I do "X" with the NGINX S3 gateway, "Y" happens instead of "Z".
28+
validations:
29+
required: true
30+
31+
- type: textarea
32+
id: behavior
33+
attributes:
34+
label: Expected Behavior
35+
description: A clear and concise description of what you expected to happen.
36+
placeholder: When I do "X" with the NGINX S3 gateway, I expect "Z" to happen.
37+
validations:
38+
required: true
39+
40+
- type: textarea
41+
id: steps
42+
attributes:
43+
label: Steps to Reproduce the Bug
44+
description: Detail the series of steps required to reproduce the bug.
45+
placeholder: When I use the NGINX S3 gateway using "X", the NGINX S3 gateway fails with "Y" error message. If I check the terminal outputs and/or logs, I see the following info.
46+
validations:
47+
required: true
48+
49+
- type: textarea
50+
id: environment
51+
attributes:
52+
label: Environment Details
53+
description: Please provide details about your environment.
54+
value: |
55+
- Version of the S3 container used: [DockerHub/GCR]
56+
- Commit/Tag (if building the NGINX S3 gateway from source):
57+
- Version of NGINX Open Source or NGINX Plus: [OSS/Plus]
58+
- Version of NGINX JavaScript: [0.8.8/0.8.7/etc...]
59+
- Target deployment platforms [e.g. AWS/GCP/local cluster/etc...]:
60+
- S3 backend implementation: [e.g. AWS, Ceph, NetApp StorageGrid, etc...]
61+
- Authentication method: [e.g. IAM, IAM with Fargate, IAM with K8S, AWS Credentials, etc...]
62+
validations:
63+
required: true
64+
65+
- type: textarea
66+
id: context
67+
attributes:
68+
label: Additional Context
69+
description: Add any other context about the problem here.
70+
placeholder: Feel free to add any other context/information/screenshots/etc... that you think might be relevant to this issue in here.

.github/ISSUE_TEMPLATE/config.yml

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
blank_issues_enabled: false
3+
contact_links:
4+
- name: 💬 Talk to the NGINX community!
5+
url: https://community.nginx.org
6+
about: A community forum for NGINX users, developers, and contributors
7+
- name: 📝 Code of Conduct
8+
url: https://www.contributor-covenant.org/version/2/1/code_of_conduct
9+
about: NGINX follows the Contributor Covenant Code of Conduct to ensure a safe and inclusive community
10+
- name: 💼 For commercial & enterprise users
11+
url: https://www.f5.com/products/nginx
12+
about: F5 offers a wide range of NGINX products for commercial & enterprise users

.github/ISSUE_TEMPLATE/feature_request.md

-23
This file was deleted.
+41
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
name: ✨ Feature request
3+
description: Suggest an idea for this project
4+
labels:
5+
- enhancement
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
Thanks for taking the time to fill out this feature request!
11+
12+
Before you continue filling out this request, please take a moment to check that your feature has not been [already requested on GitHub][issue search] 🙌
13+
14+
**Note:** If you are seeking community support or have a question, please consider starting a new thread via [GitHub discussions][discussions] or the [NGINX Community forum][forum].
15+
16+
[issue search]: https://github.com/nginx/nginx-s3-gateway/issues
17+
[discussions]: https://github.com/nginx/nginx-s3-gateway/discussions
18+
[forum]: https://community.nginx.org
19+
20+
- type: textarea
21+
id: overview
22+
attributes:
23+
label: Feature Overview
24+
description: A clear and concise description of what the feature request is.
25+
placeholder: I would like the NGINX S3 gateway to be able to do "X".
26+
validations:
27+
required: true
28+
29+
- type: textarea
30+
id: alternatives
31+
attributes:
32+
label: Alternatives Considered
33+
description: Detail any potential alternative solutions/workarounds you've used or considered.
34+
placeholder: I have done/might be able to do "X" with the NGINX S3 gateway by doing "Y".
35+
36+
- type: textarea
37+
id: context
38+
attributes:
39+
label: Additional Context
40+
description: Add any other context about the problem here.
41+
placeholder: Feel free to add any other context/information/screenshots/etc... that you think might be relevant to this feature request here.

.github/pull_request_template.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Describe the use case and detail of the change. If this PR addresses an issue on
77
Before creating a pull request (PR), run through this checklist and mark each as complete:
88

99
- [ ] I have read the [contributing guidelines](/CONTRIBUTING.md).
10-
- [ ] I have signed the [F5 Contributor License Agreement (CLA)](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md).
10+
- [ ] I have signed the [F5 Contributor License Agreement (CLA)](https://github.com/f5/f5-cla/blob/main/docs/f5_cla.md).
1111
- [ ] The PR title follows the [Conventional Commits specification](https://www.conventionalcommits.org/en/v1.0.0/).
1212
- [ ] If applicable, I have added tests that prove my fix is effective or that my feature works.
1313
- [ ] If applicable, I have checked that any relevant tests pass after adding my changes.

.github/workflows/f5-cla.yml .github/workflows/f5_cla.yml

+6-5
Original file line numberDiff line numberDiff line change
@@ -19,20 +19,21 @@ jobs:
1919
if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have hereby read the F5 CLA and agree to its terms') || github.event_name == 'pull_request_target'
2020
uses: contributor-assistant/github-action@ca4a40a7d1004f18d9960b404b97e5f30a505a08 # v2.6.1
2121
with:
22-
# Any pull request targeting the following branch will trigger a CLA check.
23-
branch: main
2422
# Path to the CLA document.
25-
path-to-document: https://github.com/f5/.github/blob/main/CLA/cla-markdown.md
23+
path-to-document: https://github.com/f5/f5-cla/blob/main/docs/f5_cla.md
2624
# Custom CLA messages.
27-
custom-notsigned-prcomment: '🎉 Thank you for your contribution! It appears you have not yet signed the F5 Contributor License Agreement (CLA), which is required for your changes to be incorporated into an F5 Open Source Software (OSS) project. Please kindly read the [F5 CLA](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md) and reply on a new comment with the following text to agree:'
25+
custom-notsigned-prcomment: '🎉 Thank you for your contribution! It appears you have not yet signed the [F5 Contributor License Agreement (CLA)](https://github.com/f5/f5-cla/blob/main/docs/f5_cla.md), which is required for your changes to be incorporated into an F5 Open Source Software (OSS) project. Please kindly read the [F5 CLA](https://github.com/f5/f5-cla/blob/main/docs/f5_cla.md) and reply on a new comment with the following text to agree:'
2826
custom-pr-sign-comment: 'I have hereby read the F5 CLA and agree to its terms'
2927
custom-allsigned-prcomment: '✅ All required contributors have signed the F5 CLA for this PR. Thank you!'
3028
# Remote repository storing CLA signatures.
3129
remote-organization-name: f5
3230
remote-repository-name: f5-cla-data
31+
# Branch where CLA signatures are stored.
32+
branch: main
3333
path-to-signatures: signatures/signatures.json
3434
# Comma separated list of usernames for maintainers or any other individuals who should not be prompted for a CLA.
35-
allowlist: 4141done, alessfg, dekobon, bot*
35+
# NOTE: You will want to edit the usernames to suit your project needs.
36+
allowlist: bot*
3637
# Do not lock PRs after a merge.
3738
lock-pullrequest-aftermerge: false
3839
env:

.github/workflows/ossf-scorecard.yml .github/workflows/ossf_scorecard.yml

+4-17
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,11 @@ name: OSSF Scorecard
44
on:
55
# For Branch-Protection check. Only the default branch is supported. See https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection.
66
branch_protection_rule:
7-
push:
8-
branches: [main]
97
# To guarantee Maintained check is occasionally updated. See https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained.
108
schedule:
119
- cron: "0 0 * * 1"
10+
push:
11+
branches: [main]
1212
workflow_dispatch:
1313
# Declare default permissions as read only.
1414
permissions: read-all
@@ -17,16 +17,10 @@ jobs:
1717
name: Scorecard analysis
1818
runs-on: ubuntu-24.04
1919
permissions:
20-
# Needed if using Code Scanning alerts
20+
# Needed if using Code Scanning alerts.
2121
security-events: write
22-
# Needed for GitHub OIDC token if publish_results is true
22+
# Needed for GitHub OIDC token if publish_results is true.
2323
id-token: write
24-
# Uncomment the permissions below if installing on a private repository.
25-
# contents: read
26-
# actions: read
27-
# issues: read # To allow GraphQL ListCommits to work
28-
# pull-requests: read # To allow GraphQL ListCommits to work
29-
# checks: read # To detect SAST tools
3024
steps:
3125
- name: Check out the codebase
3226
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
@@ -38,14 +32,7 @@ jobs:
3832
with:
3933
results_file: results.sarif
4034
results_format: sarif
41-
# (Optional) fine-grained personal access token. Uncomment the `repo_token` line below if:
42-
# - You want to enable the Branch-Protection check on a *public* repository.
43-
# - You are installing the OSSF Scorecard on a *private* repository.
44-
# To create the PAT, follow the steps in https://github.com/ossf/scorecard-action#authentication-with-fine-grained-pat-optional.
45-
# repo_token: ${{ secrets.SCORECARD_TOKEN }}
46-
4735
# Publish the results for public repositories to enable scorecard badges. For more details, see https://github.com/ossf/scorecard-action#publishing-results.
48-
# For private repositories, `publish_results` will automatically be set to `false`, regardless of the value entered here.
4936
publish_results: true
5037

5138
# Upload the results as artifacts (optional). Commenting out will disable uploads of run results in SARIF format to the repository Actions tab.

CONTRIBUTING.md

+1-3
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,7 @@ The following is a set of guidelines for contributing to this project. We really
1414

1515
## Getting Started
1616

17-
Follow the instructions on the README's [Getting Started Guide](/README.md#Getting-Started) section to get this project up and running.
18-
19-
<!-- ### Project Structure (OPTIONAL) -->
17+
Refer to the [Getting Started Guide](docs/getting_started.md) for how to build and run the gateway.
2018

2119
## Contributing
2220

README.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22
[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/nginxinc/nginx-s3-gateway/badge)](https://securityscorecards.dev/viewer/?uri=github.com/nginxinc/nginx-s3-gateway)
33
[![Project Status: Active – The project has reached a stable, usable state and is being actively developed.](https://www.repostatus.org/badges/latest/active.svg)](https://www.repostatus.org/#active)
44
[![Community Support](https://badgen.net/badge/support/community/cyan?icon=awesome)](/SUPPORT.md)
5+
[![Community Forum](https://img.shields.io/badge/community-forum-009639?logo=discourse&link=https%3A%2F%2Fcommunity.nginx.org)](https://community.nginx.org)
6+
[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/license/apache-2-0)
57
[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)](/CODE_OF_CONDUCT.md)
68

79
# NGINX S3 Gateway
@@ -103,4 +105,4 @@ Please see the [contributing guide](/CONTRIBUTING.md) for guidelines on how to b
103105

104106
[Apache License, Version 2.0](/LICENSE)
105107

106-
&copy; [F5, Inc.](https://www.f5.com/) 2020 - 2024
108+
&copy; [F5, Inc.](https://www.f5.com/) 2020 - 2025

SUPPORT.md

+5-9
Original file line numberDiff line numberDiff line change
@@ -4,19 +4,15 @@
44

55
We use GitHub for tracking bugs and feature requests related to this project.
66

7-
Don't know how something in this project works? Curious if this project can achieve your desired functionality? Please open an issue on GitHub with the label `question`.
7+
Don't know how something in this project works? Curious if this project can achieve your desired functionality? Please open an issue on GitHub with the label `question`. Alternatively, start a GitHub discussion!
88

99
## NGINX Specific Questions and/or Issues
1010

1111
This isn't the right place to get support for NGINX specific questions, but the following resources are available below. Thanks for your understanding!
1212

13-
### Community Slack
13+
### Community Forum
1414

15-
We have a community [Slack](https://nginxcommunity.slack.com/)!
16-
17-
If you are not a member, click [here](https://community.nginx.org/joinslack) to sign up. (Let us know if the link does not seem to be working at <[email protected]>!)
18-
19-
Once you join, check out the `#beginner-questions` and `nginx-users` channels :)
15+
We have a community [forum](https://community.nginx.org/)! If you have any questions and/or issues, try checking out the [`Troubleshooting`](https://community.nginx.org/c/troubleshooting/8) and [`How do I...?`](https://community.nginx.org/c/how-do-i/9) categories. Both fellow community members and NGINXers might be able to help you! :)
2016

2117
### Documentation
2218

@@ -30,8 +26,8 @@ Want to get in touch with the NGINX development team directly? Try using the rel
3026

3127
## Contributing
3228

33-
Please see the [contributing guide](/CONTRIBUTING.md) for guidelines on how to best contribute to this project.
29+
Please see the [contributing guide](/CONTRIBUTING.md) or the [Getting Started](/README.md#getting-started) guide, for guidelines on how to best contribute to this project.
3430

3531
## Community Support
3632

37-
This project does **not** offer commercial support. Community support is offered on a best effort basis through either GitHub issues/PRs/discussions or via any of our active communities.
33+
This project does **not** offer commercial support. Community support is offered on a best effort basis through either GitHub issues/PRs/discussions or through any of our active communities.

0 commit comments

Comments
 (0)