XSF Editor Team - 2014-02-25

  1. winfried

    editor meeting in 5 minutes, right?

  2. m&m


  3. winfried

    I will give a shout in the xsf muc... ;-)

  4. m&m

    graze (-:

  5. Lloyd

    yep, although my invite says its in council@muc.xmpp.org.

  6. Dave Cridland lurks

  7. winfried was wondering what that sound was...

  8. m&m goes to cobble together today's agenda from the emails

  9. Steffen Larsen

    Hi Guys!

  10. winfried


  11. Lloyd


  12. Steffen Larsen

    almost everybody here?

  13. Lloyd

    Ash should be along in a moment, his daughter is a little unwell at the moment

  14. m&m


  15. Steffen Larsen

    oohh I know the problem

  16. Steffen Larsen

    all of the family sick at the moment

  17. winfried

    Yeah, on holiday with sick kids right now...

  18. Dave Cridland

    My kids aren't sick.

  19. Steffen Larsen

    congrats Dave!

  20. Steffen Larsen


  21. winfried

    Dave Cridland should leave the muc right now...

  22. winfried

    Shouldn's Joachim be here?

  23. stpeter

    heh, another advantage of text chat

  24. winfried


  25. m&m

    ok, that looks like everyone

  26. Lloyd realises he can take his headset off

  27. Steffen Larsen


  28. Dave Cridland

    Lloyd, Leave it on, everyone will leave you alone.

  29. Ash

    Hi All.

  30. m&m


  31. m&m

    ok, let's get started

  32. m&m

    some of us are time-constrained

  33. Dave Cridland puts his on to get the kids to be quiet.

  34. m&m

    1) "What I Do" by Peter Saint-Andre

  35. winfried

    has everybody read the xep-readme?

  36. m&m

    did all of the editors read http://xmpp.org/extensions/xep-README.html ?

  37. Steffen Larsen

    yes. I have

  38. stpeter

    first of all, I'd like to thank you all for volunteering to help!

  39. winfried

    I have

  40. Ash


  41. Steffen Larsen

    svn is a bit outdated maybe

  42. Steffen Larsen


  43. Steffen Larsen

    otherwise fine

  44. stpeter


  45. m&m

    ok, some updates are necessary

  46. stpeter


  47. winfried

    peter: do you have any additions to the readme?

  48. winfried

    things we need to know right now?

  49. Steffen Larsen

    I assume that the XEP for svn is in git? ;-)

  50. stpeter

    the "Counting Council Votes" is outdated

  51. winfried

    the council posts the votes to the standards list, right?

  52. stpeter

    I'll fix up some details in the README this week

  53. stpeter

    the radar page is no longer used

  54. Steffen Larsen


  55. stpeter


  56. stpeter

    but the basics are correct

  57. Steffen Larsen

    stpeter:how often do the editor do work? I mean, maybe we should meet 2 a month or so to distribute work

  58. winfried

    stpeter: obvious changes to the readme can be made us too...

  59. Steffen Larsen

    yes for sure

  60. stpeter

    Steffen Larsen: in general there might be editorial tasks before or after each Council meeting

  61. stpeter

    e.g., publishing incoming proto-XEPs

  62. Steffen Larsen

    stpeter: ok

  63. stpeter

    issuing Last Calls, counting votes, etc. after meetings

  64. stpeter

    that kind of thing

  65. Steffen Larsen

    stupid question: how often are there council meetings?

  66. stpeter

    once a week

  67. stpeter


  68. winfried

    I have made a list of 'events' we should respond to, it is quite easy:

  69. Ash

    We could do with some kind of ticket/issue tracker system so people can pick up stuff that needs to be done rather then work having to be divvied out

  70. Dave Cridland

    Steffen Larsen, Once per week 1600 Wed.

  71. Steffen Larsen

    :-) ok

  72. stpeter

    sometimes there's no meeting

  73. stpeter

    Ash: sure

  74. Steffen Larsen


  75. Steffen Larsen

    we had jira once

  76. stpeter

    Ash: we used Jira in the past but I'm open to anything else you guys like

  77. winfried

    we should respond to: incoming xeps in editor@..

  78. Steffen Larsen

    but it was never actively used

  79. stpeter

    winfried: yes

  80. winfried

    to: council decisions

  81. Steffen Larsen

    besides me and some others

  82. stpeter

    editor@ is currently just an alias that sends stuff to me

  83. winfried

    and we should monitor experimental xeps not being updated for 12 month

  84. m&m

    I'd rather re-use infrastructure that's available

  85. stpeter

    winfried: correct

  86. Steffen Larsen

    I like a ticket system.. especially when there is more than one person

  87. stpeter

    Steffen Larsen: WFM

  88. m&m

    rather than spin up something new

  89. Steffen Larsen

    m&m: +1

  90. Ash

    Would be great if emails to editor@ could be fed straight into the ticketing too

  91. Dave Cridland

    As an alternative, a rota would probably work fine.

  92. stpeter

    Ash: sure thing

  93. stpeter


  94. Dave Cridland

    That is, have one duty editor per week.

  95. stpeter


  96. winfried

    or should we make editor@ a mailinglist?

  97. stpeter

    winfried: possible, yes

  98. winfried

    can we coordinate to ourselves too ;-)

  99. Steffen Larsen

    hmm no I think a muc and jira is perfect

  100. m&m

    I think making editor@ a mailing list is reasonable

  101. Steffen Larsen

    emails are not a ticket system. :-)

  102. m&m

    essentially write-only

  103. stpeter

    well, editor@ does receive inbound messages from authors, so making it a mailing list would enable everyone to know what's incoming

  104. winfried

    Is there already a ticketing system at the xsf?

  105. m&m

    as long as the traffic on editor@ is relatively low (which I assume it is), I think we can live with the manual conversion to a ticket

  106. Steffen Larsen

    I only know of jira

  107. stpeter

    winfried: we sort-of have Jira

  108. Ash

    \me has been working on deploying a ticketing system for the past few months so has ticketing on the brain!

  109. m&m


  110. stpeter

    m&m: yes, I think that would be fine

  111. Ash

    Jira is great as it's hosted and free and even better if it's already set up

  112. Steffen Larsen

    how many are we (editors)?

  113. Steffen Larsen


  114. Lloyd

    8 with joachim?

  115. stpeter

    Steffen Larsen: 6 or 7, I think

  116. m&m

    6 not including stpeter

  117. Steffen Larsen


  118. m&m

    7 if we include stpeter

  119. Lloyd

    - Dave, course :)

  120. Steffen Larsen

    stpeter: we might use you as a shadow in the start.. to ask questions etc.

  121. Steffen Larsen


  122. Dave Cridland

    Right, there's 8 people here, but Kev, stpeter and I aren't actually editors.

  123. stpeter

    Steffen Larsen: yes, of course!

  124. Dave Cridland

    However you're missing Joachim.

  125. m&m

    hrm … we're missing someone

  126. Steffen Larsen

    stpeter: we dont wanna mess things up.. just want to help

  127. m&m

    was Joachim on the list?

  128. Steffen Larsen

    to sec

  129. m&m

    I pulled it from Board and Council logs

  130. winfried

    Joachim raised his hand in Brussels, but was not on the list approved by the board

  131. Steffen Larsen

    hhmm maybe I should write and ask him

  132. winfried

    (And he raised his hand again on the members list)

  133. m&m

    the other name on the list was Stefan Strigler

  134. winfried

    Ah, indeed, Stefan

  135. Steffen Larsen

    yes. stefan should be here

  136. Steffen Larsen

    I'll write him now

  137. stpeter

    regarding access, IMHO each member of the editor team should have git privileges and an account on athena to run the scripts (or, you guys can figure out some subset of people)

  138. m&m

    Steffen Larsen: thanks. He should have been part of the email chain

  139. Dave Cridland

    Right, yes. Not Joachim, but Steffan.

  140. m&m

    I think granting everyone is fine

  141. winfried

    Just pinged Steve

  142. Steffen Larsen

    me too!

  143. Steffen Larsen


  144. winfried


  145. Steffen Larsen

    prob. in erlang world..

  146. Steffen Larsen

    he is coming in now

  147. winfried

    concurrent processes ;-)

  148. Steffen Larsen

    ha ha

  149. Steffen Larsen


  150. Dave Cridland

    winfried, Really slow message passing, though.

  151. m&m


  152. Steffen Larsen


  153. Steffen Larsen

    Hi Steve!

  154. zeank@jwchat.org

    hey, hi! :)

  155. Steffen Larsen


  156. winfried


  157. stpeter

    so what action items do we have?

  158. zeank@jwchat.org

    sorry, sorry, sorry

  159. m&m

    from what I've gathered so far ...

  160. winfried

    transfering editor@.. to a mailinglist

  161. m&m

    #1: setup a ticketing system

  162. Steffen Larsen

    #git access

  163. m&m

    #2: transfer editor@ to a mailing list

  164. Ash

    # update xep-README

  165. zeank@jwchat.org

    couldn't we just use github to handle most of it?

  166. m&m


  167. Lloyd

    zeank: Yes!

  168. Lloyd

    I agree

  169. m&m

    github is not canonical

  170. stpeter

    BTW we'll need list admins for editor@ to approve legitimate incoming messages

  171. stpeter

    (and we plan to deploy greylisting on atlas soon to avoid an overload of spam)

  172. winfried

    ok, editor gets 99,5% spam?

  173. stpeter


  174. Steffen Larsen


  175. winfried


  176. m&m

    such is life

  177. stpeter

    I have it redirect to my gmail.com address so all the spam magically goes away

  178. Dave Cridland

    Technically, ProtoXEP submissions MUST have a specific subject line.

  179. stpeter

    but greylisting should help

  180. stpeter

    Dave Cridland: true

  181. stpeter

    I'll let the list admins work out methods :-)

  182. winfried


  183. Dave Cridland is re-reading XEP-0001 and referenced docs.

  184. Steffen Larsen

    thanks peter :-)

  185. winfried

    On access:

  186. winfried

    to do the job we need shell access to ...

  187. m&m


  188. winfried

    where is also a git repository that is used to publish... (right?)

  189. Steffen Larsen

    I think I have access alraedy

  190. m&m

    a couple of us might already have shell access (or had it in the past)

  191. Steffen Larsen


  192. Steffen Larsen

    form way back.. doing some jingle stuff in 2007/8

  193. m&m

    I had shell access at one point, but I think those ssh keys were lost

  194. winfried

    I have no shell access...

  195. Steffen Larsen

    prob. me neither

  196. winfried

    who can coordinate that?

  197. Steffen Larsen

    how will do this? tobi?

  198. stpeter

    tobi, kev, and I have shell access to that machine

  199. m&m

    anyone from the i-team should be able to do it, no?

  200. stpeter

    and others, likely

  201. m&m

    I can harass —erm — follow up with one of those three

  202. stpeter

    editor@ list set up

  203. m&m


  204. winfried

    thanks, hit me with the spam :-P

  205. Ash


  206. m&m

    I'm already moderator for other lists, what's one more? (-:

  207. stpeter

    anyone else want to be a moderator?

  208. m&m

    I assume for shell access that the box admins will need SSH keys

  209. winfried

    shall we send pgp-signed ssh-keys to the editor list?

  210. Steffen Larsen

    ok. who is gathering the list and doing action on our bullit points?

  211. stpeter

    m&m yes please

  212. Dave Cridland

    stpeter, Stating the obvious, it's open to non-subscriber posts, right?

  213. stpeter

    winfried: sure

  214. Steffen Larsen


  215. stpeter

    Dave Cridland: it will be once I configure it correctly

  216. Dave Cridland

    stpeter, Just seemed like something worth double-checking. :-)

  217. stpeter


  218. stpeter

    T-2 minutes, right?

  219. m&m pesters Tobias about shell access

  220. stpeter

    anything else?

  221. m&m


  222. winfried

    - how to keep git tidy

  223. winfried

    - how to divide labour :-)

  224. m&m

    we should setup another meeting to finish up inauguration

  225. Steffen Larsen

    so are we using branch strategy or just pure master?

  226. Steffen Larsen

    or git flow?

  227. zeank@jwchat.org


  228. winfried

    ugh what?

  229. m&m

    see, we have more to do than just divvy out work (-:

  230. stpeter

    which email address is right for Lloyd?

  231. zeank@jwchat.org

    git flow for this sounds a bit like overhead ;)

  232. stpeter


  233. Lloyd

    stpeter lloyd@evilprofessor.co.uk please

  234. Steffen Larsen

    nah.. well it depends on the scenario

  235. stpeter

    ok I've added a bunch of you to the editor@ list

  236. winfried


  237. m&m

    stpeter: thanks

  238. zeank@jwchat.org

    uhm, added myself already ;)

  239. stpeter

    7 members, I must be missing someone

  240. m&m

    now, could the editor team be made admins for this room, please (-:

  241. m&m

    7 sounds right

  242. stpeter

    heh yes

  243. Steffen Larsen

    yes please

  244. Steffen Larsen


  245. m&m

    ok, I need to get going … how about we have a follow up meeting

  246. Steffen Larsen

    will we recevie an email about the editor list?

  247. zeank@jwchat.org

    can't you post the list of email addresses subscribed?

  248. m&m

    I cannot meet next week

  249. Steffen Larsen

    next week I am on ski

  250. Steffen Larsen

    so maybe next week again?

  251. Steffen Larsen

    some of you guys will prob. meet in london, right?

  252. m&m

    WFM, unless we have a quorum in London

  253. m&m


  254. m&m


  255. psa

    hmm, how do I change affiliations in Adium?

  256. winfried

    m&m anything that stops us from getting started?

  257. psa

    winfried: I don't think so

  258. m&m

    winfried: shell access

  259. winfried

    just keep each other informed..

  260. winfried


  261. winfried


  262. Steffen Larsen

    yes please keep me in the loop

  263. Ash

    We can always continue the discussion on the mailing list

  264. Dave Cridland

    winfried, Well, git and shell.

  265. Steffen Larsen

    when I am on vacation next week

  266. Ash

    In slower time

  267. m&m is pestering tobias about shell/git access now

  268. winfried

    git: we decided on branching strategy not?

  269. zeank@jwchat.org

    winfried: did we? which one? where? when?

  270. Dave Cridland

    I'd suggest pure master unless there's a reason to go branching.

  271. zeank@jwchat.org


  272. stpeter


  273. winfried

    well: I counted your 'ugh' as a vote for branching...

  274. winfried


  275. m&m


  276. winfried


  277. m&m

    master + email-based MINE-ing

  278. Steffen Larsen

    ash: creepy with the email!

  279. stpeter

    and the first spam message arrives!

  280. stpeter

    that didn't take long

  281. Steffen Larsen

    master is fine if work is that little

  282. Ash

    Hehe. Yeah. Great minds, eh!

  283. Steffen Larsen

    Ash: :-)

  284. stpeter

    BTW, this room is archived, as is the editor@ list

  285. Steffen Larsen

    stpeter: super!

  286. winfried


  287. zeank@jwchat.org

    for everything else there is git rebase ;)

  288. m&m

    Steffen Larsen: there's not usually much to do with the XEPs themselves

  289. zeank@jwchat.org

    uhm no I mean git push -f :D

  290. m&m


  291. m&m

    so, let's plan to meet back here in exactly two weeks

  292. Dave Cridland

    BTW, thanks to all of you for volunteering.

  293. stpeter

    m&m WGM

  294. stpeter

    WFM even

  295. Steffen Larsen

    two weeks! great!

  296. zeank@jwchat.org


  297. m&m


  298. Steffen Larsen

    11. March?

  299. Steffen Larsen


  300. stpeter

    we can create a calendar for the editor team, too

  301. m&m

    yes (-:

  302. Steffen Larsen

    17:00 CET?

  303. Tobias

    Kev, what do people need to access xsf git? isn't that handled by gitosis or so?

  304. Dave Cridland

    m&m, 2014-03-11T16:00Z then

  305. winfried

    OK, will take some planning for me.. but probably I can make it...

  306. m&m

    oh, duh

  307. Dave Cridland

    Tobias, Yeah, gitosis IIRC.

  308. m&m

    yes 2014-03-11T16:00:00Z

  309. stpeter

    I need to step out for a few minutes, bbiab

  310. Steffen Larsen

    in my calendar

  311. Steffen Larsen

    are we done or more on the agenda?

  312. stpeter

    also I think a third list admin would be helpful to cut down on the admin duties (at least until we get greylisting deployed)

  313. stpeter


  314. m&m

    for now, I think we're done

  315. m&m

    I'll try to gather minutes on this meeting, but we have the logs

  316. Steffen Larsen

    m&m: perfect!

  317. m&m

    and I'll send it through editor@xmpp.org for now, fwd to standards@xmpp.org

  318. zeank@jwchat.org

    stpeter: you can add me as well

  319. m&m

    I take it y'all are ok with me assuming the Chair role, yes? (-:

  320. m&m

    if someone else wants it, speak up!

  321. Ash

    Fine by me :)

  322. Steffen Larsen


  323. Steffen Larsen

    I am just a simple working man. :-)

  324. stpeter

    zeank@jwchat.org: thanks

  325. winfried

    its ok, but are you fine with it, m&m?

  326. m&m

    winfried: I'm fine with it … for now (-:

  327. m&m

    I think it'll work out just fine

  328. Steffen Larsen

    steve: thanks for the email :)

  329. stpeter

    zeank: do you have a preferred email address for such things?

  330. winfried

    Everybody got the test mail on the editor list?

  331. Lloyd


  332. m&m

    I got it

  333. Steffen Larsen

    ok guys. I am out of here. Have to cook some food for the family!

  334. stpeter

    winfried: I think I left Stefan off the list, let me check

  335. Ash


  336. Steffen Larsen

    got it!

  337. stpeter

    nope, n/m

  338. zeank@jwchat.org

    stpeter: zeank@jwchat.org is fine

  339. zeank@jwchat.org

    or can it be the same I registered with?

  340. zeank@jwchat.org

    then please use stefan.strigler@gmail.com

  341. stpeter


  342. stpeter

    used @gmail

  343. stpeter

    anyway, bbiaf

  344. zeank@jwchat.org


  345. Ash


  346. stpeter wanders off

  347. winfried smells nice food and hears diner sounds

  348. zeank@jwchat.org

    winfried: enjoy ;)

  349. Kev

    " I have it redirect to my gmail.com address so all the spam magically goes away stpeter @ 16:21"

  350. Kev

    Yes, that's what gets atlas blacklisted :)

  351. zeank@jwchat.org

    done with work for today as well, so bye bye ;)

  352. winfried


  353. Ash Going to go and help with dinner and my cuddle my poorly little girl!

  354. m&m

    thanks everyone

  355. m&m

    I'll track down the git/ssh access minutea

  356. Kev

    "Kev, what do people need to access xsf git? isn't that handled by gitosis or so? Tobias @ 16:38" Send me their keys.

  357. Ash


  358. m&m

    sorry, missed it!

  359. Kev

    m&m: This is just for access to the Git repo?

  360. Dave Cridland

    Kev, Shell as well.

  361. Kev

    Shell to do what?

  362. Dave Cridland

    Kev, Run the scripts in-situ, I think.

  363. Kev

    Which scripts, as which user?

  364. Dave Cridland

    Kev, This is beyond the ken of mortal folk.

  365. Dave Cridland

    Kev, I'd suggest asking stpeter but he is, sadly, in an XSF Editor meeting it seems.

  366. m&m

    it's to run the various XEP scripts as the "xsf" user

  367. m&m

    however, if you're not comfortable with the whole editorial team, this team will need to know what subset is acceptable

  368. Dave Cridland

    I think in practical terms, it really needs to be the whole team.

  369. m&m

    I agree

  370. Kev

    The whole team being able to regenerate XEPs seems fine.

  371. Kev

    I'm just not keen on handing out root to accomplish it - thus needing to know what's involved.

  372. m&m


  373. m&m

    stpeter can provide more info, but the XEP-README should have the major points

  374. stpeter

    we don't use root to run the editor scripts

  375. stpeter

    wouldn't we just need to add folks to the 'xsf' group?

  376. Kev

    No, I gathered that. But normal shell accounts presumably won't do :)

  377. Kev

    I don't know.

  378. Kev

    That's why I asked what they need :)

  379. stpeter

    that's my impression, anyway

  380. stpeter

    currently I run all those scripts as 'xsf'

  381. Kev

    Could I start with giving m&m access as a member of the xsf group, then, and waiting for the reports of "I can't do X" to come in?

  382. Dave Cridland

    If there are scripts that are safe to run (as in, they're idempotent or whatever), then could we devise a dry-run test?

  383. Kev

    I think 'safe to run' and 'idempotent' are very different things.

  384. Kev

    rm -rf / is idempotent.

  385. Kev

    (Well, loosely. It's technically not operating on itself, so it's not really idempotence)

  386. stpeter

    Kev: I think have a smaller group of script-runners seems fine to me

  387. Dave Cridland

    Yes, I've fallen foul of the "using an impressive sounding word but in the wrong way" fallacy.

  388. Tobias

    stpeter, right...basically it's changing to xsf home dir, switch to xmpp-hg, run "hg pull -u" and then ./calgen.py or extensions/gen.py -a

  389. stpeter

    Tobias: yep

  390. stpeter reviews the XEP-README

  391. Kev

    Tobias: "switch to xmpp-hg'?

  392. Tobias

    Kev /home/xsf/xmpp-hg folder

  393. Kev


  394. Kev

    Nowhere in there did you change user :)

  395. Tobias

    well..i was already the xsf user

  396. Tobias


  397. Tobias

    maybe a setuid bit or so, but that might be too much

  398. stpeter

    Kev: what's your feeling about making the editor README a XEP?

  399. Kev

    I think there's no need and no harm.

  400. stpeter

    sounds about right

  401. m&m


  402. Kev

    Well. Limited harm.

  403. Kev

    It's extra work without any clear(to me) benefit.

  404. Kev

    What's the motivation for doing so?

  405. stpeter

    no motivation here

  406. m&m

    I don't have any

  407. m&m rejects some posts to editor@xmpp.org

  408. winfried

    I don't see any reason to publish internal procedures...

  409. stpeter

    m&m: we can do those in bulk sometime

  410. stpeter nods to winfried

  411. m&m

    I was testing my password, seemed like a worthy test case (-:

  412. stpeter

    setting up greylisting seems like a higher priority now

  413. m&m


  414. Kev

    Next question is: how do I use gpg to verify m&m's key? :)

  415. Tobias

    gpg, the pinnacle of usability

  416. Kev

    m&m: Key ID?

  417. stpeter

    BTW, when the editor team processes files, we might want to not use personal initials, or use a convention like editor+psa

  418. stpeter

    e.g., when publishing initial versions

  419. stpeter

    that seems reasonable

  420. stpeter

    it's similar to what the RFC Editor does

  421. Kev

    XEP Editor(PSA), I'd have thought, would do?

  422. Kev

    Which is slightly less cryptic - but hills, etc.

  423. stpeter


  424. stpeter

    or somesuch

  425. stpeter

    I don't particularly care, as long as we're consistent :-)

  426. m&m

    back now

  427. m&m

    my gpg key should be in the public keyring by now

  428. m&m

    otherwise you'll have a wonderful opportunity to verify it a week from today (-:

  429. m&m

    if tracking the specific editor is necessary, then editor(initials) seems fine, but I don't see a problem with just using "editor"

  430. Kev

    It seems like information it's potentially useful to have, and not harmful to have, so I don't see why not to.

  431. stpeter

    http://xmpp.org/extensions/xep-README.html updated

  432. m&m


  433. Kev

    sighup:~/tmp/mmkey/> gpg --verify id_rsa.pub.sig id_rsa.pub.txt 5:43pm gpg: Signature made Tue Feb 25 17:00:42 2014 GMT using RSA key ID 109E05BB gpg: BAD signature from "Matthew A. Miller <linuxwolf@outer-planes.net>"

  434. Kev


  435. m&m


  436. Kev

    I think there's an argument about whether a key only signed by you is trusted, too :D

  437. stpeter sets the editor@ mailman config to set only a daily digest of messages in the admin queue

  438. Kev

    Editors - Does Council need to do BOSH things?

  439. Kev

    If so, what please? :)

  440. stpeter


  441. stpeter catches up on council minutes and such

  442. Neustradamus

    I have missed some discussions... but there are not logs since some months: http://logs.jabber.org/new/ Can you help me?

  443. stpeter

    Neustradamus: that doesn't have anything to do with the XEP Editor Team

  444. Neustradamus

    There is not discussion here?

  445. stpeter redirects the conversation to the appropriate chatroom

  446. Neustradamus

    before "<m&m> /nod"?

  447. Kev

    If you want the logs for this room, note that it's not on jabber.org, and look at http://logs.xmpp.org

  448. stpeter

    Neustradamus: this room is for discussion about the XEP Editor Team, not jabber.org logging issues

  449. stpeter

    right, see http://logs.xmpp.org/editor/ for logs of this room

  450. m&m


  451. Neustradamus

    ho yes, sorry!

  452. m&m

    git clone failed for me: mamille2$ git clone git@athena.jabber.org:xmpp.git Cloning into 'xmpp'... ssh: connect to host athena.jabber.org port 22: Connection refused fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

  453. Kev

    m&m: Right. I've not set it up for you because I'm hoping I have some way of verifying your key first :)

  454. stpeter

    it's not on port 22 either

  455. Kev

    Send me your key over XMPP and I'll vaguely trust it :)

  456. Steffen Larsen

    hey stpeter. I just made a quick wiki: http://wiki.xmpp.org/web/Editor_team . Who was the last couple of persons?

  457. Neustradamus

    I mix jabber.org/xmpp.org logs but my request was originaly about to see previous conversations before line that I have noted before...

  458. Kev

    Neustradamus: So follow the link that we gave you.

  459. m&m


  460. Neustradamus

    Kev: :)

  461. stpeter

    m&m: 5284 is your friend

  462. Kev

    Host athena.jabber.org Port 5284

  463. m&m

    I'm following the instructions on http://xmpp.org/about-xmpp/xsf/xsf-source-control/

  464. Kev


  465. m&m


  466. Neustradamus

    little question: editor@... is a ML? because it is not listed on http://mail.jabber.org/mailman/listinfo

  467. stpeter

    Steffen Larsen: I think that list is complete

  468. Kev

    m&m: You should have access to the xmpp repository.

  469. stpeter

    Neustradamus: it's mostly an alias and not really a mailing list -- we have other lists that are not listed there

  470. m&m

    "Ashley" ==> Ashley Ward

  471. stpeter


  472. m&m

    otherwise that looks like the right list to me

  473. Kev

    Which we very probably want to split up to only contain XEPs and associated at some point.

  474. stpeter

    not sure whether editor@ ought to be archived

  475. Neustradamus

    stpeter: ok! For me, like you want...

  476. m&m


  477. Steffen Larsen

    does anyone know if joachim actually signed up for editor? I know he signed up for upnp laison..

  478. m&m

    hmm hmm hmmm … archiving editor@ … hmm hmm

  479. stpeter

    Steffen Larsen: I defer to others on that, although we do need to get the UPnP thing going :-)

  480. Steffen Larsen

    stpeter: yes

  481. m&m

    yeah, "not it" on UPnP

  482. Steffen Larsen

    m&m: updated the names on the wiki

  483. stpeter laughs at m&m's MINE :-)

  484. m&m smacks forehead

  485. m&m

    I could have updated that list myself! (-

  486. m&m

    stpeter: (-:<

  487. m&m

    I'm now waiting for Kev to apply the public key I sent him via IM

  488. Kev

    stpeter: He did not volunteer on the list, and wasn't on the list selected by Council and Board, I think?

  489. m&m

    he was not

  490. Kev

    m&m: Scroll up four minutes.

  491. m&m

    from my reading of the list(s)

  492. stpeter

    Kev: that's my understanding

  493. Kev

    I don't see a problem with adding him, I think it just needs Council to suggest it to Board.

  494. m&m

    Kev: I did send my key over XMPP

  495. Kev

    m&m: You should have access to the xmpp repository. Kev @ 21:07

  496. Kev

    It was done, immediately!

  497. m&m


  498. m&m

    I did not see that

  499. m&m

    I do not see that

  500. m&m

    (in the history)

  501. m&m

    anyway, thank you for applying my pubkey

  502. Kev


  503. Neustradamus

    I am volunteer like I have said previously on xsf room at Dave Cridland

  504. m&m studies http://xmpp.org/extensions/xep-README.html#advancing

  505. stpeter


  506. stpeter

    it's always good to test the runbook

  507. m&m


  508. Kev

    I think the README might be missing 'assign appropriate namespaces'?

  509. Steffen Larsen

    ok g'night folks.. off to bed. cheers

  510. m&m


  511. m&m

    oh, nevermind … I skipped a step (-:

  512. m&m commits and pushes changes …

  513. m&m

    XEP-0152 is now at step 6 of XEP-README

  514. m&m

    now I need someone with shell access to finish things off

  515. Kev

    Ah yes, you needed that as well.

  516. m&m


  517. Kev


  518. Kev


  519. m&m

    the latter would be nicer, otherwise mamille2 (which is my work uid)

  520. Kev

    Let me know when you're logged in.

  521. m&m


  522. Kev


  523. Kev

    I guess you don't need a password as you're not sudoing.

  524. Kev

    You thought just being in the xsf group would be enough, yes?

  525. m&m

    well, I haven't tried to run any of the scripts yet

  526. Neustradamus

    stpeter: somes links do not work on http://xmpp.org/extensions/xep-README.html maybe a little update?

  527. Kev

    Hmm. I wonder if xmpp or xsf was what was meant.

  528. Kev


  529. m&m

    logout and login as xsf@ ?

  530. Kev

    You are now in the xsf group if you log out and in again.

  531. Kev

    Which someone thought should be enough for you.

  532. m&m

    I guess we'll see

  533. m&m


  534. Kev

    Give me a moment, I'll do something else.

  535. m&m

    assuming "Update SVN on the webserver" means "Pull to editor's workspace from local git repository", I ran into a permissions problem

  536. m&m

    if that helps suss out the next layer of this onion

  537. Kev


  538. Kev

    Can you try sudo su - please?

  539. m&m

    prompted for password

  540. Kev

    sudo /bin/bash

  541. m&m

    sudo is prompting for a password

  542. Kev

    sudo -u xsf /usr/bin/vim

  543. Kev

    And if that doesn't work, lastly

  544. Kev

    sudo -u /bin/bash

  545. Kev

    Which is the only one that should work, if I've not screwed up the sudo config.

  546. m&m

    -u by itself?

  547. Kev


  548. m&m

    -u xsf

  549. Kev

    Type what I meant, not what I said :)

  550. m&m


  551. m&m

    still prompting for a password

  552. Kev


  553. Kev


  554. m&m

    linuxwolf xsf

  555. Kev


  556. Kev

    Now log out/in and try again.

  557. m&m

    will do

  558. m&m

    but why don't I just passwd?

  559. m&m

    that worked

  560. Kev

    The config is that you can only run one command, which is /bin/bash as xsf.

  561. Kev

    I could add needing a password onto that as well. I guess that wouldn't be stupid.

  562. m&m

    I think that would be a good idea

  563. m&m

    oh, but I'll need my current password, because I'm not root (duh)

  564. Kev

    You now have your current password.

  565. Kev

    Please change it.

  566. m&m

    password updated

  567. Kev

    Good. You need your password to sudo now.

  568. m&m

    and I'm prompted for a password on sudo

  569. m&m

    ls -lhA

  570. m&m


  571. m&m

    I must be an idiot, because I can't get past my permissions problem cloning the git repo

  572. stpeter

    sorry, I was on a video call, what did I miss in those 60 messages? ;-)

  573. m&m

    I am stuck on step 6 of "Advancing a XEP"

  574. stpeter


  575. stpeter

    well, you must have a password of some kind on athena, no?

  576. m&m

    I do

  577. m&m

    I'm logged in now

  578. stpeter

    oh ok

  579. m&m

    its a basic permissions problem

  580. stpeter


  581. stpeter

    on which part?

  582. m&m

    with the local git repo

  583. stpeter

    I munged lots of steps into one

  584. stpeter


  585. m&m

    readable only by the user "git"

  586. stpeter

    local = on athena?

  587. m&m

    or anyone in the "git" group

  588. m&m


  589. m&m

    assuming that "Update SVN on the webserver" means "Pull latest into git working directory"

  590. stpeter

    oh I thought I removed all references to SVN

  591. stpeter

    ah, not quite, I see

  592. stpeter

    did you reload the README?

  593. m&m


  594. m&m

    I had a cached copy

  595. m&m

    I had reloaded, but I didn't aggressively reload (-:

  596. m&m


  597. m&m

    I see I did mess up the <revision/> block then

  598. m&m

    used <initials>Editor(mm)</initials> instead of <initials>XEP Editor (mm)</initials>

  599. m&m

    that's trivial to fix

  600. stpeter

    I foresee the need to make further fixes on the README

  601. m&m


  602. stpeter


  603. stpeter

    anyway I see: git:x:1017: xsf:x:1018:git

  604. stpeter

    which is strange

  605. stpeter

    in /etc/groups

  606. m&m


  607. m&m


  608. stpeter

    /etc/group that is

  609. m&m

    just tried to run archive.sh, and got: cp: cannot stat `/var/www/vhosts/xmpp.org/extensions/xep-.html': No such file or directory

  610. m&m

    I don't know how innocuous that is

  611. stpeter


  612. stpeter


  613. stpeter

    usage for those scripts is in the script

  614. stpeter

    my bad

  615. m&m


  616. stpeter

    we're finding errors in the documentation

  617. stpeter

    so it's './archive.sh 0152' or whatever

  618. m&m

    ah, ok

  619. stpeter

    and lastcall.py takes a date

  620. stpeter

    and so on

  621. stpeter

    bad docs, bad scripts

  622. m&m


  623. stpeter

    I'm sure the editor team can do better

  624. m&m

    so that worked

  625. m&m


  626. m&m

    "maybe" as in "maybe we could do better"

  627. m&m

    so, "List Administration"

  628. m&m

    this states I need to login to list-admin for standards@xmpp.org

  629. stpeter


  630. stpeter

    the announcement email will go there

  631. stpeter

    from running ./announce.py 0152

  632. m&m


  633. stpeter

    but email from editor@ is modded

  634. stpeter

    since otherwise we'd have lots more spam on the list

  635. m&m


  636. m&m

    it makes sense

  637. stpeter

    I think we could fix some of that in the postfix config

  638. stpeter

    discard all editor@ from addresses other than those originating locally

  639. m&m


  640. m&m


  641. m&m

    I either need the admin password for standards, or you need to clear out the queue

  642. m&m

    'cause we're ready to announce!

  643. m&m

    (or the postfix config is jiggered)

  644. stpeter

    just cleared the queue

  645. m&m

    ok, calling announce now

  646. m&m

    check the queue, should be a message pending from editor@xmpp.org