On Fri, Dec 07, 2018 at 08:15:35PM +0000, Tedd Sterr wrote: > http://logs.xmpp.org/council/2018-12-05/#16:00:08 > > 1) Roll Call > Present: Jonas, Kev, Dave, Georg > Disparu: Link
Sorry about that, I didn’t get access to wifi before one hour later… > > 3.1) AOB > Jonas suggests making use of the time while waiting for late-comers to > discuss an AOB point about the Compliance Suites, as he agreed to do the next > iteration. Jonas wonders whether it would be better to make a new XEP each > year, or a single XEP that is versioned and updated - prefers the latter, as > it provides a canonical point to find the latest incarnation, and previous > versions would still be linkable via the attic. > Georg thinks previous discussion on this led to a decision of making new > XEPs. Dave thinks XEPs are cheap enough to have one each year, and iTeam > could generate a stable URI for the latest version. Kev prefers new XEPs with > a version rather than year (no commitment to a new one every year, but a new > XEP per incarnation); Jonas thinks this is non-obvious - how to know the > latest version number? - but a stable URI is interesting. > Georg suggests recycling the XEP number and just updating the year if the > contained list of XEPs remains the same; Dave likes that idea. > Zash thinks it would be cool if Council could draft “XMPP: A Vision for the > Future” as a complement to the Compliance Suites (“XMPP: State of the Art”); > Jonas and Dave agree. Georg says it would be great if someone (else) could > write a proto-XEP for the vision statement, though maybe XEP isn't the > appropriate tool - maybe a header in the XEP list, plus a prominent link to > the latest Compliance Suites. Jonas would prefer the wiki for the vision > statement, and doesn't like the idea of a header in the XEP list. > Kev wonders why a year is needed on the Compliance Suites at all (the > publishing year is always in there); Dave and Jonas scream "Marketing!" - > it's important to have something that's clearly recent to point at, and if > the year isn't in the title does it even exist. > Dave would like to hear from the community on this fascinating subject. Marketing is a good reason for transforming compliance suites into something very different, something that would be actually marketed. I’ve heard from people outside of our community that they have no clue about them, and have no indication of whether a client like Pidgin or Conversations is “compatible”. In a nutshell, let’s not bikeshed whether we publish a new XEP, change the latest one, or (the worst imo) create a new system, and decide whether we want to do actual marketing (XMPP 2: implement this and that and that) or continue on the current system and have that be invisible. > > 2) Elect a Chair > Dave suggests opening the vote, and Link Mauve will have to vote on-list > (usual two week expiry.) > Kev and Jonas shove Dave into the Circle of Nomination; Georg gets on board > and sticks his boot in; Dave tries to play it cool and 'decides' to stand. > > Kev: Dave > Jonas: Dave > Georg: Dave > Dave: Dave > Link: [pending] Dave, welcome as our chair! > > Dave asks about current Editors - Jonas claims to be about the only one doing > any actual Git work, and JCBrand does some good repository triaging. Dave > suggests poking Board to find some new slaves - Jonas doesn't think it would > hurt. > > 3.2) AMOB > Georg has been staring deep into the abyss that is 'Moved' - it's a mess. It > relies on presence subscribe/unsubscribe stanzas, which are ephemeral; so, to > make it work reliably would require something like account tombstones on the > old server (e.g. in PEP) and then <moved/> payloads could be sent in messages > to inform clients of the change. > Jonas suggests this might all be easier with explicit server support. > Georg says there are multiple sub-tasks: informing others of the move if they > add the old JID; updating friends' rosters to the new JID; informing friends' > clients of the old—new binding, so they can merge/cross-link chat history. > Georg wanted to be able to allow partial moves (move a selection/group to the > new account), but PEP tombstones wouldn't cover that. Georg expects a full > rewrite will be required to fix everything; Jonas says it was deferred and > abandoned, and a rewrite is better than another duplicate XEP, so he should > go ahead. > > 4) Next Meeting > 2018-12-12 1600 UTC seems okay for those present. WFM. > > 5) Close > Dave thanks all; all thank the Dave. > -- Emmanuel Gil Peyrot
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
