Nÿcowho wants to proof-read the test emailing? (it is only sent to me, I will forward it)
SouLI can't unfortunately :( I'm on a long meeting starting now
Nÿcoso it's very dfficult, I don't know how to handle the copy-paste, as both Atom and GitHub rendered Markdown suck
Nÿcooops, btw the markdown is not right in the Specs section with unordered lists with - and *
wurstsalatI did that just like in the last newsletter
Nÿcowell it does not work on Tinyletter, nor on GitHub's MD flavor, I don't know for Pelican
NÿcoI'll have to pause for a series of meetings
NÿcoI've resumed the newsletter: if you can review it in the next 30 min, I'd be happy to have any help
peetahgajim screenshots appear above their introducing line
NÿcoI've seen that, but the is good
Nÿcoanyway, I've got it right in the newsletter
peetahextensions bullet points are all at the same level
Nÿcoyeah, noticed as weel, commented in thr PR
Nÿcoit is a mix of - and *
peetahoh you mean it is a github rendering issue rather than a problem with the markdown
Nÿcoyes, on that one precisely
Nÿcoit renders correctly on Atom (by GitHub)
peetahVersion 1.3.0 of [XEP-0068] => the link is not rendered on github
Nÿcoyes, commented as well
Nÿcoit seems a copy-paste issue
peetahsorry I did not notice you made comments, I was looking at the raw file and the github rendering
Nÿcooh and wrong yax.im link
Nÿcook yax.im is rendered in the newsletter... 😢
Nÿcothe newsletter is ready to go
Nÿcono help on reviewing it in your inbox?
Nÿcoyou trust me too much... 😢
Nÿcoon the blog, we can always fix it afterwards, it is a PR away
on the newsletter, once it's sent... well, too late 🙂
debacleEat your own dog food!
allo asks rightfully, why they cannot subscribe to the newsletter via XMPP
I suggest to arrange with edhelas, that XSF commteam has their own pubsub node on movim.eu and post there.
This can currently only used by movim and salutatoi, but DebXWoody is working on a desktop client for pubsub ;-)
Nice about pubsub: Typos can be fixed!
vanitasvitaeThats a great idea 😀
debaclethe idea comes from the first comment by mastodon user j.r
Nÿcoabsolutely, I tried in the past, but first you have to create a specific account, easy, but then you must again copy-paste it here, and I had issues, so that was way too much time spent for me
vanitasvitaeCan't you just bridge the RSS feed over?
Nÿcoso, no red light for the newsletter? I'll send it
vanitasvitaeI think edhelas had some rss2pubsub tool
Nÿco> Can't you just bridge the RSS feed over?
I had not thought of that, so I have not looked for it
debaclevanitasvitae Nÿco AFAIK it must be clean Atom XMPP
debaclevanitasvitae Nÿco AFAIK it must be clean Atom XML
> Nÿco AFAIK it must be clean Atom XML
vanitasvitaeedhelas thought of everything!
vanitasvitaeMaybe edhelas can be talked into bridging the newsletter?
vanitasvitaeafaik he already bridges a number of feeds
debacleI'm subscribed to Planet Jabber via Movim.
NÿcoI'm sending the newsletter
last issue, it was 361
Nÿcoso now I'm on the social media content
pep.Yeah one would "just" need to run atomtopubsub / feedcleaner and put that on an xmpp.org pubsub component to make it somewhat official
pep.Otherwise anybody can run these things and put that on their own pubsub component
pep.Nÿco, yeah.. since it's not really defined what's official and what's not :p
Nÿcofor example, I have created the fosstodon/mastodon @xmpp account and I'm the only one having the password
Nÿcoindeed, that's what I meant
Nÿcofrom my perspective, I prefer to have something setup and non-official, as long as it is benevolent
DebXWoodyAFAIK there is a Blog for the newsletter on movim. The problem, for RSS Feeds there are some things nor possible (Share, Comments). It would be nice to have a real pubsub for XMPP. I think it will be possible give access on this node for different accounts.
Nÿcooh wait, I have the first stats for this newsletter! 🙂
emus> Eat your own dog food!
> allo asks rightfully, why they cannot subscribe to the newsletter via XMPP
> I suggest to arrange with edhelas, that XSF commteam has their own pubsub node on movim.eu and post there.
> This can currently only used by movim and salutatoi, but DebXWoody is working on a desktop client for pubsub ;-)
> Nice about pubsub: Typos can be fixed!
And RSS feed?
DebXWoodyIt looks that Movim is using XEP-0277: Microblogging over XMPP. On Movim you can just write you information in md-syntax and will be pushed via PubSub. At least what I understood so far. I started to write a application to be able to read those microblogs: https://nl.movim.eu/?blog/DebXWoody/b1fb0016-1992-425e-ae45-0c7d9d027e3c
vanitasvitaeNÿco, can you add a link to the rss feed of the newsletter as "Newsletter" to the @xmpp fosstodon account's profile?
vanitasvitaeMaybe below "Website"?
vanitasvitaeHm, I don't find the newsletter landing page particularly appealing.
vanitasvitaeI'd prefer if the link would automatically contain the latest issue of the newsletter
vanitasvitaeNot sure if that's easy to do though
vanitasvitaeBut having the newsletter page contain the latest post would be a nice improvement in my opinion
MartinMaybe the paragraph advertising to sign up to the newsletter could be omitted from the email newsletter in the future. It's not very helpful for people who read the newsletter in their mailclient because they already are subscribed.
debacleDebXWoody Note, that you can post to Movim using "jp", the command line tool of salutatoi. With jp, you can even create the id for your article yourself, which then is used by Movim for the URL. E.g. "eagle_movim_microblog" instead of "b1fb0016-1992-425e-ae45-0c7d9d027e3c".
debacleBut you might have the feature in eagle soon, anyway :-)
DebXWoodyCool! Still working on OX
DebXWoodyBut I'm able to send a OX message from eagle to profanity.
debacleDebXWoody Gajim also can talk 🐂 with the gajim-openpgp plugin.
DebXWoodyprofanity -> gajim is also working
DebXWoodyneeds longer weekends ;-)
Nÿco> Nÿco, can you add a link to the rss feed of the newsletter as "Newsletter" to the @xmpp fosstodon account's profile?
let me check
NÿcoI got caught, but it's done: is it ok?
Nÿco> Maybe the paragraph advertising to sign up to the newsletter could be omitted from the email newsletter in the future. It's not very helpful for people who read the newsletter in their mailclient because they already are subscribed.
differentiating by channel is the way to go
but I already have to manage so many differences that not adding one can help
emusSouL I merged the pull request. Now I just need to wait? https://github.com/xsf/xmpp.org/blob/master/content/posts/newsletter/2020-05-01.md
Nÿcoyes, wait... and cry or celebrate 🙂
Nÿcoso, I've not been able to find time to draft the social media content... argh
wurstsalatemus, as soon as you open the next PR I’ll add the newest XEP updates ;)
peetahbefore opening the next PR, why does it have to be done via emus repo ? would'nt it be easier for any newcomer to modify the file directly on xsf repo ?
Nÿcowell, can you edit on both repos wia the website?
peetahnope only via emus repo
peetahand I can't understand why
emuspeetah: I dont know actually and dont understand neither
emusI thought you could just merge request directly
Nÿcoemus, I used to do this, create a PR from the XSF repo
emusNÿco: I did so
emuswill check later
Martinpeetah: emus creates a PR against the xsf repo and the you PR against his PR therefore in his repo. So the work is done in his fork and merged when it's ready. At least this was my understanding when I participated last month.
emusMartin: I think you are right. But is that the normal way?
emusMartin: I think you are right. But is that the way togo?
peetahso this allows someone (here emus) to have the lead on the PR, rather than having everything going through xsf repo authorized users , am I right ?
MartinDon't know I'm no Gitguru.
Martin> so this allows someone (here emus) to have the lead on the PR, rather than having everything going through xsf repo authorized users , am I right ?
I think that's the intention.
emuspeetah: I think I will add a default @mynick, so I will be informed all the time
emusI can offer you guys merge rights to my repo?
emusI you guys want to go back to use the wiki, feel free to do so. I have no motivation at the moment anyway
peetahI don't need it, I was more concerned about the non intuitive way of going through the xsf PR, then click on emus PR and then look for the file to edit it
emusWe can also go for full open, and just use yo pad or something. then we just archive the final step or log for review
emusThe intention for Github was to remove one step of formating. Also with a midterm view to host translations by xsf aswell. So you have fewer formatting hassle. Thats anyway not good as there are so many different formatying steps...
DebXWoodyI think it is quite nice: https://nl.movim.eu/?node/pubsub.movim.eu/xmpp
emusI don't know how to improve PR commit situation. I can try to give you rights in my repository.
DebXWoodyProfanity 0.9.0 has been released: https://profanity-im.github.io/blog/post/release-090/
emusCan someone just test to make a PR - eventually, there is no fork inbetween anymore
emusCan someone just test to make a PR? - eventually, there is no fork inbetween anymore
emusI think newsletter-july2020 is now just a branch in the XSF repostiory, not in mine, maybe that is better now. But I am not a gitguru either
emusI think newsletter-july2020 is now just a branch in the XSF repository, not in mine, maybe that is better now. But I am not a gitguru either
peetahbut I can't edit from the draft PR: I have to click on newletter-July2020 branch, look for the file and then edit it.
peetahit feels counter intuitive to me, but may be that's the only way to achieve what we're trying to do
peetahanyway, thanks for successfully removing one layer in this process
peetahanyway, thanks for having successfully removed one layer in this process
peetahanyway, thanks for having successfully removed one layer of this process
emus😅️ ehh that you now cannot edit anything doesn not sound like success to me 😀
emusI dont see any commits anywhere
emusso you went to Files Changed, then the three dots?
peetahemus: check the PR list or xsf repo
emusthats very good!
emusJust @mention me in the next one!
emusbut is that harder for you now?
peetahnot harder, not easier :)
peetahit just doesn't take me to your repo anymore
emuswhy are their two commits? Because I renamed the one from peetah? that was not good?