1. <Tavmjong> --------------------------- Inkscape Board Meeting --------------------------
  2. <tweenk> First thing we can talk about for the board meeting is Hackfest 2016
  3. <parclytaxel> OK, pertinent question #1: Inkscape's structure is all over the place, what are we to do?
  4. <parclytaxel> I mean, the modules and the functions and the others are all a mess.
  5. <ScislaC> tweenk: Is the goal to have it coincide with LGM again?
  6. <tweenk> parclytaxel: identify self contained portions of functionality and split them off to be compiled as separate shared libs, I think
  7. <parclytaxel> Bryce, that's a priority
  8. <tweenk> ScislaC: I guess so, this way there's no need to pay 2 separate flight fees if we want the devs to attend LGM as well
  9. <Tavmjong> parclytaxel: We can discuss that Inskcape structure under "New Business"
  10. <tweenk> so there were 4 proposals for the hackfest venue - London, Leeds, Warsaw, Phnom Penh
  11. <parclytaxel> Inkscape can be split into two: the computational part (2geom and the filter libs), the parsing part (that converts to and from SVG syntax) and the display part (that shows the results)
  12. <FailBit> parclytaxel: please hold
  13. <Mc-> LGM is London, right ?
  14. <FailBit> also that's 3
  15. <Tavmjong> Based on the Toronto LGM, I wouldn't put attending as a high priority... although it did lead to getting OpenTYpe into Inkscape.
  16. <Tavmjong> Yes, London.
  17. <tweenk> I guess we should focus on London and Leeds since Phnom Penh is very far from the LGM venue and I will no longer be in Warsaw by that time
  18. <Tavmjong> You'll be in California?
  19. <tweenk> Tavmjong: yes
  20. <Tavmjong> Great!
  21. <Tavmjong> I agree London and Leeds are preferred (although I would love to visit Phnom Pehn again).
  22. <parclytaxel> Phnom is a bad place, Tavm
  23. <parclytaxel> I'd prefer Amsterdam or something
  24. <bryce> hi
  25. <Tavmjong> I think Leeds is considerably cheaper.
  26. <parclytaxel> hi bryce
  27. <bryce> sorry, my wife just arrived and distracted me
  28. <parclytaxel> And it's 3am in Singapore
  29. <Tavmjong> http://libregraphicsmeeting.org/2016/
  30. <Tavmjong> LGM is April 15-18
  31. <ScislaC> tweenk: you going to be working on the Google campus?
  32. <parclytaxel> OK, so I believe Inkscape is too monolithic and needs some splitting
  33. <tweenk> ScislaC: yes
  34. <ScislaC> tweenk: when do you head out there?
  35. <bryce> so thanks all for coming to the Inkscape board meeting, and welcome to martin and kk
  36. <parclytaxel> Bryce, I have identified the three main components: computation, SVG interfacing and display.
  37. <tweenk> ScislaC: start date is 25th November
  38. <tweenk> ScislaC: (IIRC)
  39. <ScislaC> very cool
  40. <FailBit> parclytaxel: hold off on this until the topic is pertinent
  41. <bryce> like I suggested in the announcement, I figure we can keep the floor open agenda-wise, but keep in mind our focus here with this is more for non-technical matters
  42. <bryce> Tavmjong, you had some agenda items and already said a few words on LGM, why don't you dive into that a bit more
  43. <Tavmjong> I think we should ping Alex and see if he can host a hackfest before or after LGM.
  44. * ScislaC nods
  45. <tweenk> Tavmjong: I agree, hosting it in Leeds will be a lot cheaper.
  46. <tweenk> and London would be our backup plan then.
  47. <Tavmjong> So I can take an action to contact Alex.
  48. <bryce> Tavmjong, perfect thanks
  49. <parclytaxel> Tavm, next?
  50. <Tavmjong> We'll need to start thinking about fund raising.
  51. <bryce> Tavmjong, right
  52. <Tavmjong> It would be good to have a list of concrete things that resulted from the last hackfest.
  53. <bryce> if it helps, I recently posted some of the fundraising ideas we discussed last hackfest to wiki.
  54. <bryce> there's some good ideas there, might thumb through and see if any strike a fancy
  55. <Tavmjong> We started work on a bunch of things at the hackfest but I don't know how many got carried through.
  56. <parclytaxel> So what were the best ideas?
  57. <bryce> agreed re: list. You had written up a technical summary, maybe that'd give a starting point?
  58. <tweenk> Tavmjong: I did most of the 2Geom sync on the hackfest
  59. <Tavmjong> tweenk: good point. I got OpenType features working. How close are we on cmake?
  60. <parclytaxel> (There are chatters on #derpibooru)
  61. <tweenk> which was very long overdue since the API has changed in several important places
  62. <tweenk> one thing that as started but not finished was the GTK3 flickering fix
  63. <tweenk> *was
  64. <Tavmjong> The one big thing that I don't think has progressed is fixing are render to work with Gtk3.
  65. <tweenk> And now gtkmm 3.x requires C++11 so I guess we are blocked on that?
  66. <bryce> parclytaxel, really I don't think you could say any were "best" ideas. A good execution is the important part.
  67. <JonCruz> we probably need to update state of things. Keeping in mind that "C++11" is not a single thing, but a collection of differently implemented features
  68. <Tavmjong> I think gtkmm 2.x also requires C++11
  69. <bryce> Tavmjong, cmake went from broken to basic usability
  70. <bryce> still some odds and ends needed but it's real close
  71. <ScislaC> tweenk: glib 2.46 also requires C++11
  72. <JonCruz> *which* C++11 is key
  73. <Tavmjong> I don't think we need C++11 in Fedora 23 but definitely in Fedora 24.
  74. <Tavmjong> ... so we still have a little time.
  75. <ScislaC> bryce: I use cmake to build trunk at this point
  76. <tweenk> ScislaC: is that glib or glibmm? Isn't glib C-only?
  77. <JonCruz> e.g. we'd need to see which compiler versions can be dropped. gcc 4.6 is most problematic in its C++11
  78. <FailBit> glibmm is horrifying, honestly
  79. <tweenk> FailBit: but it's a dependency for gtkmm
  80. <FailBit> ("let's undefine G_DISABLE_DEPRECATED so we can use deprecated features and expect nothing to break!")
  81. <bryce> Tavmjong, getting back to LGM, last time most of the talks were only marginally pertinent to us, and the number of useful contacts we made seemed a bit limited to me. Do you think London will be a lot better on those measures? Or if not, would there be a different conference we should consider hooking the hackfest to?
  82. <FailBit> tweenk: gtkmm does the same horrid thing
  83. <ScislaC> tweenk: it was upstream glib that bumped the compiler requirements from what I recall
  84. <Tavmjong> If you know of a better conference, I would be open to that. What is the conference in Belgium every year?
  85. <parclytaxel> Solvay
  86. <bryce> well I was wondering if a more gnome-oriented conference might give us better connections
  87. <tweenk> FailBit: ah I remember that issue now...
  88. <Tavmjong> I'm thinking of FOSDEM. Anybody been?
  89. <bryce> no but heard great things
  90. <parclytaxel> I can't go to any confs, I'm a Singaporean
  91. <Tavmjong> It's in January so it would be tight to organize.
  92. <tweenk> Tavmjong: LGM was basically my only exposure to open source conferences
  93. * doctormon (d106bc82@gateway/web/cgi-irc/kiwiirc.com/ip.209.6.188.130) has joined #inkscape-devel
  94. <parclytaxel> And the confs held in Singapore are big business
  95. <doctormon> bryce: late!
  96. <Mc-> never been to any (yet)
  97. <Tavmjong> parclytaxel: Why not? The do have a big airport in Singapore.
  98. <bryce> doctormon, better than never!
  99. <Tavmjong> s/The/They/
  100. <doctormon> bryce: :-) what's the agenda?
  101. <parclytaxel> ???
  102. <bryce> doctormon, open agenda. Current topic LGM/Hackfest for 2016.
  103. <Mc-> doctormon: we're talking about LGM and the hackfest
  104. <parclytaxel> Singapore has the (2nd) highest GDP (PPP) per capita in the whole world
  105. <FailBit> it's also not a great place to live
  106. <parclytaxel> So lots of corporations come here, not lots of hippies
  107. <Tavmjong> bryce: I think LGM has shifted focus some and may have lost its way.
  108. <bryce> yeah :-/
  109. <parclytaxel> I'm a hacker in a sea of 5.5 million (mostly) non-hackers
  110. <doctormon> Tavmjong: What's the way and the mis-way?
  111. <tweenk> Tavmjong, bryce can you elaborate?
  112. <Tavmjong> I rather like Singapore... although it was wickedly hot and humid.
  113. <bryce> tweek, it used to be more focused on software development, now seems to be more focused to art and end user use cases
  114. <parclytaxel> And there's a haze right now. PSI peaked at 340 a few days ago.
  115. <bryce> which isn't *bad* just different, and maybe not as pertinent to our more immediate needs
  116. <ScislaC> tweenk: ahhh, I was misremembering, the glib requirement bump was related to OS X version (it just happened to coincide with glibmm's compiler requirement bump)
  117. <Tavmjong> doctormon: At the beginning, I think, LGM brought lots of developers together. Last year there didn't seem to be a very large developer presence.
  118. <Mc-> hearing what users expect from inkscape might be interesting
  119. <parclytaxel> Mc-: It is now PONY driven.
  120. <Mc-> (or just advertising inkscape to them)
  121. <Tavmjong> Sorry, I type too slow.
  122. <tweenk> bryce: so it's more an user oriented conference, is that right?
  123. <parclytaxel> By far the largest and most popular users of Inkscape are bronies.
  124. <bryce> tweenk, at least the 2015 one I'd say artist oriented
  125. <FailBit> parclytaxel: I disagree
  126. <ScislaC> It seems like it's shifting that way.
  127. <Mc-> cutters/plotters too :P
  128. <bryce> Inkscape got plenty of name drops, admittedly
  129. <parclytaxel> Liam is a brony, I am a brony and the power stroke is in fact the lroduct of many bronies asking for that feature to be ported from AI to Inkscape
  130. <JonCruz> parclytaxel: those were just a subset of users asking
  131. <FailBit> no it actually isn't
  132. <FailBit> power stroke was actually designed for calligraphy
  133. <bryce> Tavmjong, Jan feels a bit too soon to get plans in place for a hackfest though
  134. <JonCruz> cloths makers were another group
  135. <Tavmjong> bryce: I agree. So LGM may still be our best bet.
  136. <bryce> Tavmjong, what if we arranged to send a couple folks that are ~localish to scout it out this year, and then target it for 2017?
  137. <doctormon> parclytaxel: I'm a brony too
  138. <parclytaxel> Have it in Singapore, I want to see your faces.
  139. <JonCruz> does OSCON or OSBridge draw enough inkscapers?
  140. <parclytaxel> Everfree Northwest is a sure-fire, Jon
  141. <JonCruz> parclytaxel: LGM avoided the USA due to concerns about the government. Singapore might be similar for many
  142. <bryce> OSCON is way too expensive
  143. <bryce> don't know anything about OSBridge
  144. <JonCruz> bryce: mainly wondering about the people near
  145. <doctormon> We could always critical mass LGM and draw up a list of people from other FS projects; developers etc who we'd consider valuable enough to attend for?
  146. <JonCruz> SCALE is too inkscaper sparse
  147. <bryce> JonCruz, oh was just about to ask
  148. <ScislaC> JonCruz: I would disagree
  149. <JonCruz> ScislaC: two does not quite hit critical mass :-)
  150. <bryce> doctormon, that's a good idea... same could be done for any conference though
  151. <ScislaC> I think we should do a test for pr pushing that we'll have a booth there for January and see if we get a better turnout.
  152. <JonCruz> very true
  153. <JonCruz> at the least we can do a SCALE mini-Hackfest BoF
  154. <bryce> cool, so the ideas so far: PR push for SCALE, scouts to FOSDEM, hackfest at LGM.
  155. <tweenk> by SCALE you mean this? http://www.atscaleconference.com/
  156. <Tavmjong> The advantage of LGM is it gives us something to focus on... if only a couple of Inkscapers attend, so be it. The real focus for us would be in Leeds.
  157. <Tavmjong> The LGM timing is good.
  158. <ScislaC> JonCruz: we still have no clue how much it will affect general attendance with SCALE being in Pasadena
  159. <parclytaxel> Can I possibly teleconference?
  160. <JonCruz> https://www.socallinuxexpo.org/scale/14x
  161. <bryce> https://www.socallinuxexpo.org/scale/14x
  162. <Tavmjong> parclytaxel: I don't understand why you couldn't attend in person. We plan on supporting travel for Inkscape developers.
  163. <JonCruz> parclytaxel: something to look at for SCALE. In general their IT/Network team is tops.
  164. <doctormon> Tavmjong: Leeds is good for me, I can stay with my mum :-)
  165. <parclytaxel> First of all, I'm only 17
  166. <ScislaC> Went out to the convention center a couple months ago... we have SO MUCH more space.
  167. <parclytaxel> My parents are frugal
  168. <parclytaxel> And then in a year I'll be conscripted into the army
  169. <doctormon> parclytaxel: I wish you the best; must be a pita
  170. <bryce> ok so Tavmjong you will investigate London/Leeds/LGM/Hackfest a bit more and report back?
  171. <parclytaxel> I'm also studying organic chemistry
  172. <parclytaxel> bryce: LLLH. Nice.
  173. <Tavmjong> parclytaxel: At 17? Not bad.
  174. <bryce> JonCruz and ScislaC you can mind meld on ways we can improve Inkscaper turnout at SCALE?
  175. <Tavmjong> bryce: Yes. I'll investigate more.
  176. <JonCruz> can also teach tweenk about commuter flights from the bay area :-)
  177. <bryce> anyone want to look into fosdem?
  178. <Tavmjong> I can also checkout Fosdem.
  179. <ScislaC> bryce: Yep. I will also see about talking to SCALE's PR team to see if they can lend a hand.
  180. <bryce> Tavmjong, great
  181. <bryce> ok, some good action items there. Let's move on to a new discussion topic.
  182. <parclytaxel> Yes, Inkscape is spaghetti.
  183. <bryce> who's got another agenda item for us?
  184. <doctormon> I'll er, look around :-)
  185. <Tavmjong> We forgot to welcome new board members... so Welcome!!!
  186. <parclytaxel> And I mean when I was trying to fix some bugs, I had to crane my neck around modules.
  187. <ScislaC> Welcome!!!
  188. <bryce> ah right, welcome doctormon and tweenk !
  189. <parclytaxel> Er, me?
  190. <Tavmjong> How about GSOC 2016 next?
  191. <tweenk> :)
  192. <parclytaxel> Then again... the nextagenda topic
  193. <bryce> ok
  194. <tweenk> Tavmjong: yep
  195. <Tavmjong> ------------- GSoC 2016 -------------
  196. <Tavmjong> We kind of let ourselves down last year. We need a better recruiting web site according to Google, right ScislaC ?
  197. <ScislaC> That's part of it...
  198. <parclytaxel> The FSA?
  199. <doctormon> Website? I didn't get any details on that requirement :-(
  200. <parclytaxel> What is that about?
  201. <ScislaC> We need to have more specific information.
  202. <Tavmjong> I got the feeling that they expected better defined projects with mentor names attached.
  203. <ScislaC> Correct
  204. <bryce> yeah they had some specific requirements about project description and identified mentors per-project and such
  205. <bryce> they posted a pretty specific set of requirements, we just didn't get all the checkboxes crossed off in time
  206. <Tavmjong> First, do we agree we should do GSoC in 2016?
  207. <ScislaC> I think that instead of the existing bulleted list, I will see about reorganizing into tables.
  208. <parclytaxel> Don't, Tavm
  209. <parclytaxel> Don't be controlled by Google
  210. <tweenk> Tavmjong: so far it was a major driver of feature work
  211. <Tavmjong> I agree it's worth pursuing.
  212. <tweenk> parclytaxel: Google doesn't control what work gets done during GSoC, we and the students do
  213. <doctormon> It does get things done
  214. <parclytaxel> We should, instead, corral indie devs to come along
  215. <bryce> to me it depends a lot on if we have admins and mentors available to manage it
  216. <bryce> it's easy to overlook how much time commitment that end requires
  217. <doctormon> yeah
  218. <parclytaxel> Self-regulation.
  219. <Tavmjong> I am willing to spend some time on the website and help admin (as well as mentor).
  220. <Tavmjong> Anybody else?
  221. <ScislaC> I'm willing to Admin again
  222. <bryce> ScislaC, are you still able and willing to lead us?
  223. <ScislaC> yep
  224. <parclytaxel> I've always liked how systems arise naturally without supervision from small things.
  225. <tweenk> It's also important to prepare the stage, e.g. it's much easier for students to work on something that's reasonably well documented
  226. <Tavmjong> tweenk: I definitely agree!
  227. <JonCruz> ScislaC: and get me in as backup admin right away
  228. <doctormon> I'm pretty much the website man, we got a project app if that's of help
  229. <parclytaxel> So we may, for example with our own dev "apprenticeship", have two or three devs
  230. <tweenk> Tamvjong: I can mentor, but right now I have no idea how much free time I'll have
  231. <Tavmjong> OK, so ScislaC, JonCruz, and I can tackle getting us ready.
  232. <bryce> cool
  233. <tweenk> Tavmjong: so I would be able to make a commitment in ~January I think
  234. <parclytaxel> And when they get lovey-dovey we can introduce some more
  235. <bryce> we should also look into recruiting a larger pool of potential mentors
  236. <Tavmjong> tweenk: Remember to protect your 20% personal project time!
  237. <ScislaC> agreed
  238. <Tavmjong> bryce: Definitely agree.
  239. <bryce> we won't know how many slots we get, but we should make sure we have manpower to scale up if we get a lot of slots
  240. <parclytaxel> So are going to GSoC?
  241. <tweenk> Tavmjong: I will keep that in mind :)
  242. <Mc-> tweenk: you can mentor while being at google ? cool
  243. <tweenk> Mc-: hm, I need to double check
  244. <parclytaxel> *we
  245. <ScislaC> Tavmjong: from what I hear, it's a myth... it's apparently frowned upon to not work on what you're normally working on with that 20%... however, perhaps that's just within the Chrome team.
  246. <bryce> would be highly ironic if he couldn't
  247. <Tavmjong> Shall we move on to FSA?
  248. <parclytaxel> Kya
  249. <bryce> Tavmjong, ok
  250. <bryce> so, last I've heard, we were down to one last signoff needed
  251. <Tavmjong> ------------------------ Fiscal Sponsership Agreement -----------------
  252. <bryce> and that person has indicated they've done it. So afaik everything's done on our end.
  253. <parclytaxel> What do we already have?
  254. <bryce> but I've not heard from SFC on it one way or another
  255. <bryce> I figure we should consider the new FSA now official and in effect
  256. <parclytaxel> Bryce, what are the most important points?
  257. <doctormon> ok
  258. <Tavmjong> So we just need to ping them? (I sitll need to send in the paper copy... bad me.)
  259. <parclytaxel> If I somehow get my university to sponsor it
  260. <bryce> If folks want, I can take the action of following up to verify this, but it's been such a long process I kind of don't want to stir anything up! ;-)
  261. <bryce> Tavmjong, oops, yeah get that in. Might be they're waiting on odds and ends like that to filter in.
  262. <bryce> anyone else not sent in the papers?
  263. <tweenk> bryce: I'm a little out of the loop here, this FSA is a form contract for when a company wants to sponsor Inkscape?
  264. <parclytaxel> I think zo
  265. <parclytaxel> *so
  266. <Tavmjong> No... its our agreement with the Software Freedom Conservancy.
  267. <bryce> tweenk, sort of; actually it's the contract between Inkscape and the Software Freedom Conservancy, that allows them to handle our money and legal matters, and specifies requirements we must follow to remain non-profit legally
  268. <ScislaC> I mailed mine
  269. <tweenk> bryce: Ah, OK. Any action required on my part?
  270. <bryce> tweenk, I suspect you'll need to sign it as well. I assumed they'd have contacted you about that.
  271. <bryce> doctormon, anyone from SFC contact you?
  272. <ScislaC> tweenk: did you print it, sign it, scan it, email a copy to SFC, and mail them the original?
  273. <Tavmjong> bryce: I don't think they need the new board member signatures. Wasn't that the reason to hold off a couple of days on announcing the results?
  274. <doctormon> bryce: no
  275. <tweenk> ScislaC: nope, it's new to me, I can do it next week
  276. <bryce> ok, I'll take the action to follow up on this, and make sure whatever paperwork is needed gets to tweenk and doctormon
  277. <parclytaxel> And make sure you do
  278. <bryce> tweenk and doctormon probably we'll need mailing addresses, but I'll contact you offlist.
  279. <bryce> Tavmjong, yeah I'll need to doublecheck that. In any case, I'll do some digging and follow up.
  280. <Tavmjong> OK, should we move onto Website statement for code of conduct and privacy policy?
  281. <doctormon> yhanks bryce
  282. <bryce> Tavmjong, sounds good
  283. <bryce> doctormon, want to take the mike here?
  284. <Tavmjong> ------------------- Website statement for code of conduct and privacy policy -----------------
  285. <Tavmjong> What needs to be done? Who is driving it?
  286. <parclytaxel> Er, what does the code of conduct apply to?
  287. <su_v> https://inkscape.org/en/community/coc/
  288. <su_v> "THIS IS A WORK IN PROGRESS!!!"
  289. <doctormon> code of conduct is for anyone chatting, posting, uploading art to the website
  290. <doctormon> Since people can be interacting as user to user on our website, we needed to state the rules.
  291. <ScislaC> su_v!!!!
  292. * su_v waves back
  293. <doctormon> The text in the link su_v has posted needs redrafting into something agreeable.
  294. <parclytaxel> Pull it from Derpi
  295. <Tavmjong> doctormon: Who is going to do that? What is the process?
  296. <FailBit> rather don't
  297. <parclytaxel> They have clearer rules
  298. <FailBit> and are not hosted in the US
  299. <FailBit> and have rather different ideals in mind
  300. <FailBit> don't do that.
  301. <parclytaxel> Wait a minute.
  302. <JonCruz> their certs out of date, but... http://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/
  303. <parclytaxel> That statemenr about "we accept everyone regardless of..."
  304. <doctormon> Tavmjong: We (Maren and I) passed it back to the board for review.
  305. <bryce> I had done a heavy copyedit of this some time back. Not sure if anyone's touched it since then, but I seem to recall thinking at the time that it felt good enough at least for a first cut
  306. <bryce> likely would benefit from a second round of copyediting
  307. <Tavmjong> OK, so we should all read it and give comments on the board mailing list?
  308. * Perendinating has quit (Ping timeout: 265 seconds)
  309. <bryce> I'm willing to give it another go but I think a different set of eyes next would be the most beneficial
  310. <doctormon> Or we could elect the next person to edit the page and then let them come back?
  311. <ScislaC> I will give it a thorough look over too.
  312. <doctormon> Or queue up the three or four people who haven't had a chance to take turns
  313. <tweenk> bryce: I think the CoC could be cut down a little. We basically want people to be respectful and refrain from personal attacks in any form
  314. <bryce> remember that it's editable via the website
  315. <bryce> I think revisions are tracked too, in which case Just Do It might be easiest all around
  316. <bryce> doctormon, a queue's not a bad idea actually
  317. <Tavmjong> How about if ScislaC gives it a look over followed by tweenk and then we then open up a discussion on the mailing list.
  318. <bryce> put me on the end slot
  319. <bryce> Tavmjong, +1
  320. <doctormon> Tavmjong doesnt want a spot? :-)
  321. <Tavmjong> I'll comment on the mailing list after is perfect....
  322. <bryce> he can be manager ;-)
  323. <doctormon> Yay
  324. <Tavmjong> s/after is/after it is/
  325. <doctormon> OK +1 Tavmjong
  326. <tweenk> Tavmjong: OK, I can commit to reviewing the CoC no later than Sunday and posting my feedback to the mailing list
  327. <parclytaxel> Bryce, resolve disputes yourself
  328. <ScislaC> Sounds like a plan
  329. <bryce> ok, next topic?
  330. <parclytaxel> There is no point in leaving the ramble to the users
  331. <Tavmjong> I'm running out of time.... maybe one more topic for today?
  332. <parclytaxel> Yes!
  333. <parclytaxel> The one I mentioned earlier.
  334. <ScislaC> parclytaxel: that's not really board material honestly
  335. <bryce> Tavmjong, I'd actually like to status check on the funded development real quick
  336. <parclytaxel> OK, go ahead
  337. <tweenk> parclytaxel: I'll be here after the meeting and we can discuss
  338. <Tavmjong> parclytaxel: Maybe we can arrange a technical IRC meeting.
  339. <bryce> last we touched on it, iirc next action was getting two of the project descriptions fleshed out
  340. <parclytaxel> Hm. Sounds reasonable.
  341. <bryce> ScislaC, I think you took one and Tav took the other?
  342. <Tavmjong> --------------------- Funded Development -----------------------
  343. <bryce> (technical irc meeting sounds like a great idea actually...)
  344. <Tavmjong> That was so long ago... I remember working on it but don't know the status.
  345. <tweenk> bryce: agree
  346. <doctormon> +1 on technical meeting.
  347. <bryce> * inkscape: Write up GSList project [Tav]
  348. <bryce> * inkscape: Finalize/polish SVG2 flowtext [Josh]
  349. <bryce> is what I have on my list
  350. <ScislaC> I'll email the devel-list re: setting a technical meeting date/time.
  351. <bryce> ScislaC, thanks
  352. <Tavmjong> I did do that. (Since then, half of the work has been done so the project will be smaller.)
  353. <bryce> Tavmjong, oh good to hear
  354. <doctormon> Great
  355. <parclytaxel> Note that I'll be on a holiday to South Korea in late November to early December so...
  356. <ScislaC> bryce: I haven't touched it for months, I can put it on my todo list for next week to get it finished up.
  357. <bryce> Tavmjong, mind doublechecking that the description is still up to date and adequate? I think we also needed deliverables identified and a few other such details. I can help with that if it isn't clear what exactly's needed.
  358. <ScislaC> parclytaxel: I'm going to suggest it for next week, don't worry about it.
  359. <parclytaxel> But that is when I will be having exams.
  360. <parclytaxel> I need to MUG!!!
  361. <ScislaC> parclytaxel: week after next?
  362. <parclytaxel> Hm, let me see..
  363. <Tavmjong> I'm looking at http://staging.inkscape.org/en/project/remove-all-use-of-glist-and-gslist/ but that isn't the latest text.
  364. <JonCruz> would be good to get some accurate performance measurements going.
  365. <bryce> ok, that's all on funded dev for now. Once those descriptions are finalized next steps are web app dev and some PR, much of which I'll own.
  366. <JonCruz> having metrics could help those
  367. <bryce> thanks all for coming to this meeting. Shall we do again in a month?
  368. <parclytaxel> They end on 15 October, Scislac
  369. <doctormon> bryce: +1 sounds good.
  370. <Tavmjong> Maybe one more sooner and then once a month since we missed some things.
  371. <ScislaC> sounds good to me too
  372. <tweenk> Tavmjong: OK
  373. <doctormon> bryce can you let me know if you want to work on the project app together?
  374. <parclytaxel> So is the meeting over?
  375. <ScislaC> parclytaxel: if you're not subbed to the devel list, I'd recommend it since that is where the discussion about availability will happen.
  376. <bryce> Tavmjong, ok sort of a halloween special :-)
  377. <Tavmjong> Yup.
  378. <bryce> doctormon, yes would love to
  379. <parclytaxel> How can I sub?
  380. <bryce> doctormon, for me these days mostly it's a function of scraping together chunks of time
  381. <Tavmjong> OK, I'm going to sign off..... See you all...
  382. <bryce> l8r Tavmjong
  383. <parclytaxel> G'day, everyone!
  384. <tweenk> parclytaxel: https://lists.sourceforge.net/lists/listinfo/inkscape-devel
  385. <tweenk> Bye Tav
  386. <ScislaC> see ya Tavmjong!
  387. * jabiertxof has quit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
  388. <Mc-> I have (investigate style.cpp refactor (url() style items should use URIReference)) and (investigate transforms, some things need cleaning) on my "will have to do some day" todolist
  389. <doctormon> Bye Tavmjong
  390. <doctormon> bryce: I understand :-) we may need to sync up a block to at least get you set up and rolling
  1. More ...
 
 

65

 

1227

Inkscape Board Minutes 2 October 2015

-

PasteBin

Lines
390
Words
4228
Size
25.7 KB
Created
Type
text/x-irclog
Public Domain (PD)
Please log in to leave a comment!