Difference between revisions of "Board-Meeting-2023-02-16"

From XMPP WIKI
Jump to navigation Jump to search
Tags: Mobile web edit Mobile edit
 
(3 intermediate revisions by the same user not shown)
Line 36: Line 36:


- Edward wants to take over organization here
- Edward wants to take over organization here
= Minutes =
roll call
* board members: Matthew, Peter, Ralph
* regrets: Edward
* other folks: Daniel Gultsch
(Ralph summarizes)...
* follow up on FOSDEM conversations (e.g., with Stuart)
* opportunity to play a role on interoperability
* EU legislation on the way
* we haven't been at the table to participate in these discussions
* upcoming interoperability workshop in Brussels
* https://competition-policy.ec.europa.eu/dma/dma-workshops/interoperability-workshop_en
* https://competition-policy.ec.europa.eu/system/files/2023-02/20230227_dma_interoperability_workshop_agenda.pdf
* Ralph will attend (only one representative per organization)
* it should be relatively easy for us to raise funds to work on this
* if we formulate a good plan
* might be a challenge if that money flows through the XSF
* best could be if XSF functions as a fiscal host
Matthew:
* we need to figure out what we want to achieve
* this first workshop could be a good way to test the waters
* agree that we don't want to become a large organization with much money
* the fiscal hosting could be a good framework
Peter:
* yes, putting together a plan is the first step
* let's figure out the opportunities and what resources are needed (also the timeframe)
* AI: Peter create a stub plan on the wiki
Ralph:
* this workshop at the end of February seems like a good place to start
* supposedly EU expects to enforcing interoperability by 2025
topic: IETF MIMI WG
* definitely a reaction to the DMA
* but framed in a more neutral manner
* the gatekeepers might never adopt it
* and they're not involved in the WG
* it's not necessarily the case that MIMI will 100% succeed or 100% fail
* three layers: transport, encryption, content
* a document about XMPP as transport layer could help in the MIMI effort
* one challenge is e2e encryption
* if we have an MLS profile in XMPP, would that solve the problem?
* not really, because there are MLS parameters and they differ across systems
* XMPP MLS profile would help
* content layer is all being designed from scratch
* what is the delta between what we have and what the requirements are?
topic: why XMPP is a protocol of choice
* we can do a better job of this
* perhaps an initiative to create this
topic: workshop panel about interoperability and security
* representatives from Cisco, META, Mozilla, etc.
* AI: Peter to reach out to likely attendees
topic: a few thoughts on plans
* transport (and perhaps encryption and content) draft for MIMI
* MLS profile for XMPP (there's already activity here by people Matthew mentions)
* roadmap for EU interop
topic: engagement with XMPP vendors
* XSF should be more active here

Latest revision as of 18:16, 16 February 2023

Coordinates

Agenda

Follow-up:

  • Try to talk to the Matrix project to see how we can have true federation (with or without MIMI).
  • Participate in MIMI.
  • Making work on MLS on XMPP a priority.

(+1 on each point by Eddie)

Invitation to Podcast in H2 (~Sept)

  • I think we should join with at least two of us + discuss a communication line
  • Do we need confirmation by board?
  • Anyone from Board beaides me can attend?

Daniel G. proposal

  • Eddie: Well, if we ramp up sponsoring anyway, then still lets go for it if they subscribe. Basically +1 to not miss this chance

FOSSY conference in Portland this summer

~Edward applies for direct access to the twitter account~

Call to Order / Quorum

Returning Business

New Business

AOB

Date of Next Meeting

- Edward wants to take over organization here

Minutes

roll call

  • board members: Matthew, Peter, Ralph
  • regrets: Edward
  • other folks: Daniel Gultsch

(Ralph summarizes)...

Matthew:

  • we need to figure out what we want to achieve
  • this first workshop could be a good way to test the waters
  • agree that we don't want to become a large organization with much money
  • the fiscal hosting could be a good framework

Peter:

  • yes, putting together a plan is the first step
  • let's figure out the opportunities and what resources are needed (also the timeframe)
  • AI: Peter create a stub plan on the wiki

Ralph:

  • this workshop at the end of February seems like a good place to start
  • supposedly EU expects to enforcing interoperability by 2025

topic: IETF MIMI WG

  • definitely a reaction to the DMA
  • but framed in a more neutral manner
  • the gatekeepers might never adopt it
  • and they're not involved in the WG
  • it's not necessarily the case that MIMI will 100% succeed or 100% fail
  • three layers: transport, encryption, content
  • a document about XMPP as transport layer could help in the MIMI effort
  • one challenge is e2e encryption
  • if we have an MLS profile in XMPP, would that solve the problem?
  • not really, because there are MLS parameters and they differ across systems
  • XMPP MLS profile would help
  • content layer is all being designed from scratch
  • what is the delta between what we have and what the requirements are?

topic: why XMPP is a protocol of choice

  • we can do a better job of this
  • perhaps an initiative to create this

topic: workshop panel about interoperability and security

  • representatives from Cisco, META, Mozilla, etc.
  • AI: Peter to reach out to likely attendees

topic: a few thoughts on plans

  • transport (and perhaps encryption and content) draft for MIMI
  • MLS profile for XMPP (there's already activity here by people Matthew mentions)
  • roadmap for EU interop

topic: engagement with XMPP vendors

  • XSF should be more active here