Versions Compared

Old Version 30

changes.mady.by.user Peter Monks

Saved on

compared with

New Version Current

changes.mady.by.user Peter Monks

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

Avatar
Member
Organization
Role
ESCo role
John StecherGoldman SachsManaging DirectorBoard Lead
Lawrence MillerSymphony LLCEVP, Global TechnologySymphony Lead
Gabriele Columbro [Administrator]Symphony Software FoundationExecutive DirectorSecretary / Non Voting

...

TimeItemObjectivesCommentsDecisions / Resolutions
10minReview action items from previous meeting

Zero inbox (smile)

All tasks from previous meeting, except 1 deferred to next meeting.Defer to the next meeting:
  •  GC / MH: start working on a plan for Symphony readiness to open source and contribute 
10minESCo voting process
  • Quorum?
  • Majority?
  • Time / deadline for email votes?
  • Silent consensus?
  • Simple majority always applies?
  • Tie-breaker?

  • The Quorum to deliberate is 2/3 of the ESCo Project Leads.
  • The Majority required to deliberate is absolute majority (50% + 1)
  • The default deadline for email votes is 72h, unless otherwise specified.
  • Can votes be approved by silent consensus? No
  • Does the ESCo adopt resolutions by super-majority? No
  • There is no need for a tie-breaker. In case of tie the motion is not passed as the majority needs to be absolute (50% + 1).
10minESCo members rotation
  • Ratify 2y membership? Yes
  • Ratify staggering? Yes
  • So call a members meeting (special or regular in May) to elect the 2 new Member leads? Yes
  • And then all together elect ESC Community Members?

LM: Implement proper staggering, keeping in consideration community and working group actual involvement.
  • Project Leads will serve for a term of 2 year in the ESCo
  • ESCo will implement staggering for the ESCo member rotation, to ensure max 50% of the ESCo composition is changed at one time 
  • The two remaining Project Leads (Member Leads) This will naturally happen with the election of new Member Leads in May in the annual Member meeting.
  • Once the Project Leads are filled, all together they will elect the ESC Community Leads
5minSelection of symphonyoss.org naming

Gab presented that the Foundation acquired:


LM: We need to clarify, too many domains (e.g. symphony.foundation, symphonyOSF) Naming approved.
15minContribution process

Gab to present Projects and legal documents.


  • Deferred to next meeting
  • ESCo members to review and contribute to Projects
10minDiscuss Acceptance criteriaDocs, code standards, license headers, code formatting, etc.
  • Deferred to next meeting
  • ESCo members to work on acceptance criteria and contribute to Projects (section about acceptance criteria)

...

This is a record of items to be completed by this meeting:

  •  Gabriele Columbro: Create conference rooms for symphony-dev / symphony-users (access should be moderated) - approved
  •  Gabriele Columbro:  Reach out to members for working groups candidature (10 days deadline + clear responsibilities)
  •  Gabriele Columbro: Check in bylaws who nominate working groups member <-- ESCo
  •  ESCO members: define criteria of acceptance for Symphony contribution <-- Initial DRAFT available
  •  ESCo members: Check whether archive is visible with corporate email address

...