Nÿcostarting the copywriting of the newsletter, means link collection is closed
Licaon_KterYou'll include Snikket too right?
Nÿconope, it's on 1st of Feb that has been announced :)
MartinWill you clarify that the 0.8.0 release announcement in the last newsletter was wrong?
Nÿcocan you please prepare me a short one-liner?
Nÿcowe could add a "sorry I f**ked up" section :)
MartinIn the last newsletter we announced the release of profanity 0.8.0 due to a misunderstanding. Please be aware that profanity 0.8.0 is not yet released.
Buuut, the 0.8.0 will come these days so maybe it will be released by the time people read the newsletter. So maybe add some date of the newsletter deadline?
Martin> we could add a "sorry I f**ked up" section :)
Licaon_Kter> nope, it's on ???st of Feb that has been announced :)
Licaon_KterMartin: if it's announced in Feb doesn't matter...
Licaon_Kter..for January's newsletter
MartinI know, but saying it is not yet released but maybe it got released yesterday seems also weird. So say is not yet released by the date of. ..
Nÿco> So maybe add some date of the newsletter deadline?
the planning section is always there:
Nÿco> In the last newsletter we announced the release of profanity 0.8.0 due to a misunderstanding. Please be aware that profanity 0.8.0 is not yet released.
Ge0rGI've released yaxim 0.9.9 in January, but I honestly wasn't able to add it to the wiki yet
Licaon_KterNo F-Droid version? Meh no lauch :))
Licaon_KterNo F-Droid version? Meh no launch :))
NÿcoGe0rG : it's added! (and tested)
Ge0rGNÿco: aweomse, thanks. Will it land in the January newsletter? I'm so excited! :D
Nÿcogreat update, btw
pep.Nÿco, I'm compiling minutes for the Summit. When do you think the newsletter gets out?
pep.I don't think I'll make it for today though, there are quite a few pieces missing in the minutes and I'd like to poke people who lead some topics again
Nÿcook, got it
Nÿcoso, I drafted this:
As usual in this period of the year, the community of protocol makers united in the XMPP Summit. Two days of sharing and building the future of XMPP. This year has been productive, we covered various subjects such as:
XMPP Shortage Audit
Easy Passwordless Onboarding and Account Management
Account Rich Presence in PEP
End-to-End Encryption Key Management
Palaver IM Client
Why Push Notifications are not good enough?
commTeam ("Lightning talk")
Inbox / Unread / Bind2
XMPP as mandatory standard? (Lightning talk)
XHTML-IM2 / Rich markup
We will probably cover all these in more depth next month.