XSF Discussion - 2020-02-27


  1. jonas’

    marc0s: sometimes, addons such as noscript or umatrix block the files needed for renderig

  2. jonas’

    since XSL is turing complete.

  3. jonas’

    if you plan to do more XEP work, using the makefile in the xeps repository to build your document ( `make build/inbox/reminders.html`, assuming linux and your protoxep in `inbox/reminders.xml`) may be worthwhile

  4. marc0s

    thanks jonas’ . Yes I'm aware of the Makefile, I was just wondering why it didn't work. More than probably is one of those addons, which I have both

  5. jonas’

    marc0s: also I replied to your email with further instructions

  6. marc0s

    jonas’: got it, thanks

  7. marc

    > So, it would be nice to get 389 moving again. Zash: 389 is IBR after bind or what?

  8. Zash

    No

  9. marc

    I don't get the point then

  10. Ge0rG

    marc: what's the essence of our yesterday's discussion? Do you want to make token-IBR and PARS more distinct, and have a stronger highlight on the standalone token-IBR? Do you want to make the changes or shall I make another attempt at a PR?

  11. Ge0rG

    And that's actually absolutely orthogonal to the pre-IBR-IQ vs. dataforms vs. ??? question

  12. marc

    Ge0rG: wasn't the outcome that we make pars / roster subscription "more optional" in 401?

  13. marc

    > And that's actually absolutely orthogonal to the pre-IBR-IQ vs. dataforms vs. ??? question Yes, but still an open question

  14. Ge0rG

    marc: yes, that was the desired outcome. The question is, how we get there and who's in charge

  15. Ge0rG

    marc: I'm strongly convince that under the given circumstances, pre-IBR IQ is the last hacky hack.

  16. Ge0rG

    marc: I'm strongly convinced that under the given circumstances, pre-IBR IQ is the last hacky hack.

  17. marc

    > marc: I'm strongly convinced that under the given circumstances, pre-IBR IQ is the last hacky hack. 🤔

  18. Zash

    "least"?

  19. Ge0rG

    marc: I'm strongly convinced that under the given circumstances, pre-IBR IQ is the least hacky hack.

  20. Ge0rG

    Zash: thanks. My keyboard seems to be eating lttrs

  21. Alex

    @‎pep.‎ memberbot PR looks good to me. But it looks like I don't have permissions ro merge

  22. pep.

    hah

  23. pep.

    MattJ, ^

  24. pep.

    plz! :)

  25. pep.

    I might not make it in 5mn, or I'll be late (on the road)

  26. MattJ

    *nod*

  27. ralphm bangs gavel

  28. ralphm

    0. Welcome

  29. ralphm

    Hi! Who do we have?

  30. Seve

    Greetings! :)

  31. pep.

    ! somewhat. better in a few minutes

  32. MattJ

    o/

  33. ralphm

    Guus?

  34. Guus

    here

  35. ralphm

    Yay!

  36. ralphm

    1. Minute taker

  37. nyco-2

    https://mensuel.framapad.org/p/9f92-2020-02-27-xsfboardweekly

  38. ralphm

    hello nyco-2! Thanks

  39. ralphm

    2. Team memberships

  40. ralphm

    jonas’ raised this item, regarding culling the editor team from people who are not actually, well, editing.

  41. MattJ

    Right

  42. MattJ

    As agreed last week, I pinged each member currently listed on the editors team

  43. MattJ

    Nobody asked to be removed from the team, everyone indicated they intend to contribute where they can

  44. MattJ

    I understand this is probably not the outcome jonas wanted

  45. Guus

    They explicitly replied? Nice.

  46. MattJ

    Yes, everyone

  47. pep.

    ! here

  48. MattJ

    A couple of people did say that they are ok with being removed if it is a problem

  49. MattJ

    The original intention based on last week's discussion was to remove anyone who had e.g. overlooked resigning from the team

  50. MattJ

    It appears nobody falls into that category

  51. ralphm

    Right

  52. MattJ

    If we want to actively start removing people from the team, I think that's a tougher call and would need some objective criteria or someone other than me to make that call :)

  53. MattJ

    or we solve the original problem some other way, if possible

  54. ralphm

    I agree. Can't the Editor team resolve that on their own?

  55. Guus

    I'd not be in favor of removing people against their will, at least not unless the matter is more pressing to jonas’ than what I assume is the case.

  56. pep.

    well editor team is in fact mostly Jonas. Even I as the latest added member is not as active

  57. Guus

    If this is a problem to be fixed, rather than an optimization (as how I currently perceive it) I'd be happy to circle back to this.

  58. pep.

    am*

  59. Guus

    let's wait for jonas’ feedback

  60. ralphm

    Guus: agreed

  61. pep.

    k

  62. ralphm

    I did notice that stpeter is still mentioned as Executive Director on the Members list. That should be adjusted.

  63. ralphm

    Anything else on this?

  64. Guus

    not from me

  65. ralphm

    3. 2020 Sponsors

  66. Seve

    Periods of activity in our case are difficult to manage, I'm with you guys on this

  67. ralphm

    Regarding my commitments on this, as you probably have noticed, I have been busy with work the last two weeks, so I am taking this on for coming meeting.

  68. Guus

    what's the commitment regarding sponsors exactly?

  69. Guus

    reach out / renew?

  70. ralphm

    Guus: yes, the two items in trello

  71. Guus

    that just says 'sponsors 2020' 🙂

  72. Guus

    that just says '2020 sponsors' 🙂

  73. Guus

    oh, sorry

  74. ralphm

    No that's in the "Items for Discussions" column

  75. Guus

    yeah, just noticed it. apologies

  76. ralphm

    I don't think we have anything to discuss right now

  77. ralphm

    (on this)

  78. nyco-2

    ralphm the newsletter is not yet closed, should I add something about it?

  79. ralphm

    When is the deadline?

  80. nyco-2

    tomrrow?

  81. ralphm

    Hmm. I'll see what I can come up with.

  82. nyco-2

    thx

  83. ralphm

    Good idea.

  84. Guus

    +1

  85. ralphm

    4. Board voting process and discussions

  86. ralphm

    pep. raised this on the Members list. I wasn't sure if it should be discussed now.

  87. pep.

    there hasn't been much discussion around it (!)

  88. pep.

    Dave answered on the list, I don't especially agree with all. I meant to reply

  89. ralphm

    My questions are: 1) was there a trigger for this, 2) have you found this to be a problem in practice?

  90. pep.

    the trigger to me is that board is rarely managing to get all 5 in their meetings. I've been following board for as long as I'm involved in the community.

  91. pep.

    as for it being a problem, I don't want to get to that, that's why

  92. ralphm

    Ok. Then I have a response.

  93. pep.

    I wonder what made board use 2 and not 3 like council

  94. ralphm

    First on practice on this topic: as long as I have been on Board, I don't remember us taking any decision that was contested because of the way we handle quorum and majority on decisions.

  95. pep.

    so?

  96. ralphm

    Instead, we've generally either postponed meetings to get enough people (i.e. at least 3, but preferably more).

  97. pep.

    well then let's make it a rule, what's the hold up

  98. ralphm

    So I don't think there's actually a problem in need of solving. I do like the suggestion of voting on list in case of a missed meeting.

  99. ralphm

    But I also have a second point.

  100. Guus

    (while we wait for Ralph's second point): Having a vote potentially pass with just 2 votes seems undesirable to me, as that might (not sure, things can be overturned by the rest of board later) open the door for abuse. Dave's suggested fix ("try to make sure it doesn't happen") is hardly an improvement, in terms of hard rules. That does not rule out this being abused somewhere in the future. Some kind of more formal fix would be better, but I do think it would be good for us to prioritize matters that are currently more pressing than this one, to be honest. I feel that lately, we've been burning a lot of fuel, but not made much progress.

  101. Guus

    (is there a time limit on making a second point? 😉 )

  102. ralphm

    I've noticed I have become increasingly frustrated with having to discuss theoretical issues, like perceived gaps in our procedures, by-laws, etc. In my opinion, no organisation's rules and procedures are perfect, or could be, and the bylaws and other procedures like XEP-0001 are there as a framework to work within. We don't have to lock down everything to the letter. It takes (precious volunteer) time, that I'd like to use for persuing the goals of the XSF. Instead, these discussions are a big turn off for me, and make it less likely that I reserve additional time to do this.

  103. Guus

    I can relate to that.

  104. Seve

    I will send my thoughts over email as time is up, although I will take the advantage I completely understand ralphm's second point

  105. Seve

    I will send my thoughts over email as time is up, although I will take the advantage to say I completely understand ralphm's second point

  106. ralphm

    I am, of course, happy to clarify ways of working, explaining our current rules or historical stuff, but I more often also sense a desire for change as part of the clarification question, and this frustrates me.

  107. MattJ

    I was typing a response, but your last message covers it

  108. pep.

    these gaps might be perceived for a reason. and I'm happy to close them, but it won't be happy if you oppose it

  109. pep.

    these gaps might be perceived for a reason. and I'm happy to close them, but it won't be easy if you oppose it

  110. MattJ

    I think clarification and docs on many things that happen in the XSF are not clear, so I appreciate efforts to try to clean this up (and it definitely is the kind of thing Board is for)

  111. pep.

    lots of things that needs clarifying

  112. pep.

    There are too many assumptions that the XSF live with and it's extremely hard to understand all that

  113. pep.

    There are too many assumptions that the XSF lives with and it's extremely hard to understand all that

  114. MattJ

    But obviously you can go too far down that road and just chase organizational stuff for the sake of it

  115. ralphm

    pep., I am asking for this reason every time it happens, not just with you. And invariably, it feels like it is all theoretical combing through the prose that make up our bylaws and other procedures, not as a real problem in need of fixing.

  116. Kev

    For what it's worth, despite probably being one of the greybeards at this point, I do feel we have institutional knowledge that isn't recorded and should be. We can go too far in chasing perfection, but I think there are probably various bits of low-hanging fruit that will help us as more people come into the community.

  117. Kev

    (Which might be slightly distinct from wanting to change bylaws and things)

  118. ralphm

    Kev: I am for this, as I tried to convey above. The problem I have is my perceived urge to change things for the sake of it, not merely clarification.

  119. ralphm

    And, also, I suppose, I feel that we don't have to go to extraordinary lengths in making those procedures fool proof. All of our precedures have escape hatches in case a real conflict should arise.

  120. pep.

    so what now

  121. ralphm

    pep., well, I was hoping you could reflect on my point of view

  122. pep.

    didn't I?

  123. ralphm

    Can you see where I am coming from?

  124. nyco-2

    debate overload, I have to go, please finish: https://mensuel.framapad.org/p/9f92-2020-02-27-xsfboardweekly thx! 🙂

  125. ralphm

    Thanks nyco-2

  126. pep.

    fwiw I am annoyed that the excuse of volunteering is reused over and over. if you don't have time for it (and it's not a full time job, far from it) then don't apply, plus there were other candidates. I understand we have different priorities. And I think I'll leave it at that.

  127. ralphm

    I _do_ believe I have plenty of time to do things for the XSF. I just don't want to spend it on, in my opinion, theoretical discussions with little value.

  128. Guus

    That might be a matter of priorities of tasks in context of the XSF, I think. We all seem to have different priorities.

  129. ralphm

    I'd must rather use it for starting a documentation project (something that was discussed at FOSDEM), or whatever.

  130. ralphm

    much

  131. Guus

    That might be a matter of personal priorities of tasks in context of the XSF, I think. We all seem to have different priorities.

  132. Guus

    I think that as board, we should work on tasks that we think are of highest priority. What we appear to be missing is consensus of what is.

  133. ralphm

    pep., my task as Director and Chair is that the XSF can persue its goals, and particularly the business parts of running a coorporation. I will express my frustration about busy-work that doesn't match that task.

  134. Guus

    I suspect that some of us might even have very different priority lists.

  135. pep.

    because I'm also not trying to help the XSF with its goals obviously

  136. pep.

    anyway, this is not getting anywhere

  137. pep.

    shall we close

  138. ralphm

    pep., I didn't say you are not. I really appreciate various things you have done and do. My frustration is *definitely* not with just you, either. I thought it important to express my frustration instead of throwing tables and hopefully finding a solution.

  139. ralphm

    But sure, we can close the meeting.

  140. ralphm

    And maybe revisit next week if needed.

  141. ralphm

    5. AOB

  142. Seve

    None here

  143. MattJ

    None here

  144. pep.

    I'm probably not here next week at this time, I'd appreciate if we can delay this topic a other week

  145. Guus

    none

  146. ralphm

    pep., noted

  147. pep.

    I'm probably not here next week at this time, I'd appreciate if we can delay this topic another week

  148. ralphm

    6. Date of Next

  149. ralphm

    +1W

  150. ralphm

    7. Close

  151. ralphm

    Thanks all!

  152. ralphm bangs gavel

  153. pep.

    thanks

  154. jonas’

    .

  155. pep.

    ,

  156. jonas’

    thanks MattJ for pinging people. there is no reason to drop people who intend to contribute.