forked from 18F/bug-bounty
/
.about.yml
100 lines (81 loc) · 3.11 KB
/
.about.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
---
# .about.yml project metadata
#
# This is a short name of your project that can be used as a URL slug. (required)
name: bug-bounty
# This is the display name of your project. (required)
full_name: Bug Bounty
# What is the problem your project solves? What is the solution? Use the format shown below. The #dashboard team will gladly help you put this together for your project. (required)
description: A microsite for our bug bounty
# What is the measurable impact of your project? Use the format shown below. The #dashboard team will gladly help you put this together for your project. (required)
impact:
# What kind of team owns the repository? (required)
# values: guild, working-group, project
owner_type: \#cybersec
# What is your project's current status? (required)
# values: discovery, alpha, beta, live
stage: discovery
# Should this repo have automated tests? If so, set to `true`. (required)
# values: true, false
testable: true
# What are the licenses that apply to the project and/or its components? (required)
# Items by property name pattern:
# .*:
# name: Name of the license from the Software Package Data Exchange (SPDX): https://spdx.org/licenses/
# url: URL for the text of the license
licenses:
placeholder_label:
# Who is the partner for your project? (Use the full name of the partner documented here: https://github.com/18F/dashboard/blob/staging/_data/partners.yml)
partners:
-
# The main point of contact(s) and/or the issue reporting system for your project, and either a `mailto:` link or URL for each contact.
# Items:
# - url: URL for the link
# text: Anchor text for the link
contact:
-
# Who are the team members on your project? You can specify GitHub usernames, email addresses, or other organizational usernames. (required)
# Items:
# - github: GitHub user name
# id: Internal team identifier/user name
# role: Team member's role; leads should be designated as 'lead'
team:
-
# What kind of content is contained in the project repository?
# values: app, docs, policy
type:
# What are the key milestones you've achieved recently?
milestones:
-
# Name of the main project repo if this is a sub-repo; name of the grouplet repo if this is a working group/guild subproject
parent:
# What are the links to key artifacts associated with your project? e.g. the production site, documentation.
# Items:
# - url: URL for the link
# text: Anchor text for the link
# category: Type of the link
links:
-
# What tags does your organization's blog associate with your project? You can find a list of 18F blog tags here: https://18f.gsa.gov/tags/
blogTag:
-
# What technologies are used in this project?
stack:
-
# What are the services used to supply project status information?
# Items:
# - name: Name of the service
# category: Type of the service
# url: URL for detailed information
# badge: URL for the status badge
services:
-
# Organizations or individuals who have adopted the project for their own use
# Items:
# - id: The name of the organization or individual
# url: A URL to the user's version of the project
users:
-
# Tags that describe the project or aspects of the project
tags:
-