[Standards] 2017-04-19 XSF Council Minutes

2017-04-19 XSF Council Minutes == Present: Tobias, Link Mauve, SamWhited, daniel Minute taker: jcbrand 1). Link Mauve's SHA-1 migration plan Nothing new to report from Link Mauve. Tobias offered to help and Link Mauve accepted, saying that he'll share his

Re: [Standards] [Council] Council Meeting Minutes April 5th 2017

On Wed, Apr 12, 2017 at 10:14 AM, Dave Cridland wrote: > I'd be interested in Sam's counter-arguments, mind. - Discoverability: if or or whatever is only used from carbons, why do I have to click through to a different long XEP to find the one hint that I care about while

Re: [Standards] [Council] Council Meeting Minutes April 5th 2017

On Wed, Apr 19, 2017 at 9:29 AM, Tobias M wrote: > Having an own XEP for each hint feels a bit over the top. I agree, let's not do this. > Moving each hint to the XEP that uses it would lead to duplication of hints > or one XEP using > a hint defined in an otherwise

Re: [Standards] Council Meeting Minutes April 5th 2017

> On 12. Apr 2017, at 13:43, Daniel Gultsch wrote: > > 4) Vote on advancing XEP-0334: Message Processing Hints > Everyone to vote on list. > Sam considers voting -1 because it includes functionality that should > probably exist as part of other XEPs. > Daniel agrees that

Re: [Standards] [Council] Council Meeting Minutes April 5th 2017

On 19.04.2017 15:25, Tobias Markmann wrote: > > On Wed, Apr 12, 2017 at 5:14 PM, Dave Cridland > wrote: > > So, Carbons is the only consumer of - at least for now. But > is used by, at least, XEP-0313 and XEP-0136, as well as > (in

Re: [Standards] [Council] Council Meeting Minutes April 5th 2017

On Wed, Apr 12, 2017 at 5:14 PM, Dave Cridland wrote: > So, Carbons is the only consumer of - at least for now. But > is used by, at least, XEP-0313 and XEP-0136, as well as > (in principle) MUC web logs, offline storage, and so on. > > Moreover, hints work well for