Skip to content

Latest commit

 

History

History
986 lines (913 loc) · 70.7 KB

MEETINGS_TC_2022_1H.md

File metadata and controls

986 lines (913 loc) · 70.7 KB
tags: Technical Committee

Technical Committee Meetings 2022 1H

HackMD documents

Quick links

Logistics

Agenda and Notes

Please do not update the meeting agenda and notes directly on GitHub and instead use the document on HackMD.io in order to prevent notes getting out of sync.

June 30, 2022

Participants

  • TC Attendees
    • Azeem Ahmad, not present
    • Emil Bäckmark, present
    • Magnus Bäck, present
    • Mattias Linnér, present
    • Tobias Persson, not present

Agenda and Notes

Action Items

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Tobias: Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
    • [Fatih] Still pending unfortunately. Will come back to this as soon as I get some time.
    • Update 2021-08-12: Question sent to Fatih but no reply yet.
    • Update 2021-09-09: Future communication to be done directly with Nordix via their mailing list.
    • Update 2021-10-07: Cluster running, access control situation unclear.
    • Update 2021-10-21: Tobias and Mattias have SSH access to one of the hosts but we don't appear to have k8s access.
    • Update 2022-01-27: Probably simple to fix, Tobias to ping Robert at Nordix.
    • Update 2022-02-17: Tobias has pinged Robert. Waiting for response.
  • Magnus: Propose new policy of how to deal with the issue requirement for new development.
  • TC: Write issue about describing process for archiving projects and do archive eiffel-remrem-shared
  • TC: Add all TC members to all existing Eiffel Google groups
  • TC: Look into proposal made in the maintainer role presentation from the summit.
  • Emil/Mattias: Make sure questions from the CDF summit presentation are taken care of in SIG Events.
    • This can be transformed into an issue
  • Magnus: Collect feedback from the Python Podcast.__init__ interview to see if there are concrete steps we can take to improve how things are presented or explained.
  • Magnus: Go through current action list and suggest which should be migrated to issues in the community repo.
  • Magnus: Could policies like "repo maintainers should also be watchers" be enforced with e.g. github.com/github/safe-settings or github.com/probot/settings?
  • Magnus: Convert "Watch the videos" section on https://eiffel-community.github.io/ to "Media" (or similar) and add a podcast link there.
  • Magnus: Announce podcast episode on LinkedIn.
  • Mattias: Promote external repos in landscape picture and link to them from https://github.com/eiffel-community. Convert landscape picture to SVG so that we can add clickable links.
  • Magnus: Run through checklist for Azeem.
    • Almost done; the YouTube ownership invite is still pending.
  • Mattias: Locate good place to post potential master thesis projects.
  • Emil: Send summit placeholder calendar invite as soon as dates have been confirmed.
  • Emil/Mattias: Sort out with Ericsson Software Technology whether Nordix can be used for an ArangoDB evaluation.
  • Magnus: Comment in existing PR which features that aren't necessary in a minimal ER lookup API spec.

June 16, 2022

Participants

  • TC Attendees
    • Azeem Ahmad, present
    • Emil Bäckmark, present
    • Magnus Bäck, present
    • Mattias Linnér, present
    • Tobias Persson, not present

Agenda and Notes

  • Rollcall, All
    • We have quorum.
  • Approval of Previous Minutes, All
    • Approved.
  • Agenda Bashing, All
    • Approved.
  • Action Item Review, All
  • Updates from CDF sig-events, Emil & Mattias
    • CDEventsCon outcome
    • cdCon & CDEvents Contrib Summit outcome
  • Follow-up from community meeting about deployment events
  • Next community meeting on June 23rd?
    • Decision: Continue deployment event discussion.
  • Summer plans for TC
    • Vacations:
      • Emil vacation w28-31
      • Magnus vacation w28-31
      • Azeem vacation w25-30
      • Mattias vacation w25
    • Cancel regular TC meetings on July 14 and 28.
  • How to involve new organizations in the community
    • Could they present in a community meeting what they use Eiffel for?
    • Ask if they can present at a community meeting Aug 18 or 25 and we'll adjust the TC meeting schedule based on that.
  • Generate diagram with allowed event links?
  • Out of time, postponed: ArangoDB PoC
  • Out of time, postponed: Generate HTML pages from our MarkDown files?
    • CDEvents as an example
  • Out of time, postponed: Graphite.dev
    • Any good news?
  • Out of time, postponed: PRs and issues

Action Items

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Tobias: Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
    • [Fatih] Still pending unfortunately. Will come back to this as soon as I get some time.
    • Update 2021-08-12: Question sent to Fatih but no reply yet.
    • Update 2021-09-09: Future communication to be done directly with Nordix via their mailing list.
    • Update 2021-10-07: Cluster running, access control situation unclear.
    • Update 2021-10-21: Tobias and Mattias have SSH access to one of the hosts but we don't appear to have k8s access.
    • Update 2022-01-27: Probably simple to fix, Tobias to ping Robert at Nordix.
    • Update 2022-02-17: Tobias has pinged Robert. Waiting for response.
  • Magnus: Propose new policy of how to deal with the issue requirement for new development.
  • TC: Write issue about describing process for archiving projects and do archive eiffel-remrem-shared
  • TC: Add all TC members to all existing Eiffel Google groups
  • TC: Look into proposal made in the maintainer role presentation from the summit.
  • Emil/Mattias: Make sure questions from the CDF summit presentation are taken care of in SIG Events.
    • This can be transformed into an issue
  • Magnus: Collect feedback from the Python Podcast.__init__ interview to see if there are concrete steps we can take to improve how things are presented or explained.
  • Magnus: Go through current action list and suggest which should be migrated to issues in the community repo.
  • Magnus: Could policies like "repo maintainers should also be watchers" be enforced with e.g. github.com/github/safe-settings or github.com/probot/settings?
  • Magnus: Convert "Watch the videos" section on https://eiffel-community.github.io/ to "Media" (or similar) and add a podcast link there.
  • Magnus: Is there a LinkedIn post for the podcast episode that we can share with the Eiffel account?
    • Apparently not.
  • Magnus: Announce podcast on mailing list.
    • Done.
  • Magnus: Announce podcast episode on LinkedIn.
  • Mattias: Promote external repos in landscape picture and link to them from https://github.com/eiffel-community. Convert landscape picture to SVG so that we can add clickable links.
  • Magnus: Add item on https://github.com/eiffel-community/community/blob/master/howtos/introduction-of-a-new-tc-member.md to add new TC member as LinkedIn superuser. Also remove billing address item.
  • Magnus: Add new TC member checklist item for adding Slack ownership and TC Tasks board on GitHub.
  • Magnus: Run through checklist for Azeem.
    • Almost done; the YouTube ownership invite is still pending.
  • Magnus: Contact Ewelina about inviting the TC as owners of the Slack channel.
    • 2022-06-16: All current TC members are now Slack workspace owners. Magnus is the singular primary owner (the only one who can demote owners).
  • Mattias: Locate good place to post potential master thesis projects.
  • Emil: Move next community meeting from May 27(?) to June 9.

June 2, 2022

Meeting canceled due to too few participants

May 19, 2022

Participants

  • TC Attendees
    • Azeem Ahmad, present
    • Emil Bäckmark, not present
    • Magnus Bäck, present
    • Mattias Linnér, present
    • Tobias Persson, present

Agenda and Notes

  • Rollcall, All
    • We have quorum.
  • Approval of Previous Minutes, All
    • Approved.
  • Agenda Bashing, All
    • Approved.
  • Action Item Review, All
  • Updates from CDF sig-events, Emil & Mattias
    • Emil attended the SIG events day at KubeCon on May 17.
  • Slack channel ownership
    • Action Magnus: Contact Ewelina about inviting the TC as owners.
  • Meetup recap and follow-up
    • Action Mattias: Locate good place to post potential master thesis projects.
  • Next community meeting
    • Action Emil: Move next community meeting from May 27(?) to June 9.
    • Decision: Topic for the meeting is continuing the deployment event discussion.
  • PRs and issues

Action Items

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Tobias: Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
    • [Fatih] Still pending unfortunately. Will come back to this as soon as I get some time.
    • Update 2021-08-12: Question sent to Fatih but no reply yet.
    • Update 2021-09-09: Future communication to be done directly with Nordix via their mailing list.
    • Update 2021-10-07: Cluster running, access control situation unclear.
    • Update 2021-10-21: Tobias and Mattias have SSH access to one of the hosts but we don't appear to have k8s access.
    • Update 2022-01-27: Probably simple to fix, Tobias to ping Robert at Nordix.
    • Update 2022-02-17: Tobias has pinged Robert. Waiting for response.
  • Magnus: Propose new policy of how to deal with the issue requirement for new development.
  • TC: Write issue about describing process for archiving projects and do archive eiffel-remrem-shared
  • TC: Add all TC members to all existing Eiffel Google groups
  • TC: Look into proposal made in the maintainer role presentation from the summit.
  • Emil/Mattias: Make sure questions from the CDF summit presentation are taken care of in SIG Events.
    • This can be transformed into an issue
  • Magnus: Collect feedback from the Python Podcast.__init__ interview to see if there are concrete steps we can take to improve how things are presented or explained.
  • Magnus: Go through current action list and suggest which should be migrated to issues in the community repo.
  • Magnus: Could policies like "repo maintainers should also be watchers" be enforced with e.g. github.com/github/safe-settings or github.com/probot/settings?
  • Magnus: Convert "Watch the videos" section on https://eiffel-community.github.io/ to "Media" (or similar) and add a link there.
  • Magnus: Is there a LinkedIn post for the podcast episode that we can share with the Eiffel account?
  • Magnus: Announce podcast on mailing list.
  • Mattias: Promote external repos in landscape picture and link to them from https://github.com/eiffel-community. Convert landscape picture to SVG so that we can add clickable links.
  • TC: Add item on https://github.com/eiffel-community/community/blob/master/howtos/introduction-of-a-new-tc-member.md to add new TC member as LinkedIn superuser. Also remove billing address item.
  • TC: Add new TC member checklist item for adding Slack ownership and TC Tasks board on GitHub.
  • Magnus: Run through checklist for Azeem.
    • Almost done; a couple of pending invites that Azeem needs to respond to, and Emil or Daniel needs to add him to the Youtube channel. PR for GOVERNANCE.md sent.
  • Magnus: Contact Ewelina about inviting the TC as owners of the Slack channel.
  • Mattias: Locate good place to post potential master thesis projects.
  • Emil: Move next community meeting from May 27(?) to June 9.

May 5, 2022

Participants

  • TC Attendees
    • Azeem Ahmad, present
    • Emil Bäckmark, present
    • Magnus Bäck, present
    • Mattias Linnér, present
    • Tobias Persson, present

Agenda and Notes

  • Rollcall, All
    • We have quorum.
  • Approval of Previous Minutes, All
    • Approved
  • Agenda Bashing, All
    • Approved
  • Action Item Review, All
  • Updates from CDF sig-events, Emil & Mattias
    • Emil to talk about Eiffel at CDEventsCon, as part of KubeCon.
  • TC introduction for new members
  • Add authorities according to New TC member checklist
    • Action TC: Add new TC member checklist item for adding Slack ownership and TC Tasks board on GitHub.
    • Action Magnus: Run through checklist for Azeem.
  • TC co-chair election
    • Decide on meeting or send out for nominations? See governance process.
    • Decision: Skip the TC chair election and use the exceptional process where TC itself decides the chairs.
    • Emil and Magnus are both willing to continue as chairs. Nobody opposed these nominations.
    • Decision: Emil and Magnus were elected as chairs.
  • Meetup planning
  • Next community meeting
    • Currently booked at May 26th, but it is public holiday. Cancel or reschedule? June 9th? To be decided on meetup?
    • Decision: Decide during meetup whether to cancel or postpone to June 9th.
  • PRs and issues

Action Items

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Tobias: Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
    • [Fatih] Still pending unfortunately. Will come back to this as soon as I get some time.
    • Update 2021-08-12: Question sent to Fatih but no reply yet.
    • Update 2021-09-09: Future communication to be done directly with Nordix via their mailing list.
    • Update 2021-10-07: Cluster running, access control situation unclear.
    • Update 2021-10-21: Tobias and Mattias have SSH access to one of the hosts but we don't appear to have k8s access.
    • Update 2022-01-27: Probably simple to fix, Tobias to ping Robert at Nordix.
    • Update 2022-02-17: Tobias has pinged Robert. Waiting for response.
  • Magnus: Propose new policy of how to deal with the issue requirement for new development.
  • TC: Write issue about describing process for archiving projects and do archive eiffel-remrem-shared
  • TC: Add all TC members to all existing Eiffel Google groups
  • TC: Look into proposal made in the maintainer role presentation from the summit.
  • Emil/Mattias: Make sure questions from the CDF summit presentation are taken care of in SIG Events.
    • This can be transformed into an issue
  • Magnus: Collect feedback from the Python Podcast.__init__ interview to see if there are concrete steps we can take to improve how things are presented or explained.
  • Magnus: Go through current action list and suggest which should be migrated to issues in the community repo.
  • Magnus: Could policies like "repo maintainers should also be watchers" be enforced with e.g. github.com/github/safe-settings or github.com/probot/settings?
  • Magnus: Convert "Watch the videos" section on https://eiffel-community.github.io/ to "Media" (or similar) and add a link there.
  • Magnus: Is there a LinkedIn post for the podcast episode that we can share with the Eiffel account?
  • Magnus: Announce podcast on mailing list.
  • Mattias: Promote external repos in landscape picture and link to them from https://github.com/eiffel-community. Convert landscape picture to SVG so that we can add clickable links.
  • TC: Add item on https://github.com/eiffel-community/community/blob/master/howtos/introduction-of-a-new-tc-member.md to add new TC member as LinkedIn superuser. Also remove billing address item.
  • Emil: Talk to new TC member Azeem about meeting time and make sure he's invited.
  • TC: Add new TC member checklist item for adding Slack ownership and TC Tasks board on GitHub.
  • Magnus: Run through checklist for Azeem.

April 21, 2022

Participants

  • TC Attendees
    • Emil Bäckmark, present
    • Magnus Bäck, present
    • Mattias Linnér, present
    • Tobias Persson, present

Agenda and Notes

  • Rollcall, All
    • We have quorum.
  • Approval of Previous Minutes, All
    • Approved.
  • Agenda Bashing, All
    • Approved.
  • Action Item Review, All
  • Updates from CDF sig-events, Emil & Mattias
  • TC elections
    • Decide on way forward and document it in a similar way as was done last year
    • Decision: As per the charter, if there are less than 7 nominees to the TC all candidates are automatically elected. Nominees, and hence future TC members, are:
    • Action Emil: Talk to new TC member Azeem about meeting times and make sure he's invited to future meetings.
  • Topic for upcoming April 28 monthly community meeting
    • Cancel due to lack of suitable topics.
  • Meetup planning
  • PRs and issues

Action Items

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Tobias: Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
    • [Fatih] Still pending unfortunately. Will come back to this as soon as I get some time.
    • Update 2021-08-12: Question sent to Fatih but no reply yet.
    • Update 2021-09-09: Future communication to be done directly with Nordix via their mailing list.
    • Update 2021-10-07: Cluster running, access control situation unclear.
    • Update 2021-10-21: Tobias and Mattias have SSH access to one of the hosts but we don't appear to have k8s access.
    • Update 2022-01-27: Probably simple to fix, Tobias to ping Robert at Nordix.
    • Update 2022-02-17: Tobias has pinged Robert. Waiting for response.
  • Magnus: Propose new policy of how to deal with the issue requirement for new development.
  • TC: Write issue about describing process for archiving projects and do archive eiffel-remrem-shared
  • TC: Add all TC members to all existing Eiffel Google groups
  • TC: Look into proposal made in the maintainer role presentation from the summit.
  • Emil/Mattias: Make sure questions from the CDF summit presentation are taken care of in SIG Events.
    • This can be transformed into an issue
  • Magnus: Collect feedback from the Python Podcast.__init__ interview to see if there are concrete steps we can take to improve how things are presented or explained.
  • Magnus: Go through current action list and suggest which should be migrated to issues in the community repo.
  • Magnus: Could policies like "repo maintainers should also be watchers" be enforced with e.g. github.com/github/safe-settings or github.com/probot/settings?
  • Magnus: Convert "Watch the videos" section on https://eiffel-community.github.io/ to "Media" (or similar) and add a link there.
  • Magnus: Is there a LinkedIn post for the podcast episode that we can share with the Eiffel account?
  • Magnus: Announce podcast on mailing list.
  • Mattias: Promote external repos in landscape picture and link to them from https://github.com/eiffel-community. Convert landscape picture to SVG so that we can add clickable links.
  • TC: Add item on https://github.com/eiffel-community/community/blob/master/howtos/introduction-of-a-new-tc-member.md to add new TC member as LinkedIn superuser. Also remove billing address item.
  • Emil: Talk to new TC member Azeem about meeting time and make sure he's invited.

April 7, 2022

Participants

  • TC Attendees
    • Emil Bäckmark, present
    • Magnus Bäck, present
    • Mattias Linnér, present
    • Tobias Persson, present

Agenda and Notes

Action Items

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Tobias: Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
    • [Fatih] Still pending unfortunately. Will come back to this as soon as I get some time.
    • Update 2021-08-12: Question sent to Fatih but no reply yet.
    • Update 2021-09-09: Future communication to be done directly with Nordix via their mailing list.
    • Update 2021-10-07: Cluster running, access control situation unclear.
    • Update 2021-10-21: Tobias and Mattias have SSH access to one of the hosts but we don't appear to have k8s access.
    • Update 2022-01-27: Probably simple to fix, Tobias to ping Robert at Nordix.
    • Update 2022-02-17: Tobias has pinged Robert. Waiting for response.
  • Magnus: Propose new policy of how to deal with the issue requirement for new development.
  • TC: Write issue about describing process for archiving projects and do archive eiffel-remrem-shared
  • TC: Add all TC members to all existing Eiffel Google groups
  • Magnus: Add TC members' email addresses to the GOVERNANCE document (in the table of TC members).
  • TC: Look into proposal made in the maintainer role presentation from the summit.
  • Emil/Mattias: Make sure questions from the CDF summit presentation are taken care of in SIG Events.
    • This can be transformed into an issue
  • Mattias: Figure out how to deal with Eiffel-adjacent repos not in the eiffel-community organization. Should they be made visible? How? Prepare a proposal on this.
  • Magnus: Collect feedback from the Python Podcast.__init__ interview to see if there are concrete steps we can take to improve how things are presented or explained.
  • Magnus: Go through current action list and suggest which should be migrated to issues in the community repo.
  • Magnus: Could policies like "repo maintainers should also be watchers" be enforced with e.g. github.com/github/safe-settings or github.com/probot/settings?
  • Magnus: Check within Axis for recommendations on which file types require copyright notices.
    • No stated policy. Asked for general guidance in our Teams team for OSS.
    • Discussed on TC meeting. No further action at this point. If we see files in PRs without copyright notices it's fine to comment on it but let's not spend more time on it here.
  • Magnus: Convert "Watch the videos" section on https://eiffel-community.github.io/ to "Media" (or similar) and add a link there.
  • Magnus: Is there a LinkedIn post for the podcast episode that we can share with the Eiffel account?
  • Magnus: Announce podcast on mailing list.
  • Mattias: Promote external repos in landscape picture and link to them from https://github.com/eiffel-community. Convert landscape picture to SVG so that we can add clickable links.
  • TC: Add item on https://github.com/eiffel-community/community/blob/master/howtos/introduction-of-a-new-tc-member.md to add new TC member as LinkedIn superuser. Also remove billing address item.

March 24, 2022

Participants

  • TC Attendees
    • Emil Bäckmark, present
    • Magnus Bäck, present
    • Mattias Linnér, present
    • Tobias Persson, present

Agenda and Notes

  • Rollcall, All
    • We have quorum.
  • Approval of Previous Minutes, All
    • Approved.
  • Agenda Bashing, All
    • Approved.
  • Action Item Review, All
  • Updates from CDF sig-events, Emil & Mattias
    • Many upcoming conferences where CDEvents will be a topic.
  • Meetup planning
    • https://hackmd.io/wG7lMI0DQhex-c8o6t-3Rg
    • Virtual or physical only?
      • Primarily physical, but we're open to making accommodations for remote participation.
      • Mattias/Emil: Talk to potentially interested Ericsson folks about the agenda to gauge interest.
      • Tobias: Add 1-2 sentences about each agenda item.
      • Mattias: Prepare poll with agenda items and remote/physical preferences.
      • Emil: Announce on March 30
    • Agenda updates?
    • Promote the meetup to the community
      • eiffel-community mailing list
      • Slack
      • LinkedIn
  • TC elections - https://hackmd.io/@eiffel-community/H1Oyst_4u
    • Present 2022 Eiffel TC eligible community members list to Eiffel TC
      • No exemption requests so list is complete.
    • Plan to send out nomination mail to community on March 30th
  • Monthly meetup March 31st
    • Emil: Update meeting invite
  • Where should we add the link to the Python.__init__ podcast?
    • Magnus: Convert "Watch the videos" section on https://eiffel-community.github.io/ to "Media" (or similar) and add a link there.
    • Magnus: Is there a LinkedIn post for the podcast episode that we can share with the Eiffel account?
    • Magnus: Announce on mailing list.
  • Should we add the TC mailing list to any of our documents? It's only visible in the summit call.
    • Yes, add email address in the same place where the TC members are listed. There's an existing action to add the addresses of the TC members and we can add the list address there too.
  • Fork external repos into eiffel-community?
    • No forks.
    • Mattias: Promote in landscape picture and link to it from https://github.com/eiffel-community. Convert landscape picture to SVG so that we can add clickable links.
  • Planning of the next protocol edition
  • Has anybody experience of https://opensource.guide/
  • Add info about making TC members Super admins on LinkedIn when new TC is elected
  • PRs and issues

Action Items

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Tobias: Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
    • [Fatih] Still pending unfortunately. Will come back to this as soon as I get some time.
    • Update 2021-08-12: Question sent to Fatih but no reply yet.
    • Update 2021-09-09: Future communication to be done directly with Nordix via their mailing list.
    • Update 2021-10-07: Cluster running, access control situation unclear.
    • Update 2021-10-21: Tobias and Mattias have SSH access to one of the hosts but we don't appear to have k8s access.
    • Update 2022-01-27: Probably simple to fix, Tobias to ping Robert at Nordix.
    • Update 2022-02-17: Tobias has pinged Robert. Waiting for response.
  • Magnus: Propose new policy of how to deal with the issue requirement for new development.
  • TC: Write issue about describing process for archiving projects and do archive eiffel-remrem-shared
  • TC: Add all TC members to all existing Eiffel Google groups
  • Magnus: Add TC members' email addresses to the GOVERNANCE document (in the table of TC members).
  • TC: Look into proposal made in the maintainer role presentation from the summit.
  • Emil/Mattias: Make sure questions from the CDF summit presentation are taken care of in SIG Events.
    • This can be transformed into an issue
  • Mattias: Figure out how to deal with Eiffel-adjacent repos not in the eiffel-community organization. Should they be made visible? How? Prepare a proposal on this.
  • Magnus: Collect feedback from the Python Podcast.__init__ interview to see if there are concrete steps we can take to improve how things are presented or explained.
  • Mattias: Create proposal for event type categorization.
  • Magnus: Go through current action list and suggest which should be migrated to issues in the community repo.
  • Emil: Confirm with Henning, Daniel, and Kristofer that it's okay to remove them as GitHub organization owners.
  • Magnus: Could policies like "repo maintainers should also be watchers" be enforced with e.g. github.com/github/safe-settings or github.com/probot/settings?
  • Magnus: Check within Axis for recommendations on which file types require copyright notices.
  • TC: Propose good dates for the May meetup.
    • (Mattias) First meeting for the new TC is May 5th. Do we want to meet in person then?
  • Mattias: Send email to mailing list and ask for topic proposals.
  • Magnus: Convert "Watch the videos" section on https://eiffel-community.github.io/ to "Media" (or similar) and add a link there.
  • Magnus: Is there a LinkedIn post for the podcast episode that we can share with the Eiffel account?
  • Magnus: Announce podcast on mailing list.
  • Mattias: Promote external repos in landscape picture and link to them from https://github.com/eiffel-community. Convert landscape picture to SVG so that we can add clickable links.

March 10, 2022

Participants

  • TC Attendees
    • Emil Bäckmark, present
    • Magnus Bäck, present
    • Mattias Linnér, present
    • Tobias Persson, present

Agenda and Notes

  • Rollcall, All
    • We have quorum.
  • Approval of Previous Minutes, All
    • Approved.
  • Agenda Bashing, All
    • Approved.
  • Action Item Review, All
  • Updates from CDF sig-events, Emil & Mattias
  • Should we grant access to the eiffel-community organization to graphite.dev? (Tobias)
    • Yes.
  • Community meeting follow up and plan for next (March 31st)
    • Event Repository evolution? Interesting but requires a lot of preparations.
    • Possibly .NET SDK demo?
    • Protocol workshop and planning of upcoming editions?
    • Action Mattias: Send email to mailing list and ask for topic proposals.
    • Final decision on next week's meeting.
  • Fatih will talk about the coming elections (joining at 13:30)
  • Out of time, postponed: Should we add the TC mailing list to any of our documents? It's only visible in the summit call.
  • Out of time, postponed: Where should we add the link to the Python.__init__ podcast? Mattias
  • Postponed to next week's meeting: May meeting planning
  • Out of time, postponed: Fork external repos into eiffel-community?
  • Out of time, postponed: Planning of the next protocol edition
  • Out of time, postponed: PRs and issues

Action Items

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Tobias: Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
    • [Fatih] Still pending unfortunately. Will come back to this as soon as I get some time.
    • Update 2021-08-12: Question sent to Fatih but no reply yet.
    • Update 2021-09-09: Future communication to be done directly with Nordix via their mailing list.
    • Update 2021-10-07: Cluster running, access control situation unclear.
    • Update 2021-10-21: Tobias and Mattias have SSH access to one of the hosts but we don't appear to have k8s access.
    • Update 2022-01-27: Probably simple to fix, Tobias to ping Robert at Nordix.
    • Update 2022-02-17: Tobias has pinged Robert. Waiting for response.
  • Magnus: Propose new policy of how to deal with the issue requirement for new development.
  • TC: Write issue about describing process for archiving projects and do archive eiffel-remrem-shared
  • TC: Add all TC members to all existing Eiffel Google groups
  • Magnus: Add TC members' email addresses to the GOVERNANCE document (in the table of TC members).
  • TC: Look into proposal made in the maintainer role presentation from the summit.
  • Emil/Mattias: Make sure questions from the CDF summit presentation are taken care of in SIG Events.
    • This can be transformed into an issue
  • Mattias: Figure out how to deal with Eiffel-adjacent repos not in the eiffel-community organization. Should they be made visible? How? Prepare a proposal on this.
  • Fatih: Update timeline based on discussion (move elegible candidate earlier and take Easter into account) and get back to TC via mail for final confirmation.
  • Fatih: Locate script for finding eligible candidates and create PR in the community repo.
  • Magnus: Collect feedback from the Python Podcast.__init__ interview to see if there are concrete steps we can take to improve how things are presented or explained.
  • Mattias: Create proposal for event type categorization.
  • Magnus: Go through current action list and suggest which should be migrated to issues in the community repo.
  • Emil: Confirm with Henning, Daniel, and Kristofer that it's okay to remove them as GitHub organization owners.
  • Magnus: Could policies like "repo maintainers should also be watchers" be enforced with e.g. github.com/github/safe-settings or github.com/probot/settings?
  • Magnus: Check within Axis for recommendations on which file types require copyright notices.
  • TC: Propose good dates for the May meetup.
    • (Mattias) First meeting for the new TC is May 5th. Do we want to meet in person then?
  • TC: Sort out the exact quorum requirements.
  • Mattias: Send email to mailing list and ask for topic proposals.

February 24, 2022

Participants

  • TC Attendees
    • Emil Bäckmark, not present
    • Magnus Bäck, present
    • Mattias Linnér, present
    • Tobias Persson, not present

Agenda and Notes

  • Rollcall, All
    • 50% presence, quorum situation somewhat unclear. Assuming no quorum.
    • TC: Sort out the exact requirements.
  • Approval of Previous Minutes, All
    • No quorum, skipping.
  • Agenda Bashing, All
    • Approved after postponing "May meeting planning" and "Planning of the next protocol edition" to the next meeting.
  • Action Item Review, All
  • Updates from CDF sig-events, Emil & Mattias
    • Work on defining event fundamentals and possible link between events is ongoing.
  • Show and explain the current status of misalignment with REMReM. REMReM semantics pom.xml
    • eiffel-remrem-semantics v2.1.1 has 2.2.0 in pom.xml, resulting in incorrectly versioned artifacts when building from the v2.1.1 commit. The v2.1.1 unintentionally contains the Paris edition commit that was intended for v2.2.0.
  • PRs and issues

Action Items

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Tobias: Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
    • [Fatih] Still pending unfortunately. Will come back to this as soon as I get some time.
    • Update 2021-08-12: Question sent to Fatih but no reply yet.
    • Update 2021-09-09: Future communication to be done directly with Nordix via their mailing list.
    • Update 2021-10-07: Cluster running, access control situation unclear.
    • Update 2021-10-21: Tobias and Mattias have SSH access to one of the hosts but we don't appear to have k8s access.
    • Update 2022-01-27: Probably simple to fix, Tobias to ping Robert at Nordix.
    • Update 2022-02-17: Tobias has pinged Robert. Waiting for response.
  • Magnus: Propose new policy of how to deal with the issue requirement for new development.
  • TC: Write issue about describing process for archiving projects and do archive eiffel-remrem-shared
  • TC: Add all TC members to all existing Eiffel Google groups
  • Tobias: Amend the repo creation checklist in the eiffel-repository-template repo to state that TC members should be added as owners to any created Google Groups.
  • Magnus: Add TC members' email addresses to the GOVERNANCE document (in the table of TC members).
  • TC: Look into proposal made in the maintainer role presentation from the summit.
  • Emil/Mattias: Make sure questions from the CDF summit presentation are taken care of in SIG Events.
    • This can be transformed into an issue
  • Mattias: Figure out how to deal with Eiffel-adjacent repos not in the eiffel-community organization. Should they be made visible? How? Prepare a proposal on this.
  • Magnus: Create issues in all repos with .travisci.yml files to have them change to GitHub Actions.
  • Tobias: Add an organization README file (docs).
  • Fatih: Update timeline based on discussion (move elegible candidate earlier and take Easter into account) and get back to TC via mail for final confirmation.
  • Fatih: Locate script for finding eligible candidates and create PR in the community repo.
  • Magnus: Collect feedback from the interview to see if there are concrete steps we can take to improve how things are presented or explained.
  • Mattias: Create proposal for event type categorization.
  • Magnus: Can discussion items be added to a GitHub project (along with PRs and issues)?
    • No, discussion threads can have labels but can't be connected to projects.
  • Magnus: Go through current action list and suggest which should be migrated to issues in the community repo.
  • Emil: Confirm with Henning, Daniel, and Kristofer that it's okay to remove them as GitHub organization owners.
  • Magnus: Could policies like "repo maintainers should also be watchers" be enforced with e.g. github.com/github/safe-settings or github.com/probot/settings?
  • Tobias: Move SECURITY.md from the community repo to the .github repo.
  • Mattias: Check Ericsson email thread about which file types require copyright notices.

    • Hi Mattias,

      Think it very much is up to each and every open source project to decide. However if you have many different individuals/companies doing contributions the files soon become cluttered with copyright statements so one might wan to find other solutions. This blog from LF touches on the subject; https://www.linuxfoundation.org/en/blog/copyright-notices-in-open-source-software-projects/

      The readme file does not need a copyright statement as I see it. The indication of license should suffice.

  • Magnus: Check within Axis for recommendations on which file types require copyright notices.
  • TC: Propose good dates for the May meetup.
  • TC: Sort out the exact quorum requirements.

February 10, 2022

Participants

  • TC Attendees
    • Emil Bäckmark, present
    • Magnus Bäck, present
    • Mattias Linnér, present
    • Tobias Persson, present

Agenda and Notes

  • Rollcall, All
    • We have quorum.
  • Approval of Previous Minutes, All
    • Approved.
  • Agenda Bashing, All
    • Approved.
  • Action Item Review, All
  • Updates from CDF sig-events, Emil & Mattias
  • Summit planning
    • Physical two-day meetup first half of May, focused on workshopping rather than presentations.
    • Lund or Linköping or somewhere in between?
    • Summit in the autumn - physical or combined? 2-3 days. In October?
    • To be followed up next TC meeting
    • Action: TC to propose good dates for meetup
  • Show what Ericsson is prioritizing for development https://github.com/orgs/eiffel-community/projects/2/views/1
  • What about copyright headers - in what files should they exist? See eiffel-community/eiffel#292 (comment)
    • Mattias: Check mail thread on this subject in Ericsson
    • Magnus: Check in Axis for recommendations
  • Should we add a SECURITY.md file (docs)?
    • Yes. Move the one we have in community repo to .github. Action Tobias
  • Community meeting: reflections and plan for next
    • To be discussed on next weeks extra TC meeting
  • Should we require maintainers to be watchers of the repositories they maintain? https://github.com/watching, example: https://github.com/eiffel-community/eiffel/watchers
    • Yes. To be enforced in a coming guideline/rules for the maintainer role. Action TC
    • Could it be enforced through e.g. Github workflows? Action Magnus
  • Out of time, postponed: Planning of the next protocol edition
  • Out of time, postponed: PRs and issues

Action Items

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Tobias: Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
    • [Fatih] Still pending unfortunately. Will come back to this as soon as I get some time.
    • Update 2021-08-12: Question sent to Fatih but no reply yet.
    • Update 2021-09-09: Future communication to be done directly with Nordix via their mailing list.
    • Update 2021-10-07: Cluster running, access control situation unclear.
    • Update 2021-10-21: Tobias and Mattias have SSH access to one of the hosts but we don't appear to have k8s access.
    • Update 2022-01-27: Probably simple to fix, Tobias to ping Robert at Nordix.
    • Update 2022-02-17: Tobias has pinged Robert. Waiting for response.
  • Magnus: Propose new policy of how to deal with the issue requirement for new development.
  • Magnus: Process for how to lift event versions when meta object is updated needs to be added to the protocol meta PR. Ask Sven to do it?
  • Mattias/Emil: Set up 2FA for your account on the GitHub organization, https://github.com/orgs/eiffel-community/people?query=role%3Aowner
  • TC: Write issue about describing process for archiving projects and do archive eiffel-remrem-shared
  • TC: Add all TC members to all existing Eiffel Google groups
  • Tobias: Amend the repo creation checklist in the eiffel-repository-template repo to state that TC members should be added as owners to any created Google Groups.
  • Magnus: Add TC members' email addresses to the GOVERNANCE document (in the table of TC members).
  • Emil/Magnus: Revisit summit planning first half of February.
  • TC: Look into proposal made in the maintainer role presentation from the summit.
  • Emil/Mattias: Make sure questions from the CDF summit presentation are taken care of in SIG Events.
    • This can be transformed into an issue
  • Mattias: Figure out how to deal with Eiffel-adjacent repos not in the eiffel-community organization. Should they be made visible? How? Prepare a proposal on this.
  • Magnus: Create issues in all repos with .travisci.yml files to have them change to GitHub Actions.
  • Tobias: Add an organization README file (docs).
  • Fatih: Update timeline based on discussion (move elegible candidate earlier and take Easter into account) and get back to TC via mail for final confirmation.
  • Fatih: Locate script for finding eligible candidates and create PR in the community repo.
  • Magnus: Collect feedback from the interview to see if there are concrete steps we can take to improve how things are presented or explained.
  • Mattias: Create proposal for event type categorization.
  • Magnus: Can discussion items be added to a GitHub project (along with PRs and issues)?
  • Magnus: Go through current action list and suggest which should be migrated to issues in the community repo.
  • Emil: Confirm with Henning, Daniel, and Kristofer that it's okay to remove them as GitHub organization owners.
  • Magnus: Could policies like "repo maintainers should also be watchers" be enforced with e.g. github.com/github/safe-settings or github.com/probot/settings?
  • Tobias: Move SECURITY.md from the community repo to the .github repo.
  • Mattias: Check Ericsson email thread about which file types require copyright notices.
  • Magnus: Check within Axis for recommendations on which file types require copyright notices.
  • TC: Propose good dates for the May meetup.

January 27, 2022

Participants

  • TC Attendees
    • Emil Bäckmark, not present
    • Magnus Bäck, present
    • Mattias Linnér, present
    • Tobias Persson, present
  • Community Attendees
    • Fatih Degirmenci, present

Agenda and Notes

Action Items

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Tobias: Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
    • [Fatih] Still pending unfortunately. Will come back to this as soon as I get some time.
    • Update 2021-08-12: Question sent to Fatih but no reply yet.
    • Update 2021-09-09: Future communication to be done directly with Nordix via their mailing list.
    • Update 2021-10-07: Cluster running, access control situation unclear.
    • Update 2021-10-21: Tobias and Mattias have SSH access to one of the hosts but we don't appear to have k8s access.
    • Update 2022-01-27: Probably simple to fix, Tobias to ping Robert at Nordix.
  • Magnus: Prepare examples, event diagrams etc for the proposed source change events together with Sven Selberg and Tobias. That material can form the basis of source change discussions in an upcoming monthly community meeting.
    • Magnus will book meeting with Tobias and Sven for next week.
    • Update 2022-01-27: Meetings between Magnus, Tobias, and Sven held last week. Sven is preparing material and will update the issue.
  • Magnus: Propose new policy of how to deal with the issue requirement for new development.
  • Magnus: Continue examining consequences for JSON validation code when meta is extracted to a separate file.
  • Magnus: Write script for creating single-file schema files from multi-file schemas.
  • Magnus: Process for how to lift event versions when meta object is updated needs to be added to the protocol meta PR. Ask Sven to do it?
  • Mattias/Emil: Set up 2FA for your account on the GitHub organization, https://github.com/orgs/eiffel-community/people?query=role%3Aowner
  • TC: Write issue about describing process for archiving projects and do archive eiffel-remrem-shared
  • TC: Add all TC members to all existing Eiffel Google groups
  • TC: Amend the repo creation checklist in the eiffel-repository-template repo to state that TC members should be added as owners to any created Google Groups.
  • TC: Add TC members' email addresses to the GOVERNANCE document (in the table of TC members).
  • Emil/Magnus: Revisit summit planning first half of February.
  • Emil: Ask Daniel and Fatih if they want to continue being election officers.
  • TC: Look into proposal made in the maintainer role presentation from the summit.
  • Emil/Mattias: Make sure questions from the CDF summit presentation are taken care of in SIG Events.
  • TC: Figure out how to deal with Eiffel-adjacent repos not in the eiffel-community organization. Should they be made visible? How?
  • Emil/Magnus: Add Event type categorization to agenda of future TC meeting.
  • TC: Make sure all current TC members are maintainers of github.com/eiffel-community/eiffel and https://github.com/eiffel-community/eiffel-sepia.
  • TC: Create issues in all repos with .travisci.yml files to have them change to GitHub Actions.
  • Action TC: Add an organization README file (docs).
  • Action Fatih: Update timeline based on discussion (move elegible candidate earlier and take Easter into account) and get back to TC via mail for final confirmation.
  • Action Fatih: Locate script for finding eligible candidates and create PR in the community repo.
  • Action Magnus: Collect feedback from the interview to see if there are concrete steps we can take to improve how things are presented or explained.
  • Action Mattias: Create proposal for event type categorization.
  • Action Magnus: Can discussion items be added to a GitHub project (along with PRs and issues)?
  • Action Magnus: Go through current action list and suggest which should be migrated to issues in the community repo.

January 13, 2022

Participants

  • TC Attendees
    • Emil Bäckmark, present
    • Magnus Bäck, present
    • Mattias Linnér, present
    • Tobias Persson, present

Agenda and Notes

  • Rollcall, All
    • We have quorum.
  • Approval of Previous Minutes, All
    • Approved.
  • Agenda Bashing, All
    • Approved.
  • Action Item Review, All
  • Updates from CDF sig-events, Emil & Mattias
    • CD Events presentation will be held at Fosdem Feb 5-6.
  • By-election for TC?
  • Python podcast follow-up
    • Interview scheduled for January 20. Magnus and Daniel Ståhl will participate.
  • Set agenda for community meeting on source change events (or other topic?)
    • Next community meeting on February 3 will be about source change events. Magnus, Tobias, and Sven will prepare material.
    • The meeting after that (March 3) will concern the meta breakout. The next TC meeting on January 20 will be a working meeting to talk about the meta breakout.
  • Deal with summary/outcome from the summit
    • Maintainer role. Proposition to be discussed, enhanced and enforced
      • Action: Look into proposal made in presentation.
    • How to collaborate on visualizations?
    • Consider questions from summit in SIG Events continued discussions.
      • Action Emil/Mattias: Make sure questions from the presentation are taken care of in SIG Events.
    • From Jenkins broadcaster presentation: How to show existing Eiffel repos not in the eiffel community org in github, like this Jenkins plug-in for example? How to deal with community rules for repo structures and maintenance roles?
      • Visible in Community landscape
      • Action: Figure out how to deal with relevant repos not in the eiffel-community organization.
    • How to collaborate on event repository?
    • Event type categorization - how to follow up?
      • Action: Add to agenda of future TC meeting.
    • Source change events - to be handled on monthly meeting
    • Break out meta and similar structures - any actions to be taken now or as part of a coming monthly meeting?
      • Topic of next week's TC meeting.
  • Additional maintainers for github.com/eiffel-community/eiffel and https://github.com/eiffel-community/eiffel-sepia.
    • Action: Make sure all current TC members are maintainers of these repos.
  • How to force the use of Github Actions in all repos?
    • It was decided on last TC to use it, but how do we make sure it is used? And where should we document such decisions?
    • Eiffel Intelligence uses Travis CI and now have used 27610 of 35100 credits. What are the directive for moving?
    • The Eiffel repo contains a Travis file to create tar files when releasing. Should we move that to Github Actions now? It has not run for the last 2 releases, probably due to lack of Travis credits
    • All repos with Travis file: https://github.com/search?l=&q=org%3Aeiffel-community+filename%3A.travis.yml&type=code
    • Action: Create issues in all repos with .travisci.yml files to have them change to GitHub Actions.
  • Out of time, postponed: Go through https://github.com/orgs/eiffel-community/projects/3/views/1
    • Should we use it? If so, how?
  • Out of time, postponed: Show what Ericsson is prioritizing for development https://github.com/orgs/eiffel-community/projects/2/views/1
  • Out of time, postponed: Should we add a readme for the organization for introduction. Would go into the .github repo. See https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile for more info and https://github.com/keptn-sandbox as an example.
  • Out of time, postponed: What about copyright headers - in what files should they exist? See eiffel-community/eiffel#292 (comment)
  • Out of time, postponed: PRs and issues

Action Items

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Tobias: Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
    • [Fatih] Still pending unfortunately. Will come back to this as soon as I get some time.
    • Update 2021-08-12: Question sent to Fatih but no reply yet.
    • Update 2021-09-09: Future communication to be done directly with Nordix via their mailing list.
    • Update 2021-10-07: Cluster running, access control situation unclear.
    • Update 2021-10-21: Tobias and Mattias have SSH access to one of the hosts but we don't appear to have k8s access.
  • Emil: Go through the discussions in the summit presentations and see if there are things we should create issues from or have monthly community meetings about.
  • Magnus: Prepare examples, event diagrams etc for the proposed source change events together with Sven Selberg and Tobias. That material can form the basis of source change discussions in an upcoming monthly community meeting.
    • Magnus will book meeting with Tobias and Sven for next week.
  • Emil: Check how CDF's Google Calendar works.
    • It's most probably tied to a central Google account (on LinuxFoundation?) We should not tie such a calendar to a personal Google account so instead we should probably create an Eiffel Community Google account that we all get access to in one way or another.
    • Update 2022-01-13: Too complicated. Leave it for now.
  • Magnus: Propose new policy of how to deal with the issue requirement for new development.
  • Magnus: Continue examining consequences for JSON validation code when meta is extracted to a separate file.
  • Magnus: Write script for creating single-file schema files from multi-file schemas.
  • Magnus: Process for how to lift event versions when meta object is updated needs to be added to the protocol meta PR. Ask Sven to do it?
  • Emil: Check admin access to YouTube channel. Could all TC members be admins? Or should we all have access to a (new?) admin Google account?
  • Mattias/Emil: Set up 2FA for your account on the GitHub organization, https://github.com/orgs/eiffel-community/people?query=role%3Aowner
  • TC: Write issue about describing process for archiving projects and do archive eiffel-remrem-shared
  • TC: Add all TC members to all existing Eiffel Google groups
  • TC: Amend the repo creation checklist in the eiffel-repository-template repo to state that TC members should be added as owners to any created Google Groups.
  • TC: Add TC members' email addresses to the GOVERNANCE document (in the table of TC members).
  • TC: Add recommendation to not use force pushes to code review guidelines.
  • Emil/Magnus: Revisit summit planning first half of February.
  • Emil: Ask Daniel and Fatih if they want to continue being election officers.
  • TC: Look into proposal made in the maintainer role presentation from the summit.
  • Emil/Mattias: Make sure questions from the CDF summit presentation are taken care of in SIG Events.
  • TC: Figure out how to deal with Eiffel-adjaent repos not in the eiffel-community organization. Should they be made visible? How?
  • Emil/Magnus: Add Event type categorization to agenda of future TC meeting.
  • TC: Make sure all current TC members are maintainers of github.com/eiffel-community/eiffel and https://github.com/eiffel-community/eiffel-sepia.
  • TC: Create issues in all repos with .travisci.yml files to have them change to GitHub Actions.