XSF Communications Team - 2020-03-29


  1. emus

    pep.: I worked everything into the newsletter draft. Also the XEPs to my best understanding. Would be good if you or someone else could compare. It should be only the recent edits https://wiki.xmpp.org/web/index.php?title=XMPP_Newsletter_April_2020&diff=12911&oldid=12910 about the XEPs from March

  2. pep.

    Is it ok if I have a look tomorrow? I'm still on a piece of code that I'd like to finish :)

  3. emus

    sure - actually I just finished, switched of the light and left that note at your "door" not expecting any reply 😁

  4. emus

    And now im going to bed

  5. emus

    got further than expected night

  6. emus

    got further than expected tonight

  7. pep.

    night

  8. emus

    Good night

  9. Link Mauve

    Note that GitHub also offers a wiki, using Markdown too (but maybe a different flavour?), fwiw.

  10. Link Mauve

    Note that GitHub also offers a wiki, using Markdown too (but maybe a different flavour than our Pelican?), fwiw.

  11. Link Mauve

    Note that GitHub also offers a wiki fwiw, using Markdown too (but maybe a different flavour than our Pelican?).

  12. emus

    I think its not good to rely too much on github

  13. SouL

    Hi emus, using GitHub directly sounds a good idea :)

  14. emus

    Ok cool!

  15. emus

    What do you think about the translation subpages? Ok, there is the problem with subcribtion I guess

  16. emus

    I think another advantage is that the acces to Github is easier. So we are hopefully able to motivate more people to participate

  17. emus

    I think another advantage is that the access to Github is easier. So we are hopefully able to motivate more people to participate

  18. emus

    What ever we decide on, do we need to approve that officially in a XSF meeting? or mention on the mailing list

  19. pep.

    nah

  20. pep.

    if people who participate agree then it's all good

  21. emus

    ok

  22. pep.

    for this at least

  23. emus

    ok fine

  24. emus

    pep.: Have you some time to check the xeps or review at all

  25. pep.

    I'm following the call while checking poezio PRs, will have a look afterwards :)

  26. emus

    kk

  27. emus

    just ping me

  28. emus

    pep.: I mean, we dont need today

  29. DebXWoody

    Hi. I don't use GitHub, but if I remember well, it's not possible to send PR for Wiki.

  30. emus

    Hmm, but I release the current draft as a PR?

  31. emus

    DebXWoody: https://github.com/xsf/xmpp.org/pull/689

  32. pep.

    DebXWoody, I think it is

  33. pep.

    Ah it's not

  34. pep.

    But it's a git repo as well

  35. pep.

    people can push to it

  36. pep.

    Which is more or less what happens for the current wiki anyway, once people have powers they can destroy the content if they want

  37. DebXWoody

    pep., Yes, but they need access

  38. pep.

    yeah sure, I think that's sane

  39. DebXWoody

    This was just a some note. Anyway, I like the idea (apart from that I don't like github )

  40. pep.

    I can go along with using the same markup syntax and saner-than-mediawiki versioning

  41. DebXWoody

    If you are going to add more people to the repository (to be able to work on the wiki), you may should think about protecting master branch of the repository. I think this should be possible - but I'm not sure.