1. <Tavmjong> ============ Weekly Meeting ==============
  2. <Tavmjong> Who is here?
  3. <ScislaC> here
  4. <DASPRiD> here
  5. <Tavmjong> doctormon: Ping?
  6. <Tavmjong> bryceh_: Ping?
  7. <doctormon> Tavmjong: pong
  8. <bryceh_> heya
  9. <Tavmjong> Do we have an agenda?
  10. <bryceh_> yes, I posted one last night
  11. <bryceh_> do we have a karen or mo?
  12. <doctormon> mizmo: ping
  13. <Tavmjong> bryceh_: Where did you post it? I can't seem to find it.
  14. <ScislaC> Tavmjong: board list
  15. <doctormon> Does this mean the meeting is a board meeting?
  16. <Tavmjong> Got it.
  17. <bryceh_> 14 To Tavmjong Bah ( 68) └─>[Inkscape-board] Agenda for tomorrow's meeting (was Re: Hacking Sessions)
  18. <bryceh_> doctormon, no; the meeting was organized by and started off by the board but is made open projectwide.
  19. <bryceh_> I should have posted the agenda to the devel list, but was just replying to the original organizational thread.
  20. <mizmo> hey
  21. <bryceh_> == Agenda ==
  22. <bryceh_> * decide indiegogo or paypal.
  23. <bryceh_> then itemize some tasks.
  24. <bryceh_> * fundraising pitch wordsmithing
  25. <bryceh_> * estimate costs
  26. <bryceh_> * finalize dates and locale decisions & update wiki.
  27. <bryceh_>
  28. <doctormon> Alright. I'm a proponent of paypal, it's more open and we'll be able to do more with it later.
  29. <ScislaC> one more if we can get to it
  30. <ScislaC> * Create a standard policy for promoting commercial items not created by the project proper.
  31. <ScislaC> doctormon: what do you mean by we will be able to do more with it later?
  32. <bryceh_> I'm fine with paypal if we can get a volunteer to take care of the page development and whatnot
  33. <tedg> Is there any difference cost wise?
  34. <ScislaC> tedg: we'd get double dipped on indiegogo
  35. <bryceh_> tedg, karen mentioned the difference in an earlier meeting, let me dig up her notes
  36. <doctormon> ScislaC: Paypal provisions us with more control over why someone is paying us, ability to record those amounts etc. IndieGoGo allows us to create projects along the structure of that funding site.
  37. <tedg> Ah, so we'd have to make the "campaigns" ourselves using PayPal.
  38. <JonCruz> doctormon: so.... figure out why 5 seconds is evil?
  39. <ScislaC> JonCruz: meeting is happening right now
  40. <doctormon> We'd use zipfelchappe to perform the campiagns and payment side of things.
  41. <JonCruz> ScislaC: yay meeting
  42. <doctormon> http://zipfelchappe.readthedocs.org/en/latest/installation.html#payment-providers
  43. <bryceh_> hmm, not spotting it in the notes but yeah, double-dipping on the money vs. having to do the campaigns and page setup ourselves
  44. <johan_e_> (sorry I am late, su_v warned me )
  45. <Tavmjong> Where does the zipfelchappe code go?
  46. <ScislaC> well, with what I read about indiegogo this morning, I don't really feel like it's any less risky than going it on our own...
  47. <bryceh_> hopefully we would be doing enough fundraisers that we'd be able to reuse the setup effort many times
  48. * ScislaC nods
  49. <bryceh_> ScislaC, what'd you read?
  50. <johan_e_> total noob here, but, if we go with paypal, does that allow the donor to assign the money to a certain goal? or does it all end up in one account?
  51. <ScislaC> One was - http://www.theverge.com/2013/8/7/4594824/less-than-10-percent-of-projects-on-indiegogo-get-fully-funded The other was looking back at a handful of proposed ones which fell far short.
  52. <tedg> Yeah, so then I'm +1 on Paypal. I think we basically need to setup the campaigns anyway.
  53. <ScislaC> (ones related to adding features to open source projects)
  54. <doctormon> Tavmjong: It'd be pulled in via pip, although the intergration code would be on inkscape-web. There's a dep on fiencms which will conflict with django-cms, so I'll probably need to recreate that part of it. (it's weird to have a django app depend on a cms)
  55. <bryceh_> johan_e_, it'd all go into one account. We'd need tooling to separately track that. But we're planning to do that anyway.
  56. <johan_e_> bryceh_: ok thanks
  57. <ScislaC> +1 on Paypal for me
  58. <johan_e_> (withholding vote, i do not know enough about either)
  59. <bryceh_> is anyone pro-Indiegogo?
  60. <bryceh_> alrighty... sounds like we have a rough consensus favoring the paypal approach.
  61. <JonCruz> are we going to have open-source-we-take-your-money issues with paypal?
  62. <doctormon> JonCruz: You mean refund issues?
  63. <bryceh_> JonCruz, maybe that's a question for when karen's here
  64. <JonCruz> http://pydanny.com/we-are-not-using-paypal.html
  65. <JonCruz> no, I mean paypal says "our robots noticed odd transactions, so we freeze your money"
  66. <JonCruz> or stuff along those lines
  67. <bryceh_> JonCruz, that's happened to us before and SFC took care of it. So if they're recommending we use PayPal I trust they're giving us ok advice
  68. <JonCruz> aka arbitrary freezing of accounts and seizing of assets from open source
  69. <houz> you should at least move all money from the paypal account to a real bank account so a frozen paypal account doesn't harm too much
  70. <ScislaC> bryceh_: that's what I thought (that it happened and they got it resolved)
  71. <JonCruz> just wanted to be sure their ongoing practice was finally changed
  72. <bryceh_> houz, indeed, and SFC will handle automation of that, as they did previously
  73. <bryceh_> for a while SFC was recommending we use google checkout, but I guess their terms changed so they're not ideal anymore
  74. <ScislaC> So, without Karen here, should we move on to the next item?
  75. <bryceh_> the important thing here is that we're going to handle the front end ourselves. The backend could theoretically be swapped with something else if we needed.
  76. <doctormon> Yeah we took the google checkout away from the website.
  77. * ScislaC nods at bryce
  78. <doctormon> If the SFC has a payment gateway like worldpay, we could take creditcards directly (by which I mean pass along the info, not store them). But there must be a reason SFC don't dot hat.
  79. <bryceh_> ScislaC, before we move on, I'd like to itemize some near-term tasks for the paypal work
  80. <ScislaC> cool beans
  81. <Tavmjong> Any estimate at how long it will take to setup zipfelchappe?
  82. <bryceh_> doctormon, you mentioned zipfelchappe as one possibility, have you used that previously for other things? Is it a good & solid for us?
  83. <bryceh_> doctormon, or any other options you know of that might be worth considering?
  84. <doctormon> bryceh_: I have not used it, my searches show few pre-built options and the more pre-built the more incompatible. but that's not too much of a problem because django apps are pretty modular. Timescales are fuzzy though, because we don't have a spec.
  85. <bryceh_> doctormon, ok, so sounds like maybe first task would be an experimentation/proof-of-concept ?
  86. <doctormon> bryceh_: Yes
  87. <bryceh_> doctormon, would you be willing to own that ?
  88. <doctormon> bryceh_: As the resident python developer, yes. :-)
  89. <doctormon> But any help, please.
  90. <johan_e_> perhaps, if it is not so well known yet, the zipfelchappe guys would be happy to help out a "big project" like inkscape ;)
  91. <doctormon> This has interesting things to say about paypal: https://github.com/feinheit/zipfelchappe/
  92. <bryceh_> another task is to decide where to integrate this into the website
  93. <bryceh_> i.e. where in the menu to fit it
  94. <Tavmjong> Look at the bottom of https://github.com/feinheit/zipfelchappe
  95. <Tavmjong> Does this mean that it doesn't currently work with PayPal?
  96. <bryceh_> we'll need to determine whether to set up a new paypal account or use the existing inkscape paypal account (Q for karen I think)
  97. <doctormon> Although I'm questing the sanity of that repo, it has a sqlite db comitted into it.
  98. <doctormon> We'll need a bunch of keys for the cross-site intergration for whichever account we get.
  99. <bryceh_> will we need a page design for this?
  100. <JonCruz> >_<
  101. <bryceh_> guessing we do. ok any other tasks?
  102. <tedg> bryceh_, Nope
  103. <tedg> bryceh_, I think alot depends on the first run.
  104. <tedg> We should know where we need to go after that.
  105. <doctormon> Tavmjong: That's an unknown question. I'm actualyl going to take zipfelchappe off the table. I may choose to take some of it's design patterns, but the quality of the code isn't good enough.
  106. <doctormon> bryceh_: You need two parts right, one is projects, the other is backers+transactions.
  107. <Tavmjong> What do other SFC project use?
  108. <JonCruz> doctormon: support you in the db being a red-flag
  109. <doctormon> JonCruz: There's also other stuff, duplicate model behaviours, lack of models I would expect to see. So I'm digging through the code more.
  110. <doctormon> bryceh_: Can I do some research and get back for next week on it?
  111. <JonCruz> yeah, when security or money become involved, quality of the codebase is very important
  112. <bryceh_> doctormon, sounds like a good plan
  113. <doctormon> My nursery school just called about an administrative issue, I gotta go pick up my 20 year project.
  114. <bryceh_> ok, cya doctormon
  115. <bryceh_> ok, can everyone take a quick 2 minute peek at the fundraiser pitch and give me any wordsmithing suggestions?
  116. <johan_e_> ok
  117. <Tavmjong> Can you remind us where it is (I've got a faulty brain)?
  118. * ScislaC has a faulty brain atm too
  119. <bryceh_> http://wiki.inkscape.org/wiki/index.php/Hackfest2015#The_Pitch
  120. <Tavmjong> s/Us/Our/
  121. <johan_e_> and board so our volunteer developers to attend the working sessions. -> and board so our volunteer developers can attend the working sessions in person.
  122. <johan_e_> Things we hope to… -> Things we plan to...
  123. <JonCruz> "Us developers work remotely" seems awkward
  124. <Tavmjong> Things we hope to... -> Things we will...
  125. <ScislaC> I wish the wiki had multi-user simultaneous editing...
  126. <JonCruz> but "We the developers" would be too formal :-)
  127. <JonCruz> sub-etha is mourned
  128. <johan_e_> The whole pitch is somewhat formal I find. Not very exciting.
  129. <Tavmjong> Us developers -> Our developers
  130. <Tavmjong> johan_e: Agreed
  131. <bryceh_> johan_e_, got some verbage to supply?
  132. <johan_e_> perhaps you can say something about what makes an IRL meeting special. something like:
  133. <tedg> bryceh_, I like that karaoke is suggested.
  134. <johan_e_> tedg: your welcome :D
  135. <Tavmjong> If this is going to be a public plea, it needs to be jazzed up with some figures. Maybe some images of what we will be working on?
  136. <johan_e_> Being together in one room allows us to work on things that we can't do remote: ...
  137. <ScislaC> I guess a question is, are we wanting formal yet fun? Because we don't want to come across as unprofessional.
  138. <JonCruz> might we want the tone of Mythbusters as opposed to Nova?
  139. <ScislaC> I like Nova... :-/
  140. <johan_e_> or "tasks that need thorough discussion and coordination among developers"
  141. <JonCruz> ScislaC: yes. as do we. However...
  142. <johan_e_> Is this our first hackathon?
  143. <JonCruz> the tone of their usual narration is interesting.
  144. <JonCruz> johan_e_: first sponsored I believe
  145. <johan_e_> In that case, we need to tell that too. It is exciting of itself
  146. <johan_e_> by itself*
  147. <tedg> bryceh_, Perhaps we could talk about it like this: "We've noticed that in-person meetings bring about greater cohesion and more creative results. We want your help in making Inkscape have a bright future."
  148. <ScislaC> We could use a blink tag on the word bright!
  149. <tedg> "making sure Inkscape has"
  150. <JonCruz> tedg: "greater cohesion" is just a half step from "leveraging synergies". Might need to tweak that sub-phrase
  151. * bryceh_ nods
  152. <JonCruz> or...
  153. <tedg> "stronger relationships"
  154. <JonCruz> "making sure Inkscape brings benefit to end users" - but with good phrasing
  155. <bryceh_> ok thanks, good suggestions. I'll incorporate all these before the next meeting, unless someone else wants to take a shot at doing the next revision?
  156. <JonCruz> reminding people that the software is not the end goal, just the tool that will result in them being able to bring their creative endeavors to life
  157. <johan_e_> i dunno , we can be frank about it. "greater cohesion" -> "greater cooperation"
  158. <tedg> "making sure Inkscape has a bright future bringing benefits to designers everywhere."
  159. <johan_e_> we should not only focus on designers, i think.
  160. <JonCruz> right
  161. <JonCruz> I was just thinking of phrasing on that point
  162. <johan_e_> most users I know are simple figure drawers like me
  163. <ScislaC> our users
  164. <JonCruz> "users from all walks of life"
  165. <tedg> johan_e_, Sure, but everyone needs to believe if they "just learned a little more" they'd become Monet ;-)
  166. <johan_e_> tedg: haha
  167. <ScislaC> :)
  168. <johan_e_> tedg: my peers wouldn't be happy with Monet'esque pieces, but yeah
  169. <JonCruz> tedg: yeah... that aspect of bringing their visions to life
  170. <JonCruz> johan_e_: picaso then? :-)
  171. <johan_e_> what about fixing bugs?
  172. <johan_e_> people must like us fixing bugs
  173. <johan_e_> "particularly nasty bugs"
  174. <JonCruz> "teaming up to squash bugs"
  175. <Tavmjong> I like us fixing bugs.
  176. <tedg> "Difficult to remotely coordinate bug hunting"
  177. <ScislaC> johan_e_: they do, but they want us to fix specific bugs mostly...
  178. <JonCruz> "hands-on group bug smashing"
  179. <Tavmjong> Donate and nominate a bug...
  180. <JonCruz> or...
  181. <bryceh_> so apparently my wife wants to kill my 3yr old daughter. While they were at Target she opened a thing of liquid soap and got it over everything in the cart. ><
  182. <JonCruz> "Donate, but also nominate a bug"
  183. <ScislaC> YIKES!
  184. <bryceh_> so, next on the agenda is cost estimates
  185. <JonCruz> depends on which kind of soap
  186. <Tavmjong> bryceh_: Clever girl!
  187. <tedg> bryceh_, At least everything is clean now!
  188. <bryceh_> Tavmjong, hazards of having children with an engineer I guess...
  189. <ScislaC> bryceh_: is this for the LGM related one or the otherwise discussed smaller one?
  190. <bryceh_> so one question I have is did we finalize the decision of Toronto vs Boston? I'm fuzzy on that and the wiki page doesn't help
  191. <ScislaC> LGM
  192. <bryceh_> ScislaC, lets focus on LGM for now
  193. <ScislaC> I don't think it was finalized by leaning more toward Toronto for costs and less visa hassle
  194. <Tavmjong> I think LGM makes more sense... but have we gotten feedback from them?
  195. <JonCruz> travel to/from meet, but not local transport, right?
  196. <bryceh_> JonCruz, tbd
  197. <bryceh_> Tavmjong, I haven't seen anything recent
  198. <ScislaC> Who had reached out to them?
  199. <Tavmjong> Doctor Mo me thinks.
  200. <JonCruz> there is the visa hassle issue, but then also the 'avoiding the large oppressive government' factor. Not as big for this hackathon
  201. <bryceh_> yep, with Josh and I CC'd
  202. <Tavmjong> Did we get any thing back from LGM at all?
  203. <ScislaC> bryceh_: just re-read it... no wonder I didn't remember clearly, last word was 3 weeks ago...
  204. <bryceh_> they asked about # people, technical requirements we have, etc. but say they could roll us into the booking without trouble
  205. <johan_e_> i assume everybody brings a laptop?
  206. <bryceh_> Martin answered the questions, and then no word since that I know of
  207. <ScislaC> Last message said Ginger was going to reach out to the local linux community and CS groups as well.
  208. <Tavmjong> Are they OK with us meeting before or after?
  209. <bryceh_> "We're talking a two solid day, maybe three days (if you think Torronto
  210. <bryceh_> is a place we should see and not just visit ;-)), a projector, wifi, a
  211. <bryceh_> room for about 15 people and some networking contacts to get the message
  212. <bryceh_> out there for the recruitment portion."
  213. <bryceh_> Tavmjong, didn't get discussed
  214. <ScislaC> From Ginger's last email "We'll be booking rooms at the University of Toronto for the duration of LGM (which will run from ~29 April to 2 May), and it shouldn't be much trouble at all to extend that in one direction or another." So it seems open in either direction.
  215. <Tavmjong> LGM is a pretty low-key meeting so there is time for hacking during the meeting but it would definitely be better to have some time before or after.
  216. <bryceh_> ok, so sounds like we need to touch base with a few more people before calling consensus on location
  217. <bryceh_> so that task is still open
  218. <bryceh_> as an exercise let's go ahead and assume Toronto
  219. <bryceh_> what's our preference for before vs. after?
  220. <bryceh_> and as to length... 2 days, 3 days...?
  221. <ScislaC> Both of those issues I am open on as others likely have more constraints
  222. <Tavmjong> I'm going to have to think about it.... I may have a scheduling conflict I just realized.
  223. <bryceh_> having it after might let us hold some preparatory conversations during LGM. Having it beforehand might help us be more focused and then use LGM time for followup tasks
  224. <bryceh_> ok, for sake of exercise let's arbitrarily pick 3 days prior to LGM in Toronto.
  225. <bryceh_> would someone be willing to look up general hotel costs for Toronto in this time period, for next meeting?
  226. <bryceh_> also, would someone mind looking up rough estimates on airfare costs from 3-4 different places?
  227. <Tavmjong> Pick the cities: Paris, San Francisco, Boston, ?
  228. <johan_e_> Zurich :P
  229. <bryceh_> those four sound good
  230. <JonCruz> LAX?
  231. <bryceh_> LAX will be < san fran
  232. <JonCruz> usually I've seen it >
  233. <bryceh_> or in the same ballpark at least
  234. <bryceh_> alright then, LAX instead of San Fran
  235. <Tavmjong> Paris: $900,
  236. <Tavmjong> LAX: $750
  237. <Tavmjong> Zurich: $900
  238. <Tavmjong> Boston: $300
  239. <Tavmjong> These are if booked now. Fares tend to drop the closer you get then rise up again.
  240. * bryceh_ nods
  241. <bryceh_> thanks Tav
  242. <bryceh_> ok, anyone looking up hotel costs?
  243. <Tavmjong> Two star hotel ~$100 per night, probably can do better. Can also share rooms.
  244. <Tavmjong> The LGM organizers should have suggested places for less.
  245. <JonCruz> what about the student-ish accomodations?
  246. <bryceh_> JonCruz, the first LGM the student accomodations were really bad
  247. <Mc-> a quick search shows up return flights paris-toronto at ~$600
  248. <Tavmjong> Hostel ~$30 per night.
  249. <bryceh_> like tiny beds with no mattresses
  250. <johan_e_> guys i have to leave, sorry
  251. <Tavmjong> MC- for which dates?
  252. <Mc-> around end of april to beginning of may
  253. <johan_e_> gn
  254. <bryceh_> thanks johan_e_
  255. <JonCruz> ustay in Wellington had issues. yeah
  256. <bryceh_> alright thanks Tav for the estimates
  257. <bryceh_> ok, let's wrap the meeting. thanks all
  258. <Mc-> (my search was 04/27 - 05/04 on kayak.com for an hypothetical entire week stay )
  259. <bryceh_> I'll take care of posting the meeting minutes and updating action items and following up on some stuff. Would someone be willing to write and post meeting minutes?
  260. <Tavmjong> MC- Iceland Air does have a cheap flight depending on some dates.
  261. <Mc-> yeah, i saw it show up, never took a flight with this company ^^ i'm more used to delta or air france
  262. <Tavmjong> MC-: I am using Google Flights which seems to be pretty good. Allows you to scan prices for departure dates and return dates.
  263. <Mc-> (in my long history of ... 3 transatlantic flights)
  1. More ...
 
 

75

 

1779

Board Meeting - October 15, 2014

-

PasteBin

Размер:
18,2 КБ
Создан:
Тип:
text/x-irclog
Creative Commons Attribution Share-Alike 3.0 (CC-BY-SA 3.0)
Пожалуйста, войдитев систему, чтобы оставить комментарии!