XSF Discussion - 2010-11-10

  1. Nÿco

    meeting in 12 minutes?

  2. Nÿco


  3. bear

    is there a board muc like there is for council?

  4. Will

    hi jack

  5. Florian


  6. Florian

    so ... time for the board meeting?

  7. Will

    30 seconds :-)

  8. Will

    Are we all here?

  9. Florian

    Peter is missing

  10. jack

    seems so

  11. jack

    Welcome everyone to the first meeting of the 2010/2011 board :)

  12. Will


  13. Will

    welcome especially Mike

  14. jack


  15. Florian


  16. jack

    Fresh blood is always good.

  17. bear


  18. bear

    oh me!

  19. Will

    some bloke, i dunno

  20. jack

    So as with every newly seated board, we have to nominate some officers

  21. Florian


  22. jack

    I believe we need ED, Secretary, and Treasurer

  23. Florian

    I'd propose Peter to take the position of ED if he's up for it

  24. jack

    oh, and board chair

  25. jack


  26. Will


  27. jack

    I'll volunteer for treasurer again

  28. Will

    especially as he's not here ;-)

  29. Florian


  30. bear


  31. Will

    stpeter now gets all the bad jobs

  32. Florian


  33. jack

    Alexander is our current secretary, and he did a good job as I recall last year. Does anyone know if he's up for doing it again?

  34. Will

    he's not said as far as i know.

  35. Florian


  36. Florian

    I'd say ... let's ask him

  37. jack

    I'd suggest we contact him and ask

  38. Will


  39. Florian


  40. Will

    note we're not contacting peter, just assuming

  41. Florian


  42. jack

    I'll email them both right now

  43. Will


  44. jack

    Bear, you seemed to be quite organized :) Want to ttake a crack at Chair?

  45. Florian


  46. bear

    what does that entail?

  47. Will

    quick, vote him in while he's still typing on typewithme and doesn't notice ;-)

  48. bear


  49. Florian


  50. jack

    mostly that you make some agendas

  51. Will

    you get to have a longer title than the rest of us and bang a gavel

  52. jack

    although I guess nyco has been doing that :)

  53. bear

    if it is just herding cats and making thingssmooth for others - sure

  54. Will

    I second bear for big chairman role

  55. jack

    There might be a bylaw or two were you break tie votes for other things, but AFAIK none of that has ever been used.

  56. bear


  57. Will

    you have no real power, we just get to blame you if things go wrong

  58. bear

    well damn, since you put it that way, where do I sign up!

  59. Will

    I'm not hearing anything from nyco - is he here?

  60. Florian


  61. bear

    he did a "lag test" about 15 minutes before the meeting started

  62. Will

    latency in france must be a b**ch

  63. Florian


  64. Neustradamus


  65. Nÿco


  66. Will


  67. Florian

    he's alive!

  68. Nÿco

    my client is

  69. Nÿco


  70. Nÿco


  71. Nÿco

    but still I can follow

  72. Florian

    using OneTeam again? :p

  73. Nÿco

    no, Psi+

  74. Florian

    sorry ... just had to crack that joke :p

  75. bear chuckles

  76. Nÿco

    the lag does not come from the client

  77. jack

    Alex responded that he is up for secretary again.

  78. Will


  79. jack

    +1 from me

  80. Will


  81. jack

    other votes?

  82. Nÿco

    as for the chair, I'm comfortably sit, thx ;-)

  83. Will


  84. Florian


  85. Florian

    ok .. so the board is sorted?

  86. Will

    i think so

  87. Nÿco

    sort... of

  88. Nÿco

    next item?

  89. Florian


  90. Nÿco

    bumonthly meetings?

  91. Will

    regular meetings +1

  92. Nÿco


  93. Nÿco


  94. jack

    I am +1 for the regular meeting slot.

  95. Florian


  96. Nÿco

    the biggest question will be time?

  97. Florian

    good time at the moment

  98. Will

    I'm ok for this time

  99. Nÿco

    we have a timezone overlap, let's choose in this timeframe

  100. Nÿco

    I'm ok too

  101. Nÿco

    "17:00 aka 5:00pm GMT/UTC"

  102. bear

    this time or earlier is good for me

  103. Florian

    I can't do 16:00

  104. Florian

    can't do earlier than 17:00

  105. Nÿco

    no one against this time?

  106. jack

    I think everyone confirmed.

  107. Florian

    ok ... great :)

  108. bear

    cool, so bi-weekly at 1700 GMT starting today

  109. jack

    Next topic, new website

  110. Will

    items on website....

  111. Nÿco

    every two weeks, bi-weekly being twice a week

  112. Nÿco


  113. Nÿco

    my mistake I don't find time to publish them

  114. Florian

    shouldn't that be something for the commteam?

  115. Will

    They were good, I'm happy to take lead in re-starting, with nyco's help

  116. Nÿco


  117. Nÿco

    drafts are in the wiki

  118. Will

    i'll take a look tomorrow

  119. Nÿco

    how would like to work? go on with drafting on the wiki?

  120. Will

    I think we should draft in the wordpress installation

  121. Florian

    +1 for wordpress

  122. Nÿco

    -1 for WP

  123. Will

    I suppose it is less public

  124. Nÿco

    this wiki lets other people watch and contribute, like for example Neustradamus, who is a great help

  125. Will

    so i understand where nyco is coming from

  126. Nÿco


  127. Florian

    what about Etherpad?

  128. Nÿco

    -1 for Etherpad: doesn't fit

  129. jack

    I think the wiki is fine

  130. Will

    i withdraw my +1 for WP and convert it to keeping with wiki

  131. Nÿco

    it is not optimal, I confess, but it works mostly

  132. jack

    Or rather, I vote for whatever Nyco would prefer, since he is the one drafting most of them :)

  133. Nÿco

    can we have a better tool someday?

  134. Will


  135. Florian


  136. jack

    Nyco, what would you like in a better tool?

  137. Will

    how about google wave <snigger>

  138. Nÿco

    I would define the roundups as being more successful, if we have more contribs, so any tool for contribs would do

  139. Florian

    instead of wave, I'd say etherpad

  140. Will

    we'll stick with wiki for the moment i think

  141. Florian


  142. Nÿco

    etherpad ahs no links, no traceability, etc.

  143. Nÿco

    etherpad is good for one-shots

  144. Nÿco


  145. Nÿco

    "new website" agenda item: anything to add?

  146. Will

    the tables have stopped working (not editable) again, Kev is looking to see if permissions have changed. If he can't find a reason, we'll try another way of generating them

  147. bear

    i'm working on getting access to git and going to switch the services, libs and clients table to generated tool like what is used for xeps

  148. Will

    plus the ics plugin that was causing the performance issues has a new version out which i'll try tomorrow probably....

  149. Will

    which should enable us to at last fill in this page: http://xmpp.org/participate/future-events/

  150. Will

    bear: that'd be good

  151. bear

    yea, going to use the same input format if possible

  152. Neustradamus

    I would like an update of the very old mediawiki version.

  153. Nÿco

    maintaining the tables data needs more contributions as well...

  154. Nÿco

    can we open the edition to some subsections of the website to special users?

  155. bear

    the person who maintains a spanish version of the tables has contacted me to help

  156. Will

    Nÿco: agree but we're short of volunteers at the moment.

  157. Nÿco


  158. Kev

    Nÿco: I don't know if that's possible in wordpress, is it?

  159. Nÿco

    I meant, can we do it technically?

  160. Nÿco


  161. Kev

    I thought you had to be a sitewide editor, but I'm no wordpress guru.

  162. Nÿco

    ok, no fine grained persmissions?

  163. bear

    if the tables can be generated then we can use git pull-requests :)

  164. Nÿco

    yes, from where?

  165. Will

    no fine grained permissions as standard but we can set people up as contributors which means their changes would be held until released by someone with higher permissions?

  166. Will

    i bet there's a plugin for that though (fine grained)

  167. bear

    let's let the current wp changes get made and then we could revisit the workflow

  168. Will


  169. Will

    walk first, run second

  170. Nÿco


  171. Nÿco

    anything else on the website?

  172. Will

    nothing here

  173. Nÿco

    I tend to agree on the Mediawiki version, but it's a low priority

  174. Nÿco

    next item? Sponsors?

  175. Will


  176. jack

    I will send an invoice to Collecta this week. They agreed to sponsor.

  177. jack

    Has anyone asked anyone else? Perhaps we should ask Jonas and see if google is interested :)

  178. bear

    do we have a list of past sponsors? and have they been contacted?

  179. Will

    I've not yet started asking, but a generic message to members to see if they know of anyone (employyers?) would be a good idea

  180. Nÿco


  181. Will

    I think peter is our best source for list of past sponers...

  182. Will

    i seem to recall we've talked about this before?

  183. bear

    is someone working on the past list then?

  184. Will

    i think "working might be stretching it

  185. bear


  186. bear

    ok, i'll contact peter about the past list and do an email to member list about suggestions

  187. Will

    I'll draft an email to Members

  188. bear


  189. Nÿco

    web archive machine may help

  190. Nÿco

    Wayback machine, sorry

  191. Nÿco


  192. Nÿco

    Special Thanks to Our Sponsors: IBM | Hitachi

  193. Nÿco


  194. Nÿco


  195. Nÿco

    in 2002

  196. Will

    you know that opening statement on that page is better than anything we currently have

  197. Nÿco

    next item?

  198. Nÿco


  199. jack

    We typically strive to keep the board meetings short. Shall we adjourn today and continue with the remaining items in 2 weeks?

  200. Nÿco

    - Roadmap update - GSoC - Elections - Mini Summits

  201. Nÿco


  202. bear


  203. Will

    +1 and we need to talk FOSDEM next meeting as well

  204. bear

    I would put that at the top of the list then

  205. Nÿco


  206. Nÿco

    Next meeting: 2010-11-24 17:00 aka 5:00pm GMT/UTC

  207. jack

    did someone contact htem?

  208. jack

    the call for devrooms closed October 16th :(

  209. Will

    jack: we have a devroom

  210. Nÿco

    Please, update your agendas

  211. Kev

    Ralph has arranged a room for the Saturday, I believe.

  212. jack

    will: ok good :)

  213. jack

    ok, see everyone in 2 weeks :)

  214. bear waves

  215. Will

    bye bye

  216. Nÿco


  217. Nÿco

    thx to all

  218. Will

    bear: do i have permission to leave now? ;-)

  219. bear bangs the gavel

  220. bear

    ok, meeting over

  221. Will


  222. bear


  223. bear

    who normally sends out meeting summary?

  224. Nÿco

    the one who asks...

  225. bear


  226. Nÿco


  227. Nÿco

    welcome to the board bear! ;-)

  228. bear

    ok, i'll work up a brief summary and post it to the members list

  229. Will


  230. bear


  231. Nÿco

    maybe no need for a summary, http://typewith.me/y1i9CHJHLH may be enough

  232. Nÿco

    with the log

  233. bear

    that should go to the wiki IMO with a link to the log

  234. bear

    but yes, my summary was going to be a shortened version of the typewith.me doc

  235. Nÿco

    why not... you want to archive everything? if we send to lists, it is archived, no?

  236. bear


  237. Nÿco

    mmm... yes to what?

  238. bear

    in the absence of past experience i was just going with what i've done - but sure, I will do that

  239. bear

    yes to your question

  240. Nÿco

    which one?

  241. bear

    do you have a link to the log

  242. Nÿco

    ah let me check

  243. bear

    yes I feel everything shoud b archived - which would be handled by a log link

  244. bear

    and the mailing list would serve as notice

  245. Kev

    For what it's worth, I think sending semi-formal minutes is worthwhile. I think a copy of the typewith.me document very nearly covers that, if not completely.

  246. bear


  247. Nÿco

    like this

  248. Nÿco


  249. Nÿco


  250. bear


  251. Kev

    Thanks bear.

  252. bear

    glad to help

  253. Nÿco

    ok, the Mediawiki definitely needs an upgrade

  254. Nÿco

    Neustradamus? do you wish to upgrade it?

  255. Kev

    I will do this after the interop event.

  256. Kev

    It's a big upgrade and I don't want to do it while we need the wiki for arranging stuffs.

  257. Nÿco

    http://wiki.xmpp.org/web/Special:Version Product MediaWiki Version 1.13.2 http://www.mediawiki.org/

  258. Nÿco

    Current version

  259. Nÿco

    1.16.0 – 2010-07-28

  260. Nÿco


  261. Nÿco

    why not

  262. Nÿco

    do you need help?

  263. Kev

    No, I can do it - but my experience with upgrading mediawiki is that it tends to be painful.

  264. Kev

    I guess we've enough time to fix it if it does go wrong and have it back for the interop.

  265. Kev

    Ok, I'll have a look at it.

  266. Kev

    But not tonight.

  267. Kev adds to todo.

  268. Neustradamus

    Kev: ok

  269. Nÿco

    yes, painful is quite close to what I experienced also

  270. Neustradamus

    after the update, you must add (a new time) the XMPP URIs -> http://wiki.xmpp.org/web/XMPP_URIs#MediaWiki

  271. Kev

    Let's get to the upgrade first.

  272. Nÿco

    yes, it's quite lower priority

  273. Neustradamus

    yes yes

  274. Nÿco

    though it would be nice to have XMPP URIs at the XSF ;-)

  275. Neustradamus


  276. Kev

    Nÿco: I wonder if this is something it's worth the XSF pursuing.

  277. Kev

    A relatively low proportion of clients will deal with system-click xmpp: URIs.

  278. Nÿco

    nevermind, if we don't have it, then who?

  279. Kev

    Sorry, I realise you can read what I said either way.

  280. Kev

    I mean:

  281. Kev

    Maybe it's worth the XSF pursing this and persuading clients to implement xmpp: handlers.

  282. Neustradamus

    Kev: yes

  283. Nÿco

    ah yes, indeed I read the other way round ;-) (which was surprising from you ;-) )