Re: [Standards] Call for new compliance suites author

2018-03-19 Thread Kevin Smith
On 17 Feb 2018, at 16:58, Jonas Wielicki wrote: > > On Samstag, 20. Januar 2018 11:24:50 CET Stefan Hamacher wrote: >> Hi! >> >> Am 19.01.2018 um 22:46 schrieb Peter Saint-Andre: >>> Did the publication of compliance suites in 2007, 2009, 2010, or 2012 >>> solve any of the issues we hope the 201

Re: [Standards] Call for new compliance suites author

2018-02-17 Thread Jonas Wielicki
On Samstag, 20. Januar 2018 11:24:50 CET Stefan Hamacher wrote: > Hi! > > Am 19.01.2018 um 22:46 schrieb Peter Saint-Andre: > > Did the publication of compliance suites in 2007, 2009, 2010, or 2012 > > solve any of the issues we hope the 2018 suite will solve? If not, was > > that because we didn'

Re: [Standards] Call for new compliance suites author

2018-01-22 Thread Jonas Wielicki
On Freitag, 19. Januar 2018 11:31:49 CET Sam Whited wrote: > If that sounds like you, please reach out and I'd be happy to help you get > started picking back up where I left off. I’ll be happy to take over the '18 suites for the sake of getting them published this week. I don’t know what the co

Re: [Standards] Call for new compliance suites author

2018-01-20 Thread Tedd Sterr
> Date: Fri, 19 Jan 2018 12:13:44 -0600 > From: Sam Whited > I also hope they make it far easier to navigate the XEPs list. When I talk to > developers at events and mention XMPP one of the biggest complaints I get is > "oh, we looked at XMPP but there were multiple things to implement the > f

Re: [Standards] Call for new compliance suites author

2018-01-20 Thread Stefan Hamacher
Hi! Am 19.01.2018 um 22:46 schrieb Peter Saint-Andre: > Did the publication of compliance suites in 2007, 2009, 2010, or 2012 > solve any of the issues we hope the 2018 suite will solve? If not, was > that because we didn't active tell developers about it? If I may just drop my 0.2c: In my opin

Re: [Standards] Call for new compliance suites author

2018-01-19 Thread Peter Saint-Andre
On 1/19/18 11:40 AM, Daniel Gultsch wrote: > 2018-01-19 19:13 GMT+01:00 Sam Whited : >> On Fri, Jan 19, 2018, at 11:55, Peter Saint-Andre wrote: > >> I also hope they make it far easier to navigate the XEPs list. When I talk >> to developers at events and mention XMPP one of the biggest complaint

Re: [Standards] Call for new compliance suites author

2018-01-19 Thread Daniel Gultsch
2018-01-19 19:13 GMT+01:00 Sam Whited : > On Fri, Jan 19, 2018, at 11:55, Peter Saint-Andre wrote: > I also hope they make it far easier to navigate the XEPs list. When I talk to > developers at events and mention XMPP one of the biggest complaints I get is > "oh, we looked at XMPP but there wer

Re: [Standards] Call for new compliance suites author

2018-01-19 Thread Sam Whited
On Fri, Jan 19, 2018, at 11:55, Peter Saint-Andre wrote: > I have a meta-level question: of what use are the compliance suites and > are the benefits worth the costs? I think they're (probably) worth having just because they encourage clients and servers to implement the things on the list and do

Re: [Standards] Call for new compliance suites author

2018-01-19 Thread Kevin Smith
On 19 Jan 2018, at 17:55, Peter Saint-Andre wrote: > I have a meta-level question: of what use are the compliance suites and > are the benefits worth the costs? I think the main two benefits could be 1) Give an intended direction of travel 2) Give a guideline on what implementors practically need

Re: [Standards] Call for new compliance suites author

2018-01-19 Thread Peter Saint-Andre
I have a meta-level question: of what use are the compliance suites and are the benefits worth the costs? Peter On 1/19/18 10:31 AM, Sam Whited wrote: > Hi all, > > As you might know I've been trying to revive the compliance suites that the > XSF last published (in draft/final form) in 2012. >

[Standards] Call for new compliance suites author

2018-01-19 Thread Sam Whited
Hi all, As you might know I've been trying to revive the compliance suites that the XSF last published (in draft/final form) in 2012. The compliance suites are lists of features and XEPs that serve three purposes: - To offer client/server authors a minimal set of XEPs that should be implement