XSF Discussion - 2019-11-14


  1. nyco

    Neustradamus please give full access to ralphm at least

  2. nyco

    there, I tried it, we'll see what happens: https://www.linkedin.com/feed/update/urn:li:activity:6600654130799304704

  3. Ge0rG

    That's not visible without submitting to LinkedIn

  4. nyco

    submit what?

  5. nyco

    you mean that's another Walled Garden? yes, it is... but the people we want to reach out to are there

  6. jonas’

    nyco, submit yourself

  7. nyco

    right

  8. Ge0rG

    I once got a contact invitation from a person I was very interested in a business contact with. After registering on LI and actually talking to them it turned out that we both fell for LI dark patterns

  9. Ge0rG

    Most of the people who "are there" aren't there by active choice but because they were tricked into it. Just saying. No action required.

  10. !XSF_Martin

    Ge0rG: LI is like an international xing?

  11. Ge0rG

    !XSF_Martin: yes, but less ethical.

  12. !XSF_Martin

    Xing is ethical?

  13. Ge0rG

    !XSF_Martin: that's not what I said

  14. !XSF_Martin

    If it is more ethical than something else means it's not not ethical. 😃

  15. Seve

    I thought Xing was "eatn" by LinkedIn

  16. !XSF_Martin

    Dunno, didn't log in in years I guess.

  17. !XSF_Martin

    Now I want to hear 'eaten' 'my one desire my only wish is to be EAATEEEEN'

  18. Seve

    I thought Xing was "eaten" by LinkedIn

  19. Ge0rG

    !XSF_Martin: your conclusion is wrong. Even among two unethical entities, one can be less ethical than the other.

  20. jonas’

    -10000 < -1000 is true, not just -10000 < 2

  21. Ge0rG

    It's not a binary property, unless you are part of a fundamental religious group (which is unethical in its own ways)

  22. ralphm

    If you mean that ethics are fluid and subjective, sure.

  23. !XSF_Martin

    Ge0rG, jonas’: Than I would rather say xing is less unethical than li if both are negative. 😃

  24. Ge0rG

    !XSF_Martin: which would mean that xing is better, whereas what I said means that LI is worse.

  25. nyco

    https://linguistics.stackexchange.com/questions/981/is-double-positive-meaning-negative-a-common-phenomenon

  26. jonas’

    Ge0rG, "even less ethical" would’ve worked to convey that

  27. Ge0rG

    jonas’: thanks, didn't think of that

  28. !XSF_Martin

    jonas’: That's the best way to express this I think. 😃

  29. nyco

    FYI: https://wiki.xmpp.org/web/Social_Media

  30. Holger

    How would clients using multi-item PEP nodes (such as for Bookmarks 2) handle the case where the number of bookmarks exceeds the max pubsub#max_items value the server accepts? "Dear user, you can't add this room without ditching another?"

  31. pep.

    badly, for sure

  32. pep.

    But then you're asking for infinite storage? (if it's not for bookmarks2 it'll be for something else)

  33. pep.

    Think pubsub nodes in movim/sàt (communities)

  34. pep.

    edhelas, goffi ^ (how) do you handle that?

  35. Ge0rG

    Holger: the server should refuse adding new items in such a case, with a proper error, and clients should display that to the user

  36. Holger

    I would've thought this is not just an academic issue as many (non-recent?) servers won't accept pubsub#max_items > 1 or > 10 or so. Movim/Sàt always required servers with good PubSub support, clients joining rooms didn't.

  37. Holger

    Ge0rG: Awesome UX.

  38. pep.

    Holger, anybody can use a movim instance.. I can join with my crappy server config and still be able to post something on microblog :P

  39. pep.

    Also https://mail.jabber.org/pipermail/standards/2019-October/036503.html

  40. Holger

    pep.: I forgot whether

  41. Ge0rG

    Holger: not sure if sarcastic

  42. Holger

    pep.: I forgot whether Movim uses PEP nodes (at least for comments), where the limits are often way more restrictive.

  43. pep.

    Holger, it depends on the user's account

  44. pep.

    For communities it depends on the pubsub server that's being used?

  45. Holger

    Ge0rG: I'm just unsure whether the advantages of Bookmarks 2 really outweigh this downside right now. But I get how multi-item PEP is the new hot thing, and I get how it's nicer in theory.

  46. Ge0rG

    Holger: yes

  47. Link Mauve

    Holger, I would expect clients to not use bookmarks 2 before servers expose the urn:xmpp:bookmarks:0#compat disco#info feature.

  48. Link Mauve

    And servers with a limit of ten bookmarks shouldn’t advertise this feature.

  49. Link Mauve

    Prosody’s current limit is 255 items, which does feel low (I’m at 100+ already) but should be usable for most people.

  50. pep.

    What Holger asks though doesn't just apply to bookmarks2

  51. pep.

    People only using XMPP as chat are just now starting to realize it's an issue but it has always been there

  52. Neustradamus

    Any news for an XMPP planet and that I have requested since several years ago?

  53. pep.

    Any news about Linkedin?

  54. ralphm

    scroll up

  55. Seve

    What is the request? Change the name?

  56. Link Mauve

    Yes, I remember ten years ago when I was working on a blogging engine and had to write my own PubSub component because Ejabberd’s didn’t provide me the features I needed.

  57. Neustradamus

    pep.: If you follow here, you have seen ;)

  58. pep.

    wow, stuff happened

  59. Neustradamus

    January 1999: Jabber is born October 2004: Jabber has been renamed to XMPP: https://tools.ietf.org/html/rfc3920 October 2006: Jabber Enhancement Proposals (JEPs) -> XMPP Extension Protocols (XEPs) January 2007: Jabber Software Foundation -> XMPP Standards Foundation Now, maybe after several years of battle, planet.jabber.org will be move to planet.xmpp.org?

  60. MattJ

    and jabber.org... what should happen to that?

  61. Ge0rG

    CNAME it to matrix.org

  62. Seve

    jabber.org is not XSF, isn't it

  63. Zash

    Nor is planet.jabber.org

  64. MattJ

    Correct (to both)

  65. Seve

    Then Neustradamus the request would be to ask the XSF to have its own planet

  66. MattJ

    which duplicates one that already exists, so I'm guessing the XSF will decide not to :)

  67. Maranda

    Planet X?

  68. Maranda

    There's one already!

  69. Zash

    Does it help facilitate discussion or manage XEP development? If not, hard to see how it should be run by the XSF.

  70. Seve

    Weeell, that could be debatable, but I see your point.

  71. Ge0rG

    There is a difference between jabber and xmpp that nobody wants to acknowledge

  72. Zash

    Who's this 'nobody'?

  73. pep.

    Jabber is the company name that was sold to Cisco, and XMPP is the protocol name? :p

  74. fippo

    zash: that is unclear but he shot jack beauregard

  75. Seve

    Ge0rG, enlighten us

  76. Ge0rG

    Seve: jabber is the federated IM network based on the XMPP protocol. Also a Cisco trademark

  77. Zash

    Something something "jabber" more community than the protocol

  78. pep.

    I'd limit Jabber to Jabber Inc. fwiw, and the XMPP protocol. The rest is just confusion to me

  79. pep.

    I'd limit Jabber to Jabber Inc. fwiw, and XMPP to the protocol. The rest is just confusion to me

  80. Ge0rG

    pep.: because you are not part of the huge jabber user base, which mainly happens on other continents

  81. pep.

    not sure I understand

  82. Link Mauve

    Ge0rG, even in France there are a lot of Jabber users.

  83. Link Mauve

    People who will look at you as if you spoke Greek to them if you tell them about XMPP.

  84. ralphm

    There's no battle over Planet Jabber, by the way. Just a difference of opinion, Neustradamus.

  85. Ge0rG

    pep.: play a bit with https://trends.google.com/trends/explore?q=xmpp,jabber

  86. pep.

    Ge0rG, yes, confusion :P

  87. nyco

    Ge0rG the problem is "jabber" is a common language term

  88. pep.

    People saying Jabber when they're actually using XMPP

  89. Ge0rG

    pep.: in Russia for example, almost nobody knows "xmpp" but many tech people know "jabber"

  90. Ge0rG

    pep.: you "are using xmpp" when you develop an IoT middleware. You "are using jabber" when you do XMPP-federated IM

  91. MattJ

    I've had the "Oh! You mean Jabber" response multiple times

  92. nyco

    there is confusion indeed, that's why I often use both, as "Jabber/XMPP" or "XMPP/Jabber", and afaik it kind of works

  93. pep.

    MattJ, I have too. That doesn't mean..

  94. MattJ

    from a range of different people

  95. Seve

    Jabber? that old thing for chat?

  96. Seve

    Is what people tell me

  97. pep.

    That ^

  98. MattJ

    pep., trying to define these words in this chatroom is like writing a dictionary that doesn't reflect real world language

  99. Ge0rG

    Speaking of hosting. Our MLs are hosted on mail.jabber.org, is that wrong as well?

  100. MattJ

    Many people still actively use Jabber, and yes, as far as they are concerned it is a 20 year-old thing (but still functional)

  101. MattJ

    and generally Pidgin is the best way to connect to it, in my experience

  102. pep.

    MattJ, sure it's not what I'm saying

  103. Ge0rG

    pep.: https://mail.jabber.org/pipermail/members/2017-July/008586.html didn't went very far, unfortunately

  104. Ge0rG

    Luckily, this is all off-topic for the XSF, and there is no other organization tasked with making XMPP-based IM more popular.

  105. Ge0rG

    So the whole discussion is moot.

  106. Ge0rG

    Unless, you know, somebody founds a Jabber Software Foundation and gets appropirate permits from the XSF.

  107. pep.

    that's just a can of worms

  108. pep.

    With Jabber in the name

  109. MattJ

    Agreed

  110. MattJ

    I'd love to revive Jabber as an end-user term, but I don't think it can happen

  111. Ge0rG

    Or funds a giant marketing campaign to let everybody and their aunt know that XMPP-based IM is now known as Xubber.

  112. DebXWoody

    When I'm talking with technical persons, I prefer to use XMPP. If I talk with "normal" users, I prefer to use jabber, because I have the feeling it is easier from them.

  113. pep.

    Ge0rG, I'd vote for that rather (name TBD)

  114. Ge0rG

    DebXWoody: it's also easier to pronounce

  115. nyco

    for me: XMPP is to Jabber what HTTP+HTML+JS+CSS is to the web

  116. Ge0rG

    pep.: I said "fund", not "vote"

  117. Ge0rG

    reality is, most users of xmpp IM actually know it as "jabber"

  118. pep.

    And jabber has all that bagage that I'm not ready to take on (esp. Cisco)

  119. Ge0rG

    we can face that reality and do the best we can with the trademark rights we have, or abandon all the brand value

  120. pep.

    Everytime somebody pronounces jabber that's one more coin for the trademark jar

  121. Ge0rG

    pep.: you can buy a license once you've got 500 coins together.

  122. pep.

    Or the free advertizing for Cisco. However you want to call it

  123. Ge0rG

    Cisco doesn't have exclusive rights. We are just all too RMSsy to use our part

  124. !XSF_Martin

    'Normal people' usually know neither jabber nor xmpp. Only one guy said 'oh no, you're using Cisco jabber' as he is forced to use that at work.

  125. pep.

    They do have a product named Jabber. And they also have unlimited resource* (compared to the XSF or anybody in this room)

  126. pep.

    They do have a product named Jabber. And they also have unlimited resources* (compared to the XSF or anybody in this room)

  127. Ge0rG

    pep.: yes. Let's use "Ex-Em-Pee-Pee based federated Eye-Am chat network" as our end-user-facing term then.

  128. pep.

    Ge0rG, I understand all you're saying. This is not being RMSsy this is being cautious

  129. pep.

    (whatever RMSsy would mean)

  130. pep.

    (I guess it doesn't mean "cautious")

  131. Ge0rG

    pep.: religious about FLOSS-style Openness of everything

  132. MattJ

    I don't think that's the reason

  133. pep.

    Ge0rG, yeah no that's not my reason, at least

  134. Neustradamus

    MattJ: https://www.jabber.org/: Jabber.org is the original IM service based on XMPP and one of the key nodes on the XMPP network. It is based on Isode M-Link, you know it ;) I hope an upgrade too, like the OS, there are some tickets about compatibility problems.

  135. Neustradamus

    And please note that the planet.jabber.org speaks about XMPP.

  136. Neustradamus

    For French people, the problem is that some people speak always about Jabber instead of XMPP. Example, in 2012, the creation of a french "Loi 1901" association for the XMPP promotion with the old name. -> http://www.journal-officiel.gouv.fr/association/index.php?ctx=eJxtyjEKwyAUANB*FHHt4FeqaLcQKGRphriL2F9SSNUaW!jte4G8!YUNHg3CN0Pc95IgvCGVVkuLnURvRBfuSxVjuZNf6UUCUSMiZ!yo!V8lFnMuOZEYlmUep8FP840fbQ4hwUmi0xbPShptjXESrXIQ1me*frYNlIY*3JMyIg__&page=15&JTH_ID=005000&JTY_ID=ASSOCIATION

  137. nyco

    well, there is JabberFr.org, and still no xmppFr.org :)

  138. Holger

    The way French people speak is weird either way.

  139. Link Mauve

    Oui baguette.

  140. nyco

    das ist "true"

  141. Neustradamus

    And please do not forget that I have requested the XMPPFR name for this association before the creation ;)

  142. nyco

    we may forget :)

  143. Link Mauve

    Neustradamus, this association exists since 2003.

  144. Link Mauve

    It was just a de facto association until 2012, at which point we officialised it to give us more resources (notably a bank account).

  145. nyco

    and the right to go to jail... :/

  146. nyco

    (we'll bring you oranges, don't worry...)

  147. nyco

    Board meeting time

  148. Seve

    Hello, how are you?

  149. Neustradamus

    The domain name jabberfr.org can exist but without to be an association ;)

  150. ralphm

    /bangs gavel

  151. ralphm

    0. Welcome + Agenda

  152. ralphm

    Hi all

  153. ralphm

    Who do we have

  154. Guus waves

  155. MattJ

    o/

  156. Seve

    🙋

  157. nyco

    .

  158. ralphm

    Any additional items?

  159. Seve

    None here

  160. Ge0rG

    I would like to add an item

  161. Ge0rG

    specifically the "Post-Election Hand-Over Phase" email to members@ from 2019-11-07

  162. Ge0rG

    https://mail.jabber.org/pipermail/members/2019-November/009028.html

  163. ralphm

    Noted

  164. ralphm

    1. Minute taker

  165. ralphm

    ...

  166. jonas’

    sorry, I have to leave in a minute

  167. MattJ

    I'm explicitly not volunteering, I don't have time today

  168. nyco

    :'(

  169. nyco

    ok

  170. nyco

    give it to me

  171. nyco

    but one "minute", not more... :)

  172. ralphm

    Thank you nyco.

  173. ralphm

    2. Post-Election Hand-Over Phase

  174. Guus

    Just moving the date of the hand-over phase is a bit silly: we should define what we expect to happen between the election, and the handover.

  175. ralphm

    I think this is a good idea in itself.

  176. MattJ

    I don't really see the need for it, myself

  177. ralphm

    Practically, one of the issues is that it requires modification of our Bylaws, I believe.

  178. ralphm

    The start of a term currently coincides with the annual meetings

  179. ralphm

    And in previous years where this has come up, we said that this time of year is better to start work than January 1

  180. nyco

    please follow and contribute: https://mensuel.framapad.org/p/qn9jumhvzk-2019-11-14-xsf-board-weekly-meeting

  181. Guus

    I can see how Jan 1st would have a lot of people absent.

  182. Seve

    Well, it could be the start of the period

  183. Guus

    I'm a bit ambiguous. What's the pragmatic solution we're looking for? What does this solve exactly?

  184. nyco

    Jan 1st is a bad idea: in northern hemispehere, it's cold, motivation down, nights are long, and... hangover

  185. nyco

    I guess a handover is more needed in the Council

  186. Guus

    There have been 20 handovers now? Did we ever run into issues, or anticipate issues in the future?

  187. ralphm

    Not really.

  188. ralphm

    Usually there's a bunch of overlap.

  189. ralphm

    Also, old Directors have been more than willing to help resolve ongoing issues.

  190. Guus

    I don't really mind changing it (although I'd dislike having to go through the hoops of getting the Bylaws changed), but I'm not seeing a need for it myself.

  191. nyco

    a handover/overlap does not have to be strict

  192. David Cridland

    FWIW, the main problem the Council has with "zero handover" is that some votes are terminated and re-run. I'd have thought that continuity in Board is a more pressing issue with the abrupt handover.

  193. nyco

    isn't it good to restart a vote with a new council?

  194. MattJ

    But it's not like it's a surprise, the election date is set far in advance

  195. ralphm

    I meant overlap as in the diff between Directors in subsequent terms being small.

  196. MattJ

    So don't start votes before the election date?

  197. David Cridland

    To be clear, the Council situation is not a problem for me.

  198. nyco

    yes, I remember, but I may be wrong, that we discussed in the past avoiding 100% of the board renewed at a new election, rigth?

  199. ralphm

    Generally, in all orgs I have served with, people tend to not take on larger things as their term nears completion.

  200. Guus

    If this solves an issue that we're suffering for, we should apply changes. If this is more of a theoretical exercise, I'm not in favor of spending effort on it.

  201. Ge0rG

    MattJ: Last Calls have a very dynamic runtime, depending on how soon Council members cast their votes

  202. ralphm

    Guus: agreed

  203. nyco

    yes, the cost of changing the bylaws is quite high

  204. MattJ

    Ge0rG, they are limited in length though, right? 2 weeks?

  205. ralphm

    Ge0rG: this is current practice, not what it is supposed to be. AFAIK, Council has 2 weeks to make judgement?

  206. Seve

    Maybe Council could discuss this issue?

  207. Seve

    As I can't talk for them

  208. Ge0rG

    MattJ: a Last Call vote is cast, and can go up to two weeks. Then there is the at-least-two-weeks Last Call period, and then there is a Council vote to advance, which can take up to two weeks

  209. ralphm

    Seve: maybe, but procedurally, XEP-0001 makes Board responsible for Council's process. Of course with their imput.

  210. ralphm

    input

  211. David Cridland

    MattJ, 2 weeks of Last Call plus 2 weeks of vote.

  212. Ge0rG

    so we are speaking of something between three and seven weeks.

  213. MattJ

    I don't see how a handover period helps

  214. ralphm

    Right

  215. David Cridland

    This is all a good argument for Council getting their votes in quicker, of course.

  216. ralphm

    Indeed

  217. MattJ

    You propse that ex-Council should still be entitled to vote?

  218. Guus

    Ge0rG has this actually lead to issues before, or do we foresee issues with that?

  219. MattJ

    What if new stuff comes up during handover period? Who votes on that?

  220. Seve

    > You propse that ex-Council should still be entitled to vote? Does not sound right :)

  221. Ge0rG

    Guus: yes, Last Calls fell under the carpet multiple times in the past

  222. Ge0rG

    sorry, I'm in a work meeting right now

  223. nyco

    >> You propse that ex-Council should still be entitled to vote? > Does not sound right :) seems fair to me as well: like in "finish stuff"?

  224. ralphm

    Ge0rG: well, Council not following their own process is something we can regret, but I don't feel that we have to change procedures at this point.

  225. MattJ

    Finish it before the election, or accept that the new Council takes over

  226. ralphm

    I've heard a bunch of opinions, and think we can put this to a motion.

  227. Seve

    nyco: I feel is a job for the new board/council to decide on following up with past and unfinished work or not, as opinions may change with elections

  228. ralphm moves we alter the start date of a new term for Council and Board, to achieve a "handover" period.

  229. ralphm

    -1

  230. nyco

    -1

  231. Guus

    0 is effectively -1, right?

  232. ralphm

    0 is a valid choice distinct from -1

  233. Guus

    but a majority of proponents is needed to carry, right?

  234. MattJ

    -1, unless a clearer proposal is drawn up, with a list of concrete benefits

  235. ralphm

    It is /not/ affirmative, however, so indeed 0s don't attribute to a motion being passed

  236. MattJ

    Happy to discuss my objection with anyone who still thinks this is a necessary thing to have

  237. ralphm

    Seve, Guus?

  238. Seve

    It is a bit abstract in some cases, I do think as MattJ

  239. Guus

    I'm 0, with the same argument as MattJ.

  240. Seve

    -1

  241. ralphm

    With 4x -1, 1x 0, this motion is rejected.

  242. ralphm

    Thanks for everyone's input!

  243. ralphm

    3. Web team

  244. ralphm

    This was discussed in the xsf@ room earlier this week.

  245. ralphm

    It basically comes down to unclarity of permissioning in GitHub

  246. Guus

    I don't think an XSF WorkTeam exists that is 'web team'. 'web team' is a group of users on Github only.

  247. ralphm

    AFAIR, MattJ was going to have a look at the current GitHub teams defined for the xsf org, and adjust according to XSF Work Teams, Council, Board.

  248. nyco

    and the technical process between GitHub repo and the live website

  249. ralphm

    There used to be a time where there was no comms team, and we did have people working on the web site

  250. nyco

    the website content, as far as I see it, does not belong only to commteam

  251. MattJ

    Yeah

  252. Guus

    I think it'd make sense to have at least everyone in the comms team to have the ability to change the website.

  253. MattJ

    This is already the case

  254. ralphm

    I think it would be fair to say that we'd at least want Comms Team, Board, and other Officers, to be able to alter the website.

  255. nyco

    we're officially 4 in the commteam, two are active these days

  256. Guus

    ralphm I have no objections to that either.

  257. Seve

    Agree ralphm

  258. ralphm

    And I believe that's entirely in line with instructions given to iteam in the past

  259. Guus

    Do we explicitly want to limit access to those groups though?

  260. Guus

    (eg: I got in webteam before I was on board)

  261. nyco

    open to iTeam as well

  262. ralphm

    I am happy for iteam to make decisions on (temporary) exceptions, or ask board when in doubt.

  263. ralphm

    nyco: iteam has access to all the things, right now, and I think that's fine

  264. Guus

    (nyco: this lists three, not four people for Comms : https://xmpp.org/about/xsf/comm-team.html)

  265. MattJ

    Guus, as I said the other day, if someone wants to contribute, I don't see why they shouldn't be in commteam

  266. nyco

    ok, thx

  267. MattJ

    We still accept PRs from non-members anyway, but only commteam would be able to merge them

  268. nyco

    oops

  269. ralphm

    MattJ: after appointment by Board, obviously.

  270. ralphm

    MattJ: indeed

  271. Guus

    Matt: I don't mind doing the occasional merge, but I don't want to be in commsteam.

  272. ralphm

    Guus: nor do I :-)

  273. Guus

    (as that implies more responsibilities than that I care to take on)

  274. ralphm

    MattJ (with his iteam hat on): is this sufficient instruction?

  275. MattJ

    Guus, I think you should be in commteam, or not merge, or we agree that Board also has website powers

  276. MattJ

    and if you lose your Board seat, you can't merge

  277. nyco

    huh... please: it's commteam, not commsteam, that may be read as "comm steam", which is wrong :)

  278. MattJ

    I don't think we should have an ambiguous web team

  279. ralphm

    nyco: whatever

  280. ralphm

    MattJ: make it so

  281. Guus

    MattJ I don't mind having an ambiguous web team, but won't object to that no longer being the case in the future.

  282. MattJ

    We agreed commteam+iteam, what about board?

  283. ralphm

    I mentioned Board above. I think they should have access, but generally let the Communications Team handle PRs

  284. Seve

    Board should have I think. To speed up processes as well.

  285. Guus

    board is not ment to be an operational entity, is it?

  286. MattJ

    Guus, access and responsibilities are different in my opinion

  287. Seve

    Hmmm

  288. Guus

    I don't think it should be needed to have board be able to merge, but as it's in their mandate to apply changes, I'm not against them having access either.

  289. MattJ

    I think people we trust to steer the organisation we should also trust enough to give repo access to our website

  290. ralphm

    Board should be able to change the website without the consent of the Communications Team, should that need arise.

  291. ralphm

    Yes

  292. MattJ

    Guus, note that you lose your ability to merge if we don't

  293. ralphm

    :-)

  294. Guus

    I know

  295. ralphm

    Ok

  296. Kev

    I think the alternative is an explicit webteam, approved by Board, chartered, whatever.

  297. Guus

    but that shouldn't drive my vote.

  298. MattJ

    ok, so I think we're good

  299. Kev

    And this seems easier than that :)

  300. ralphm

    Indeed

  301. ralphm

    4. AOB

  302. nyco

    we already have iteam, board, commteam, let them merge PRs

  303. ralphm

    (as we're already past 16:00)

  304. MattJ

    commteam manages website repo, iteam and board also have permissions

  305. Guus

    wfm. Maybe ask iteam to have an explicit check/update of permissions after elections?

  306. Kev

    Expectation being that iteam generally won't, unless it's a technical thing, but have the ability, right?

  307. Guus

    (I think that currently fails)

  308. ralphm

    Oh, the Mediawiki item is something for iteam, not Board.

  309. nyco

    ok

  310. Guus

    Kev: I'd say so, yes.

  311. nyco

    where should I report it then?

  312. Guus points at Matt

  313. ralphm

    with iteam, MattJ is their lead

  314. nyco

    ok

  315. ralphm

    5. Date of Next

  316. ralphm

    +1W

  317. Seve

    +1

  318. MattJ

    wfm

  319. ralphm

    6. Close Thanks all!

  320. Guus

    wfm

  321. ralphm bangs gavel

  322. Guus

    Thanks

  323. Seve

    Super, thank you!

  324. nyco

    thx all

  325. nyco

    MattJ: our current Mediawiki version is unsupported, it would be nice to upgrade soon-ish, no pressure, no hurry, just to avoid some worries

  326. MattJ

    Yeah, thanks, it's on my radar

  327. nyco

    thx

  328. nyco

    please review the minutes draft before I send it: https://mensuel.framapad.org/p/qn9jumhvzk-2019-11-14-xsf-board-weekly-meeting?lang=fr

  329. pep.

    So it's great stuff gets decided etc., as a newbie where can I learn about all that (starting in the xsf). Should task each team or board or.. To write this down somewhere when something gets changed?

  330. pep.

    So it's great stuff gets decided etc., as a newbie where can I learn about all that (starting in the xsf). Should we task each team or board or.. To write this down somewhere when something gets changed?

  331. pep.

    (I'm happy the website situation got "clarified" :))

  332. rion

    Hi. regarding Jingle XEP. If some action doesn't explicitly state "action is used to add one or more new content definitions to the session", does it mean it's applicable to just one content definition?

  333. MattJ

    Who is behind @xmpp@fosstodon.org on mastodon?

  334. vanitasvitae

    MattJ: i guess the 404 guy

  335. vanitasvitae

    404.city

  336. Zash

    nyco? https://wiki.xmpp.org/web/Social_Media#Mastodon_.28experiment.29

  337. MattJ

    Ah, good