XSF Discussion - 2021-01-15

  1. intosi has joined
  2. krauq has joined
  3. debacle has left
  4. wladmis has left
  5. marek has left
  6. marek has joined
  7. emus has left
  8. j.r has left
  9. j.r has joined
  10. paul has left
  11. krauq has left
  12. krauq has joined
  13. intosi has left
  14. intosi has joined
  15. Adi has left
  16. Adi has joined
  17. intosi has left
  18. purplebeetroot has left
  19. govanify has left
  20. govanify has joined
  21. govanify has left
  22. govanify has joined
  23. marek has left
  24. marek has joined
  25. alacer has left
  26. alacer has joined
  27. intosi has joined
  28. Neustradamus has joined
  29. intosi has left
  30. sonny has left
  31. sonny has joined
  32. intosi has joined
  33. sonny has left
  34. sonny has joined
  35. Seve has joined
  36. Yagiza has joined
  37. intosi has left
  38. sonny has left
  39. sonny has joined
  40. Andrzej has joined
  41. krauq has left
  42. krauq has joined
  43. chronosx88 has joined
  44. alex-a-soto has left
  45. intosi has joined
  46. alex-a-soto has joined
  47. sonny has left
  48. sonny has joined
  49. krauq has left
  50. krauq has joined
  51. sonny has left
  52. sonny has joined
  53. krauq has left
  54. krauq has joined
  55. intosi has left
  56. sonny has left
  57. sonny has joined
  58. sonny has left
  59. sonny has joined
  60. intosi has joined
  61. stefan has left
  62. stefan has joined
  63. sonny has left
  64. sonny has joined
  65. intosi has left
  66. sonny has left
  67. sonny has joined
  68. sonny has left
  69. sonny has joined
  70. govanify has left
  71. govanify has joined
  72. sonny has left
  73. sonny has joined
  74. intosi has joined
  75. krauq has left
  76. Seve has left
  77. krauq has joined
  78. sonny has left
  79. sonny has joined
  80. marek has left
  81. intosi has left
  82. sonny has left
  83. sonny has joined
  84. sonny has left
  85. sonny has joined
  86. intosi has joined
  87. andy has joined
  88. sonny has left
  89. sonny has joined
  90. intosi has left
  91. Adi has left
  92. sonny has left
  93. sonny has joined
  94. krauq has left
  95. krauq has joined
  96. krauq has left
  97. krauq has joined
  98. Adi has joined
  99. intosi has joined
  100. paul has joined
  101. Mikaela has joined
  102. Tobias has joined
  103. sonny has left
  104. sonny has joined
  105. govanify has left
  106. govanify has joined
  107. wurstsalat has joined
  108. Mikaela has left
  109. intosi has left
  110. paul has left
  111. paul has joined
  112. sonny has left
  113. sonny has joined
  114. jcbrand has joined
  115. emus has joined
  116. chronosx88 has left
  117. chronosx88 has joined
  118. peetah has left
  119. intosi has joined
  120. peetah has joined
  121. chronosx88 has left
  122. chronosx88 has joined
  123. Seve has joined
  124. mukt2 has joined
  125. neshtaxmpp has left
  126. chronosx88 has left
  127. chronosx88 has joined
  128. Adi has left
  129. neshtaxmpp has joined
  130. chronosx88 has left
  131. chronosx88 has joined
  132. paul has left
  133. paul has joined
  134. Mikaela has joined
  135. mathijs has left
  136. mathijs has joined
  137. mukt2 has left
  138. marek has joined
  139. mukt2 has joined
  140. Adi has joined
  141. lionelexecrec has joined
  142. Mikaela has left
  143. Alex has left
  144. Alex has joined
  145. peetah has left
  146. peetah has joined
  147. chronosx88 has left
  148. chronosx88 has joined
  149. mukt2 has left
  150. purplebeetroot has joined
  151. lionelexecrec has left
  152. lionelexecrec has joined
  153. Arne has joined
  154. Arne has left
  155. lionelexecrec has left
  156. lionelexecrec has joined
  157. lionelexecrec has left
  158. lionelexecrec has joined
  159. goffi has joined
  160. lionelexecrec has left
  161. lionelexecrec has joined
  162. lionelexecrec has left
  163. lionelexecrec has joined
  164. marc has joined
  165. lionelexecrec has left
  166. lionelexecrec has joined
  167. lionelexecrec has left
  168. lionelexecrec has joined
  169. mukt2 has joined
  170. moparisthebest has left
  171. lionelexecrec has left
  172. lionelexecrec has joined
  173. Guus has joined
  174. lionelexecrec has left
  175. lionelexecrec has joined
  176. moparisthebest has joined
  177. lionelexecrec has left
  178. lionelexecrec has joined
  179. mukt2 has left
  180. pasdesushi has joined
  181. Kev has joined
  182. peetah has left
  183. peetah has joined
  184. lionelexecrec has left
  185. lionelexecrec has joined
  186. LNJ has joined
  187. alameyo has joined
  188. xecks has joined
  189. winfried has left
  190. winfried has joined
  191. krauq has left
  192. krauq has joined
  193. mukt2 has joined
  194. Zash has left
  195. krauq has left
  196. Zash has joined
  197. krauq has joined
  198. lionelexecrec has left
  199. lionelexecrec has joined
  200. Arne has joined
  201. Arne has left
  202. Ge0rG has left
  203. marc has left
  204. alameyo has left
  205. mukt2 has left
  206. Ge0rG has joined
  207. marc has joined
  208. pasdesushi has left
  209. mukt2 has joined
  210. chronosx88 has left
  211. chronosx88 has joined
  212. Andrzej has left
  213. Andrzej has joined
  214. moparisthebest has left
  215. mukt2 has left
  216. eevvoor has left
  217. eevvoor has joined
  218. Mikaela has joined
  219. lionelexecrec has left
  220. lionelexecrec has joined
  221. lionelexecrec has left
  222. lionelexecrec has joined
  223. lionelexecrec has left
  224. lionelexecrec has joined
  225. lionelexecrec has left
  226. lionelexecrec has joined
  227. lionelexecrec has left
  228. lionelexecrec has joined
  229. lionelexecrec has left
  230. mukt2 has joined
  231. alameyo has joined
  232. mukt2 has left
  233. moparisthebest has joined
  234. alameyo has left
  235. Arne has joined
  236. Arne has left
  237. Arne has joined
  238. Arne has left
  239. chronosx88 has left
  240. chronosx88 has joined
  241. flow FYI GSoC org application starts 29.1, unfortunately due to personal constraints I will not be able to act as GSoC org admin this year
  242. flow FYI GSoC org application starts 29.1. Unfortunately, due to personal constraints, I will not be able to act as GSoC org admin this year
  243. debacle has joined
  244. marc has left
  245. marc has joined
  246. mukt2 has joined
  247. SamWhited has left
  248. wladmis has joined
  249. alameyo has joined
  250. goffi Hello, I don't see any mention of a XMPP summit this year, will there be any? I know that FOSDEM is online, but isn't there any plan to do an online summit too?
  251. arc has left
  252. arc has joined
  253. mukt2 has left
  254. arc has left
  255. arc has joined
  256. Neustradamus has left
  257. lionelexecrec has joined
  258. lionelexecrec has left
  259. lionelexecrec has joined
  260. lionelexecrec has left
  261. lionelexecrec has joined
  262. andrey.g has joined
  263. mukt2 has joined
  264. lionelexecrec has left
  265. lionelexecrec has joined
  266. lionelexecrec has left
  267. lionelexecrec has joined
  268. lionelexecrec has left
  269. lionelexecrec has joined
  270. LNJ has left
  271. Mikaela has left
  272. purplebeetroot has left
  273. purplebeetroot has joined
  274. alacer has left
  275. mukt2 has left
  276. pasdesushi has joined
  277. krauq has left
  278. krauq has joined
  279. alacer has joined
  280. pasdesushi has left
  281. pasdesushi has joined
  282. purplebeetroot has left
  283. purplebeetroot has joined
  284. x51 has joined
  285. Mikaela has joined
  286. moparisthebest has left
  287. lionelexecrec has left
  288. lionelexecrec has joined
  289. lionelexecrec has left
  290. lionelexecrec has joined
  291. lionelexecrec has left
  292. lionelexecrec has joined
  293. lskdjf has joined
  294. lionelexecrec has left
  295. lionelexecrec has joined
  296. pasdesushi has left
  297. LNJ has joined
  298. lionelexecrec has left
  299. lionelexecrec has joined
  300. purplebeetroot has left
  301. purplebeetroot has joined
  302. intosi has left
  303. mukt2 has joined
  304. lionelexecrec has left
  305. lionelexecrec has joined
  306. moparisthebest has joined
  307. LNJ has left
  308. lionelexecrec has left
  309. lionelexecrec has joined
  310. intosi has joined
  311. mathijs has left
  312. mathijs has joined
  313. Paganini has left
  314. nyco has left
  315. edhelas has left
  316. edhelas has joined
  317. mukt2 has left
  318. Paganini has joined
  319. lionelexecrec has left
  320. lionelexecrec has joined
  321. LNJ has joined
  322. intosi has left
  323. purplebeetroot has left
  324. SamWhited has joined
  325. LNJ has left
  326. intosi has joined
  327. arc has left
  328. arc has joined
  329. nyco has joined
  330. arc has left
  331. arc has joined
  332. arc has left
  333. arc has joined
  334. LNJ has joined
  335. lionelexecrec has left
  336. lionelexecrec has joined
  337. debacle has left
  338. LNJ has left
  339. Mikaela has left
  340. lionelexecrec has left
  341. lionelexecrec has joined
  342. pasdesushi has joined
  343. intosi has left
  344. lionelexecrec has left
  345. lionelexecrec has joined
  346. Arne has joined
  347. pasdesushi has left
  348. Arne has left
  349. Mikaela has joined
  350. krauq has left
  351. krauq has joined
  352. lionelexecrec has left
  353. lionelexecrec has joined
  354. Kev has left
  355. Kev has joined
  356. intosi has joined
  357. nyco has left
  358. LNJ has joined
  359. mukt2 has joined
  360. marek has left
  361. marek has joined
  362. intosi has left
  363. lionelexecrec has left
  364. lionelexecrec has joined
  365. marek has left
  366. marek has joined
  367. lionelexecrec has left
  368. lionelexecrec has joined
  369. Kev has left
  370. Kev has joined
  371. eevvoor has left
  372. Kev has left
  373. Kev has joined
  374. jonas’ SamWhited, re your last email in the DOAP thread: I think you might’ve misunderstood what mathieui was trying to say in the first quote you made.
  375. lionelexecrec has left
  376. lionelexecrec has joined
  377. jonas’ He was trying to say that projects which do not provide a DOAP file will remain at the status quo (pre-DOAP) regarding their listing.
  378. jonas’ projects which do provide a DOAP file get extras (pictures, xep info etc.)
  379. jonas’ so a DOAP file is still no requirement whatsoever to be listed
  380. pasdesushi has joined
  381. SamWhited Yes, that is how I understood it. It's better than them not being listed, but it's still not okay.
  382. SamWhited There is some level of complexity where that is okay, but DOAP is far above it. This will only hurt us and make fewer projects able to be listed in a nice looking way.
  383. LNJ has left
  384. Ge0rG I really don't understand the amount of hate towards XML in the XMPP community.
  385. intosi has joined
  386. MattJ Ge0rG, have you ever worked on non-XMPP XML-based systems/protocols? :)
  387. MattJ Apart from XMPP, almost everything is terrible
  388. Ge0rG MattJ: I have really horrible memories of a SOAP API I was involved in.
  389. SamWhited The supposed "knee jerk" reactions people have too it aren't entirely wrong. I work on XMPP because I think it's the best way to do federated chat and it does XML about as well as it's possible to do it, but XML still introduces tons of security issues, needless complexity that leads to bugs, etc. and we shouldn't fall into the XML communities trap of "it's so powerful that we need to rewrite everything using XML".
  390. pasdesushi has left
  391. pasdesushi has joined
  392. SamWhited If we're going to use more XML, we should at least restrict ourselves to the sane subset of XML that XMPP uses which makes it sort of tolerable to work with.
  393. MattJ That didn't happen with DOAP, we didn't set out to find a way to express project data in XML
  394. MattJ It just happens that DOAP -> RDF -> XML
  395. Ge0rG SamWhited: could you imagine writing a simple yaml2doap converter?
  396. marc has left
  397. SamWhited Ge0rG: again, this is the problem: if I need extra tools and converters and DSLs or whatever just to display some metadata we've already failed.
  398. MattJ I can, and I honestly volunteer to do it if you give me a spec
  399. marc has joined
  400. Zash I wrote a small shell script that can turn CSV into DOAP
  401. MattJ No, I just want this format bikeshedding to stop
  402. Arne has joined
  403. MattJ It really doesn't matter 99% as much as getting the job done
  404. Zash At least the XEP table thing
  405. arc has left
  406. arc has joined
  407. Ge0rG SamWhited: I had to write an extra tool and DSL for DOAP because I wanted to use the same basic document structure for Bruno the Jabber™ Bear as well as for yaxim. There is no other document format that would have saved me from *that*
  408. SamWhited Normally I'd agree with MattJ, but I do think DOAP is worse than not doing the job and just listing things on the website when the author files an issue or whatever.
  409. Ge0rG SamWhited: I think you've already made yourself clear in that regard.
  410. Ge0rG It also looks like most people disagree with you on that.
  411. Zash Didn't half the (client) projects listed already adopt DOAP? IIRC from looking at Link Mauves render
  412. arc has left
  413. arc has joined
  414. arc has left
  415. arc has joined
  416. papatutuwawa has joined
  417. arc has left
  418. Ge0rG I've adopted DOAP in 2019
  419. arc has joined
  420. SamWhited My site generator (currently hugo, but that may change soon; I'm sure most of them do something like this) can spit out files in various formats (JSON, XML, CSV, probably others). You can put some simple key values in and get a file out. Great. However it doesn't support downloading schemas and validating them and writing namespace prefixes which are sort of their own extra side metadata channel and etc. and nor should it, there's no reason to add all that complexity, it's as simple as that.
  421. MattJ I agree with everything you just said
  422. pasdesushi has left
  423. lionelexecrec has left
  424. lionelexecrec has joined
  425. lionelexecrec has left
  426. lionelexecrec has joined
  427. MattJ I don't know why you think that stuff is necessary
  428. SamWhited Even if I'm writing my own implementation, ie. in my site I have a python file that converts yaml or whatever, it's easy to marshal an object to some simple format, it's not trivial to figure out how to parse a schema and validate it, for example.
  429. MattJ It just feels like you're /trying/ to see it as more complicated than it is
  430. lionelexecrec has left
  431. lionelexecrec has joined
  432. Ge0rG SamWhited: your site generator can convert a HTML template and a set of variables / arrays into a webpage. It surely can convert an XML template into a DOAP file
  433. MattJ Nobody is doing that
  434. SamWhited All of this is necessary because if I just pick a file and copy/paste it as I've tried to do multiple times half of them use different technologies and namespaces that aren't discoverable, there's no documentation for what the fields are or how to change them, etc.
  435. SamWhited Ge0rG: it can't.
  436. MattJ SamWhited, let us know what you're stuck on, we can help... and document it
  437. SamWhited The entire format needs documentation, so far every time I say "what are the fields" someone links me to a blob of XML. That is not documentation, I have no idea how to read it and it's not helpful.
  438. Ge0rG yeah, you can help improve the documentation!
  439. SamWhited Not to mention that that blob of XML doesn't even cover all the fields because they're defined in like 3 or 4 different places.
  440. SamWhited Apparently I need to figure out DOAP and RDF and SPDX and FOAF and SCHEMA or whatever just to figure out what fields I can even write
  441. jonas’ lesson learnt: don’t try to fix a potential misunderstanding.
  442. mukt2 has left
  443. Ge0rG SamWhited: with the amount of energy you invested (and took from everybody reading and answering), you could have created a splendid XMPP RDF manual.
  444. pasdesushi has joined
  445. SamWhited Or I could spend the time fighting for a sane format, which is a much better use of the time than accepting this overengineered garbage from people who should know better
  446. mukt2 has joined
  447. SamWhited This is exactly why no one uses XMPP anymore, we make the same damn mistakes over and over again and it's infuriating.
  448. Ge0rG There is an awesome saying in German hacker culture, "wer macht, hat recht" - loosely translated it means "the one who's doing things, is in the right"
  449. SamWhited As I've said, I'm happy to introduce an alternate format.
  450. Ge0rG SamWhited: yes. please use your time machine to travel into 2017 and introduce it back then
  451. Ge0rG SamWhited: or, if you are inclined to improve the situation as it is today, write a yaml2doap converter for the people who look for an easy key-value solution.
  452. Ge0rG or json2doap, or whatever.
  453. SamWhited Ge0rG: no, as I've also said multiple times that's a stupid way to do it and means we've already failed.
  454. SamWhited It's infuriating that I'd need tooling just to list some metadata
  455. Ge0rG SamWhited: I used a text editor as my tooling.
  456. SamWhited Well lucky you, I've tried that and I have no idea if it's valid or works or what all the fields are
  457. lionelexecrec has left
  458. lionelexecrec has joined
  459. Ge0rG SamWhited: well, then write a doap2yaml converter and convince everybody to use your schema-less new efficient format
  460. SamWhited Ge0rG: yes, I have already volunteered to do that
  461. lionelexecrec has left
  462. lionelexecrec has joined
  463. Ge0rG I have volunteered to do many things in the past. Most of them never were actually done.
  464. pasdesushi has left
  465. SamWhited I don't understand the argument, this is the second time someone has said "so do it yourself" and I've said "fine, I will" and then the answer is "well we'll just use DOAP anyways" or "well it probably won't get done". What was the point in asking in the first place?
  466. Ge0rG SamWhited: it would make you stop complaining and distract you with pointless action? ;)
  467. Ge0rG SamWhited: seriously though, if there is a lossless converter into a different format and a documentation for that format, you *might* have a chance to convince the people to switch
  468. Ge0rG However, nobody in the XSF has the resources to maintain a meta-data specification project, and using an existing one is the next-best solution.
  469. Ge0rG If you want to compete with DOAP, you need to do better than DOAP in terms of long-term reliability
  470. SamWhited Yah, I'm working on it. I don't know about the converter part because I can't figure out how doap works in the first place and if I write it I'm sure everyone will just complain that it's actually wrong because I had to guess at how fields worked and left out every schema in existance that could be improted, etc., but the spec should be easy enough
  471. SamWhited We don't need any of that to display some clients on the website.
  472. SamWhited We need the like dozen or so simple values that let us show links to a readme and a license and a screenshot and what not.
  473. Ge0rG or two screenshots. or an array
  474. Ge0rG also multiple resolutions
  475. SamWhited Sure, I wasn't actually enumerating every single thing we'd need. But we can't fall into the trap of "we need everything", we need something "good enough".
  476. SamWhited What that is we can bike shed on a bit during the XEP process.
  477. lionelexecrec has left
  478. lionelexecrec has joined
  479. lionelexecrec has left
  480. lionelexecrec has joined
  481. SamWhited Anyways, we'll see, it's a bit of a self fullfilling prophecy because I both want to finish this and try to convince people to switch, and have been told alternatives probably won't be considered so I'm not sure if there's a point and either way I'm stuck in the position of "why didn't you do it? we wouldn't have even tried to use it anyways, but why didn't you do it?" so I may or may not finish it.
  482. Ge0rG SamWhited: nobody wants to bikeshed what we need. We just want to have a format for writing down a list of XEPs and some meta-data
  483. MattJ I have no desire for bikeshedding anything, which is why we'll be sticking with DOAP, but I'm not opposed to an alternative format if there is a conversion possible
  484. MattJ That is, I'm not opposed to another format existing
  485. SamWhited I mean, sure, I'd rather not argue over exactly what image formats shoudl be required either, but it's better than "so support everything under the sun with no documentation, what could go wrong?"
  486. MattJ DOAP is more interoperable with other stuff, so that's what I'd prefer to use
  487. purplebeetroot has joined
  488. Arne has left
  489. mukt2 has left
  490. LNJ has joined
  491. emus has left
  492. lionelexecrec has left
  493. lionelexecrec has joined
  494. emus has joined
  495. Adi has left
  496. Adi has joined
  497. lskdjf has left
  498. lskdjf has joined
  499. lionelexecrec has left
  500. lionelexecrec has joined
  501. lionelexecrec has left
  502. lionelexecrec has joined
  503. eevvoor has joined
  504. Guus This is a recurring discussion. I feel that the effort going in this discussion outweighs the benefit of having automation around discovery what the description of a project is. What are we using this for? Slightly more data (yet inconsistent and thus possibly presented in an ugly way) on our website?
  505. lskdjf has left
  506. lskdjf has joined
  507. Ge0rG Guus: as a client developer, it's good to see which (OSS) implementations cover a given XEP, to steal code^W^Wget inspiration, and which other implementations one needs to do interop-testing with
  508. Ge0rG as a user, I want to see which clients have the IM Compliance Suite 2021 badge attached.
  509. MattJ Guus, personally I think this is going to be on the list of the best things that have happened to XMPP for a long time
  510. MattJ and I can barely comprehend a stance that it will be hardly useful
  511. Ge0rG also gamification effects!
  512. MattJ We have so much XMPP software to choose from, and nobody knows what is up to date and what is not
  513. Guus Ok, I'd be happy if that's the case. I'm skeptical, but happy to be proven wrong.
  514. MattJ Having this data is useful for so many things
  515. MattJ Even for XEP work, it's useful to be able to know at a glance what implements a XEP
  516. krauq has left
  517. krauq has joined
  518. lskdjf has left
  519. lskdjf has joined
  520. nyco has joined
  521. mathieui Ge0rG, this is a tool to make the ecosystem more readable, by 1) listing for each XEP, which client/library/server implements it (self-reported, which is as good as we will get), which helps developers pick and choose both which implementation to go with, and which they may want to implement 2) For users, it gives the opportunity to see at a glance which client implements which compliance suite, which is easy to map to desired features not saying it is a panacea or that it will have a miraculous effect, but it should help
  522. Ge0rG mathieui: no need to convince *me*
  523. Steve Kille has left
  524. mathieui err, Guus*
  525. Ge0rG BTW, having DOAP should be a huge marketing benefit for xmpp library developers, cc flow
  526. lionelexecrec has left
  527. lionelexecrec has joined
  528. lionelexecrec has left
  529. Guus I remain skeptical and happy to be proven wrong.
  530. lionelexecrec has joined
  531. lionelexecrec has left
  532. lionelexecrec has joined
  533. moparisthebest Guus, what's to be skeptical about? haven't seen Link Mauve 's work that is already done and demonstrates the utility? unfortunately I don't have that link handy...
  534. Link Mauve moparisthebest, https://linkmauve.fr/software/clients.html and https://linkmauve.fr/extensions/ maybe?
  535. mathieui (probably worth it to link to an extension page, where it is imo the most useful, e.g. https://linkmauve.fr/extensions/xep-0199.html )
  536. Link Mauve Right.
  537. pasdesushi has joined
  538. MattJ It's easy to forget that outside of our core community, people really struggle with discovering this information
  539. marc has left
  540. marc has joined
  541. lionelexecrec has left
  542. jonas’ (not just outside the core community)
  543. Guus moparisthebest I have no doubt that the technology will work. I'm doubtful that it'll lead to the availability of an accurate set of data of a good cross-section of the ecosystem.
  544. Steve Kille has joined
  545. Ge0rG Guus: I think we can help that by making good use of this data on our website
  546. Zash Guus, don't underestimate the attractiveness of shiny green checkmarks
  547. Ge0rG Zash: badges!
  548. Zash YES
  549. Ge0rG Zash: didn't you want to make some progress with badges?
  550. Zash here's my badge so far: `"badges":{"av":"advanced","web":"advanced"}`
  551. Zash Dunno if Link Mauve uses this or made their own thing?
  552. Link Mauve I use it directly, see https://git.linkmauve.fr/xmpp-doap.git/
  553. Zash Oh, source code
  554. Link Mauve And then parse its stdout.
  555. Link Mauve It even comes in a docker thingy!
  556. Ge0rG is there a badge rendering thing where we can combine multiple Compliance Categories into one badge?
  557. Zash Ge0rG, yeah, that's the main question atm I think
  558. Link Mauve Ge0rG, that was my request a few days ago, which theTedd replied with interested eyes. :)
  559. Link Mauve Ge0rG, that was my request a few days ago, to which theTedd replied with interested eyes. :)
  560. Ge0rG Link Mauve: this is ending up in significant bike shedding again
  561. Link Mauve “14:27:05 SamWhited> Well lucky you, I've tried that and I have no idea if it's valid or works or what all the fields are”, honest question, why do you feel like this needs more validating than, say, your website, or a random stanza you send over the wire?
  562. Zash Shouldn't there exist RDF (documentation) viewers?
  563. Ge0rG I suppose that a badge format like [XMPP Compliance 2020: Core IM, Advanced Web] with the : as a color separator would be better, but how do you color-code "Advanced Web"?
  564. Zash EMOJI!
  565. Zash Ge0rG, "Core Core" ... ‽
  566. SamWhited Link Mauve: I mean, I want it to actually work if I'm going to go to all the trouble of learning it and not just copy/paste which means that one bug gets repeated over and over again
  567. Ge0rG Zash: "Core Server"
  568. SamWhited If people really would support an alternate format, would you prefer a documented set of keys that gets stuck in an XML file in .well-known (or wherever), or a microformat in the code of the site itself?
  569. Ge0rG googles: DOAP schema > Did you mean: SOAP schema NOOOO!!111!!!
  570. Zash Ge0rG, I mean, Core being both a category and a compliance level makes for confusion.
  571. jonas’ I would accept an alternate format which is already defined elsewhere.
  572. jonas’ SamWhited, making up a format when we could reuse DOAP is not going to sit well with me
  573. Ge0rG Zash: yes, I've stumbled upon that when creating badges for all combinations, and I solved it by de-duplicating "Core"
  574. SamWhited I think if I had to pick a single main complaint about this garbage fire of a format it's that it's not documented in a single place and is actually like 5 formats jammed together. If we come up with a small one for our own use it's documented in a single place which seems like the biggest win to me.
  575. MattJ SamWhited, microformats in HTML are more effort to parse in my opinion
  576. SamWhited MattJ: good point
  577. Link Mauve SamWhited, I’ve found multiple DOAP validators, if you really want to go down that road.
  578. SamWhited Again, I shouldn't have to use alternate tools. If it's not human readable first and machine readable second we've already failed.
  579. Adi has left
  580. lskdjf How about not putting the "Core" caterogy onto badges? It's not understandable what this category entails. And since a big point of the badges is to let users know how advanced clients/servers are, I'd leave it out. It just adds noise.
  581. Adi has joined
  582. Link Mauve SamWhited, DOAP is both, thankfully. :)
  583. SamWhited It's not and I think you know it.
  584. lskdjf How about not putting the "Core" category onto badges? It's not understandable what this category entails. And since a big point of the badges is to let users know how advanced clients/servers are, I'd leave it out. It just adds noise.
  585. Zash I say it's perfectly readable as long as you avert your eyes from the xmlns:prefix definitions.
  586. SamWhited And as long as you know how XML schemas work apparently since the only documentation is itself a giant blob of even more XML technologies to learn
  587. krauq has left
  588. Kev To be fair (and I'm not defending DOAP, or saying I want us to use it), I think anyone involved in writing XMPP software already has a fair clue how schemas work or they'll be in trouble :)
  589. Kev No, I take that back, that's not true.
  590. krauq has joined
  591. Kev Ignore :)
  592. SamWhited Maybe I'm just an idiot then, because I have never had to write a schema or learn any of this prefix nonsense to write XMPP and any time I've tried I've gotten bogged down in contradictions and terrible docs and never figured it out
  593. Link Mauve I remember my first client doing sprintf(stanza, "<message><body>%s</body></message>", message); :°)
  594. Mikaela has left
  595. Ge0rG can't Link Mauve provide a link to a working DOAP schema verifier, SamWhited use that verifier to check their favorite client's hand-rolled DOAP and then document the fields and their meaning in human-readable HTML?
  596. Link Mauve SamWhited, XMPP uses XML Schema to describe the protocol extensions starting with draft specifications.
  597. lskdjf Link Mauve, the number of doap files are currently given as e.g. "3/6", which translates to "3 out of 6". However 6 isn't the total number of clients, and there probably will never be DOAP files for _all_ implementations. I'd maybe leave it out and just say "3", to not suggest a false number of total implementations.
  598. Kev Link: No, it doesn't, not really.
  599. Ge0rG Link Mauve: which is why nobody ever achieves Draft.
  600. Kev It uses schemas only illustratively, it's the text that's definitive.
  601. Link Mauve Ge0rG, there is one right in the DOAP repository: https://github.com/ewilderj/doap/tree/master/validator
  602. Kev So there's ~= no reason to read the schema in a XEP.
  603. Link Mauve lskdjf, good idea!
  604. SamWhited Link Mauve: and I have never written one or been able to read one. I have seen people find errors in them on a fairly regular basis though.
  605. Link Mauve lskdjf, is that better?
  606. Link Mauve SamWhited, yes, I am part of these people.
  607. lskdjf Link Mauve, that was quick 😉 imho it is better, yes
  608. Link Mauve Our usage of XML Schema has been fairly useless to me as an implementor, I usually use it as a list of known elements and their attributes, but I have to use my own DSL.
  609. Link Mauve lskdjf, just a small .js file to modify. ^^
  610. Ge0rG Link Mauve: can you add a tooltip listing all the clients over the number? with the respective logo?
  611. Ge0rG or make the number collapsible? :D
  612. SamWhited Alternative suggestion: is it possible to just say "anything the website pulls from DOAP has to also be accepted in an issue and the web people will add it to the list manually"?
  613. Ge0rG SamWhited: NO!
  614. Link Mauve Ge0rG, I tried to yank Wikipedia’s popover plugin when someone suggested that a full list of all implementations would be too large, but then saw they use npm and my motivation vanished instantly.
  615. moparisthebest are we striving for perfection or "way better than we have currently / really good" ? because what Link Mauve has is already well past the second bar
  616. MattJ Ge0rG, we could always maintain DOAP files for people in an XSF repo :)
  617. lskdjf > or make the number collapsible? 😀 +1 for making the "Implementations" column hidable (and maybe hide it by default? unsure)
  618. lskdjf > or make the number collapsible? 😀 +1 for making the "Implementations" column hideable (and maybe hide it by default? unsure)
  619. moparisthebest been talking to non-XMPP folk a lot about XMPP over the last week, and all the technical ones have been very confused about XEPs to say the least
  620. moparisthebest in the "XMPP is useless because so many XEPs" "I could never implement them all" sense
  621. chronosx88 has left
  622. chronosx88 has joined
  623. Ge0rG lskdjf: I'd leave the column in, and make the number a button that toggles display of the implementations
  624. lskdjf actually, if it's not hidden by default, perhaps it also doesn't make sense to make it hidable at all 🤔️
  625. lskdjf Ge0rG, ah, I see. I misunderstood your idea
  626. Link Mauve The JS already has the information needed to create the popover, I’m just not good enough at web dev to achieve a popover.
  627. Ge0rG Link Mauve: https://www.gwern.net/Changelog#december-2020
  628. Link Mauve Yes, like that!
  629. mukt2 has joined
  630. Zash MattJ: Us maintaining more things?
  631. krauq has left
  632. Ge0rG MattJ: we could have a wiki page with all the DOAP pasted in.
  633. MattJ Zash, changing stuff in HTML or elsewhere is roughly equivalent
  634. krauq has joined
  635. MattJ I'm just saying, if we're going to allow projects without DOAP files to have equivalent data on our site, we should probably just create them a DOAP file so we can use the same automation
  636. MattJ and that's an "if"
  637. Ge0rG MattJ: we could write to the website visitors' GPU RAM!
  638. Ge0rG MattJ: right. That's a possible logical step.
  639. Ge0rG For the developers that can host their download portal but not a small XML file.
  640. MattJ Exactly that
  641. Ge0rG or maybe for developers that are allergic to XML?
  642. Zash MattJ, I mean the format doesn't matter. Having the projects do the work of keeping them up to date is, as opposed to adding to the XSF workload.
  643. Link Mauve ↑ that was my original idea, btw.
  644. Ge0rG Zash: I'm sure the XSF has plenty of free resources for that, counted by the amount of bikeshedding we perform.
  645. Link Mauve That each project has people who know the current and planned features and their limitations, and they are in the best place to keep machine-readable information about that.
  646. MattJ I totally agree
  647. inky has left
  648. inky has joined
  649. MattJ But I also can't stand the cries of the victims of this decision, and if we have to compromise for a handful of projects, I don't think it's the end of the world
  650. Ge0rG Also my gut feeling that having a per-XEP format that describes the XEP version, the app version, support level and optional comments will be ugly in any file format
  651. Link Mauve I’d rather not commit us to keeping up to date with the feature set of each XMPP software.
  652. chronosx88 has left
  653. chronosx88 has joined
  654. MattJ We are not committing to that
  655. Zash I tried it with that big table, but eventually gave up. And that format was much simpler.
  656. Ge0rG let's just keep the data in a google docs spreadsheet.
  657. Ge0rG one spreadsheet, all implementations.
  658. Ge0rG bonus feature: auto-complete over all projects for the per-xep excuse comments
  659. Mikaela has joined
  660. mukt2 has left
  661. Zash cell(xep, project) := ( "yes" / "no" / ">=x.y.z" ), ", comment"
  662. Ge0rG Zash: one line per xep per client, because we need three data elements.
  663. SamWhited FWIW I wasn't suggesting that the XSF web person would have to go look up my software and figure out what it supports. Just that I would paste all the information I had into an issue and they could do whatever they do with it.
  664. SamWhited If that includes the supported XEPs great, if not, we didn't require those anyways whether you write a DOAP file or not.
  665. SamWhited The point is just that if we want to list software we shouldn't be putting a large burden on the software authors and that's what we're doing with DOAP. Putting anyone who ddoesn't want to deal with XML namespaces and schemas into a second class citizens bucket is not okay IMO.
  666. Ge0rG SamWhited: pasting things into an issue is the opposite of reducing our webteam's workload
  667. Zash Nothing with the current approach prevents storing DOAP files in an XSF repo afaik
  668. SamWhited Ge0rG: I'm more concerned with the workload of the software authors which we are adding to if they want their software listed.
  669. Ge0rG SamWhited: you are confusing your impulse to provide 100% correct and validated XML with how people tend to work to get a green checkmark on a webpage.
  670. SamWhited Ge0rG: I'm not sure what you mean?
  671. Arne has joined
  672. Zash In the Prosody support channel we regularly hear from people going to great lengts to catch all the green checkmarks from the Conversations compliance tester.
  673. Ge0rG SamWhited: nobody particurly likes the DOAP format, but it is good enough, it is there, it does the job, and nobody expects to perform automatic validation of its XML
  674. SamWhited I don't expect it to either, I don't understand what you're arguing
  675. Arne has left
  676. Ge0rG SamWhited: most developers will pick an existing RDF file, replace the values, update the XEP list and be done with it
  677. SamWhited And now the bugs in that first RDF file are propogated down into all the other projects, yay complexity.
  678. jonas’ do you truly believe that would be different for any other format?
  679. SamWhited yes, absolutely
  680. Ge0rG jonas’: a schema-less format wouldn't have validation errors.
  681. SamWhited I'm not saying it will be bug free, but less complexity means fewer bugs.
  682. jonas’ Ge0rG, oh, true
  683. SamWhited Also having a single place where the format is fully documented means fewer bugs instead of just an XEP that documents a tiny part of it and links you to another schema instead of documentation.
  684. Ge0rG SamWhited: stop arguing and write down an informal description. Make a template RDF and run it through https://github.com/ewilderj/doap/tree/master/validator
  685. SamWhited I already did write down an informal description of one possibility
  686. SamWhited It's in the mailing list somewhere.
  687. SamWhited Or maybe it was here, I forget.
  688. Ge0rG SamWhited: if you'd have followed that path, everybody would be much happier and you wouldn't have burned through dozens of hours of people's time.
  689. SamWhited Still, I wasn't the one arguing, I asked about an alternative and then you started going back into the previous arguments again
  690. peetah has left
  691. peetah has joined
  692. pasdesushi has left
  693. Ge0rG SamWhited: well, in that case we can all go back to doing productive things again.
  694. SamWhited So, back to the original question: regardless of what format we use I think it shouldn't restrict us from listing a client or server or what not. The more complex the format, the fewer projects will implement it (of course, maybe I'm wrong and everyone will do it except me and it's fine if only one project is left out, I dunno), so I feel like we need an alternative either way.
  695. SamWhited We don't want to put too much on the website maintainers, so I agree they can't be expected to go look up a clients details just because the author asked to have it listed.
  696. SamWhited But I also think we shouldn't require authors to learn and write DOAP. I'm hopeful some web person can agree to a middle ground.
  697. Ge0rG SamWhited: the web team doesn't have resources beyond adding a link to an externally hosted file
  698. mathieui Again, nobody ever said it would restrict us from listing it on the website. Link Mauve put them first in the example, but if we agree that aesthetics don’t matter, it could be mixed without an issue.
  699. SamWhited Then we shouldn't add these doap enhancing features at all regardless of the format IMO
  700. Ge0rG maintaining the detailed information on the XSF repositories is a significant burden without any benefit
  701. Ge0rG SamWhited: those features provide multiple benefits
  702. Ge0rG the work has been done
  703. mukt2 has joined
  704. SamWhited The benefit is that authors don't have to learn DOAP or modify files on their web server which they may or may not have access too if they're using one of those easy website design or blogging things, etc.
  705. Ge0rG there is no reason not to make use of them.
  706. Zash Compromise suggestion: Add a logo and screenshot field to the clients.json format.
  707. SamWhited I completely disagree with that statement. I mean, I do think it's nice to have, but just because something has been done doesn't mean we need to maintain and support it going forward.
  708. Ge0rG SamWhited: implementation develoers will have some way to host files for users to download their implementations
  709. moparisthebest is the argument now that XMPP devs can learn+read+implement 300+ XEPs but not copy/paste/edit a doap file?
  710. SamWhited Zash: what is clients.json?
  711. Zash SamWhited, the list of clients used by the website curretly
  712. SamWhited Ge0rG: not necessarily, mine is just on GitHub.
  713. mathieui SamWhited, software developers who don’t have access to either a website or a public repo, really?
  714. andy has left
  715. Ge0rG SamWhited: https://github.com/xsf/xmpp.org/blob/master/data/clients.json
  716. SamWhited mathieui: do we support pulling from repos? That does negate that particular argument, I thought this was a website thing
  717. Zash https://github.com/xsf/xmpp.org/tree/master/data#software-directory-readme
  718. Ge0rG SamWhited: you can link to a raw file on github
  719. mathieui as long as it can be accessed with http's)
  720. mathieui as long as it can be accessed with http(s)
  721. pasdesushi has joined
  722. SamWhited That's fair then, I assume most (all?) repos are available over HTTP in some form.
  723. mathieui Of course, for non-opensource implementation the repo is a big no
  724. SamWhited So back to "I shouldn't be a second class citizen just because I don't know how 5 complicated XML technologies work and don't want to waste tons of time learning when I could just provide the information to put on the website"
  725. mathieui but then the entity probably has the resources to maintain an XML file on a website
  726. Ge0rG SamWhited: copy&paste the template RDF.
  727. SamWhited Ge0rG: we've already been through this. Then you end up propogating any mistakes in that down the chain. This is just bad software engineering.
  728. moparisthebest I can only do CSV and all this XML is too much for me, I shouldn't be forced to use XML to develop XMPP software, we need to rewrite the RFCs to use CSV
  729. SamWhited And bad web design for that matter. This is how half the netscape tags became things we had to live with.
  730. Ge0rG SamWhited: there is a DOAP validator.
  731. MattJ SamWhited, and this is terrible how? Actually?
  732. SamWhited Ge0rG: we've been through that too
  733. Zash moparisthebest, `xml2 | 2csv` is the best thing since pandoc!
  734. MattJ Worst case, we fix bugs we find
  735. moparisthebest Zash, but I shouldn't be forced to use tooling!!!
  736. Neustradamus has joined
  737. Ge0rG SamWhited: you dislike the format and are looking for excuses not to use it. This is fine. You are also trying to block everybody else from doing it / using the work they've already done. Please stop with that.
  738. SamWhited This work is garbage that will harm the XSF by making fewer projects be listed on the page, so yes, we shouldn't use it without modification.
  739. Zash moparisthebest: `csv2 | sed | xml2` then 😉
  740. MattJ SamWhited, your argument seems to be that because RDF has a schema, we are compelled to use it. Or we can create a custom format from scratch with no schema and that would be just fine.
  741. SamWhited I think that's a bullshit argument. I've written plenty of XEPs that had implementations that had to change after the fact, I didn't necessarily like it, but that's how we come to the best solution.
  742. SamWhited MattJ: yes, more or less, assuming some level of simplicity. I don't especially care if there is a schema or not, but I shouldn't have to read that schema to know how to write it.
  743. andy has joined
  744. SamWhited If someone wants to write a schema, fine.
  745. mathieui SamWhited, I believe a possible addition to the current XSF website CI could be a tool that pulls the new doap files and validate the schema
  746. SamWhited And I shouldn't have to import external namespaces, namespaces and namespace prefixes are just an anti-pattern.
  747. pasdesushi has left
  748. pasdesushi has joined
  749. moparisthebest Zash, and now you are expecting me to deeply understand the entire complexity of sed just to develop xmpp in csv? I just want to write CSV
  750. SamWhited But the point is mostly just complexity. This is all too much stuff that I'm not going to do. If I'm alone in that maybe it's fine and the XSF doesn't need to care, but I suspect I'm not and that outside this group there will be plenty of people who won't want to deal with it.
  751. mathieui (that would help notify software authors that their files are invalid, and prevent any mistake)
  752. Zash moparisthebest, leave that to Link Mauve or me then. I'm sure we can demangle your csv
  753. SamWhited mathieui: that's definitely something we would need to do either way I think
  754. mathieui SamWhited, yes
  755. mathieui I was thinking that in any case it is kind of required
  756. SamWhited But okay, my question was answered, sounds like this will be the only way and you can't just submit information if you want your client listed
  757. Ge0rG mathieui: in the end it will make the website CI fail on publishing unrelated page updates!
  758. mathieui Ge0rG, I was thinking of the CI pull requests only
  759. SamWhited Ge0rG: you don't have to make the publish fail, just alert that "file X was invalid this time and its entry won't show up in the table"
  760. Ge0rG SamWhited: yeah, that's the theory.
  761. SamWhited ?
  762. SamWhited I don't understand that statement, I thought you were just saying to mathieui that CI wouldn't work?
  763. Ge0rG SamWhited: I was saying that care needs to be applied so that CI won't fail for somebody else
  764. SamWhited oh sure
  765. SamWhited gotcha
  766. Ge0rG as a good software engineer you probably know that. But maybe you don't test it when implementing the CI addition, and in the end it fails in a different way leading to the website becoming unpublishable
  767. Ge0rG Or you run into a network timeout when pulling the remote spec file.
  768. SamWhited yah, I agree, we'd need CI for this regardless of the solution and if the solution involves downloading external files that CI shouldn't stop the whole website from publishing.
  769. paul has left
  770. Ge0rG and with XML being XML, well... you know the issues
  771. paul has joined
  772. mukt2 has left
  773. papatutuwawa has left
  774. Link Mauve “16:01:33 Zash> Nothing with the current approach prevents storing DOAP files in an XSF repo afaik”, in my current deployment, they are stored in $XDG_CACHE_HOME/xmpp-doap after having run the script, I could store them in the directory that will be served on the web instead, that way we don’t have to use the repository for every change.
  775. pasdesushi has left
  776. pasdesushi has joined
  777. chronosx88 has left
  778. chronosx88 has joined
  779. alameyo has left
  780. pasdesushi has left
  781. pasdesushi has joined
  782. pasdesushi has left
  783. pasdesushi has joined
  784. Ge0rG Link Mauve: storing them permanently will add another hidden cache
  785. Link Mauve It is a well-known cache.
  786. purplebeetroot has left
  787. pasdesushi has left
  788. pasdesushi has joined
  789. Ge0rG also it won't really solve any of the problems, just slightly mitigate them.
  790. purplebeetroot has joined
  791. pasdesushi has left
  792. pasdesushi has joined
  793. Link Mauve mathieui, my current tool kind of already validates that it at least is valid RDF/XML.
  794. Link Mauve I already caught Dino updating to invalid language tags as per BCP47.
  795. Link Mauve It’s based on the sophia crate.
  796. mukt2 has joined
  797. Ge0rG I tried to build the validator, but gave up after reading this: > error CS0006: Metadata file `Redland.dll' could not be found
  798. mathieui Link Mauve, I was saying, in the CI pipeline for the website merge requests, not for the website integration
  799. paul has left
  800. paul has joined
  801. Ge0rG mathieui: but that would make unrelated PRs also fail
  802. Link Mauve That also wouldn’t catch updates that are done without a PR, for instance synchronised to a client release.
  803. mathieui Ge0rG, you can get the diff of a PR and run it only if a file is added (which is the only point)
  804. mathieui and yes, the website thing needs to also validate and ignore the invalid ones, of course
  805. Ge0rG maybe just providing easy-to-use tooling to validate an RDF file would suffice?
  806. Ge0rG Like... host a validator? 😁
  807. Link Mauve “16:20:19 SamWhited> Ge0rG: you don't have to make the publish fail, just alert that "file X was invalid this time and its entry won't show up in the table"”, the way my tool works atm is that it will reuse the previously valid cached version in case the latest downloaded file was invalid this time.
  808. SamWhited I was forgetting this is all javascript too so CI wouldn't catch it. It doesn't seem great that things would just dissapear from the list and the old one would be used.
  809. Link Mauve It’s actually Rust.
  810. Ge0rG Link Mauve: that would work, except for server timeouts
  811. Link Mauve The JS is only for the presentation on XEP pages.
  812. SamWhited Oh, nevermind then, if it's on the backend we can add some alerting presumably
  813. SamWhited As long as there's some sort of alert that "Dino is now failing, please inform the authors"
  814. Link Mauve Ge0rG, timeouts are also handled (thankfully louiz’s forge was down at the time I wrote it :D), and will go the same path.
  815. Guus has left
  816. Arne has joined
  817. Ge0rG Link Mauve: are you doing all downloads in parallel? Because otherwise you'll end up with cumulative timeouts possibly exceeding the CI job lifetime
  818. Link Mauve SamWhited, yeah, currently it’s a warning being printed, I’m sure with some emailing integration it could do that automatically.
  819. Zash Link Mauve, is there a rust csv parser? 🙂
  820. Link Mauve Ge0rG, yes.
  821. Guus has joined
  822. Ge0rG Link Mauve: awesome job!
  823. Link Mauve Zash, https://crates.io/search?q=csv
  824. Zash obligatory "thanks, a blank page" <insert js rant>
  825. SamWhited Oh boy, wait until you realize that you can only log in if your project is on github.
  826. Link Mauve SamWhited, no, you need a GitHub account because that’s what they use as their authentication mechanism, but you can host your project anywhere.
  827. SamWhited or rather, if you have a github account. I guess the project doesn't have to be there.
  828. SamWhited Yah, that.
  829. Link Mauve Which I’m not fine with, but I understand the reasoning.
  830. Link Mauve Authentication is hard.
  831. Ge0rG At least it's not "login with facebook"
  832. Arne has left
  833. moparisthebest Zash, no JS required https://lib.rs/search?q=csv
  834. Zash shiny
  835. mukt2 has left
  836. arc has left
  837. arc has joined
  838. arc has left
  839. arc has joined
  840. arc has left
  841. arc has joined
  842. Link Mauve moparisthebest, oh thanks, I’ll use it starting from now.
  843. Neustradamus has left
  844. Neustradamus has joined
  845. moparisthebest np, I find it handy
  846. Andrzej has left
  847. Andrzej has joined
  848. MattJ Holger, since XEP-0045 differences are flavour of the month, do you happen to know if ejabberd supports additional data in the MUC registration form? i.e. this one: https://xmpp.org/extensions/xep-0045.html#example-71
  849. MattJ and if it does, when the user is already registered, does it include that form in a jabber:iq:register type=get?
  850. MattJ According to https://xmpp.org/extensions/xep-0045.html#example-70 the form should not be included if there is already a registration
  851. MattJ But if custom fields are supported, I don't see why you wouldn't want to provide that info to the client...
  852. MattJ and allow them to modify the registration
  853. Ge0rG And can we have DOAP support for individual features?
  854. andy has left
  855. Zash Oh glob
  856. Steve Kille has left
  857. purplebeetroot has left
  858. Andrzej has left
  859. Andrzej has joined
  860. Neustradamus has left
  861. Wojtek has joined
  862. emus has left
  863. emus has joined
  864. Andrzej has left
  865. Holger MattJ: Would have to check but the whole registration thing is outdated in ejabberd anyway, you register against the MUC service rather than individual rooms.
  866. Holger MattJ: I'd be motivated to change things to make Siskin work 🙂
  867. MattJ Ok, I'm sticking to XEP-0045 for now unless Siskin doesn't like it (early indications suggest it's fine)
  868. purplebeetroot has joined
  869. x51 has left
  870. paul has left
  871. paul has joined
  872. arc has left
  873. arc has joined
  874. arc has left
  875. andy has joined
  876. arc has joined
  877. debacle has joined
  878. arc has left
  879. arc has joined
  880. papatutuwawa has joined
  881. arc has left
  882. arc has joined
  883. Andrzej has joined
  884. Andrzej has left
  885. purplebeetroot has left
  886. ralphm Something's come up, can't make it today.
  887. ralphm (the Board meeting, that is)
  888. dwd Someone else want to Chair, then?
  889. MattJ "Go for it?" :)
  890. andrey.g has left
  891. MattJ First item on the agenda: XML or JSON
  892. dwd YAML
  893. Zash CSV
  894. dwd Blank Verse.
  895. dwd OK.
  896. dwd 1) Roll Call?
  897. MattJ Here
  898. mathijs has left
  899. dwd ENOQUORUM?
  900. Zash Seve, arc ?
  901. MattJ I don't think Seve will be joining us today
  902. Wojtek has left
  903. MattJ prods arc's alarm clock
  904. dwd OK, unless arc is about we have to can it. And I'm inclined to can it anyway without Seve and ralphm.
  905. MattJ wfm
  906. dwd 2) Try Again Next Week.
  907. dwd Let's try again next week.
  908. MattJ Pity, I was hoping we'd at least make it to the eternal debate: vim or nano
  909. Wojtek has joined
  910. Zash What about FOSDEM or Summit?
  911. MattJ Every board meeting results in: it's up to SCAM
  912. MattJ Pretty clear someone from SCAM needs to weigh in on that
  913. Zash Who was SCAM‽
  914. larma Maybe add GSoC to the list of things to think about?
  915. emus has left
  916. emus has joined
  917. dwd larma, We did, and (IIRC) I said I'd do something. We all also agreed to look at something else. We are lacking minutes from that one, and my memory is shot.
  918. larma Ah, great
  919. larma What "something else"
  920. dwd larma, But loosely, we noted that GSoC student time and money is halved this year, and we were talking about making up that shortfall ourselves.
  921. dwd larma, The something else was a similar thing to GSoC for under-represented groups, as I recall.
  922. larma Hmm. I was actually thinking that I like their idea of smaller projects
  923. larma At least if that means to have more projects/students accepted
  924. dwd larma, I don't think that's the implication here. I think it's just intended to be workload reduction due to COVID.
  925. Steve Kille has joined
  926. Zash I'm not seeing any activity in SCAM since October.
  927. mr_darcy has joined
  928. larma dwd: I understood the announcement such that the change is meant to persist and not related to covid
  929. lskdjf > larma, I don't think that's the implication here. I think it's just intended to be workload reduction due to COVID. To my understanding that is not the case. Google said they do it to open gsoc to more people and increase diversity. They think it makes it easier for non-US people to take part due to the summer break times. And for people with summer jobs. And they opened gsoc for people from further institutions.
  930. floretta has left
  931. lskdjf ^ dwd
  932. purplebeetroot has joined
  933. lskdjf And I can totally see all those points, that's why I liked the change towards shorter projects.
  934. dwd Ah, then I misunderstood.
  935. Zash Board members: Who's head of SCAM now?
  936. mukt2 has joined
  937. mathijs has joined
  938. Zash Guus, daniel, nyco?
  939. mathijs has left
  940. floretta has joined
  941. nyco Yes?
  942. Zash Hey nyco. You're listed on the website as a member of the SCAM team. Do you know what the status of that team is? I'm wondering because I haven't found any activity since October.
  943. Kev has left
  944. purplebeetroot has left
  945. deuill has left
  946. nyco for me, I have not been active for at least that amount of time sorry for this it means I don't know how to answer your question 🙂
  947. mukt2 has left
  948. Guus I assume that technically I am - but I've been equally inactive
  949. dwd TBH, I think it's too late to arrange a Summit for the "usual" time. I'm not convinced that';s even a sensible thing to do anyway if we're not in Brussels.
  950. Zash I'm getting the impression that only pep. was active, and they left the XSF.
  951. purplebeetroot has joined
  952. mukt2 has joined
  953. nyco We can do something online, my company can provide a BigBlueButton
  954. SamWhited pep left the XSF? Is there info on that somewhere?
  955. SamWhited I was gone for a while, so I'm still catching up on the stuff I missed.
  956. Neustradamus has joined
  957. purplebeetroot has left
  958. Arne has joined
  959. mukt2 has left
  960. Neustradamus has left
  961. emus has left
  962. emus has joined
  963. purplebeetroot has joined
  964. MattJ Just a "shift of priorities" I think
  965. mathijs has joined
  966. paul has left
  967. paul has joined
  968. marc has left
  969. marc has joined
  970. purplebeetroot has left
  971. marc has left
  972. marc has joined
  973. mathijs has left
  974. Wojtek has left
  975. deuill has joined
  976. Guus has left
  977. chronosx88 has left
  978. chronosx88 has joined
  979. marc has left
  980. marc has joined
  981. jcbrand has left
  982. Seve has left
  983. Seve has joined
  984. jcbrand has joined
  985. paul has left
  986. sidereal has left
  987. andrey.g has joined
  988. floretta has left
  989. paul has joined
  990. mukt2 has joined
  991. andrey.g has left
  992. j.r has left
  993. j.r has joined
  994. mukt2 has left
  995. floretta has joined
  996. benharri has left
  997. mathijs has joined
  998. Seve has left
  999. marc has left
  1000. flow I think I would love an online summit with ~15min talks where people talk about what they did with xmpp recently (given that they are enough people wo want to hold such a talk)
  1001. Seve has joined
  1002. Vaulor has left
  1003. Paganini has left
  1004. nyco has left
  1005. edhelas has left
  1006. mukt2 has joined
  1007. Paganini has joined
  1008. nyco has joined
  1009. nyco yes, definitely something simple
  1010. nyco we can't have a 2 days long open discussion with 20 to 50 active participants
  1011. Seve has left
  1012. floretta has left
  1013. marek has left
  1014. marek has joined
  1015. edhelas has joined
  1016. sidereal has joined
  1017. Zash Sounds good
  1018. mukt2 has left
  1019. lskdjf has left
  1020. lskdjf has joined
  1021. lskdjf has left
  1022. lskdjf has joined
  1023. lskdjf has left
  1024. Wojtek has joined
  1025. Seve has joined
  1026. chronosx88 has left
  1027. floretta has joined
  1028. Vaulor has joined
  1029. Yagiza has left
  1030. marc has joined
  1031. lskdjf has joined
  1032. arc Dwd sorry! I was conked out hard this morning.
  1033. Vaulor has left
  1034. Vaulor has joined
  1035. neshtaxmpp has left
  1036. arc But yeah SCAM is running fosdem con and we need to get our stuff in to them toward that end.
  1037. adiaholic has left
  1038. mr_darcy has left
  1039. andrey.g has joined
  1040. mr_darcy has joined
  1041. floretta has left
  1042. floretta has joined
  1043. goffi has left
  1044. Mikaela has left
  1045. SnowCode has joined
  1046. xsf has left
  1047. mr_darcy has left
  1048. xsf has joined
  1049. mr_darcy has joined
  1050. papatutuwawa has left
  1051. Seve has left
  1052. mr_darcy has left
  1053. mr_darcy has joined
  1054. mukt2 has joined
  1055. Seve has joined
  1056. mr_darcy has left
  1057. mr_darcy has joined
  1058. debacle has left
  1059. mr_darcy has left
  1060. mr_darcy has joined
  1061. debacle has joined
  1062. mr_darcy has left
  1063. mr_darcy has joined
  1064. mr_darcy has left
  1065. mr_darcy has joined
  1066. mr_darcy has left
  1067. mukt2 has left
  1068. mr_darcy has joined
  1069. mr_darcy has left
  1070. mr_darcy has joined
  1071. mr_darcy has left
  1072. mr_darcy has joined
  1073. mr_darcy has left
  1074. mr_darcy has joined
  1075. alameyo has joined
  1076. mr_darcy has left
  1077. mr_darcy has joined
  1078. mr_darcy has left
  1079. mr_darcy has joined
  1080. mr_darcy has left
  1081. mr_darcy has joined
  1082. mr_darcy has left
  1083. mr_darcy has joined
  1084. mr_darcy has left
  1085. mr_darcy has joined
  1086. mr_darcy has left
  1087. mr_darcy has joined
  1088. mr_darcy has left
  1089. mr_darcy has joined
  1090. debacle has left
  1091. Calvin has joined
  1092. Seve has left
  1093. Chobbes has joined
  1094. Chobbes has left
  1095. mukt2 has joined
  1096. Tobias has left
  1097. alex-a-soto has left
  1098. alex-a-soto has joined
  1099. paul has left
  1100. esil has joined
  1101. esil has left
  1102. Vaulor has left
  1103. adiaholic has joined
  1104. marc > I think I would love an online summit with ~15min talks where people talk about what they did with xmpp recently (given that they are enough people wo want to hold such a talk) +1
  1105. Vaulor has joined
  1106. edhelas has left
  1107. edhelas has joined
  1108. edhelas has left
  1109. edhelas has joined
  1110. pasdesushi has left
  1111. pasdesushi has joined
  1112. pasdesushi has left
  1113. pasdesushi has joined
  1114. mukt2 has left
  1115. pasdesushi has left
  1116. pasdesushi has joined
  1117. pasdesushi has left
  1118. pasdesushi has joined
  1119. Vaulor has left
  1120. esil has joined
  1121. esil has left
  1122. pasdesushi has left
  1123. pasdesushi has joined
  1124. marc has left
  1125. floretta has left
  1126. Vaulor has joined
  1127. pasdesushi has left
  1128. pasdesushi has joined
  1129. andy has left
  1130. esil has joined
  1131. esil has left
  1132. neshtaxmpp has joined
  1133. pasdesushi has left
  1134. pasdesushi has joined
  1135. wladmis has left
  1136. floretta has joined
  1137. lskdjf has left
  1138. Wojtek has left
  1139. esil has joined
  1140. esil has left