Skip to content

Commit ededb25

Browse files
Merge pull request #9 from pytorch-fdn/reginankenchor-patch-8
Create tuple-oss-request.yml
2 parents cb2298a + 21e6737 commit ededb25

File tree

1 file changed

+90
-0
lines changed

1 file changed

+90
-0
lines changed
Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,90 @@
1+
name: "Tuple OSS Request"
2+
description: "Apply for free Tuple access for your open source team"
3+
title: "Tuple OSS request: <project/repo name>"
4+
labels: ["tac:review", "tuple-oss"]
5+
assignees:
6+
- your-github-handle
7+
8+
body:
9+
- type: markdown
10+
attributes:
11+
value: |
12+
### Open source teams get Tuple for free (forever) 🎉
13+
Maintaining open source projects is hard—doing it alone is even harder. Tuple offers free access to OSS teams that qualify.
14+
15+
Please complete this form so we can review your request.
16+
17+
- type: input
18+
id: owner_email
19+
attributes:
20+
label: Which email address should we invite as the team owner?
21+
description: We'll use this to send the Tuple invite.
22+
placeholder: jane@example.com
23+
validations:
24+
required: true
25+
26+
- type: textarea
27+
id: oss_links
28+
attributes:
29+
label: Where can we find the work your open source team is producing?
30+
description: GitHub, GitLab, or Bitbucket links, please (repos/orgs).
31+
placeholder: |
32+
https://github.com/pytorch-fdn/tac
33+
https://github.com/<org>/<repo>
34+
validations:
35+
required: true
36+
37+
- type: dropdown
38+
id: team_size
39+
attributes:
40+
label: How many people are on your open source core team?
41+
options:
42+
- 1
43+
- 2–3
44+
- 4–6
45+
- 7–10
46+
- 11+
47+
validations:
48+
required: true
49+
50+
- type: input
51+
id: current_pairing
52+
attributes:
53+
label: What does your team currently use for pairing?
54+
placeholder: e.g., Zoom, VS Code Live Share, Tmux, None
55+
validations:
56+
required: false
57+
58+
- type: textarea
59+
id: planned_use
60+
attributes:
61+
label: How are you planning to use Tuple for your open source team?
62+
description: The more detail, the better!
63+
placeholder: e.g., Regular triage sessions, mentoring new contributors, release coordination, remote pairing on PRs, etc.
64+
validations:
65+
required: true
66+
67+
- type: checkboxes
68+
id: eligibility
69+
attributes:
70+
label: Eligibility confirmation
71+
options:
72+
- label: Our primary OSS repo(s) have ≥ 100 stars (or equivalent community adoption).
73+
required: true
74+
- label: Our usage will be for open source work (non-commercial).
75+
required: true
76+
- label: We agree that the team owner email above may receive the Tuple invite.
77+
required: true
78+
79+
- type: textarea
80+
id: notes
81+
attributes:
82+
label: Anything else we should know?
83+
placeholder: Deadlines, special requests, links to press/issues proving adoption, etc.
84+
validations:
85+
required: false
86+
87+
- type: markdown
88+
attributes:
89+
value: |
90+
**Submit your application** using the button below. A TAC reviewer will follow up in this thread.

0 commit comments

Comments
 (0)