XSF Discussion - 2013-02-27


  1. bear

    most of the really broken style stuff has been fixed; sidebar with sponsors is fixed; nav bar with dropdown is fixed;

  2. bear

    still need to fix some metadata in secondary pages and clean up things like sidebar, feed and some centering issues

  3. bear

    k, cleaned up the dup title glitch (articles that had both a Title: metadata item and also a # Title line in the body)

  4. ralphm

    bear: keep up the good work

  5. jabberjocke

    bear: just say if you need any testing help

  6. Ashley

    i'm so here and ready to collaborate!

  7. stpeter

    heh

  8. stpeter

    let's see if bear is around

  9. stpeter

    I did update the calendar, but it was last night

  10. stpeter

    poked him via IM

  11. stpeter

    brb

  12. stpeter

    back

  13. Ashley

    so….

  14. stpeter

    well

  15. Ashley

    i was so happy i actually made it :)

  16. bear

    i'm here

  17. Alex

    so am I ;-)

  18. bear

    am I late?

  19. stpeter

    happy to see that http://www.coversant.com/ is back online, although I think we've not seen Jason in a while

  20. Kev

    Coversant have been back for a while.

  21. stpeter

    Kev: the site had some wonky unavailable message a few days ago

  22. Kev

    Ah, OK.

  23. Kev

    I thought you meant Coversant in general :)

  24. stpeter

    "account suspended" or somesuch

  25. stpeter

    not sure I have Arc in my buddy list

  26. bear

    arc may not be able to make it - he also had a conflict with schedules

  27. stpeter

    ah ok

  28. stpeter

    I just invited Florian

  29. Florian

    hi all

  30. bear

    we traded emails, I told him about the agenda and invited him to send email if he had an special requests

  31. stpeter

    hey :-)

  32. stpeter

    so it seems that the Board has a quorum

  33. bear

    \o/

  34. bear

    should be a fast meeting - shall we start?

  35. stpeter

    fire away, boss!

  36. Ashley

    sure!

  37. bear

    I had only two items to talk about, does anyone have anything to add to the agenda?

  38. bear

    first item is post FOSDEM - as peter pointed out, we should make sure the checklist is updated

  39. Ashley

    do we need to talk about the github TOS?

  40. bear adds to the list

  41. Kev

    (GSoC)

  42. bear

    I'll send an email to the members list asking everyone to update that wiki page with anything they fell is needed for next year

  43. bear

    do we have any financial obligations (billing sponsors, paying someone from receipts)?

  44. bear

    no? ok

  45. bear

    if anyone has anything to add to the followup, please do pile onto the email I'll send in a bit

  46. stpeter

    I've updated http://wiki.xmpp.org/web/FOSDEM_Checklist

  47. bear

    cool

  48. stpeter

    bear: I need to send invoices / receipts for dinner sponsors, will do that Friday afternoon

  49. bear

    ta

  50. stpeter adds it to his calendar

  51. bear

    ok, next item - Office(r) assignments

  52. bear

    I need to send an email from the board to the current Officers asking if they want to remain

  53. bear

    if not, then we need to find new warm bodies

  54. bear

    plus we need to find a Treasurer - right?

  55. Alex

    I volunteer again for secretary

  56. bear

    that is very much appreciated Alex

  57. stpeter

    bear: we've essentially not had a Treasurer since the old Jabber Inc. days, I've been serving pro-tem in that capacity but I think think it might be good to have someone else fill that role for the sake of transparency

  58. bear

    agreed, the hard part is finding someone who 1) has the skills and 2) is close enough to you to review the books properly

  59. bear

    I know I have no skills with non-profit accounting

  60. Alex

    and 3) be familiar with US laws

  61. bear

    is this something we open to the members list? my opinion is that it may be opening us up for some grief if we just send a blanket email

  62. stpeter

    it doesn't need to be a member

  63. stpeter

    another option is to use a bookkeeping service of some kind, of course

  64. stpeter

    but our volume is quite low

  65. bear

    maybe I should ask Julie from &yet if she wouldn't mind

  66. bear

    she does our books and a number of other non-profits

  67. stpeter

    ah, that's not a bad idea

  68. bear

    k, lets table treasurer until the board members who are absent can bring up some possibilities - i'll send an email to them saying that I will be approaching julie and for them to bring up some solutions

  69. stpeter

    Jack Moffitt volunteered to do it a while back but we never got him set up properly at the bank

  70. stpeter

    bear: sounds good

  71. bear

    he mentioned he might still be interested, i'll reach out

  72. stpeter

    and Jack is really too busy anyway

  73. stpeter

    ok

  74. stpeter

    he always seems to be busy, anyway :-)

  75. bear

    yea, serial entrepeneur and all that

  76. bear

    ok, moving on...

  77. bear

    github tos

  78. bear

    I don't think it's an issue anymore

  79. Ashley

    so, as i read it, the github tos doesn't seem to make any claims about IP ownership

  80. Ashley

    ah, well, in that case… :)

  81. bear

    having read it, it no longer has some of the onerous issues that it used to years ago

  82. bear was agreeing with Ashley

  83. Kev

    This is explicitly only for mirroring and not for accepting contributions, right?

  84. bear

    correct

  85. Ashley

    that's our use case, right?

  86. stpeter

    right, just mirroring

  87. bear

    everything goes thru the mailing list for submissions, so we wouldn't use it for PullRequests or Issues

  88. Zash

    BTW: http://tos-dr.info/#github

  89. Kev

    I'm still not clear what the great rush to mirror to github as well as gitorious that we've been using for years, but anyway. /me goes back to lurking.

  90. Alex

    I think this discussion is some kind of conflict between open source developers and commercial developers. Because they have a different viewpoint when it comes to copyright and ownership

  91. Zash

    For short summary

  92. stpeter

    Kev: social coding :-)

  93. stpeter

    Kev: visibility etc.

  94. bear

    kev - I think the issue just became visible and it shown bright enough to distract folks from their coding and stirred up the ant hill

  95. bear

    once we say "ok, it's mirrored" things will settle down

  96. bear

    until someone asked for mercurial mirroring or some such

  97. stpeter

    anyway I've set up https://github.com/organizations/xsf (Pedro Melo transferred the 'xsf' account to me and I changed it into an organization)

  98. stpeter

    I see no problem with multiple mirrors

  99. stpeter

    anyway, tempest in a teapot AFAICT

  100. bear

    yep, i've added a logo and after I finish with the static site I will work on the git mirror commit hooks

  101. bear

    ok, lets settle this by being decisive and if someone really is bothered we can invite them to the infra team

  102. stpeter

    bear: happy to work with you on the static site

  103. stpeter

    bear: wfm

  104. bear

    I'll be posting a not tonight or tomorrow about that - it's down to text clean up now

  105. stpeter

    bear: super

  106. bear

    anyone with any major grief/issues/questions about github mirroring?

  107. Kev

    Not me.

  108. Ashley

    no

  109. bear

    k, moving on

  110. bear

    last item - GSoC

  111. bear

    from the wiki page, it appears that we have 4 other folk to help with the admin side

  112. bear

    (other than me)

  113. stpeter

    (oh, as with Alex, I am willing to continue serving as executive director, but of course the board is welcome to search for other candidates :-)

  114. bear

    the wiki page being http://wiki.xmpp.org/web/Summer_of_Code_2013

  115. Alex

    thats not a lot

  116. bear

    dang - now I don't have anyone to send emails to asking for their continued support ! ;)

  117. Kev

    bear: My view is that there hasn't been sufficient interest from mentors of projects that we'd be able to have under us, and we should skip a year.

  118. Ashley

    brb

  119. stpeter

    I tend to concur with Kev

  120. bear

    I agree, knowing from past how much attrition happens to even the most ardent of supporters, I don't think we have sufficient coverage

  121. stpeter

    it's really about the projects, not the org admin type folks

  122. bear

    sounds like we have consensus

  123. stpeter

    but there are plenty of worthy projects out there and there's no use taking up space in GSoC if we can't have an effective summer

  124. bear nods

  125. bear

    ok, unless someone objects, I will summarize it to the members that we do not have the resources to give the students the proper mentorship they require and will be skipping this year

  126. stpeter

    bear: well said

  127. Ashley

    ok

  128. Kev

    Thanks.

  129. bear

    and if someone complains, I will invite them to be on the gsoc team next year

  130. stpeter

    :-)

  131. Alex

    +1

  132. Kev

    Oh, quite the opposite.

  133. Kev

    If someone complains but didn't offer to help in advance...

  134. stpeter

    heh

  135. bear

    true, I would need to put on my "kev" hat when dealing with them (or my "cridland" hat)

  136. bear

    k, approaching 30(ish) minutes, any other issues to deal with?

  137. stpeter

    I think we're done

  138. bear

    ... not hearing anything ...

  139. bear bangs the gavel

  140. Kev

    Thanks.

  141. stpeter

    thanks, all

  142. bear

    thanks everyone

  143. bear wanders off to write some emails

  144. Ashley

    cheers

  145. ralphm

    bear: good plan!

  146. jabberjocke

    Hi was thinking of having a workshop around xep for sensorsystem

  147. jabberjocke

    do we have access to a webex account?

  148. jabberjocke

    and do any of you have any history around the issues with using xmpp for sensor data

  149. bear

    jabberjocke - you should ask this in the jdev chat room - you will get more people listening

  150. jabberjocke

    yes thanks will do that

  151. jabberjocke

    but do xsf have any support for holding meetings such as webex

  152. bear

    most of the meetings we hold are chat only

  153. bear

    because of how distributed our members are and how many OSs that are not covered by webex

  154. bear

    now that doesn't say we don't use webex like during the last Summit

  155. jabberjocke

    Think it's good to have more direct discussion when having a workshop on the subject

  156. jabberjocke

    Will go for the mailinglists to collect intrest first and se how many that wuld like to participate

  157. ralphm

    We've traditionally always used text, as bear said, as that is usually more productive for multi-party discussions. That said, if you really need audio/video, I'd suggest using Google Hangouts

  158. ralphm

    maybe the Live variant, so that you can also have it recorded and published at Youtube

  159. jabberjocke

    good point thanks

  160. jabberjocke

    i've seen several different suggestions Sensor-Over-XMPP (aka SOX)

  161. jabberjocke

    was there any discussion during the summit of "internet of things" and real distributed sensor and control

  162. stpeter

    given that I work on the WebEx team I might be able to set something up ;-) but we could also use something free like http://conversat.io/

  163. ralphm

    n

  164. jabberjocke

    It's probably just me being unused to just text

  165. ralphm

    jabberjocke: you are so missing out

  166. jabberjocke

    youre probably right about productivity

  167. jabberjocke

    ralphm: you mean that there was a discussion during the summit?

  168. ralphm

    I meant that you are missing out on productive text-based discussions

  169. jabberjocke

    true

  170. jabberjocke

    :)

  171. bear

    meeting minutes: (done)

  172. bear

    officer summary: (done)

  173. bear

    i'll report on the github and static site status later tonight - first I need to make my $dayjob bosses happy ;)

  174. Kev

    Thanks. And thanks for looking after the migration.

  175. bear

    glad I can help

  176. bear toddles off to find some food