Nÿcoa lot of people contributed this month: https://wiki.xmpp.org/web/index.php?title=XMPP_Newsletter_January_2020&action=history
thanks a lot everybody, merci ! :)
Martin.has joined
Wojtekhas joined
debaclehas left
vanitasvitaehas left
vanitasvitaehas joined
genofirehas left
genofirehas joined
betahas left
debaclehas joined
betahas joined
betahas left
betahas joined
Vaulorhas left
Vaulorhas joined
betahas left
arnaudjhas left
Licaon_KterNÿco: too late to include this advisory?
https://github.com/ThomasLeister/prosody-filer/security/advisories/GHSA-qmfx-75ff-8mw6
vanitasvitaeLicaon_Kter: +1
betahas joined
ralphmhas left
betahas left
ralphmhas joined
betahas joined
betahas left
genofirehas left
genofirehas joined
Nÿcook, so what should our policy be?
my untold policy was: a news/info/release published a month is covered by the newsletter at the beginning of the next month
can this be kept? and we do an exception for alerts?
emusI think the last one is okay. but you are discussing to alter the previous newsleter after release?
pep.I'm also in favor of including security stuff to reach the most people possible
emusBut I wonder if changes to a release version make sense?
NÿcoI don't know about security advisories
they should be released/published/relayd as soon as they arrive
here, we only do a curation process, which happens once a month, so an alter could be one month old, which does not serve the purpore
arnaudjhas joined
emusBut wait, go a step back, this is a Newsletter
emusWe are not a security ticker
Nÿcoa newsletter published should not be touched, for be, because it is not reposted/re-relayed
NÿcoI agree @emus
emusOf course we should inform about it, but we shouldnt spam. we rather can provide or collected background ibformation about it
Nÿcoa summary of last month alerts is... well... not very useful
emusI would release important cases or refer to a ticker we run ourselfs seprarately
Nÿcoit is our duty as a commteam, but the newsletter is not the right vehicle
emusSometimes there are also blog posts with more ibfornation, could be put also in there
emus> it is our duty as a commteam, but the newsletter is not the right vehicle
Yes, maybe we need an extra tracker
emusThe newsletter can inform about the trackers exisitence
Nÿcohttps://wiki.xmpp.org/web/XMPP_Newsletter_January_2020 is copywritten, empty sections cleaned up
NÿcoI'll go on git now
Nÿco(just added the translations)
emus> (just added the translations)
What fo you meant?
Nÿcosorry, not clear: in the current January newsletter, I have added links to translations of the previous newsletter
Nÿcohttps://github.com/xsf/xmpp.org/pull/667 is ready for your reviews!
