You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* chore(docs): OCM TSC Call
Signed-off-by: Jakob Möller <jakob.moeller@sap.com>
* chore(docs): fixup
Signed-off-by: Jakob Möller <jakob.moeller@sap.com>
* chore(docs): remove non public apeiro link
Signed-off-by: Jakob Möller <jakob.moeller@sap.com>
* chore(docs): add zoom links and notes
Signed-off-by: Jakob Möller <jakob.moeller@sap.com>
* chore(docs): maintain next agenda
Signed-off-by: Jakob Möller <jakob.moeller@sap.com>
---------
Signed-off-by: Jakob Möller <jakob.moeller@sap.com>
- Are there requirements/best-practices of LF/CNCF/NeoNephos?
39
-
- Should creation of branches be restricted?
40
-
- Present LFX tools, e.g. for voting
41
-
- Revisit Developer Certificate of Origin (DCO) and mandatory enforcement
42
-
43
36
## Votes
44
37
45
-
- Gergely Bräutigam as Candidate for TSC Voting Member
46
-
47
-
## Action Items / Notes
38
+
- Gergely Bräutigam as Candidate for TSC Voting Member / Individual Contributor (4/5 Votes)
39
+
- Forbid direct write access by default in the OCM Github Organization for any new repository (5/6 Votes)
40
+
- DCO that is present in current contributing guideline should be maintained and enforced in the OCM Github Organization. (5/6 Votes)
41
+
- All TSC Voting Members are eligible to vote for the list of OCM Github Organization Administrators. (5/6 Votes)
42
+
- Proposal for Github Project Administrators for the OCM Github Organization:
43
+
- Christian Cwienk
44
+
- Fabian Burth
45
+
- Jakob Möller
46
+
(5/6 Votes)
48
47
49
-
###Action Items
48
+
##Previous Action Items
50
49
51
50
-[X] Adjust descriptions to mention that OCM is now owned by NeoNephos, not SAP
52
51
-[X] Priyanka, Tristan: Look at our suggestions / comments on Project Charters
53
-
-[ ] Present LFX Tooling in next meeting, setup for voting offline
54
-
-[ ] Tristan: Will the OCM Github Organization be contributed to NeoNephos / replaced by another Org?
52
+
-[X] Present LFX Tooling in next meeting, setup for voting offline
55
53
-[X] Jakob: Contact Florian Müller regarding the Developer Certificate of Origin (DCO) and the mandatory enforcement as mentioned in the Project Charter.
56
54
-[X] Jakob to copy over internal prepared and accepted Charter into [CHARTER.md](../CHARTER.md) and publish it through the PR.
57
-
-[ ] Christian to confirm ODG based repositories in OCM Github Organization only use Licenses acceptable for reuse under Apache 2.0 or MIT to conform with Charter.
58
55
-[X] Fabian to double-check REUSE files in our OCM Organization for any non-compliant use.
59
56
57
+
## Action Items
58
+
59
+
-[ ] Tristan: Will the OCM Github Organization be contributed to NeoNephos / replaced by another Org?
60
+
- This needs a follow-up / Maybe that's a TAC decision
61
+
- Jakob to keep tracking this
62
+
-[ ] Fabian to check for DCO enforcement in the OCM Github Organization.
63
+
-[ ] Christian to confirm ODG based repositories in OCM Github Organization only use Licenses acceptable for reuse under Apache 2.0 or MIT to conform with Charter.
64
+
- This needs a follow-up
65
+
-[ ] Jakob to ask OSPO when next TAC meeting is organized
66
+
-[ ] Jakob to ask OSPO to make TAC calls public
67
+
-[ ] Gergely to ask OSPO to get access to ApeiroRA community repo (currently internal, reach out for details)
68
+
-[ ] Jakob to add Gergely to the TSC
69
+
60
70
### Notes
61
71
62
-
- The CONTRIBUTING.md file under the OCM Github organization will be adopted as our official contribution guide.
72
+
- Revisit Developer Certificate of Origin (DCO) and mandatory enforcement
73
+
- Present LFX tools, e.g. for voting
74
+
- LFX tools presented and TSC members are onboarded.
75
+
- Gerald asked for LFX project admin access for everyone, but that was rejected by Tristan
76
+
- Currently onboarded are Fabian, Frederic, Gerald, Jakob. (If we have issues with that, we can escalate via LF ticket)
77
+
- PCC Admin Tool Maintenance
78
+
- Formatting Meeting Invites should be possible via HTML syntax (waiting for Gerald to get his access to verify this)
- Are there requirements/best-practices of LF/CNCF/NeoNephos?
85
+
- Should creation of branches be restricted?
86
+
Answer: Github Repo Setup of ApeiroRA (apeirora/community/Project/Project_Security_Guide.md#github-repository-setup) => Guidance is yes we should add branch protection rules.
63
87
64
88
## Next Meeting Agenda
65
89
66
-
- TBD
90
+
- Dependency for Domain Transfer / Mailing List as well as OCM Offboarding from SAP infrastructure.
91
+
- Discuss Github Code Owners "Reset" (Charter states: A Contributor may
92
+
become a Code Owners by a majority approval of the existing Code Owners.)
93
+
- Discuss Rights of Github Maintainers Team in Github Organization ([Maintainers](https://github.com/orgs/open-component-model/teams/maintainers) and [Collaborators](https://github.com/orgs/open-component-model/teams/collaborators))
-[Meeting link to Zoom](https://zoom-lfx.platform.linuxfoundation.org/meeting/92759697838?password=8cbe7411-952b-44d5-9bcf-0816ce9293ad)
6
+
7
+
## Meeting Slides / Content
8
+
9
+
-[docs/steering/meeting-notes](.)
10
+
11
+
## Attendees
12
+
13
+
### Technical Steering Committee Representatives
14
+
15
+
-[ ] Member - Organization
16
+
17
+
Quorum: ✅ / ❌
18
+
19
+
### Non-Voting Representatives or Observing Participants
20
+
21
+
-[ ] Member
22
+
23
+
## Agenda Items
24
+
25
+
- Revisit previous action items
26
+
-[ ] Tristan: Will the OCM Github Organization be contributed to NeoNephos / replaced by another Org?
27
+
- This needs a follow-up / Maybe that's a TAC decision
28
+
- Jakob to keep tracking this
29
+
-[ ] Fabian to check for DCO enforcement in the OCM Github Organization.
30
+
-[ ] Christian to confirm ODG based repositories in OCM Github Organization only use Licenses acceptable for reuse under Apache 2.0 or MIT to conform with Charter.
31
+
- This needs a follow-up
32
+
-[ ] Jakob to ask OSPO when next TAC meeting is organized
33
+
-[ ] Jakob to ask OSPO to make TAC calls public
34
+
-[ ] Gergely to ask OSPO to get access to ApeiroRA community repo (currently internal, reach out for details)
35
+
-[ ] Jakob to add Gergely to the TSC
36
+
- Discuss the relation of Open Delivery Gear and Open Component Model
37
+
- ODG is a project under the OCM umbrella, but not all OCM projects are ODG projects.
38
+
- There is the wish from Christian to have a clear distinction between ODG and OCM and to separate the projects
39
+
- We had an incident in which the DCO enforcement was temporarily suspended in the ODG project
40
+
41
+
## Votes
42
+
43
+
- Remove Temporary Suspension of DCO Enforcement in ODG Project Repositories
44
+
45
+
## Action Items
46
+
47
+
-[ ] Tristan: Will the OCM Github Organization be contributed to NeoNephos / replaced by another Org?
48
+
- This needs a follow-up
49
+
-[ ] Fabian to check for DCO enforcement in the OCM Github Organization.
50
+
-[ ] Christian to confirm ODG based repositories in OCM Github Organization only use Licenses acceptable for reuse under Apache 2.0 or MIT to conform with Charter.
51
+
- This needs a follow-up
52
+
-[ ] Jakob to revisit the OCM Project Onboarding and the Github Org move once the first TAC meeting has taken place.
53
+
54
+
## Next Meeting Agenda
55
+
56
+
-[ ] TODO
57
+
58
+
## Antitrust Policy Notice
59
+
60
+
```text
61
+
Linux Foundation meetings involve participation by industry competitors, and it is the
62
+
intention of the Linux Foundation to conduct all of its activities in accordance with applicable
63
+
antitrust and competition laws. It is therefore extremely important that attendees adhere to
64
+
meeting agendas, and be aware of, and not participate in, any activities that are prohibited
65
+
under applicable US state, federal or foreign antitrust and competition laws.
66
+
67
+
Examples of types of actions that are prohibited at Linux Foundation meetings and in
68
+
connection with Linux Foundation activities are described in the Linux Foundation Antitrust
69
+
Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions
70
+
about these matters, please contact your company counsel, or if you are a member of the
71
+
Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove
72
+
LLP, which provides legal counsel to the Linux Foundation.
0 commit comments