tickets/.forgejo/issue_template/rfr.yaml
2026-04-23 20:39:12 +02:00

46 lines
1.8 KiB
YAML

name: Request for resources
about: Ticket for requesting resources in Fedora Infrastructure
title: Request for resources
labels:
- request-for-resources
body:
- type: markdown
attributes:
value: |
This is to gather needed information for granting your project the appropriate resources within the Fedora Infrastructure.
- type: textarea
id: rfr
attributes:
label: request for resources
description: Fill in your information
value: |
Before creating a request, please read the [SOP about Requests for resources](https://docs.fedoraproject.org/en-US/infra/sysadmin_sops/requestforresources/)
Keep the values empty until you know answers - you can go back later and edit the ticket to fill in information as it develops.
## Phase I
**Software:** <mynewservice>
**Advantage for Fedora:** <It will give us unicorns>
**Sponsor:** <someone>
## Phase II
**Upstream source:** https://github.com/...
**Development contacts:** <person1, person2>
**Maintainership contacts:** <person2, person3>
**Load balanceable:** <yes/no>
**Caching:** <yes/no, which paths, ...
## Phase III
**SOP link:** https://docs.fedoraproject.org/infra/sysadmin_guide/...
**Application Security Policy self-evaluation:**
Audit request: https://forge.fedoraproject.org/infra/tickets/issues/... (can be same)
**Audit timeline:** <04-11-2025 - 06-11-2025> (timeline to be provided by the security officer upon audit request)
## Phase IV
**Ansible playbooks:** <ansible/playbooks/groups/myservice.yml>
**Fully rebuilt from ansible:** <yes>
**Production goal:** <08-11-2025>
**Approved audit:** https://forge.fedoraproject.org/infra/tickets/issues/...