XSF Communications Team - 2020-07-05

  1. peetah

    I will have a look some times before the end of today

  2. emus

    okay, is fine

  3. peetah

    currently reviewing july newsletter: should'nt the images be hosted on xsf github accounts ?

  4. peetah

    I remember we decided to store them in content/images and I propose that we create a directory for each newsletter (i.e. july2020) and store the newsletter image in this directory

  5. peetah

    then they are refered like this in the newsletter: [profanity 0.9 screenshots](content/images/july2020/ "profanity 0.9") ✎

  6. peetah

    then they are refered like this in the newsletter: [profanity 0.9 screenshots](content/images/july2020/profanity09.jpg "profanity 0.9") ✏

  7. peetah

    then they are refered like this in the newsletter: [profanity 0.9 screenshots](/images/july2020/profanity09.jpg "profanity 0.9") ✏

  8. peetah

    then they are refered like this in the newsletter: [profanity 0.9 screenshots](/images/newsletters/july2020/profanity09.jpg "profanity 0.9") ✏

  9. peetah

    I correct: images could be stored in /content/images/newsletters/<monthYYY>/

  10. peetah

    this way pelican should deal with it automatically, but I don't know about the emailed newsletter and others ways of publication

  11. peetah

    emus: ^

  12. emus

    I have no clue tbh

  13. DebXWoody

    peetah: Markdown format for images it '![Alt Text](URL)' Alt Text will be displayed, if your browser do not support images. ✎

  14. DebXWoody

    peetah: Markdown format for images is '![Alt Text](URL)' Alt Text will be displayed, if your browser do not support images. ✏

  15. peetah

    DebXWoody: right, I missed the '!', but I'm pretty sure the text between double-quotes inside the parenthesis is the one used as the image title when you hover it

  16. DebXWoody

    peetah: Ah, right. https://nl.movim.eu/?blog/debxwoody%40movim.eu/182ed65c-c0cc-498e-a8d3-7b24bf60f9f0 this is like '![Test](https://codeberg.org/xmpp-messenger/eagle/wiki/raw/img/eagle/Screenshot_Addressbook_abook.png "ABC")'

  17. DebXWoody

    hover,.. Neumodischer Schnickschnack :-)

  18. peetah

    ya mein herr, whatever you said :)

  19. emus

    😂

  20. DebXWoody

    BTW, I like the idea of https://planet.debian.org/ this is a feed aggregator.

  21. Licaon_Kter

    DebXWoody: there's one for XMPP too...

  22. emus

    Planet Jabber

  23. DebXWoody

    Ah, on jabber.org

  24. emus

    peetah - I have no clue how to do the picutre situation right now. There are claims to provoke high traffic to website for the direct links. There are claims that we should not bloat the XSF repository. However, I prefer to keep our responsiblity on our side. And its not that we have many MB of data each time. I think it would be best to keep it at XSF as you said. To keep the data low we can reduce the number of pictures to 2. What do you think. But I would like to do that to the next version as I want to talk to the iTeam first on this

  25. emus

    ralphm: Hello ralph, may I have administrator rights? I want to edit the MUC description for each newsletter.

  26. emus

    Another question: There are a bunch of open PRs in the xmpp.org repo - https://github.com/xsf/xmpp.org/pulls Shall we consider to act on those from our side? SouL?

  27. peetah

    The picture situation has already been discussed several times. From my understanding, as jcbrand suggested, it was considered a better solution to keep images in the xsf control, and as verified with Nÿco , technically it is already feasible on the pelican side

  28. emus

    okay

  29. emus

    Will try tomorrow. You can also PR if you want