Skip to content

Latest commit

 

History

History
990 lines (904 loc) · 63 KB

MEETINGS_BTC.md

File metadata and controls

990 lines (904 loc) · 63 KB

Bootstrap Technical Committee Meeting Archive

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.

April 22, 2021

Participants

TC Attendees

  • Emil Bäckmark, Ericsson, present
  • Fatih Degirmenci, Ericsson Software Technology, present
  • Fredrik Fristedt, Axis, present
  • Kristofer Hallén, Ericsson, present
  • Mattias Linnér, Ericsson, present
  • Christian Madsen, Grundfos, not present
  • Raja Maragani, Ericsson/TCS, not present
  • Henning Roos, Ericsson, present
  • Ola Söder, Axis, not present
  • Daniel Ståhl, Ericsson, not present
  • David Westberg, Volvo, present
  • Ewelina Wilkosz, Eficode, not present

Community Attendees

  • <addme>

Agenda and Notes

Action Items

  • New Eiffel TC to decide who should be owners of Eiffel Community on GitHub - https://github.com/orgs/eiffel-community/people?query=role%3Aowner
  • Emil to update the governance document and list the elected TC members
  • Henning to update eiffel-community maintainers list on Eiffel Community organization on April 23rd and add elected TC Members. Edit by Henning 2021-04-23: Done!
  • Fatih to remove bootstrap process - #90 on April 23rd
  • Fatih to send mail to Eiffel Maillist, announcing the new TC with the date the TC assume their seats
  • Fatih to close election process on GitHub - #87
  • Fatih to add the elected TC to Eiffel HackMD team
  • Emil to send invitation for the next Eiffel TC Meeting if a better time is determined
  • Henning and Fatih to work on clarifying how the eligibility is determined in governance document, CODEOWNERS vs mainateiners groups. Edit by Henning 2021-04-23: PR submitted for review (#94)
  • TC to discuss whether to adapt co-chair setup after the new TC is seated
  • Mattias to publish API for ER
  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • 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.

April 8, 2021

Participants

TC Attendees

  • Emil Bäckmark, Ericsson, present
  • Fatih Degirmenci, Ericsson Software Technology, present
  • Fredrik Fristedt, Axis, present
  • Kristofer Hallén, Ericsson, present
  • Mattias Linnér, Ericsson, present
  • Christian Madsen, Grundfos, not present
  • Raja Maragani, Ericsson/TCS, present
  • Henning Roos, Ericsson, not present
  • Ola Söder, Axis, present
  • Daniel Ståhl, Ericsson, not present
  • David Westberg, Volvo, not present
  • Ewelina Wilkosz, Eficode, not present

Community Attendees

  • <addme>

Agenda and Notes

Action Items

  • Henning and Fatih to work on clarifying how the eligibility is determined in governance document, CODEOWNERS vs mainateiners groups
  • TC to discuss whether to adapt co-chair setup after the new TC is seated
  • Fatih to send mail to Eiffel Maillist asking for election officer nominations
  • Mattias to publish API for ER
  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • 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.
  • Document the term and the process to appoint security officers as part of TC creation, Fatih
    • [Fatih] PR is open for review: #92

March 25, 2021

Participants

TC Attendees

  • Emil Bäckmark, Ericsson, present
  • Fatih Degirmenci, Ericsson Software Technology, present
  • Fredrik Fristedt, Axis, present
  • Kristofer Hallén, Ericsson, present
  • Mattias Linnér, Ericsson, present
  • Christian Madsen, Grundfos, present/not present
  • Raja Maragani, Ericsson/TCS, present/not present
  • Henning Roos, Ericsson, present
  • Ola Söder, Axis, present/not present
  • Daniel Ståhl, Ericsson, present
  • David Westberg, Volvo, present/not present
  • Ewelina Wilkosz, Eficode, present/not present

Community Attendees

  • <addme>

Agenda and Notes

Action Items

  • TC to discuss whether to adapt co-chair setup after the new TC is seated, TC

  • Fatih to send mail to Eiffel Maillist asking for election officer nominations

  • Mattias to publish API for ER

  • Magnus to file a PR to Sepia for best practices for routing key.

    • Issue created, but no PR yet.
    • FD - a PR exists so this action item will be discussed and closed during the next meeting

  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.

    • Issue already exists that could contain this improvement: eiffel-community/eiffel#226, but no PR yet
    • Fatih to check with Magnus if there is a PR for this

  • 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.

  • Document the term and the process to appoint security officers as part of TC creation, Fatih

    • [Fatih] Still pending unfortunately. Will come back to this as soon as possible.

  • Mattias: Look into if all files need a copyright/license statement or not, inline with this comment: eiffel-community/eiffel-repository-template#14 (comment)

    • Response from Gunnar Nilsson

    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.

  • Fatih to include exception process as well as what to do when there is a tie

  • Fatih to document TC Chair election process

    • could be as simple as an agree within the first TC meeting where new TC assumes their seats assuming the TC meeting has a quorum
    • if there are multiple candidates, TC goes for an election within its members

March 11, 2021

Participants

TC Attendees

  • Emil Bäckmark, Ericsson, present
  • Fatih Degirmenci, Ericsson Software Technology, present
  • Fredrik Fristedt, Axis, not present
  • Kristofer Hallén, Ericsson, not present
  • Mattias Linnér, Ericsson, not present
  • Christian Madsen, Grundfos, not present
  • Raja Maragani, Ericsson/TCS, not present
  • Henning Roos, Ericsson, present
  • Ola Söder, Axis, present
  • Daniel Ståhl, Ericsson, present
  • David Westberg, Volvo, not present
  • Ewelina Wilkosz, Eficode, not present

Community Attendees

  • <addme>

Agenda and Notes

  • Rollcall, All
  • Agenda Bashing, All
  • Action Item Review, All
  • Status of Community Governance Documentation, All
    • Election Process: #82
    • [Fatih] Will amend the PR and update based on comments received. If you haven't reviewed yet please do so their comments could be taken into account when the work proceeds.
    • Some comments remain to be answered/finished and more reviews are needed.
  • Community Election Timeline, All
    • TC Election
      • The aim is to have the election process PR merged by March 25th
      • The candidate list gets published on March 29th
      • Nomination period is between April 1st-9th
      • The vote mail is sent to Eiffel Group on Google April 12th
      • Voting period is between April 12th-20th
      • The new TC assumes their seats by the TC meeting on April 22nd
    • TC Chair Election
      • TC Chair nomination period is April 22nd-28th
      • TC Chair election period is April 29th-May 5th
      • The new TC chair assumes her/his seat by the TC meeting on May 6th
  • CDF SIG Events, Emil Bäckmark

Action Items

* Magnus to call meeting to discuss ER with Emil, Mattias, Kristofer, Fredrik, Tobias * Outcome of the meeting was to publish API for ER by Mattias which resulted in the AP below

  • Mattias to publish API for ER
  • Magnus to file a PR to Sepia for best practices for routing key.
    • Issue created, but no PR yet.
    • FD - a PR exists so this action item will be discussed and closed during the next meeting
  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • 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.
  • Document the term and the process to appoint security officers as part of TC creation, Fatih
    • [Fatih] Still pending unfortunately. Will come back to this as soon as possible.
  • Mattias: Look into if all files need a copyright/license statement or not, inline with this comment: eiffel-community/eiffel-repository-template#14 (comment)
  • Fatih to include exception process as well as what to do when there is a tie
  • Fatih to document TC Chair election process
    • could be as simple as an agree within the first TC meeting where new TC assumes their seats assuming the TC meeting has a quorum
    • if there are multiple candidates, TC goes for an election within its members

February 25, 2021

This meeting was cancelled due to public holidays.

February 11, 2021

Participants

TC Attendees

  • Emil Bäckmark, Ericsson, present
  • Fatih Degirmenci, Ericsson Software Technology, not present
  • Fredrik Fristedt, Axis, present
  • Kristofer Hallén, Ericsson, present
  • Mattias Linnér, Ericsson, present
  • Christian Madsen, Grundfos, not present
  • Raja Maragani, Ericsson/TCS, present
  • Henning Roos, Ericsson, present
  • Ola Söder, Axis, not present
  • Daniel Ståhl, Ericsson, present
  • David Westberg, Volvo, present
  • Ewelina Wilkosz, Eficode, not present

Community Attendees

  • Magnus Bäck, Axis Communications

Agenda and Notes

Action Items

  • Mattias to send a PR to Sepia to add ER Swagger specificationgithub.com/eiffel-community/eiffel-event-repository#11
  • Magnus to call meeting to discuss ER with Emil, Mattias, Kristofer, Fredrik, Tobias
  • Magnus to update eiffel-community/eiffel#253 with name Paris
  • Magnus to file a PR to Sepia for best practices for routing key.
  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices.
  • Fredrik to propose an update to README.md in community repo and governance document about how one can join to the community as member. Closing as no work was needed
  • 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 the project lifecycle document to add mail requirement to maillist for increased visibility, Fatih PR79 [Fatih] This AP can be closed. PR merged.
  • Document the term and the process to appoint security officers as part of TC creation, Fatih
    • [Fatih] Still pending unfortunately. Will come back to this as soon as possible.
  • Send PRs to repos to apply badges to the repos, Fatih [Fatih] This AP can be closed. I believe most of the PRs applying badges have been merged.For the ones that are still open or the repos that miss the badge can be fixed when we notice them.
    • eiffel-community/eiffel - being graduated so sandbox badge won't be applied
    • The repos below either have non-standard readmes or no readmes at all. Readmes will be created using readme from the template repository which contains the sandbox badge as well.
      • eiffel-community/eiffel-persistence-technology-evaluation
      • eiffel-community/eiffelactory
      • eiffel-community/ml-jmespath-generator
      • eiffel-community/eiffel-jira-plugin
      • eiffel-community/simple-event-sender
      • eiffel-community/eiffel-easy2use
      • eiffel-community/eiffel-store
      • eiffel-community/eiffel-playground
  • Mattias: Look into if all files need a copyright/license statement or not, inline with this comment: eiffel-community/eiffel-repository-template#14 (comment)

January 28, 2021

Participants

TC Attendees

  • Emil Bäckmark, Ericsson, present
  • Fatih Degirmenci, Ericsson Software Technology, present
  • Fredrik Fristedt, Axis, present
  • Kristofer Hallén, Ericsson, present
  • Mattias Linnér, Ericsson, present
  • Christian Madsen, Grundfos, not present
  • Raja Maragani, Ericsson/TCS, not present
  • Henning Roos, Ericsson, present
  • Ola Söder, Axis, not present
  • Daniel Ståhl, Ericsson, present
  • David Westberg, Volvo, not present
  • Ewelina Wilkosz, Eficode, not present

Community Attendees

  • Magnus Bäck, Axis Communications

Agenda and Notes

  • Rollcall, All
    • Quorum reached
  • Agenda Bashing, All
    • Agenda approved
  • Action Item Review, All
  • Status of Community Governance Documentation, All
    • EB: Concern: Meeting poll answered by 5 BTC members only, and community PRs take long to get reviewed. What could we do to increase the level of commitment? Emil
    • FD: We need to continuously monitor the health of the community and act if things need improvement.
  • Eiffel Protocol Graduation is still not approved? Emil
    • Agree: Eiffel Protocol is approved to be moved to graduated stage.
  • Info/discussion: A new Eiffel protocol release - Agen-2 is about to be released, Emil
    • EB: The proposal is to release Agen as a patch release since there are few/small changes.
    • DS: We had version policy.
    • EB: We shouldn't take up a new revision for bugfix releases but there isn't a clear process around this.
    • EB: Things are released at will. Should we have some structure with regards to releases in general - e.g., twice a year?
    • DS: Suggestion is to just stick with the names. If it is about the new event versions, we step.
    • DS: The current process around versioning, naming, editions is documented on https://github.com/eiffel-community/eiffel/blob/master/eiffel-syntax-and-usage/versioning.md
    • EB: We could take the next name.
  • Discussion: How can we establish a standard for RabbitMQ topics for Eiffel exchanges to improve interoperability between producers and consumers (Slack thread) Magnus
    • MB: Right now there is no standard around topics, causing difficulties for filtering.
    • MB: RemREM has something for this but it is not very well documented which requires you to dive into code deeper.
    • MB: It would be beneficial to have some kind of standard around this and documented.
    • MB: This is not part of the Eiffel Protocol so where/how should we deal with this?
    • DS: This could be in "infrastructure configuration reporitory", proposing canonical configuration, essentially saying this is adviced way of configuring it.
    • HR: Sepia was created for this purpose?
    • FF: There was a discussion around having best practices documented/good to know.
    • MB: That kind of repository could contain information about other practices as well such as different repositories.
    • EB: Examples in protocol could be renamed to best practices perhaps. (e.g., what is a good way to link series of events)
    • MB: Concurs - examples could be renamed to recommendations. Examples talk about how the events look like but not much about how to use them for.
    • EB: All Sepia maintainers are from a single company and it would be good to broaden maintainers list with more people from different companies.
  • Discussion: The question of a standard API for event repositories was brought up at a previous TC meeting and an action was given to Emil and Tobias, but this was dropped. Let's try again? (Slack thread) Magnus
    • MB: The event repository implementation is not public and everyone has their own event repository.
    • MB: How should we have some progress on this topic to start discussions?
  • Events in CI/CD Workstream in CDF SIG Interoperability, Emil
    • EB: It was proposed to make Events in CI/CD a top level SIG. A PR is currently being worked on to propose the SIG.
    • EB: Draft charter for the SIG was brought up to CDF Technical Oversight Committee and the feedback was very good.
    • ML: Cloudevents is something the group is looking into as well.
  • Open PRs, All
    • Agree: This PR can be merged: #80

Action Items

  • Mattias to send a PR to Sepia to add ER Swagger specification
  • Magnus to call meeting to discuss ER with Emil, Mattias, Kristofer, Fredrik, Tobias
  • Magnus to update eiffel-community/eiffel#253 with name Paris
  • Magnus to file a PR to Sepia for best practices
  • Magnus to file another PR to Eiffel Protocol repo to move from examples to best practices
  • Kristofer to drive planning for Eiffel Summit 2021
  • Send mail to Eiffel maillist, pointing the inclusive language initiative, Fredrik
  • Fredrik to propose an update to README.md in community repo and governance document about how one can join to the community as member
  • Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
  • Conclude the badging discussion and then start applying badges, eiffel-community/eiffel-repository-template#9
  • Update the project lifecycle document to add mail requirement to maillist for increased visibility, Fatih PR79
  • Document the term and the process to appoint security officers as part of TC creation, Fatih
  • Send PRs to repos to apply badges to the repos, Fatih
    • eiffel-community/eiffel - being graduated so sandbox badge won't be applied
    • The repos below either have non-standard readmes or no readmes at all. Readmes will be created using readme from the template repository which contains the sandbox badge as well.
      • eiffel-community/eiffel-persistence-technology-evaluation
      • eiffel-community/eiffelactory
      • eiffel-community/ml-jmespath-generator
      • eiffel-community/eiffel-jira-plugin
      • eiffel-community/simple-event-sender
      • eiffel-community/eiffel-easy2use
      • eiffel-community/eiffel-store
      • eiffel-community/eiffel-playground

December 7, 2020

Participants

TC Attendees

  • Emil Bäckmark, Ericsson, present
  • Fatih Degirmenci, Ericsson Software Technology, present
  • Fredrik Fristedt, present
  • Kristofer Hallén, Ericsson, present
  • Mattias Linnér, Ericsson, present
  • Christian Madsen, Grundfos, not present
  • Raja Maragani, Ericsson/TCS, present
  • Henning Roos, Ericsson, not present
  • Ola Söder, Axis, present
  • Daniel Ståhl, present
  • David Westberg, present
  • Ewelina Wilkosz, not present

Agenda and Notes

  • Rollcall, All
    • Quorum reached
  • Agenda Bashing, All
    • Agenda approved
  • Action Item Review, All
  • Status of Community Governance Documentation, All
    • Close to be accepted - missing 1 approval WIP: Security/Vulnerability reporting and response processes (PRs available) PR72 and PR15
    • WIP: Community Vision, Mission, Goals (PR available) PR80 and PR17
    • WIP: Election procedure (PR available) PR82
  • Date for Next Meeting?
    • Agreed: January 18th is the next meeting date
  • Formation of TC - part of TC charter, All
    • No of members in TC: BTC had 5 meetings with average attendance of 8 from TC members
    • Company cap: This is a common practice applied by the communities to ensure diversity. We could start with something and then we expect to lower it over time. (start with 3 for example and reduce to 2 over time)
    • Company Cap: Representing a certain company regardless of affiliation?
    • Question: What happens a TC member changes employment? Will the person need to step down from TC?
    • Question: Having company cap my prevent representation from a company with fewer voters.
    • Question: Why do we need company cap (diversity, etc) needs to be documented?
    • Agreed: Update the governance document and incldue 8 as no of TC members and 3 as the company/affiliation cap.
  • How to handle approvals to community processes?, All
    • Currently the changes could come in in the form of issue and/or PR which is time consuming.
    • Should we use PRs solely to remove an extra step?
    • For the things that do not result in PRs, they could be included in TC meeting and decisions could be taken quickly? (can consider silence as +1)
    • Proposal (can't take decisions this meeting): Use issues to describe the problem. Issues do not have to be approved. Create PRs to describe solutions.
    • It is better to look at actual solution rather than the issue.
    • Agreed: Issues will continue to be used but no approval should be expected for them. The PR implementing what is documented in the issue is what gets reviewed/approved/declined.
    • Question: What to do with the issues where the corresponding PRs are not accepted? Who marks the issues as invalid or close with no action?
  • Eiffel summit next year, Kristofer
    • The last event happened in May 2020.
    • Should we plan something for new year?
    • Software Center, CDF, and other communities can be invited to the event.
  • Eiffel Protocol Graduation needs approval: #78, eiffel-community/eiffel#247
  • Meeting with Scania on Eiffel
    • Reach out to Kristofer and Emil if you want to be part of the discussion
  • Eiffel Lucia/Fika
    • 14th of December. The invitation is on Slack.
  • <addme>

Action Items

  • Kristofer to drive planning for Eiffel Summit 2021
  • Send mail to Eiffel maillist, pointing the inclusive language initiative, Fredrik
  • Fredrik to propose an update to README.md in community repo and governance document about how one can join to the community as member
  • Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
  • Conclude the badging discussion and then start applying badges, eiffel-community/eiffel-repository-template#9
  • Update the project lifecycle document to add mail requirement to maillist for increased visibility, Fatih PR79
  • Document the term and the process to appoint security officers as part of TC creation, Fatih
  • Send PRs to repos to apply badges to the repos, Fatih
  • Add link to eiffel-community.github.io for security page, Fredrik
  • Daniel to document Community Vision, Mission, Goals and include it on eiffel-community.github.io PR80 and PR17
  • Fatih to document election procedure as part of governance PR82 ~~* Follow up November 23 meeting items since decisions could not be taken. Fatih
  • Eiffel summit next year? Kristofer

November 23, 2020

Participants

TC Attendees

  • Emil Bäckmark, Ericsson, present
  • Fatih Degirmenci, Ericsson Software Technology, present
  • Fredrik Fristedt, not present
  • Kristofer Hallén, Ericsson, present
  • Mattias Linnér, Ericsson, present
  • Christian Madsen, Grundfos, not present
  • Raja Maragani, Ericsson/TCS, not present
  • Henning Roos, Ericsson, present
  • Ola Söder, Axis, not present
  • Daniel Ståhl, present
  • David Westberg, not present
  • Ewelina Wilkosz, not present

Agenda and Notes

  • Rollcall, All
    • Quorum NOT reached
  • Agenda Bashing, All
  • Action Item Review, All
  • Status of Community Governance Documentation, All
  • Formation of TC - part of TC charter, All
    • No of members in TC: BTC had 5 meetings with average attendance of 8 from TC members
    • Company cap: This is a common practice applied by the communities to ensure diversity. We could start with something and then we expect to lower it over time. (start with 3 for example and reduce to 2 over time)
  • How to handle approvals to community processes?, All
    • Currently the changes could come in in the form of issue and/or PR which is time consuming.
    • Should we use PRs solely to remove an extra step?
    • For the things that do not result in PRs, they could be included in TC meeting and decisions could be taken quickly? (can consider silence as +1)
    • Proposal (can't take decisions this meeting): Use issues to describe the problem. Issues do not have to be approved. Create PRs to describe solutions.

Action Items

  • Send mail to Eiffel maillist, pointing the inclusive language initiative, Fredrik
  • Fredrik to propose an update to README.md in community repo and governance document about how one can join to the community as member
  • Fatih to get Tobias and Mattias in touch with Nordix for Kubernetes cluster installation
  • Conclude the badging discussion and then start applying badges, eiffel-community/eiffel-repository-template#9
  • Create a PR to graduate Eiffel Protocol, Emil Pull request #78
  • Update the project lifecycle document to add mail requirement to maillist for increased visibility, Fatih Pull request #79
  • Update project lifecycle with instructions of adding badges, Mattias Pull request #76
  • Update template repository with default sandbox logo/icon, Henning
  • Document the term and the process to appoint security officers as part of TC creation, Fatih
  • Create a google group for Eiffel Security, Kristofer Issue #60
  • Axis and Ericsson to drive the ER topic, Tobias & Emil
  • Send PRs to repos to apply badges to the repos, Fatih
  • Add link to eiffel-community.github.io for security page, Fredrik
  • Daniel to document Community Vision, Mission, Goals and include it on eiffel-community.github.io
  • Fatih to document election procedure as part of governance
  • Follow up November 23 meeting items since decisions could not be taken. Fatih
  • Eiffel summit next year? Kristofer

November 9, 2020

Participants

TC Attendees

  • Emil Bäckmark, Ericsson, present
  • Fatih Degirmenci, Ericsson Software Technology, present
  • Fredrik Fristedt, Axis, present
  • Kristofer Hallén, Ericsson, present
  • Mattias Linnér, Ericsson, present
  • Christian Madsen, Grundfos, not present
  • Raja Maragani, Ericsson/TCS, not present
  • Henning Roos, Ericsson, present
  • Ola Söder, Axis, not present
  • Daniel Ståhl, present
  • David Westberg, present
  • Ewelina Wilkosz, not present

Agenda and Notes

  • Rollcall, All
    • Quorum reached
  • Agenda Bashing, All
    • Agenda approved
  • Action Item Review, All
  • Eiffel Community Security & Vulnerability Process, Fredrik & Kristofer
    • PR is open for review: #72
    • Security officers/contacts - Kristofer, Fredrik
  • Event Repository, Tobias Persson/All
    • Which event repository API should be the standard interface for all event repositories?
    • Should we work together to come up with something new?
    • Should this be documented somewhere in the community?
    • The topic could be discussed outside of TC meeting to look for options
    • People from broader community could take part in this discussion
    • It is a good opportunity to work on this collaboratively to put the pieces in place as a community
    • This would also allow bringing experiences from others
    • Event data aggragation could be seen as an item under this discussion
    • Lack of ER caused some difficulties so this would help with it
  • Project Lifecycle Stages, All
  • Guidelines for publishing community videos/recordings, All
    • Do we need to have guidelines for community for publishing videos/recordings?
    • The guidelines will be documented as part of the creation of the next community recording

Action Items

  • Send mail to Eiffel maillist, pointing the inclusive language initiative, Fredrik
  • ETOS project to reach out to Daniel Stahl whenever they think they want to have a video
  • Fatih to add topic on having guidance on community videos/recordings to next meeting
  • Fredrik to propose an update to README.md in community repo and governance document about how one can join to the community as member
  • Pass Kubernetes deployment details on community repo, Tobias
  • Fatih to get Tobias in touch with Nordix for Kubernetes cluster installation
  • Conclude the badging discussion and then start applying badges, eiffel-community/eiffel-repository-template#9
  • Prepare graduation proposal for Eiffel Protocol project, Emil Issue 77
  • Create a PR to graduate Eiffel Protocol, Emil
  • Update the project lifecycle document to add mail requirement to maillist for increased visibility, Fatih
  • Update project lifecycle with instructions of adding badges, Mattias Pull request #76
  • Update template repository with default sandbox logo/icon, Henning
  • Document the term and the process to appoint security officers as part of TC creation, Fatih
  • Create a google group for Eiffel Security, Kristofer
  • Axis and Ericsson to drive the ER topic, Tobias & Emil
  • Send PRs to repos to apply badges to the repos, Fatih

October 26, 2020

Participants

TC Attendees

  • Emil Bäckmark, Ericsson, present
  • Fatih Degirmenci, Ericsson Software Technology, present
  • Fredrik Fristedt, Axis, not present
  • Kristofer Hallén, Ericsson, not present
  • Mattias Linnér, Ericsson, present
  • Christian Madsen, Grundfos, not present
  • Raja Maragani, Ericsson/TCS, not present
  • Henning Roos, Ericsson, present
  • Ola Söder, Axis, not present
  • Daniel Ståhl, present
  • David Westberg, present
  • Ewelina Wilkosz, not present

Community Attendees

Agenda and Notes

Action Items

  • Send mail to Eiffel maillist, pointing the inclusive language initiative, Fredrik
  • Kristofer and Fredrik to look at security vulnerability process, Fredrik and Kristofer
  • Daniel Stahl to help doodling things/videos for community videos, Daniel Stahl
  • ETOS project to reach out to Daniel whenever they think they want to have a video
    • EB: Should we have some recommendations of ways to creating videos to set the way forward?
    • DS: I'm happy to help.
  • Fatih to add topic on having guidance on community videos/recordings to next meeting
  • Fredrik to propose an update to README.md in community repo and governance document about how one can join to the community as member
  • Pass Kubernetes deployment details on community repo, Tobias
  • Conclude the badging discussion and then start applying badges, eiffel-community/eiffel-repository-template#9
  • Prepare graduation proposal for Eiffel Protocol project, Emil
  • Update project lifecycle with instructions of adding badges, Mattias

October 12, 2020

Participants

TC Attendees

  • Emil Bäckmark, Ericsson, present
  • Fatih Degirmenci, Ericsson Software Technology, present
  • Fredrik Fristedt, Axis, present
  • Kristofer Hallén, Ericsson, present
  • Mattias Linnér, Ericsson, not present
  • Christian Madsen, Grundfos, not present
  • Raja Maragani, Ericsson/TCS, not present
  • Henning Roos, Ericsson, present
  • Ola Söder, Axis, present
  • Daniel Ståhl, not present
  • David Westberg, present
  • Ewelina Wilkosz, not present

Community Attendees

  • Tobias Persson, Axis Communications

Agenda and Notes

  • Rollcall, All
    • Quorum reached
  • Agenda Bashing, All
    • Agenda approved
  • Action Item Review, All
  • Reflections from cdCon, All
    • FF: It was interesting to hear what people were discussing about such as having JSON schema to help with interoperability issues.
    • FF: They kind of described Eiffel without knowing about it.
    • EB: Attended the both days. It was intersting and there were a lot of talks about events everywhere. People may have different opinions about events.
    • EB: There was a presentation about Keptn from Dynatrace - Event driven CD. There were interesting talks.
    • EB: SIG Interoperability held BoF session and there were new people in the session. They may join to SIG.
    • KH: Were there more people you haven't seen before?
    • EB: People talk about interoperability but they are not aware of existence of the SIG.
    • EB: Tekton presentation was given by Andreas Frittoli and he looks forward to standardizing sending events for others to see their actions.
    • EB: Events in CI/CD meeting this evening 18:30.
    • EB: 1300 registrants and 800 accessed to the conference portal.
  • Eiffel Community Security & Vulnerability Process, Fredrik & Kristofer
    • Working on the initial document.
    • Other communities don't seem to describe what happens once the issue is filed. (internal process)
    • Few steps need to be documented in order to explain the process so everyone knows how it works.
    • How projects themselves could publish identified/fixed security issues. (shortcut for projects)
  • Inclusive Language Initiative and Impacts on Eiffel Community, Fatih & All
    • Discussion on whether community feels the need to work on adopting more inclusive language
    • Heads up on potential impacts introduced by other communities and organisations on Eiffel Community
    • If we start changing things and adapt inclusive language, we need to document this clearly in governance and project guidelines.
  • Eiffel Community Infrastructure, Mattias & Fatih
  • Eiffel Community Organization Contacts, Henning
    • Who has right to add/invite people to Eiffel Organization on GitHub?
    • Any volunteers to help with this?
    • Issue #71 tries to address this
  • Project Lifecycle Stages - How do we mark our repositories? Do we have badges or should we use lables? Documenation states it is clearly marked allthough very few (None) are marked.
  • CDF SIG Interoperability Whitepaper

Action Items

  • Send mail to Eiffel maillist, pointing the inclusive language initiative, Fredrik
  • Clarify which repos the BTC should have permission on and document it. PR created.
  • Document quorum requirements
    • Already documented in the governance: Quorum for Technical Committee meetings requires at least a majority of all voting members of the Technical Committee to be present.
  • Kristofer and Fredrik to look at security vulnerability process
  • Henning to create eiffel-playground repo and create maintainers group with Mattias and Fatih as initial members
  • Daniel Stahl to help doodling things/videos for community videos
  • Fatih and Henning to add topic/issue on community infra/organization champions/contacts with a simple/short process. PR.
  • Fredrik to propose an update to README.md in community repo and governance document about how one can join to the community as member
  • Pass Kubernetes deployment details on community repo, Tobias
  • Conclude the badging discussion and then start applying badges, eiffel-community/eiffel-repository-template#9
  • Prepare graduation proposal for Eiffel Protocol project, Emil

September 28, 2020

Participants

TC Attendees

  • Emil Bäckmark, Ericsson, present
  • Fatih Degirmenci, Ericsson Software Technology, present
  • Fredrik Fristedt, Axis, present
  • Kristofer Hallén, Ericsson, present
  • Mattias Linnér, Ericsson, present
  • Christian Madsen, Grundfos, present
  • Raja Maragani, Ericsson/TCS, present
  • Henning Roos, Ericsson, present
  • Ola Söder, Axis, not present
  • Daniel Ståhl, not present
  • David Westberg, present
  • Ewelina Wilkosz, not present

Community Attendees

  • Isac Holm
  • Martin Lundberg

Agenda and Notes

  • Rollcall
    • Quorum reached
  • Agenda Bashing
    • Agenda is approved
  • Action Item Review
    • Action items reviewed
  • Responsibilities of TC Members and Chair
    • This topic came up based on Daniel’s comment - who does what: #57 (comment)
    • We already appointed people - TC
    • Monitoring community repository, maillist for the questions, issues, and PRs and providing opinion
    • Taking part in and driving TC activities such as establishing processes and procedures - examples to this are documenting security and vulnerability process, working with infrastructure
    • Joining meetings
    • More details on TC responsibilities are documented in governance
    • Chair monitors maillist/community repo, bumps threads, and pulls in people accordingly as well as what's documented in governance
  • Eiffel Community Security & Vulnerability Process
    • Looking for volunteers
    • Kristofer Hallen and Fredrik Fristedt volunteer
  • Eiffel Community Infrastructure
  • New Project: ETOS
    • The project was proposed by Axis
    • Axis intends to use the open source version of the project once the project is fully migrated to GitHub
    • There may be bumps as a small issue has been identified but it should be working fairly well
    • The project is interesting for David and it is in their watchlist
    • If desired, a demo/discussion can be set up for the interested people/organizations
    • It may be good to have a short video published on Eiffel Youtube channel but it may be too much for a video
    • A condensed version of the demo is a possibility depending on the priorities
    • It may be valuable to have this type of recordings/demos for other/all Eiffel projects as well
    • The project is up & running
  • Github roles within maintainer groups and community membership
    • Particulary the community-maintainer list and eiffel community members
    • Each member in a maintainer group can have one of two different roles, member and maintainer.
    • Members (as well as maintainers) of a maintainer group can work with issues/PRs (accept, label, merge etc) of the associated repositories.
    • Maintainers of a maintainer group can also add & delete members of their maintainer group and change their roles
    • Who should be maintainers for Eiffel Community organization maintainer list
    • TC chair can be natural member of the team as maintainer
    • TC can appoint/empower few community members as the people to help with administering the Eiffel Organization
    • A suggestion is to allow maintainers to take care of their own maintainer list
  • cdCon - Inaugural summit for CD Foundation
  • Process/ guidelines on how to contribute and how to join into the community is lacking
    • Information on how to join and contribute needs to be more visable
    • How to add new member to a repository as member?
    • There was very little information about how one can join to Eiffel Community
    • This needs to be documented
    • Other communities have instructions about how to join to community
    • The governance document can be updated to tell people how to join the community https://github.com/eiffel-community/community/blob/master/GOVERNANCE.md#contributors

Action Items

  • Update eiffel-community/community repo with the list of BTC members, Henning Roos
  • Update governance document and list members and chair of the BTC
  • Clarify which repos the BTC should have permission on and document it
  • Make code of conduct and contributions guidelines more visible
  • All BTC members to join Maillist/Google Group
  • Document quorum requirements
  • Kristofer and Fredrik to look at security vulnerability process
  • Henning to create eiffel-playground repo and create maintainers group with Mattias and Fatih as initial members
  • Daniel Stahl to help doodling things/videos for community videos
  • Fatih and Henning to add topic/issue on community infra/organization champions/contacts with a simple/short process
  • Fredrik to propose an update to README.md in community repo and governance document about how one can join to the community as member

September 14, 2020

Participants

  • Kristofer Hallén, Ericsson
  • Fatih Degirmenci, Ericsson Software Technology
  • Christian Ekberg, Ericsson
  • Daniel Ståhl, Ericsson
  • Edvin Agnas, Volvo
  • Fredrik Fristedt, Axis
  • Christian Madsen, Grundfos
  • Henning Roos, Ericsson
  • Maniette Daniel, Volvo
  • Martin Kitchen, Grundfos
  • Ola Söder, Axis
  • Mattias Linner, Ericsson
  • Emil Bäckmark, Ericsson
  • Raja Maragani, Ericsson/TCS
  • David Westberg, Volvo

Agenda and Notes

  • Rollcall and Introductions
    • Everyone introduced themselves.
  • Agenda Bashing
    • Agenda is approved.
  • Appoint a chairman for the meeting
    • Kristofer Hallén nominated Fatih Degirmenci as the chair for the meeting.
    • Fatih Degirmenci accepted the nomination.
    • The group agrees.
  • Appoint a secretary for the meeting
    • Emil Bäckmark is the secretary for the meeting.
  • Decide on the bootstrap committee responsibilities
  • Decide on the members of the bootstrap committee
    • It is expected from BTC members to be able to spend a couple of hours/month for participation in meetings and review of PRs
    • Decided:
      • Fatih Degirmenci, Ericsson Software Technology
      • Ola Söder, Axis
      • Fredrik Fristedt, Axis
      • Daniel Ståhl, Ericsson
      • Emil Bäckmark, Ericsson
      • Raja Maragani, Ericsson/TCS
      • Henning Roos, Ericsson
      • Ewelina Wilkosz, Eficode
      • Mattias Linnér, Ericsson
      • Kristofer Hallén, Ericsson
      • David Westberg, Volvo
      • Christian Madsen, Grundfos
    • The people in the BTC should be the same as the maintainers in the Eiffel Community repo, i.e. this list will be reflected on Github after the meeting (AP Henning).
  • Decide if the committee should have regular meetings and if so how frequently
  • Decide on the chairman for the committee
    • Emil Bäckmark nominated Fatih Degirmenci as the chair for the Boostrap Committee.
    • Fatih Degirmenci accepted the nomination.
    • Decided: Fatih Degirmenci
  • Decide on a deadline for the bootstrap committee to run an election for technical committee
  • Status of community process documentation
    • Done: Governance
    • Done: License
    • Done: Project Maintainers
    • Done: Project Lifecycle
    • Done: Project List
    • Done but with an AP: Code of Conduct (this needs to be moved to community repo)
      • HR: It should probably not be moved as it is needed to fulfill the Github magic.
      • AP to BTC to sort this out
    • Done but with an AP: Contribution Guidelines (this needs to be moved to community repo)
      • HR: It should probably not be moved as it is needed to fulfill the Github magic.
      • AP to BTC to sort this out
    • Missing: Technical Committee Charter (pieces of this is in governance document but few things such as election process require to be decided and documented)
      • To be created/updated by BTC
    • Missing: Security/Vulnerability reporting and response processes (not available yet)
      • To be created/updated by BTC
    • Missing: Community Vision, Mission, Goals (not available yet)
      • To be created/updated by BTC
    • Missing: Election procedure - part of governance
  • Maillist/Google group: https://groups.google.com/g/eiffel-community?pli=1

Action Items