This repository has been archived by the owner on Jul 15, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
/
.about.yml
120 lines (99 loc) · 4.06 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
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
---
# .about.yml project metadata
#
# Copy this template into your project repository's root directory as
# .about.yml and fill in the fields as described below.
# This is a short name of your project that can be used as a URL slug.
# (required)
name: pzsvc-exec
# This is the display name of your project. (required)
full_name: pzsvc-exec
# 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: Currently, Piazza has relatively few services available to it, and the Piazza interfaces are both not entirely trivial to use and rapidly changing. Pzsvc-exec provides an easy way to publish any application with a CLI as a Piazza service
# 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: Pzsvc-exec significantly reduces the effort necessary to bring external Piazza services online, especially in the case of things like Beachfront algorithm services, which are often produced by people who are subject matter experts first and developers second.
# What kind of team owns the repository? (required)
# values: guild, working-group, project
owner_type: project
# What is your project's current status? (required)
# values: discovery, alpha, beta, live
stage: alpha
# 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:
pzsvc-exec:
name: Apache-2.0
url: https://github.com/venicegeo/pzsvc-exec/blob/master/LICENSE.txt
# 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:
- National Geospatial-Intelligence Agency
# 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:
- url: mailto:benb@imagemattersllc.com
text: Benjamin Barden
# 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:
- github: bbarden
id: bbarden
role: lead
# What kind of content is contained in the project repository?
# values: app, docs, policy
type: app
# 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: VeniceGeo
# 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:
- url: https://github.com/venicegeo/pzsvc-exec/blob/master/README.md
text: pzsvc-lib Readme
category: text
# 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:
- open-source
# What technologies are used in this project?
stack:
- Golang
# 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: