XSF logo XSF Discussion - 2010-04-29


  1. bear has left
  2. MiGri has joined
  3. koski has joined
  4. luca tagliaferri has joined
  5. luca tagliaferri has left
  6. luca tagliaferri has joined
  7. MiGri has left
  8. MiGri has joined
  9. petermount has joined
  10. petermount has left
  11. petermount has joined
  12. petermount has left
  13. petermount has joined
  14. jprieur has joined
  15. jprieur has left
  16. jprieur has joined
  17. jprieur has left
  18. jprieur has joined
  19. jprieur has left
  20. Neustradamus has joined
  21. Kev has left
  22. Kev has joined
  23. jprieur has joined
  24. jprieur has left
  25. jprieur has joined
  26. jprieur has left
  27. jprieur has joined
  28. jprieur has left
  29. jprieur has joined
  30. jprieur has left
  31. Kev has joined
  32. jprieur has joined
  33. jprieur has left
  34. Kev has joined
  35. Neustradamus has joined
  36. Neustradamus has left
  37. Neustradamus has joined
  38. jprieur has joined
  39. jprieur has left
  40. Kev has left
  41. Kev has joined
  42. bear has joined
  43. stpeter has joined
  44. luca tagliaferri has left
  45. koski has left
  46. petermount has left
  47. koski has joined
  48. koski dudes, what's the current url to the JIRA ?
  49. koski All the ones i found/bookmarked do not work anymore.
  50. Kev Jira's not running at the moment.
  51. Kev Bear's going to upgrade and bring it back when he's got a moment.
  52. koski ok
  53. koski Thanks.
  54. Neustradamus hi all, can you update mediawiki ?
  55. stpeter heh, I just noticed this in the council logs: [14:02:24] <bear> wow - the more I do with GSoC the more I see that needs to be done. I have no idea how you managed to do this solo in the past! [14:02:30] *bear hugs stpeter thanks, bear!
  56. Florian has joined
  57. zooldk@gmail.com has joined
  58. zooldk@gmail.com the tech review meeting is in 5 min, right?
  59. stpeter yes
  60. stpeter at least, so says my calendar
  61. zooldk@gmail.com good... phew.. thought I was late..
  62. Tobias has joined
  63. stpeter :)
  64. stpeter heats up some lunch
  65. koski beer o'clock here so i have time to get a pint
  66. zooldk@gmail.com me too.. mmmm good stout! :-)
  67. waqas has joined
  68. koski It's time?
  69. zooldk@gmail.com +1
  70. Florian +1
  71. koski +1
  72. Neustradamus I am here but I am not in tech review team
  73. stpeter ok so who is in charge?
  74. zooldk@gmail.com shouldn't it be Fabio Forno, the team lead?.. but I assume he is not here?
  75. koski Fabio should but He does not seem to be here.
  76. stpeter I put koski in charge for today :)
  77. zooldk@gmail.com +1
  78. zooldk@gmail.com :-)
  79. zooldk@gmail.com BTW: Jira is still down?.. still because of the security flaw?
  80. stpeter he said: Now, what should we discuss during the meeting? Should we prepare a list to make it successful? Here are my thoughts: * How to use the created tool Jira better? * How could we help stPeter more? (it seems to me that people still wait actions from stPeter). * Decide witch XEPs we could concentrate and how to follow those "projects" (what was done right with http://xmpp.org/extensions/xep-0045.html and what was done wrong).
  81. stpeter I think the Jira flaw applies only to Apache
  82. stpeter and we use lighttpd
  83. koski OK, let's start then.
  84. zooldk@gmail.com ok.. but it is still down
  85. stpeter bear said he would upgrade it
  86. koski [19:52:44] <Kev> Jira's not running at the moment. [19:52:52] <Kev> Bear's going to upgrade and bring it back when he's got a moment.
  87. zooldk@gmail.com unless someone changed the address
  88. zooldk@gmail.com ok
  89. koski Yes. It's still down. Anybody part of the technical team to who could give bear a hand in this? I think he might be busy with the gSOC
  90. zooldk@gmail.com its probably just a tomcat that needs to be turned around, together with lighthttpd
  91. koski OK, zooldk@gmail.com you are familiar with this stuff? Could you contact beer later on when you have time to ask if he needs a hand? (i'm afraid i'm useless in those admin stuff)
  92. stpeter koski: Kev and I will lean on bear and if he doesn't have time we'll find someone else to help
  93. zooldk@gmail.com yeah.. but I have no admin or insight in our infrastructure. But I know jira pretty well from work.. And we are using tomcat as a servlet container.
  94. koski stpeter: sounds like a plan!
  95. koski ok, next - When the Jira is back, how can we use it better?
  96. zooldk@gmail.com stpeter: great
  97. stpeter just poked the iteam list
  98. koski Step number one: start using it?
  99. zooldk@gmail.com how about sending out mails from jira when someone has filed an issue?..
  100. stpeter that already works
  101. zooldk@gmail.com to the correct group.. in our case the techreview, when an issue is filed there
  102. bear bah - I *knew* I was supposed to do something last night besides go to bed early
  103. stpeter hmm
  104. stpeter bear: heh
  105. koski bear: hah
  106. zooldk@gmail.com stpeter: does it also send out mail to techreview when new one are arriving?.. have not seen one yeat
  107. zooldk@gmail.com yet
  108. bear i'm in a bunch of remote meetings today - i'll multitask on it while I look like i'm listening
  109. stpeter bear: zooldk (Steffen Larsen) said he can help if needed
  110. zooldk@gmail.com stpeter: sure no problem..
  111. stpeter Tobias: your client is spamming me with tunes updates :P
  112. Tobias stpeter: yeah...you know a person who could take care of that? :) i've been hearing there's someone working on psi over the summer
  113. bear stpeter - I will for sure raise the "help!" flag if I cannot do it in the next 3 hours
  114. stpeter bear: ok thanks!
  115. zooldk@gmail.com bear: cool
  116. koski great.
  117. bear it would be nice to have backup anyways - gsoc may make me rather busy in a couple weeks
  118. stpeter nod
  119. Tobias stpeter: but hey, i can hardly be worse than identi.ca :)
  120. stpeter as to using Jira, it would be good to log more tickets, but I think the main problem we face is editing the specs / schemas / etc. based on the tickets
  121. stpeter i.e., finding people who are comfortable editing the documents
  122. koski stpeter: yes, i was just about to write the same thing.
  123. koski How ever the good thing with Jira is that the ticket is always assigned to someone, so we know who is "on it".
  124. zooldk@gmail.com jira probably fit the infrastructure guys better, than this..
  125. zooldk@gmail.com koski: jup..
  126. koski We should add posts like this to jira: http://mail.jabber.org/pipermail/standards/2010-April/023371.html
  127. Tobias stpeter: i think with a different versioning system we could make collaboration to the XEPs easier, collaboration of any kind
  128. stpeter Tobias: do you think it would really help to use git?
  129. zooldk@gmail.com or mercurial.. its nice to have local commits... But I do not think that it will help that much
  130. koski Tobias, good point taken. Could you please write a mail about that to mailing list to start discussion about that?
  131. Tobias stpeter: it makes collaboration easier; ideally the changes just need to be reviewed shortly and can go online :)
  132. koski We are hardly not reaching decicion about that in this meeting. what do you think?
  133. Tobias koski: it's already in the works :)
  134. koski ok :) great
  135. stpeter fixing up Experimental specs is easy, but we have more process for fixing up Draft & Final specs
  136. stpeter because the Council needs to approve things
  137. Tobias just ask Kev hard enough until he does it :) it's on his todo
  138. bear hmm, I need sudo privs on athena to do some of this
  139. stpeter bear: please hold
  140. zooldk@gmail.com how about making different states then in jira, for a workflow?.. for moving the spec along in exp. , to draft, to final etc.
  141. stpeter or ask Kev, isn't he team lead for Infrastructure? ;-)
  142. koski stpeter: heh, i was thinking the same.
  143. stpeter I think that most of the bug reports we get are for Draft and Final specs
  144. bear yea, my plea was more pointed to him than the active folks
  145. stpeter ideally, using Jira would enable us to move more quickly, or at least keep better track of things
  146. zooldk@gmail.com stpeter: I agree
  147. stpeter but that's ideally :)
  148. bear oh wait - duh - /me reads his own README
  149. stpeter heh
  150. bear ok, jira up
  151. stpeter woot!
  152. bear i'll start working on the upgrades after you guys clear the back log
  153. koski Ok, so should we make a "rule of thumb" that every time a mailing thread leads to some short of "consensus" we create a jira ticket out of it?
  154. koski Mazel Tov!
  155. bear stpeter: do you have the login info for my.atlassian.com for the xsf?
  156. bear I will need to generate a new key for 4.* jira
  157. stpeter bear: I think that data is in /root/ on athena or somesuch
  158. stpeter looks
  159. stpeter bear, it's at /home/atlassian
  160. bear ?? /me looks
  161. bear wow - am I the master of not seeing the obvious today
  162. bear thanks
  163. stpeter :)
  164. stpeter koski: I think it might work the other way -- people submit tickets, we have list discussion or groupchat or whatever, then update the ticket with the consensus (text, schema fix, etc.)
  165. koski stpeter: good point.
  166. stpeter e.g., the other someone poked me about a feature that is missing from XEP-0249
  167. koski (i just tried to create a ticket. I cannot modify it and it got directly assigned to stpeter.
  168. stpeter i.e., XEP-0249 doesn't support <continue/> (as XEP-0045 does)
  169. stpeter koski: http://tracker.xmpp.org/browse/SPEC-11 ?
  170. koski Yep.
  171. koski stpeter: sorry, i did not mean to assign it to you. :)
  172. zooldk@gmail.com hey its up and running
  173. stpeter koski: it seems that all spec issues are automatically assigned to me
  174. koski You want to change this? :)
  175. koski Should we took couple of guys who would be the default assignee's and those guys would take care that the created tickets are discussed in the mailing list, chatroom, etc?
  176. zooldk@gmail.com could be a good idea..
  177. koski And not turned out to be "zombies".
  178. zooldk@gmail.com to take the load off
  179. stpeter koski: I just made you a project administrator for the SPEC project
  180. stpeter so I think we need to assign roles to more people
  181. stpeter e.g., everyone on the tech review team should be a developer on the SPEC issues project
  182. koski ok, cool. I was just about to write that i have an half an hour per week to give time to take a look at the tickets and give a push to them.
  183. zooldk@gmail.com stpeter: really good idea
  184. stpeter that means you can edit issues, etc.
  185. koski stpeter: good point.
  186. stpeter I don't know how to change the default assignee
  187. stpeter zooldk@gmail.com: are you registered at the tracker site?
  188. koski stpeter: should i be able to edit the ticket?
  189. stpeter koski: I thinjk so
  190. zooldk@gmail.com stpeter: I am on the jira site
  191. koski it seems that i only got "Delete" option more.
  192. zooldk@gmail.com http://confluence.atlassian.com/display/JIRA/Managing+Project+Role+Membership
  193. koski Do you guys think it would make sense to have that "assign this ticket to me" option enabled? At least i don't have it.
  194. zooldk@gmail.com stpeter: I just have to remember the user/pass.. just got a new laptop! :-)
  195. koski I think that's the one of the best part in jira: it's always clear who is or at least should be "working on it"
  196. stpeter koski: I think so
  197. stpeter but I'm not sure how to do that
  198. koski stpeter: i'm no jira admin either. sorry.
  199. stpeter maybe bear knows :)
  200. koski stpeter: was hoping the same.
  201. zooldk@gmail.com koski: what are you looking for?
  202. koski We could change the "Component/s:" field to XEP . What do you guys think?
  203. stpeter ?
  204. zooldk@gmail.com +1
  205. koski zooldk@gmail.com: that I could assign a ticket to me or modify it.
  206. stpeter not sure what the Components field is
  207. koski stpeter: when creating a ticket, it asks for a "component".
  208. koski http://athena.jabber.org:18081/browse/SPEC-11
  209. koski if you check that, now the "component/s" "versions" and "fix versions" are empty.
  210. koski or "None".
  211. zooldk@gmail.com we are using component for defining the piece of area/part of software we are working on..
  212. koski The component at least does not serve a purpose for us, right?
  213. zooldk@gmail.com so for us it could be: core, xep etc.
  214. stpeter also might be schemas, registries, perhaps some others
  215. zooldk@gmail.com or we could define each XEP as a component.. its then easier to filter in jira
  216. zooldk@gmail.com stpeter: yes
  217. zooldk@gmail.com depends of the level of detail
  218. koski OK. Maybe we leave that to the future and see first how we start to use the Jira. What do you think guys?
  219. zooldk@gmail.com yes.. because now we only have a few issue
  220. koski To start working with Jira, i think we need help from Bear or other admins to help us to set the rights correclty. So that others can modify/close and work with the tickets than stpeter. stpeter do you agree?
  221. zooldk@gmail.com issues
  222. koski stpeter: i have understood you are busy busy busy lately with the IETF. Right?
  223. stpeter koski: yes, we need to distribute the permissions so that more people can do things
  224. stpeter koski: I always have a little time, but not very much right now
  225. stpeter however, I want to help the tech review team succeed because otherwise people will depend on me to do things, and if I don't do them our work will stall
  226. zooldk@gmail.com stpeter: plus one on that one..
  227. zooldk@gmail.com stpeter: you need help of course..
  228. koski stpeter: noted. That's why i'm ready to help you. But i know that the first steps to start moving stuff to someone else's responsibility usually takes a bit more time.
  229. stpeter although sometimes I think it would be good to take a rest for a few years so that developers could catch up with all the specs ;-)
  230. koski stpeter: :-D
  231. zooldk@gmail.com me hungry... need food
  232. waqas notes that some of the specs are lagging behind ^^
  233. stpeter koski: you should have admin privs for the SPEC project now, so hopefully you can make some people Developers
  234. stpeter waqas: I can make you a Developer too :P
  235. stpeter waqas: which ones?
  236. koski stpeter: let me check what i can break after this MUC Meeting
  237. stpeter koski: ok
  238. waqas stpeter: I have been gathering feedback on a number of specs. MUC included.
  239. stpeter waqas: ok good
  240. stpeter waqas: I have lots of edits on MUC but I haven't entered them yet :(
  241. stpeter maybe I should scan them in :P
  242. zooldk@gmail.com i have some stuff about muji (multi-user jingle).. who is up for discussing that at some time?
  243. stpeter zooldk@gmail.com: yeah that needs a lot of work
  244. zooldk@gmail.com stpeter: yup.. alot.
  245. stpeter I poked the Collabora guys about that in January or so, but no progress yet
  246. stpeter if I had the time I'd be tempted just to start editing the spec :P
  247. zooldk@gmail.com stpeter: but we do not have to wait for them..
  248. zooldk@gmail.com BTW: anyone know which GSOC project that was accepted?
  249. stpeter bear knows :)
  250. bear it's at the bottom of this page: http://socghop.appspot.com/gsoc/org/home/google/gsoc2010/xsf
  251. zooldk@gmail.com ha ha.. shh.. don't disturb him :-)
  252. bear :)
  253. koski What do you guys say that if i write to the review-team mailing list descriptions about how the components could be named: XEP, Core, etc... Then we could assign Leaders to all these "components". The leader of the component would take care that there is any ticket that becomes a zombie.
  254. zooldk@gmail.com bear: thanks.. interesting
  255. stpeter koski: I think most of the tickets will be about XEPs, and a few will be about schemas or registries
  256. zooldk@gmail.com koski: yes.. my ideas as well.. Maybe we can use some of the stuff we already have as interests on the wiki: http://wiki.xmpp.org/web/Review_team .. like: jingle, core, s2s, scalability, pubsub, etc.
  257. stpeter nod
  258. koski zooldk@gmail.com: good idea.
  259. stpeter that might be more useful
  260. stpeter so someone to watch over Jingle stuff, someone else for BOSH, and so on
  261. zooldk@gmail.com stpeter: si! :-)
  262. stpeter see also http://xmpp.org/tech/
  263. koski ok, great. zooldk@gmail.com could you write about this to the mailing list? You seem to have good idea about that.
  264. zooldk@gmail.com koski... ok. I'll do that later today then.
  265. koski i could too ofcourse, but it's stupid for me to write badly a good idea to the mailing list :)
  266. koski I'm not lazy! :)
  267. zooldk@gmail.com koski: no prob.
  268. zooldk@gmail.com koski: can I do these components in jira as well?.. or will you?
  269. koski zooldk@gmail.com: let's do couple based on the mail as a example for people and then let's finish them when we agree on the mailing list?
  270. stpeter I think we would have MUC, Jingle, PubSub, BOSH, s2s, core, i18n, security, and perhaps a few others
  271. zooldk@gmail.com I am still looking for my user/pass.... and waiting for an email
  272. stpeter zooldk@gmail.com: :)
  273. zooldk@gmail.com koski: ok
  274. stpeter we also need to make sure that all tech review team members have Jira accounts, then we can set them up with the right permissions
  275. zooldk@gmail.com stpeter: yes
  276. stpeter is that enough for today?
  277. stpeter I'm happy to stay here and keep chatting, of course :)
  278. koski stpeter: yes, i think we did 2/3 "points".
  279. stpeter I think we need a new "group" in Jira
  280. zooldk@gmail.com stpeter: BTW is there some way that we could alter our svn folders?.. because I have made some xsd validation script, but it is hard to map the schemas (xmpp/trunk/schemas) when they are named muc.xsd instead of xep-0045.xsd.
  281. stpeter existing groups are iteam and commteam
  282. koski i think we have some ideas how to make the Jira usage better. Good. stpeter, do you think this will help you a bit at least in the future?
  283. zooldk@gmail.com koski: so we agree that I should write to the tech team about the new jira components?
  284. luca tagliaferri has joined
  285. koski zooldk@gmail.com: +1
  286. zooldk@gmail.com koski: okie
  287. stpeter ok
  288. stpeter I created a techreview group
  289. stpeter now I'll add some people to it
  290. koski zooldk@gmail.com: i can help you to set them up. Just contact me when you have time to start for that.
  291. koski stpeter: great
  292. zooldk@gmail.com koski: I need a login firstly
  293. zooldk@gmail.com :-)
  294. stpeter I don't know what it means to be part of a group, but we'll find out :)
  295. zooldk@gmail.com koski: yeah.. I'll think I IM you later.. and then we'll find out what to do
  296. Kev stpeter: you can assign groups to ACLs instead of people.
  297. stpeter right
  298. stpeter just figured that out
  299. stpeter so now anyone in the techreview group is automatically a SPEC developer
  300. zooldk@gmail.com wuhuuu
  301. mckinley49039 has joined
  302. waqas_ has joined
  303. stpeter do we want to make issues "Unassigned" by default so that I don't need to re-assign them?
  304. Kev Seems sane.
  305. koski =1
  306. zooldk@gmail.com stpeter: good idea
  307. koski +1
  308. stpeter done
  309. stpeter so we've made a bit of progress here
  310. zooldk@gmail.com ha ha
  311. stpeter Jira is back, tech review people can edit SPEC issues, etc.
  312. zooldk@gmail.com (thumbs up!)
  313. stpeter now we need all tech review team members to register with Jira
  314. koski stpeter: a proposal. Do you think you would have time in coming months to write a example how you would see the "spec review" working and we could talk about that in mailing list and in the next meeting? (the review you started with the MUC XEP). I think you had a very good idea there. It was just a shame it did not really catch up fire and support from others.
  315. stpeter and we can assign them all to the techreview group
  316. koski stpeter: i can write about that in mailing list and kick the sleepy ones.
  317. stpeter koski: part of the problem was that XEP-0045 is too big -- it would have been better to start with a smaller spec
  318. stpeter koski: ok thanks!
  319. stpeter koski: but yet I can do that
  320. stpeter brb
  321. koski stpeter: yes, this is also why i'm kindly asking you to write it since you know the best what "succeed and what not and why". Sorry but you are still the best in this :D
  322. waqas_ Will we discuss XEP-0045 in this meeting?
  323. zooldk@gmail.com sorry guys.. I need some food now. If you are not finished in the next 10 min. then talk to you a bit later..
  324. koski waqas_: it was not planned to discuss about the XEP itself. But we can of course.
  325. waqas_ Is there a meeting planned for it?
  326. koski waqas_: as far as I know, no.
  327. stpeter koski: the members of the techreview group in Jira are now you, me, Kev, Waqas, Peter Mount, Safa, Steffen (zool), Fabio, Ali, and Luca -- so we need Fritzy, Joe Maissel, and Alex Malgaroli to register at Jira and tell us their usernames so that we can add them to the techreview group
  328. koski stpeter: sir, yes sir!
  329. koski stpeter: I'll handle that
  330. stpeter koski: you and Fabio are admins for the SPEC project but I don't think you can edit the techreview group
  331. stpeter not sure
  332. stpeter is just learning Jira
  333. koski let me check
  334. stpeter waqas_: we can schedule a meeting or two or three about MUC
  335. stpeter but I think we've made some progress today and we can consider this meeting to be ended (we've been talking for almost 1.5 hours) :)
  336. koski stpeter: you were right. I cannot modify the group
  337. koski stpeter: yes. I was just about to write the same.
  338. zooldk@gmail.com stpeter: I've ordered my password for JIRA but haven't received an email yet? do the postfix run on the server or?
  339. stpeter koski: ok
  340. stpeter koski: well, have only three more people to add, that's easy enough for me to do
  341. stpeter zooldk@gmail.com: I can reset your password and then you can change it
  342. zooldk@gmail.com stpeter: please... :-)
  343. zooldk@gmail.com just stranged that I havent received any by email yet
  344. zooldk@gmail.com strange
  345. stpeter yeah
  346. stpeter not sure why
  347. stpeter I do receive emails from Jira
  348. stpeter so it is set up correctly to send email
  349. stpeter zooldk@gmail.com: see PM for password
  350. stpeter BTW the logs for this meeting are at http://xmpp.org:5290/muc_log/muc.xmpp.org/xsf/100429/
  351. koski stpeter: i'll write to the list about the group and ask the missing ones to sign in and notify you?
  352. zooldk@gmail.com the email seems correct :-)
  353. stpeter koski: they can reply to the list mail with their usernames
  354. zooldk@gmail.com and i'll write about the JIRA components..
  355. koski stpeter: ok
  356. zooldk@gmail.com is it ok if I do it tomorrow?
  357. stpeter sure
  358. koski zooldk@gmail.com: sure, of course. we are not in a hurry in this.
  359. zooldk@gmail.com ok.. hopefully I'll have the password then.. ;-)
  360. stpeter zooldk@gmail.com: I sent you the password via private message
  361. zooldk@gmail.com stpeter: me don't see.....
  362. koski do we write any meeting minutes about that or just notify the mail thread of "call for a meeting" with the muc_log link? :)
  363. stpeter oh
  364. stpeter koski: an informal report is fine, no official minutes needed I suppose
  365. stpeter zooldk@gmail.com: Gmail issues
  366. koski stpeter: agree
  367. zooldk@gmail.com ha ha.. ok
  368. koski stpeter: zooldk@gmail.com: yes, was fighting with those whole day today at work. there is something "weird" happening in google.
  369. koski at google even...
  370. zooldk@gmail.com ok.. I've had no problems with gmail.com lately..
  371. stpeter who receives email for SPEC issues?
  372. zooldk@gmail.com maybe I should start using my @jabber.org account instead for these meetings
  373. koski stpeter: who will receive or who is receiving?
  374. zooldk@gmail.com stpeter: shouldn't it be all of the tech review group?
  375. stpeter who is receiving now?
  376. stpeter zooldk@gmail.com: I think so
  377. stpeter I just created SPEC-13
  378. zooldk@gmail.com Then we are notified..
  379. zooldk@gmail.com could be nice..
  380. stpeter zooldk@gmail.com: yes that's the way it should be
  381. koski i did not receive. Yet at least.
  382. zooldk@gmail.com me neither
  383. zooldk@gmail.com thats what I said earlier
  384. stpeter I received it
  385. zooldk@gmail.com hmmm
  386. koski i only received for the ones i created. Or assigned myself as one.
  387. zooldk@gmail.com gmail issues? ;-)
  388. koski i got notifications of SPEC-11 and 12 that i created.
  389. zooldk@gmail.com when it is only a few issues that we have at the moment, every one in the tech review group should receive it
  390. stpeter aha
  391. stpeter I found the config option for this
  392. koski so the "creator" and the assignee receives the messages, but not others. i think
  393. koski stpeter: good :)
  394. zooldk@gmail.com change please. :-)
  395. bear google was down completely for some about an hour ago
  396. zooldk@gmail.com bear: wow really?? I did not notice a thing
  397. koski bear: in france there were problems during the whole day.
  398. Florian I guess someone lost their job :)
  399. koski with google that is.
  400. bear it seems to be regional - at least according to my twitter/identica social graph
  401. zooldk@gmail.com stpeter: wheei my JIRA login worked. thanks
  402. zooldk@gmail.com no probs in Denmark
  403. zooldk@gmail.com for google that is
  404. stpeter oh
  405. stpeter hmmmmm
  406. zooldk@gmail.com what is the default priority of the issues?
  407. zooldk@gmail.com and who can change them
  408. stpeter I might have just messed up the config
  409. waqas has joined
  410. luca tagliaferri has left
  411. stpeter fixes
  412. zooldk@gmail.com it could also nice to have affects and fix version on the XEPs...
  413. zooldk@gmail.com that relates to the versions of the XEP specs
  414. zooldk@gmail.com so people can track when the implementation has changed in the spec
  415. stpeter zooldk@gmail.com: I think that any Developer should be able to change priority etc.
  416. stpeter and all members of the techreview group are Developers for the SPEC project
  417. zooldk@gmail.com stpeter: ok
  418. stpeter if it doesn't work that way, we can fix it in the config
  419. stpeter is discovering that Jira is infinitely configurable
  420. zooldk@gmail.com I know!
  421. zooldk@gmail.com been there
  422. waqas_ has left
  423. zooldk@gmail.com Guys.. I've out of where.. I'll game a bit before my girlfried gets home. :-)
  424. zooldk@gmail.com koski: talk to you later about the components.. right?
  425. luca tagliaferri has joined
  426. koski zooldk@gmail.com: deal. i might be very busy tomorrow so during the weekend or beginning of the next week, don't hesitate to kick me.
  427. zooldk@gmail.com koski: ok, deal.. later
  428. zooldk@gmail.com cheers all of you!
  429. bear jira can be excellent in implementing the death-by-1000-cuts mode for admins
  430. stpeter ok I modified the default notification scheme so that project developers receive notiications
  431. stpeter zooldk@gmail.com: thanks!
  432. stpeter bear: yea
  433. zooldk@gmail.com has left
  434. petermount has joined
  435. stpeter hi petermount
  436. petermount i know i'm late but this is the first chance i've got to get online tonight :-(
  437. petermount hi peter
  438. luca tagliaferri has left
  439. stpeter petermount: no worries, we're all doing the best we can :)
  440. petermount blames the local train company :-(
  441. petermount so what have I missed? :-)
  442. stpeter we made some progress on Jira for issue tracking
  443. petermount thats always good
  444. stpeter bear got Jira running again, I created a new Jira group for all techreview members, and you'll be receiving more Jira emails soon because I updated the notification scheme
  445. stpeter Tuomas and Steffen will be sending email to the techreview@xmpp.org list regarding some further action items
  446. petermount have you patched for the security issue from last week?
  447. stpeter petermount: I think bear did -- but in any case the security issue was (AFAIK) related to Apache and we run lighttpd
  448. luca tagliaferri has joined
  449. luca tagliaferri has left
  450. petermount iirc it was in jira itself rather than outside - at least when I saw it when kenai did the update (which host my jira instances)
  451. stpeter petermount: I think bear took care of this but he'll know for sure
  452. petermount will double check
  453. petermount np
  454. petermount did anything get said about pubsub?
  455. bear petermount - the security issue is "fixed" in so far as xsf's implementation isn't directly impacted but i'm also taking the time to upgrade to 4.*
  456. petermount bear: ok, at work we use jira and i notified them as soon as i heard from my provider - if we are up to date then no problem - at least we are up to date ;-)
  457. petermount thinks its better to be safe 99% of the time ;-)
  458. bear agreed - we use jira at my old work place so I used their support account to call in and review the raw details
  459. bear and found that it was a specific apache+jira interaction
  460. stpeter petermount: indeed
  461. luca tagliaferri has joined
  462. bear but yes, being 99.9% sure is what is driving the 4.* upgrade
  463. petermount ah crafty bear - at my work they left their a/c to expire :-S
  464. bear ick
  465. petermount yep ick
  466. bear I always build into the quote a full year of support
  467. bear so they can't let it lapse
  468. petermount we here sould surely get an o/s account shouldnt we? if not why dont we ask them?
  469. luca tagliaferri has left
  470. stpeter we have one
  471. petermount thats goos
  472. petermount good even :-S
  473. petermount what I wanted to find out was what we are planning on reviewing - recently it's been busy for a lot of us but for me it's going to get quieter
  474. stpeter I'm hoping we can finish the MUC review :)
  475. petermount and i've been holding back on pubsub because I remembered we were planning on pubsub after muc
  476. stpeter yeah
  477. stpeter well
  478. stpeter first we need to push out version 1.13 of XEP-0060 :)
  479. stpeter we'll have a never-ending pubsub review :P
  480. luca tagliaferri has joined
  481. petermount peter: yes I think muc needs finishing - at least both of us have been held back for varioes reasons - you more than me ;-\)
  482. petermount yep
  483. stpeter petermount: clearly I need to set aside a bit of time each week to key in the changes I've already marked on my paper copy of XEP-0045
  484. petermount peter: the main reason i'm interested in pubsub in the next month or so is that I need to implement from scratch - which to me is an ideal time to do a review - I can hold it back currently but to me its ideal as it means we have a reference-point from start to finish
  485. stpeter nods
  486. petermount stpeter: I need to catch up
  487. stpeter and I am also reviewing draft-ietf-xmpp-3920bis these days because we have an August deadline to send that to the IESG for advancement
  488. petermount i've been the emails - it's a long weekend here in the uk so I should get a chance to catch up on that
  489. stpeter see http://www.ietf.org/mail-archive/web/xmpp/current/msg00705.html for details
  490. koski MUC, PubSub and draft-ietf-xmpp-3920bis ... Why did you start from the shortest and the most simplest ones?
  491. petermount muc the simplest?
  492. petermount ;-)
  493. stpeter and I have another 800 pages of Internet-Drafts to review and comment on by next Thursday for my IESG responsibilities
  494. koski petermount: it was ment to be a "sarcastic joke" :)
  495. petermount grr not even home and about to restart part of work - one mo
  496. stpeter I also have a marked-up copy of XEP-0050
  497. koski stpeter: i'm sure you looked like a human last time i saw you. But you must be a machine...
  498. stpeter haha
  499. stpeter koski: thanks for the message to the list~!
  500. koski no worries, i hope i got the main points to get right people interested.
  501. stpeter yep
  502. stpeter I sent a corrected URL :)
  503. stpeter but other than that it looks good
  504. koski Thanks.
  505. petermount koski: recently it seems like i'm a machine :-|(
  506. bear has left
  507. petermount the last couple of months have been wiped out, hence why i've been quiet here - even had some public releases from the begining of march i'm only going to do finally this weekend :-( sob
  508. luca tagliaferri has left
  509. stpeter ouch
  510. stpeter yeah, everyone is so busy
  511. petermount and you thought you would be with the ietf?
  512. petermount being sarcastic there ;-)
  513. petermount the ITEF must be a real drain - but you havent eased off yet
  514. stpeter petermount: it's about an extra 30 hours a week
  515. bear has joined
  516. stpeter so now I work 70-80 hours a week
  517. stpeter shrugs
  518. petermount stpeter: not good :-(
  519. stpeter I'm a workaholic, so it's not that bad
  520. stpeter but I'm getting a bit old for this kind of thing ;-)
  521. petermount stpeter: same here ;-)
  522. bear pfft - your both probably younger than me
  523. petermount Occasionally I still the "Post midnight" programming session - but can't so that too often these days
  524. petermount bear: do you spend 6hrs a day commuting? & thats when it work ok :-(
  525. bear true - one of the reasons I love working from home
  526. petermount bear: not supposed to but I try to once a week ;-)
  527. luca tagliaferri has joined
  528. petermount o...k...
  529. petermount just read the email about what got said during the meeting
  530. petermount & unless my mail has got filtered most of it was helping taking work load (quite rightly) from peter?
  531. koski yes, and to find a ways to wake up the "team" and start working.
  532. koski everybody wanted jira, now let's use it :D
  533. luca tagliaferri has left
  534. petermount yes jira is now there, so lets use it.
  535. petermount but jira isnt the only tool there though
  536. petermount remembers the 'tool' threads from a couple of months ago :-S
  537. stpeter tools discussions never end....
  538. luca tagliaferri has joined
  539. koski yes.
  540. petermount they never doo ;-(
  541. koski but now i will end this discussion and will moge the dreamworld to catch some beautiful Fairies.
  542. koski moge .... move to even ...
  543. petermount koski: hehe
  544. koski have a good end of the day guys!
  545. koski Cheers! Bye!
  546. petermount i'm going to have to go offline - this netbook only has a limited livetime without power - and it's done good tonight
  547. petermount koski: catch you lateer
  548. stpeter thanks guys
  549. petermount stpeter: np, we'll probably catchup when we'll all aroun
  550. petermount i need to go offline shortly as my netbook's battery is now in the red - unless i get the mac out :-(
  551. koski night!
  552. koski has left
  553. petermount catch you all later
  554. petermount has left
  555. Neustradamus has left
  556. Florian has left
  557. Tobias has left
  558. Tobias has joined
  559. stpeter has left
  560. luca tagliaferri has left
  561. luca tagliaferri has joined
  562. luca tagliaferri has left
  563. luca tagliaferri has joined
  564. bear has left
  565. bear has joined
  566. bear has left
  567. bear has joined
  568. luca tagliaferri has left
  569. waqas has left
  570. bear has left