XSF Discussion - 2011-04-13


  1. bear

    FYI board meeting in 1 hour (if my calendar is accurate)

  2. Kev

    Thanks.

  3. bear

    board meeting in 15 minutes

  4. bear

    meeting notes are here: http://typewith.me/mLIIGK2glS

  5. bear

    are you doing the twitter'ing stpeter?

  6. stpeter

    howdy

  7. stpeter

    I can, yes

  8. bear

    thanks

  9. stpeter

    I was busy writing an email message to the Board about possible discussion topics

  10. bear is trying this new thing called "prepared"

  11. stpeter

    heh

  12. stpeter

    so I mentioned several possible topics: 1. GScC update 2. Summit #11 3. Removing "proposed" state from XEP-0001 4. Voxeo page for website 5. Public services list 6. Microblogging / blogging 7. Trademark sublicensing applications

  13. stpeter

    noodle on those, I'll be right back

  14. bear

    k

  15. Florian

    evening all

  16. stpeter

    hi Florian!

  17. bear

    hello

  18. stpeter

    Mr. Sheward and I can also give a report on the website -- I think we're finished with http://wiki.xmpp.org/web/XSF_website_gap_analysis_notes and can think about what new pages to add, if desired

  19. bear adds that to the top

  20. will.sheward

    Evening

  21. stpeter

    any sign of Jack or NĂ¿co?

  22. Florian

    evening Will :)

  23. bear

    just poked jack

  24. stpeter

    ok

  25. stpeter

    yes, he's online

  26. bear

    don't see nyco online

  27. will.sheward

    Anyone know what's happened to collecta?

  28. Florian

    me n'either

  29. stpeter

    at least at his current address -- Jack seems to move around a lot :)

  30. stpeter

    will.sheward: presumably Jack can tell us

  31. stpeter

    I don't know the story

  32. bear

    jack is in SF all week doing contract work for Yammer

  33. bear

    so he will be missing this one

  34. stpeter

    ok

  35. Florian

    let's go?

  36. will.sheward

    May need to remove the collect widget from the home page

  37. bear

    time to start then

  38. stpeter

    some of my items will really be for discussion in 2 weeks, they are organizational right now

  39. stpeter

    s/discussion/decisions/

  40. bear

    meeting notes are here: http://typewith.me/mLIIGK2glS

  41. stpeter

    here is what I posted earlier: 0. Website update 1. GScC update 2. Summit #11 3. Removing "proposed" state from XEP-0001 4. Voxeo page for website 5. Public services list 6. Microblogging / blogging 7. Trademark sublicensing applications

  42. stpeter

    typewith.me is nice

  43. stpeter

    ok

  44. Florian

    looks good

  45. will.sheward

    We can combine 0 and 4 I think

  46. stpeter

    nod

  47. stpeter

    so GSoC first?

  48. Florian

    sure

  49. stpeter defers to bear

  50. bear

    we received the 7 slots we asked for

  51. Florian

    great

  52. bear

    working with the python gsoc group to fit in some of their xmpp related projects

  53. bear

    we have 4 really solid students so far

  54. bear

    and kev is whipping into shape some of the others to see if they will make it in

  55. stpeter

    heh

  56. will.sheward

    Do we not have enough of our own?

  57. bear

    my hunch is that we will have 5 or 6 solids

  58. stpeter

    do we need to use all 7 slots?

  59. stpeter

    I'd prefer to have fewer solid students

  60. bear

    we have a lot of really iffy applications

  61. stpeter

    if needed

  62. Kev

    We asked for 7 because that's the number that the mentors asked for.

  63. stpeter nods

  64. stpeter

    last year we had 3

  65. bear defers to kev to fill in the details

  66. stpeter

    IIRC

  67. will.sheward

    Iffy I'm what way?

  68. Kev

    4 the mentors said were outstanding, 3 more the mentors said were good and they wanted.

  69. will.sheward

    In

  70. Kev

    will.sheward: Nothing more than usual. Not all applications are good.

  71. stpeter

    will.sheward: yes you are iffy

  72. Kev

    stpeter: 3, we asked for another and got it.

  73. bear

    most were just from students who gave little to no thought on their app and then were not heard from again

  74. stpeter

    will.sheward: the scent of money attracts some flaky students

  75. stpeter

    hell, I was a flaky student myself once :)

  76. Florian

    hehe

  77. will.sheward

    Ok

  78. Kev

    This year the scheme was changed to ask for the number of outstanding (4) students and the number you'd like (7) in an ideal world.

  79. Kev

    We got all 7.

  80. stpeter

    so typically we need to weed out a lot of chaff

  81. Kev

    If a mentor changes their mind about wanting their student, we give the slot back and Carol hands it out to another org.

  82. stpeter

    yep

  83. stpeter

    that works fine

  84. stpeter

    hi Emil

  85. stpeter

    anything else related to gsoc?

  86. Kev

    We can't discuss what the applications were here, but Board are welcome to sign up to Melange and look at them there.

  87. Kev

    Yes.

  88. Kev

    We need to devote significantly more effort to it next year.

  89. stpeter

    hmm

  90. stpeter

    it's always a lot of work

  91. Kev

    Trust me, I know.

  92. stpeter

    is it becoming even more work? :)

  93. Kev

    Well, if we want to get more high quality students, we need to attract them somehow.

  94. stpeter thinks about costs and benefits

  95. bear

    the mentor side is more work this year

  96. Kev

    bear: Based on what?

  97. bear

    the org admin side is minimal

  98. Kev

    Ahem.

  99. stpeter

    heh

  100. will.sheward

    Heh

  101. bear

    just seeing how busy you are chasing students and mentors

  102. Kev

    Yes, that's org admin work :)

  103. bear hides

  104. Florian

    :p

  105. Emil Ivov

    hey Peter :)

  106. Kev

    Between mentor and org admin, my effort's been measured in hours/day for the last few weeks.

  107. Kev

    But anyway.

  108. Kev

    The reward of getting new contributors to the projects is, I think, significant and worthwhile.

  109. stpeter

    Kev: every year we say we need to plan more fully, and either we don't do the planning or we neglect to capture lessons learned from the previous year...

  110. Kev

    So we can not do any more recruiting than we normally do, and that's fine.

  111. stpeter

    so we need to get better at that

  112. Kev

    stpeter: Well, myself and people from KDE/Gentoo/X.org have been writing a series of lessons on the Google Open Source blog for that.

  113. stpeter

    and I'm part of the problem, so I'm volunteering to help

  114. stpeter

    Kev: excellent

  115. Kev

    http://google-opensource.blogspot.com/2011/04/dos-and-donts-of-google-summer-of-code.html for exampel.

  116. bear

    i'm also part of the problem to be blunt - I have been giving minimal support and will fix that

  117. Kev

    Anyway. We've had an apathy from projects this year. Swift, Buddycloud and PySoy have each put in considerable work and have as a consequence got great proposals.

  118. stpeter

    right

  119. stpeter

    you get out what you put in

  120. Kev

    Others less so, and I'd really like us to have more active projects.

  121. stpeter

    yep

  122. Florian

    yeah

  123. stpeter

    but that's a bigger problem

  124. Kev

    And the OneSocialWeb incident was *not* good.

  125. bear

    I think we need to put into the calendar a couple months *before* the signup to start banging the drum about the next one

  126. Kev

    bear: Yes, that was what I was going to suggest.

  127. bear

    stpeter - can you add a "tickler" event to the calendar for next year?

  128. stpeter

    I was thinking just an hour ago or so that we don't have a lot of active projects, and that's a problem, but it's a bigger problem than GSoC

  129. stpeter

    bear: yes

  130. Florian

    stpeter: indeed ...

  131. Kev

    stpeter: True, although GSoC is a great opportunity for projects to become active.

  132. bear

    maybe we can use the gsoc project list as a bit of guilt for the others - start really talking them up

  133. Florian

    hey ... this might be something ...

  134. Florian

    why not let us organize something post GSoC?

  135. Florian

    i.e. the XMPP Winter of Code :p

  136. Kev

    When fringe groups (And I'm not using the term derogitavely) like BC and PySoy are getting better applications for XMPP than anyone other than Swift, it's a sad sad sign.

  137. Kev

    better is the wrong description.

  138. Kev

    More XSF-relevant.

  139. bear

    can we move this discussion to the list for followup

  140. Florian

    +1

  141. Kev

    Sure, I don't have much more :)

  142. bear

    k

  143. will.sheward

    Then we need to define what is relevant well before the event

  144. stpeter

    Kev: thanks for sharing :)

  145. stpeter

    bear: I put it on my calendar for October 10 so that we can raise this topic with the incoming Board at that time

  146. bear

    stpeter - can you add will's comment to the tickler

  147. Kev

    will.sheward: We do. We should generaly be more engaged further in advance.

  148. stpeter

    right

  149. bear

    ok, next - website update?

  150. stpeter

    ok

  151. Florian

    sure

  152. stpeter

    so Will and I finished http://wiki.xmpp.org/web/XSF_website_gap_analysis_notes

  153. stpeter

    that took longer than expected, but most things do :)

  154. will.sheward

    Well, you mostly

  155. stpeter

    the last pages to be fixed were related to the public services

  156. stpeter

    now at http://xmpp.org/resources/public-services/

  157. stpeter

    we've had discussion on the operators@ list about that

  158. stpeter

    and some volunteers

  159. stpeter

    open question how to manage that going forward

  160. stpeter

    and whether we need more features

  161. will.sheward

    Volunteers,good

  162. stpeter

    but I think we at least have a path to updating it more often

  163. stpeter

    not sure how to sync the WP page with the .xml file that clients use

  164. will.sheward

    We/I still need to sort out the sponsor stuff..was planning to delete non sponsors tomorrow

  165. stpeter

    but we can work that out

  166. stpeter

    will.sheward: ok good

  167. stpeter

    will.sheward: and we need a page for Voxeo

  168. will.sheward

    As the CEO is on holiday :-)

  169. stpeter

    heh

  170. will.sheward

    Voxeo, check

  171. stpeter

    will.sheward: by "check" do you mean you'll come up with content?

  172. stpeter

    will.sheward: the sponsor pages are typically brief

  173. will.sheward

    Yes

  174. stpeter

    ok

  175. stpeter

    thank you

  176. Florian

    gret

  177. will.sheward

    Then I'll check with the sponsor for changes

  178. stpeter

    super

  179. stpeter

    anything else on the website?

  180. stpeter

    we talked about recruiting maintainers for various sections

  181. will.sheward

    Tunnels coming up, may lose you for a few minutes

  182. stpeter

    I updated the history page recently http://xmpp.org/about-xmpp/history/

  183. stpeter

    ok

  184. stpeter

    moving on to the Summit, then

  185. Florian

    ok

  186. stpeter

    OSCON is directly opposite the IETF meeting in Quebec City

  187. stpeter

    I am wondering about holding the Summit in QC

  188. stpeter

    e.g., Saturday and Sunday before IETF meeting

  189. Florian

    interesting

  190. stpeter

    QC is nice

  191. Florian

    would we get the audience we'd want for the Summit?

  192. stpeter

    and I could work with IETF to get the XMPP meeting on Monday

  193. bear

    that will be sad for those of us who normally go to oscon :(

  194. stpeter

    yeah

  195. stpeter

    not sure what to do

  196. stpeter

    or y'all can meet in Portland, but I can't join

  197. stpeter

    (nor can some others, I'd think, who are involved in IETF stuff -- Joe Hildebrand etc.)

  198. bear

    most of the core summit folk will be missing - it would be a "hey, this is xmpp" type event

  199. stpeter

    not that you need me to be there necessarily

  200. stpeter

    maybe a hackathon would be more productive in some ways anyway

  201. stpeter

    I'm still interested in that XMPP validator :)

  202. Florian

    :)

  203. Florian

    well ... if we do it before OSCON

  204. stpeter

    I think I can also raise money for the validator

  205. Florian

    Sat / Sun ... would people be willing to come to the Summit?

  206. bear

    I had wanted to continue the work we started last time, but the core folks will be missing

  207. Florian

    in QC

  208. bear

    we should mail the members and find out

  209. stpeter

    QC is a bit hard to get to, but easier for folks in Europe perhaps

  210. will.sheward

    Let's mail and see if anyone has strong views

  211. stpeter

    Florian: we could potentially do Friday and Saturday in QC

  212. stpeter

    ok

  213. stpeter

    next item, "Removing "proposed" state from XEP-0001" -- I think we can discuss that next time

  214. stpeter

    we had discussion on the members@ list

  215. stpeter

    I'd like to poll the Council about that at its next meeting

  216. stpeter

    then ask the Board to perhaps take action

  217. stpeter considers Kev's 30-minute meeting rule :)

  218. Florian

    sounds good.

  219. bear

    +1

  220. stpeter

    "Public services list" we already discussed

  221. stpeter

    briefly about "Trademark sublicensing applications" -- I will put three applications in the tracker at http://tracker.xmpp.org/browse/TRADEMARKS?report=com.atlassian.jira.plugin.system.project%3Aopenissues-panel for discussion by the Board at its next meeting

  222. Florian

    ok

  223. Florian

    can someone give me an account on there?

  224. stpeter

    I have reached out to all the projects listed on our website that have "JABBER" in the name

  225. will.sheward

    Ok

  226. stpeter

    Florian: yes, will do in a minute

  227. Florian

    great, thanks

  228. stpeter

    Florian: in fact you have an account

  229. stpeter

    it's tied to your florianjensen.com address

  230. Florian

    ah, ok

  231. stpeter

    username florian

  232. Florian

    strange ... but will check :)

  233. Florian

    thx

  234. stpeter

    you can ask for a password reset

  235. bear

    blogging?

  236. stpeter is slowly catching on myriad topics after RFC publication

  237. stpeter

    bear: in Brussels, Johann Prieur volunteered to post to the identi.ca / Twitter account

  238. bear

    will he be working from a set list of topics or doing it adhoc?

  239. stpeter

    do we want to just hand out credentials to those accounts, or set up a bot that people can post to?

  240. stpeter

    adhoc, I think

  241. stpeter

    so we need to think about how we want to do that

  242. bear

    a bot would allow for single source for credentials and be able to add/remove cleanly IMO

  243. stpeter

    e.g., do we want to have something of a communications plan / program for microblogging and blogging?

  244. will.sheward

    Adhoc +1

  245. stpeter

    bear: agreed

  246. Florian

    AdHoc +1

  247. stpeter

    I mean, we can always coach people on topics

  248. bear

    I would love to have items go to the list for possible preparation but adhoc for sure

  249. will.sheward

    Well never get a coms plan off the ground

  250. bear

    and the bot could also post to the list

  251. Kev

    We've got a whole comm *team*

  252. Kev

    And very active it is too.

  253. stpeter

    it's hard to plan for microblogging -- it's supposed to be a spontaneous kind of activity :)

  254. Kev

    I'd suggest not adding too many barriers to entry in light of this!

  255. stpeter

    Kev: indeed

  256. bear

    i'm more worried about having it seem like spam if 5 people all post in a day on the same topic

  257. will.sheward

    Trust the team to plan itself I think

  258. bear

    +1 for comm team assignment

  259. Florian

    +1

  260. bear

    let them tell us what they need

  261. stpeter

    WFM

  262. stpeter

    but the bot would help -- let's poke that iteam

  263. bear

    :)

  264. stpeter

    I think we had a similar bot at one point, didn't we?

  265. stpeter

    I'll poke Matthew Wild about that

  266. stpeter

    I think he had a similar bot

  267. stpeter

    ok

  268. stpeter

    so that's it from me

  269. will.sheward

    +1 for poking people other than me

  270. stpeter

    heh

  271. Florian

    nothing to add here

  272. will.sheward

    Or here

  273. stpeter

    we have some action items

  274. stpeter

    next meeting?

  275. stpeter

    is it in the calendar already?

  276. stpeter checks

  277. stpeter

    2 weeks from today I will be flying to New Jersey for a W3C workshop on web tracking and user privacy

  278. Florian

    next week?

  279. stpeter

    3 weeks from today I will be flying back from the IESG retreat in Amsterdam

  280. Florian

    as Jack and Nyco were missing?

  281. stpeter

    that's fine with me

  282. bear

    next week works for me

  283. Florian

    +1

  284. will.sheward

    Ok

  285. stpeter updates the calendar

  286. Florian

    great

  287. stpeter

    I'll check the typewith.me page here in a second so we can capture all the action items

  288. will.sheward

    We done? gavel banging tinne?

  289. stpeter

    yep

  290. stpeter

    seems so

  291. will.sheward

    Time

  292. Florian

    cools ... thanks everyone

  293. bear

    thanks

  294. stpeter

    yes, thanks

  295. bear

    any changes to the meeting notes?

  296. Florian

    none from me

  297. bear

    who is mailing the list for the summit poll?

  298. stpeter

    bear: checking

  299. stpeter

    minutes look good

  300. stpeter

    thanks for that

  301. bear

    np

  302. bear sends to members list

  303. stpeter

    calendar updated

  304. bear

    i'll email the comm team about bot

  305. bear

    can someone who is familiar with the QC IETF meeting compose the poll question

  306. stpeter

    bear: ok thanks

  307. stpeter

    bear: I can send the poll, sure

  308. bear

    thanks

  309. stpeter

    message sent to members@

  310. stpeter

    I'll forward to summit@ too

  311. bear

    I emailed the comm team also

  312. stpeter

    I saw

  313. stpeter

    thanks