Skip to content

Commit 6be7c1e

Browse files
authored
Create Project-Contribution.md
1 parent f563063 commit 6be7c1e

File tree

1 file changed

+60
-0
lines changed

1 file changed

+60
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
name: "\U0001F58AProject Contribution and Onboarding"
3+
about: To Contribute a Project to FINOS
4+
title: 'Project Contribution and Onboarding'
5+
labels: ''
6+
assignees: 'maoo, aitana16'
7+
8+
---
9+
10+
# Identify project meta
11+
- [ ] Project Title
12+
- [ ] Category and sub-category (for FINOS Landscape)
13+
- [ ] Existing code or new Github repository
14+
- [ ] Existing code releases (and which artifact repositories are used)
15+
- [ ] Team composition: lead maintainer and other maintainers
16+
- [ ] Meetings (existing/yes/no)
17+
- [ ] Meeting minutes, agenda, attendance tracking (existing/yes/no)
18+
- [ ] Continuous Integration (existing/yes/no)
19+
- [ ] Documentation website (existing/yes/no)
20+
21+
# Maintainers, contributors and CLAs
22+
- [ ] For each maintainer identified in the previous step, collect: the following info:
23+
- Fullname
24+
- GitHub username
25+
- Corporate email address
26+
- [ ] Identify other existing contributors (assuming there's a contribution history (eg Git history)
27+
- [ ] Check if maintainers and other contributors are all covered by FINOS CLA
28+
- [ ] Engage with FINOS Legal team to figure out what’s needed to cover all maintainers and contributors with FINOS CLA
29+
- [ ] Reach out to contributors and employers to coordinate CLA signatures
30+
31+
# Code validation (only if code is contributed)
32+
- [ ] The codebase doesn’t have HIGH or CRITICAL CVEs across direct and transitive libraries
33+
- [ ] The codebase doesn’t have any unfriendly licenses across direct and transitive libraries
34+
- [ ] (optional - if a build system is provided) The build process runs successfully
35+
- [ ] The codebase doesn’t include any patent or copyright that conflicts with FINOS Governance and bylaws (to be validated with FINOS Legal team)
36+
- [ ] The codebase complies with FINOS Project Blueprint
37+
38+
# Voting
39+
- [ ] FINOS accepts the contribution and the project can be created (or transferred)
40+
41+
# Code transfer and infra setup
42+
- [ ] (optional) Transfer code assets under github.com/finos
43+
- [ ] Add project to metadata
44+
- [ ] Add identities, orgs and affiliations to metadata
45+
- [ ] Invite GitHub usernames to GitHub FINOS Org
46+
- [ ] Apply project blueprint contents - see ODP docs
47+
- [ ] Update project badge
48+
- [ ] Add logo to FINOS landscape
49+
- [ ] Add project maintainers emails to [email protected] list
50+
- [ ] Add project maintainers GitHub usernames to the project-maintainers Team
51+
- [ ] Enable security vulnerabilities scanning
52+
- [ ] Enable meeting attendance tracking (optional)
53+
54+
# Announcement
55+
- [ ] Work with FINOS marketing to send out announcement to [email protected]
56+
57+
# Onboarding and training
58+
- [ ] FINOS Project Governance
59+
- [ ] FINOS Project Lifecycle
60+
- [ ] ODP Training

0 commit comments

Comments
 (0)