Add issue templates
This adds a default, a planned outage and a oidc client request templates for issues. It likely needs adjustment, but it probibly is good enough to try now. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit is contained in:
parent
685fafb113
commit
d47ec24793
4 changed files with 123 additions and 0 deletions
11
.forgejo/issue_template/config.yml
Normal file
11
.forgejo/issue_template/config.yml
Normal file
|
|
@ -0,0 +1,11 @@
|
|||
# Disable blank issues to force template usage
|
||||
blank_issues_enabled: false
|
||||
|
||||
# Provide alternative support channels
|
||||
contact_links:
|
||||
- name: Fedora Infrastructure Matrix Room
|
||||
url: https://matrix.to/#/#admin:fedoraproject.org
|
||||
about: Join the Fedora Infrastructure Matrix room
|
||||
- name: infrastructure-team tag on the Support Forum
|
||||
url: https://discussion.fedoraproject.org/tags/c/project/7/infrastructure-team
|
||||
about: posts in the Fedora community forum with the infrastructure-team tag
|
||||
20
.forgejo/issue_template/default.yaml
Normal file
20
.forgejo/issue_template/default.yaml
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
name: Infrastructure ticket
|
||||
about: File a Fedora Infrastructure ticket here with your request
|
||||
labels:
|
||||
- "Needs Review"
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
If your issue is for a security matter or deails with sensitive information
|
||||
please mail admin@fedoraproject.org to arrange a way to share it in private.
|
||||
|
||||
Please check https://www.fedorastatus.org for known outages
|
||||
before filing a ticket about an outage.
|
||||
- type: textarea
|
||||
id: ticket-request
|
||||
attributes:
|
||||
label: Description of request
|
||||
description: What is your request?
|
||||
placeholder: |
|
||||
Describe your request, and if there's a deadline, please note it (YYYY/MM/DD)
|
||||
46
.forgejo/issue_template/oidc-request.yaml
Normal file
46
.forgejo/issue_template/oidc-request.yaml
Normal file
|
|
@ -0,0 +1,46 @@
|
|||
name: OpenID Connect Enrollment
|
||||
about: Ticket to coordinate adding a application to our oidc provider
|
||||
title: OpenID Connect Enrollmen
|
||||
labels:
|
||||
- needs_review
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
This is to gather needed information for us to onboard your
|
||||
application to use the fedoraproject OIDC for authentication.
|
||||
- type: textarea
|
||||
id: oidc-enroll
|
||||
attributes:
|
||||
label: oidc-enroll
|
||||
description: Fill in your information
|
||||
value: |
|
||||
To help us register your application in our OIDC service, we need some
|
||||
information from you:
|
||||
|
||||
Note: all the default values provided here are based on the default choice/
|
||||
implementation of flask-oidc. If you do not use this library you may have to
|
||||
refer to the documentation of your library.
|
||||
|
||||
Some generic information first:
|
||||
- What is the application main URL?
|
||||
- Who will be the main contact for the application, or will this be core
|
||||
infrastructure?
|
||||
- What privacy policy will be applicable to the application, or will this be
|
||||
the standard Fedora privacy policy?
|
||||
|
||||
Some more OIDC specific information then:
|
||||
- Which redirect URI(s) will the application use?
|
||||
- flask-oidc defaults to: ``<APPLICATION_URL>/oidc_callback``
|
||||
but it's configurable (so double-check)
|
||||
- Does the application need the user names, or will an application-specific
|
||||
pseudonym suffice?
|
||||
- ie: using flask-oidc, do you ever rely on ``OIDC.user_getfield('sub')`` to
|
||||
get the user's username. If not, this question likely does not matter for
|
||||
your application
|
||||
- Which authorization flow does the application use?
|
||||
- flask-oidc: authorization_code
|
||||
- Which token authentication method does the application use?
|
||||
- flask-oidc: client_secret_post
|
||||
- Which response type does the application rely on?
|
||||
- flask-oidc: Code
|
||||
46
.forgejo/issue_template/planned-outage.yaml
Normal file
46
.forgejo/issue_template/planned-outage.yaml
Normal file
|
|
@ -0,0 +1,46 @@
|
|||
|
||||
name: Planned outage
|
||||
about: Ticket for a planned outage
|
||||
title: Planned Outage - NAME - YYY-MM-DD HH:MM UTC
|
||||
labels:
|
||||
- needs_review
|
||||
- outage
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
This issue type is to schedule and track a planned outage.
|
||||
- type: textarea
|
||||
id: outage
|
||||
attributes:
|
||||
label: planned outage
|
||||
description: Modify this template with your outage info
|
||||
value: |
|
||||
Planned Outage - NAME - YYYY-MM-DD HH:MM UTC
|
||||
|
||||
There will be an outage starting at YYYY-MM-DD HH:MMUTC,
|
||||
which will last approximately X hours.
|
||||
|
||||
To convert UTC to your local time, take a look at
|
||||
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
|
||||
or run:
|
||||
|
||||
date -d 'YYYY-MM-DD HH:MM UTC'
|
||||
|
||||
Reason for outage:
|
||||
|
||||
<describe reason for outage here>
|
||||
|
||||
Affected Services:
|
||||
|
||||
<describe services that will be affected>
|
||||
|
||||
Ticket Link:
|
||||
|
||||
https://pagure.io/fedora-infrastructure/issue/NNNN
|
||||
|
||||
Please join #admin:fedoraproject.org / #noc:fedoraproject.org on matrix.
|
||||
or add comments to this ticket for more information or feedback.
|
||||
|
||||
Updated status for this outage may be available at
|
||||
https://www.fedorastatus.org/
|
||||
Loading…
Add table
Add a link
Reference in a new issue