1. Nov 04 12:00:50 <Tavmjong> ============ Board Meeting ==============
  2. Nov 04 12:01:08 <Tavmjong> Who's here?
  3. Nov 04 12:01:11 <doctormon> I'm here
  4. Nov 04 12:01:36 <rindolf> Tavmjong: I am
  5. Nov 04 12:01:43 <rindolf> su_v: hi'
  6. Nov 04 12:01:45 <Tavmjong> tedg, bryce, ScislaC ?
  7. Nov 04 12:01:48 <Lazur> hi
  8. Nov 04 12:01:50 <brynn> I might need to leave early
  9. Nov 04 12:02:01 <Tavmjong> su_v: Hi!!!
  10. Nov 04 12:02:09 <bryce> hey hey
  11. Nov 04 12:02:34 <su_v> hi all
  12. Nov 04 12:02:59 <bryce> brynn, then let's start with the forum. How are things proceeding?
  13. Nov 04 12:03:12 <Tavmjong> ====== Forum =======
  14. Nov 04 12:03:39 <brynn> We're having sporadic talks with OSUOSL, and it looks like they can probably host the forum, but it's not definite yet
  15. Nov 04 12:04:00 <brynn> Currently waiting for response from Courtney, re some stats they asked for
  16. Nov 04 12:04:27 <Tavmjong> Are they worried about overloading their systems?
  17. Nov 04 12:04:38 <brynn> bryce or doctormon could explain the details about the server setup they mentioned - I don't really understand much about it
  18. Nov 04 12:06:15 <doctormon> brynn: Which person was those details from and what date is the email?
  19. Nov 04 12:06:25 <bryce> brynn, do you know when Courtney will be delivering the data files? I imagine that is the main blocker right now...
  20. Nov 04 12:07:07 <brynn> looking for the message - I'm ready to send Courtney a reminder. yes, that is the next big thing
  21. Nov 04 12:07:14 <doctormon> Tavmjong: Pretty much, we're asking for another machine. Although the majority of the load will come from media. :-/ we don't have another Fastly cache to help with that either.
  22. Nov 04 12:07:47 <Tavmjong> doctormon: Do we need to offer to pay for the machine?
  23. Nov 04 12:08:16 <brynn> 10-11-16 from Justin Dugger
  24. Nov 04 12:09:00 <doctormon> brynn: 2016-10-11?
  25. Nov 04 12:09:09 <brynn> yes
  26. Nov 04 12:09:24 <bryce> I figure worst case we can arrange our own hosting provisioning elsewhere, though that would require some ongoing monthly costs and potentially more administrative attention on our end
  27. Nov 04 12:09:51 <brynn> There are a couple of other possiblities for gratis hosting, which have not been explored yet
  28. Nov 04 12:10:11 <brynn> tux family and I'll have to look up the other one
  29. Nov 04 12:10:18 <doctormon> OK so
  30. Nov 04 12:10:52 <doctormon> OSUOSL are in a bit of transition, they want to move to a more managed setup, where apps can be plug and play.
  31. Nov 04 12:10:57 <bryce> fwiw I don't appear to have the 2016-10-11 email
  32. Nov 04 12:11:39 <bryce> doctormon, is the lack of a Fastly cache for media an issue we need to address?
  33. Nov 04 12:12:14 <doctormon> But out systems are not just legacy, all over the place and special**, but also we want more ;-) so they'd prefer to transition us. Start off with a Chef VM instance for the forum, unknown CPU, unknown memory, based of existing stats for existing forum.
  34. Nov 04 12:12:43 <brynn> bryce, I just forwarded to you. Sorry, I thought you were Cc'd
  35. Nov 04 12:12:50 <doctormon> bryce: Not having it won't hurt the website, but OSUOSL might have to provision a larger machine for the forum than otherwise.
  36. Nov 04 12:13:53 <bryce> brynn, thanks
  37. Nov 04 12:14:03 <bryce> ok, any action items for forum we need to track?
  38. Nov 04 12:14:46 <bryce> if not, let's move on to an SVG 2 update from Tav
  39. Nov 04 12:14:50 <doctormon> As the website administrator; I'm concerned that pushing OSUOSL will cause them to push back and ask us to move the website to one of these newer app based VMs, it's scares the living nighmare out of me because it took years to adaminster the website into a non-snail speed and I doubt any app service would be at the same level. So I saw it as rocki
  40. Nov 04 12:14:50 <doctormon> ng the boat a bit.
  41. Nov 04 12:15:02 <brynn> bryce, you mentioned potential mentoring on installing the f orum
  42. Nov 04 12:15:18 <bryce> brynn, ah right, I need to do that still.
  43. Nov 04 12:15:48 <Tavmjong> ============== SVG 2 Status =============
  44. Nov 04 12:16:11 <Tavmjong> I've prepared a summary for the status of SVG 2: http://tavmjong.free.fr/svg2_status.html
  45. Nov 04 12:16:23 <brynn> could I make another comment on the forum/server issue?
  46. Nov 04 12:16:32 <bryce> brynn, go ahead please
  47. Nov 04 12:17:10 <brynn> I just wanted to ask, if it's going to be a big problem for osuosl, it probably would be the end of the world, if the forum wasn't hosted in the same place as the website
  48. Nov 04 12:18:02 <brynn> I trust what doctormon is saying about those p otential problems - don't think he's exaggerating
  49. Nov 04 12:18:17 <bryce> brynn, certainly. There is an administrative simplification to having services together in one place, which is the only concern I have really.
  50. Nov 04 12:18:38 <brynn> oops, that was "would not be the end of the world"
  51. Nov 04 12:19:17 <brynn> yes, I understand it's better to have all together
  52. Nov 04 12:19:30 <bryce> but I've expected we might eventually outgrow OSUOSL, and if they're pushing us to something we're not 100% certain is going to meet our needs going forward, that could possibly be a signal we need to start looking where we need to be down the road a bit
  53. Nov 04 12:20:16 <doctormon> Administrative burden is the key there I think. Perhaps for OSUOSL too.
  54. Nov 04 12:20:18 <bryce> however, I would like to avoid piecemealing infrastructure; if we outgrow OSUOSL I'd want to perhaps look at arranging something more fully under our own management
  55. Nov 04 12:20:46 <brynn> I was thinking that too, although with much less well informed info
  56. Nov 04 12:20:50 <doctormon> (they're also not responding to requests for a mailman3 service)
  57. Nov 04 12:23:11 <bryce> hmm, well it can't hurt to at least sketch out some ideas of assembling an alternative hosting solution, but let's make that an agenda item for next month. Meantime, collect ideas. :-)
  58. Nov 04 12:23:12 <doctormon> Should we move onto SVG 2?
  59. Nov 04 12:23:18 <bryce> Tav, please proceed, sorry for the delay.
  60. Nov 04 12:23:43 <brynn> collecting ideas.... Thanks
  61. Nov 04 12:24:04 <Tavmjong> A quick summary is that SVG 2 is in trouble. It almost got shut down completely last month. It is limping along at the moment. The things most interesting to Inkscape are the most threatened.
  62. Nov 04 12:24:43 <Tavmjong> One thing that is important is to demonstrate that there is interest in the new features. This can be done by generating lots of content using the new features.
  63. Nov 04 12:26:18 <Tavmjong> One thing we can do is to ship 0.92 with mesh gradients enabled. I've spent a bit of time in the last couple of weeks improving the GUI. I've fixed the undo bugs which was the most serious problem.
  64. Nov 04 12:26:46 <prkos> how much content? Where should the content be published to matter? Can we encourage it for About screen contest if the tools exist already?
  65. Nov 04 12:27:32 <bryce> sounds like going back to the days when we were clamoring for browsers to support SVG at all
  66. Nov 04 12:27:32 <rindolf> Tavmjong: ah, why is there trouble in the SVG 2 standardisation process?
  67. Nov 04 12:27:40 <Tavmjong> Anywhere where, for example, Chrome's use counters pick it up.
  68. Nov 04 12:28:35 <Tavmjong> Mostly lack of interest by the browser vendors. SVG 2 has taken a long time to mature which has dampened interest.
  69. Nov 04 12:28:58 <doctormon> I'd vote +1 on mesh gradients being enabled.
  70. Nov 04 12:29:24 <Tavmjong> There is "newer, more exciting" stuff coming out (Houdini).
  71. Nov 04 12:29:25 <brynn> wouldn't that be a nice surprise!
  72. Nov 04 12:29:40 <doctormon> prkos: We can encourage content on inkscape.org with contests, even a gradient mesh special contest. Maybe some t-shirt rewards :-)
  73. Nov 04 12:30:08 <brynn> speaking of t-shirts - t-shirt design contest....
  74. Nov 04 12:30:14 <prkos> doctormon: yes that would be exciting :)
  75. Nov 04 12:30:19 <Tavmjong> A contest would be a good idea. I would love to see what people can do with it.
  76. Nov 04 12:30:39 <Lazur> I'd say that would target the professionals more
  77. Nov 04 12:30:40 <doctormon> Tavmjong: Would it be helpful if the website detected the browser in use, detected the use of mesh or other features in an uploaded svg and gave a warning + link to complain?
  78. Nov 04 12:30:58 <Tavmjong> And having cool examples would help.
  79. Nov 04 12:30:58 <Lazur> and that they would more appreciate a cmyk save feature with svg-s
  80. Nov 04 12:31:23 <Tavmjong> doctormon: Probably if done carefully.
  81. Nov 04 12:31:30 <doctormon> After a contest :-D
  82. Nov 04 12:31:32 <Lazur> for new comers the spray tool's new feature is a real eye candy on picking the colours
  83. Nov 04 12:31:33 <bryce> Tavmjong, I recall adding the WITH_MESH support to cmake as part of the 'disable unstable features' task
  84. Nov 04 12:32:03 <bryce> Tavmjong, so I hesitate with a +1 in that I'm worried there might be instability concerns enabling it this late in the release?
  85. Nov 04 12:32:22 <bryce> Tavmjong, or was it disabled due to SVG 2 not being out yet?
  86. Nov 04 12:32:47 <doctormon> Not out and I bet concerns over changing spec
  87. Nov 04 12:33:15 <Tavmjong> bryce: Mostly SVG 2 not being out but also due to the undo bugs (which are now fixed).
  88. Nov 04 12:33:36 <bryce> I don't know how others feel about having features that potentially conflict with the spec, but given that the SVG 2 process is in question it seems to me less a concern
  89. Nov 04 12:34:08 <su_v> at the time the report was filed, it was mostly stability concerns, and future changes in the spec (the report asked for a discussion whether or not to disable the GUI for the tool - the feature itself for rendering is enabled anyway)
  90. Nov 04 12:34:40 <bryce> if svg 2 gets canceled, then obviously we'll be on our own anyway
  91. Nov 04 12:35:14 <su_v> he configure option itself just hides the tool in the toolbox, and the button in Fill&Stroke
  92. Nov 04 12:35:23 <bryce> su_v, right. Are the stability concerns resolved to your satisfaction? Do we need further testing first?
  93. Nov 04 12:35:54 <su_v> bryce: I have not tested it lately in 0.92pre2
  94. Nov 04 12:36:10 <bryce> hmm
  95. Nov 04 12:36:25 <bryce> so maybe what we should do is re-enable it now, and push the release date out a bit to give more testing time
  96. Nov 04 12:36:29 <su_v> copy&paste as well as duplicate support I'd consider an essential though (last time I checked it was missing)
  97. Nov 04 12:36:45 <Tavmjong> Can people give the mesh gradient tool a workout in trunk this week? (Some things have not yet been backported to 0.92 yet as it would break string freeze.)
  98. Nov 04 12:37:26 <bryce> I can then roll a pre3 after it's turned on by default, and y'all can do gradient mesh contests and if problems crop up we still have a chance to disable before the release
  99. Nov 04 12:38:01 <su_v> bryce: it can be tested with 0.92pre2 already - users simply have to define a custom shortcut for the tool in the preferences
  100. Nov 04 12:38:05 <Ede_123> We shouldn't reproduce the flowed text debacle with mesh gradients... In my opinion the lack of support in other rendering software damaged the project more than a lack of flowing text support would have...
  101. Nov 04 12:38:09 <su_v> and use the shortcut to activate the mesh tool.
  102. Nov 04 12:38:50 <prkos> can I have the new nightly installed in a separate folder? I don't want to run over the 0.92
  103. Nov 04 12:39:12 <tedg> Sorry I'm late.
  104. Nov 04 12:39:19 * tedg reads backlog
  105. Nov 04 12:39:21 <bryce> Tavmjong, has it been your experience that the SVG WG or W3C gives weight to Inkscape as a significant SVG implementor?
  106. Nov 04 12:40:07 <Tavmjong> Definitely by the SVG WG. The W3C is more of a mixed bag.
  107. Nov 04 12:40:14 <doctormon> Tavmjong: Do we set the svg version to 2.0 when using these features? in the svg tag?
  108. Nov 04 12:40:43 <Tavmjong> doctormon: We could... but the SVG version tag has been removed (!!!!).
  109. Nov 04 12:40:58 * doctormon slaps head in comic doh fashion
  110. Nov 04 12:41:15 <bryce> Ede_123, that is a fair point
  111. Nov 04 12:41:33 <Tavmjong> Actually, we probably should set the version flag for our own use.
  112. Nov 04 12:41:41 <rindolf> Tavmjong: isn't it an attribute?
  113. Nov 04 12:41:56 <Tavmjong> rindolf: Yes, it's an attribute.
  114. Nov 04 12:41:57 <doctormon> The difference I think is that we don't tell users our text is broken, we didn't do a good job falling back and the resulting render on others was a mess
  115. Nov 04 12:41:57 <bryce> prkos, not sure what OS you're on but afaik there's always some way to run in parallel
  116. Nov 04 12:42:15 <prkos> bryce: ubuntu
  117. Nov 04 12:42:44 <bryce> prkos, yes if you build it via cmake you can install to /usr/local (it should do so by default)
  118. Nov 04 12:42:51 <prkos> I remember doing it years ago, compiling in a separate folder, but I had a cheat sheet of commands
  119. Nov 04 12:43:14 <bryce> prkos, also see the README, I jotted some directions for configuring install target there iirc
  120. Nov 04 12:43:27 <prkos> ty I will
  121. Nov 04 12:43:32 <bryce> ok, so action items on SVG 2 life support mission
  122. Nov 04 12:43:35 <Tavmjong> Yes, we need to make it more apparent that meshes have limited support outside of Inkscape.
  123. Nov 04 12:43:58 <rindolf> prkos: -DCMAKE_INSTALL_PREFIX=...
  124. Nov 04 12:44:07 <Tavmjong> I need to finish with the GUI changes for meshes. And I will respond to any bug reports ASAP.
  125. Nov 04 12:44:16 <tedg> Can we have a feature flag? "enable cool stuff" with a warning about portability?
  126. Nov 04 12:44:26 <prkos> rindolf: ty!
  127. Nov 04 12:44:37 <Tavmjong> Mostly what is left is saner handling of mesh in the Fill and Stroke dialog. That is almost ready.
  128. Nov 04 12:44:43 <doctormon> Tavmjong: And everything else. Using paint order for example is weird in that we support it, as do several browsers, but not svg 1.1 unlike whatour svg tag says.
  129. Nov 04 12:44:47 <bryce> Tavmjong, how much time will you need? And do you want that landed in a 0.92pre3, or just trunk for now?
  130. Nov 04 12:45:06 <bryce> tedg, there's already a WITH_MESH cmake feature flag
  131. Nov 04 12:45:13 <Tavmjong> Give me a week to get it into 0.92
  132. Nov 04 12:45:22 <rindolf> prkos: you're welcome .
  133. Nov 04 12:45:26 <tedg> bryce: I was thinking runtime
  134. Nov 04 12:45:34 <tedg> Most users probably aren't compiling it.
  135. Nov 04 12:46:24 <bryce> tedg, yet another preferences option ;-)
  136. Nov 04 12:47:25 <bryce> honestly this is more like a file format compatibility issue than just a user tweakable knob
  137. Nov 04 12:48:04 <bryce> perhaps the right way to solve it would be to register it as a different file type (SVG 2 Experimental or somesuch)
  138. Nov 04 12:48:14 <tedg> Yes, I see that. I guess I'm more worried how to we get people to use it, but yet understand the risks of compatibility if they do.
  139. Nov 04 12:49:16 <bryce> but none of that's really doable in the 0.92 timeframe, and evidently by 0.93 we should know the prognosis for SVG2
  140. Nov 04 12:49:18 <doctormon> Default should be inkscape svg. We can create a SVG for the Web option perhaps, make it more obvious that we'll clean and warn for the web that way.
  141. Nov 04 12:49:57 <bryce> ok, so action item for Tav is to get the GUI bits done and landed in 0.92, then I'll roll a 0.92pre3 with it.
  142. Nov 04 12:50:08 <bryce> any other action items for svg2?
  143. Nov 04 12:50:13 <Tavmjong> Will do.
  144. Nov 04 12:50:19 <Tavmjong> Not at the moment.
  145. Nov 04 12:50:21 <tedg> Yeah, Tavmjong could we just inkscape: prefix it all. And then "save as svg2" which would change the namespace on save?
  146. Nov 04 12:50:36 <doctormon> I'm going to take a look at warning/cleaning for "plain svg", maybe it's easy enough to warn the user.
  147. Nov 04 12:51:07 <doctormon> Add as action item bryce
  148. Nov 04 12:51:15 <bryce> doctormon, got it
  149. Nov 04 12:51:22 <bryce> ok, if there's nothing else, moving on...
  150. Nov 04 12:51:30 <Tavmjong> doctormon: Warning of saving would be a good idea.
  151. Nov 04 12:51:45 <Tavmjong> Next topic?
  152. Nov 04 12:51:53 <brynn> see you guys, and thanks :)
  153. Nov 04 12:51:58 <bryce> ============== Merchandise Sales ==============
  154. Nov 04 12:52:11 <doctormon> thanks brynn! have a good weekend
  155. Nov 04 12:52:17 <bryce> SFC has set up a Spreadshirt account for us to use
  156. Nov 04 12:52:36 <bryce> I am still waiting on getting actual login credential access, but will reping on that.
  157. Nov 04 12:52:58 <tedg> bryce: That's cool, thanks for getting that setup.
  158. Nov 04 12:53:08 <bryce> I don't think I'll have time to actually do the store setup and administrative work. I might poke at it a bit, but would better trust someone else to focus on it
  159. Nov 04 12:53:08 * tedg hugs bryce
  160. Nov 04 12:53:42 <bryce> Mc had proposed the idea originally, so I'm hopeful he is still interested/willing/available to take charge on it
  161. Nov 04 12:53:42 <doctormon> Nothing in the credentials repository, bryce I'd love to see the interface for spreadshirt
  162. Nov 04 12:54:05 <bryce> but for redundancy I'd also like a second volunteer
  163. Nov 04 12:54:24 <doctormon> I'll jump in, since I'm very interested in it.
  164. Nov 04 12:54:44 <bryce> doctormon, this is another service that is going to be per-person credentials rather than a shared account we can put in the credentials repo
  165. Nov 04 12:55:06 <doctormon> bryce: Great, what's the first step in getting an account?
  166. Nov 04 12:55:13 <bryce> doctormon, you've just completed it :-)
  167. Nov 04 12:55:27 <bryce> doctormon, I'll forward your name and email to SFC so they can set you up as well as me
  168. Nov 04 12:56:12 <bryce> if Mc is not interested we'll need to find another volunteer. I think 2 people + me as backup should be adequate
  169. Nov 04 12:56:38 <bryce> we had discussed starting with using the Inkscape logo on a few articles/items
  170. Nov 04 12:57:26 <bryce> doctormon, btw you can register a dummy account there if you want to poke around at the interface, it's pretty slick. But the banking info has to be there before you can actually set stuff up for real.
  171. Nov 04 12:58:14 <prkos> I'd love to help out but I'm not up to speed about what the expectations are
  172. Nov 04 12:58:52 <tedg> I think logo shirts are a really good first step, but I think it is something we can grow.
  173. Nov 04 12:59:15 <bryce> prkos, I think this is new territory for pretty much all of us
  174. Nov 04 12:59:44 <bryce> so doing some shirts with the logo would be a simple first step, and I don't think should be hard
  175. Nov 04 13:00:01 <prkos> I guess I can help with anything except programming so CMI if you need me
  176. Nov 04 13:00:06 <bryce> there'll be some tasks to do for promoting it -- adding news items on our website, putting out the word, etc.
  177. Nov 04 13:00:25 <doctormon> bryce: So far I'm stuck on uploading an avatar, only jpegs, only 120x120 or more, unknown error come back later.
  178. Nov 04 13:00:30 <prkos> I can do articles, marketing etc
  179. Nov 04 13:00:52 <bryce> prkos, great! thanks
  180. Nov 04 13:01:13 <bryce> prkos, no programming necessary on this I believe
  181. Nov 04 13:01:14 <doctormon> prkos: Happy to work with you, can you send me an email?
  182. Nov 04 13:01:58 <fguimont> I'd like to see badges you can sow on a bag or coat.
  183. Nov 04 13:02:16 <bryce> there's been a ton of ideas for phase 2, everything from contests to the past about screens to even hired artwork
  184. Nov 04 13:02:55 <bryce> so as you get up the learning curve on this, you guys should brainstorm on direction forward there
  185. Nov 04 13:03:38 <bryce> there's obviously going to be some consideration needed to be given to usage rights and so on, we certainly want to make sure we use art respectfully
  186. Nov 04 13:03:45 <doctormon> Wow so many problems with the spreadshirt website, I think it might actually hate me. ;-) will keep trying
  187. Nov 04 13:04:03 <bryce> at the same time I expect purchasers of our wares are going to have high expectations for artistic quality ;-)
  188. Nov 04 13:04:13 <Tavmjong> I don't get past "Your design is being checked."
  189. Nov 04 13:06:11 <doctormon> I cn
  190. Nov 04 13:06:16 <doctormon> t even set my real name ;-)
  191. Nov 04 13:06:21 <bryce> doctormon, prkos ok so next action for me will be to request admin access for you two to the account (unless prkos you want to *just* focus on promotion and not on admin)
  192. Nov 04 13:06:38 <doctormon> I'd like prkos to have admin, even if not focused
  193. Nov 04 13:06:51 <bryce> Tavmjong, doctormon :-/ it seemed to work ok for me back when I tried it, although I didn't test uploading actual designs
  194. Nov 04 13:06:52 <prkos> happy to help, CMI
  195. Nov 04 13:07:01 <bryce> prkos, doctormon great
  196. Nov 04 13:07:32 <bryce> ok, so guess your action item will be to have fun and experiment a bit :-)
  197. Nov 04 13:07:34 <Tavmjong> I just got a simple rectangle/circle design to upload. Kind of neat that you can change the colors in the design after uploading.
  198. Nov 04 13:07:59 <bryce> alright, we'll revisit this next meeting.
  199. Nov 04 13:08:05 <bryce> I'd like to squeeze in one more quick topic
  200. Nov 04 13:08:24 <bryce> ============== Sponsorship level followup ==============
  201. Nov 04 13:08:53 <bryce> this has been percolating on our todo list for months, but I think we're pretty close to being able to get it wrapped up
  202. Nov 04 13:09:03 <bryce> https://sourceforge.net/p/inkscape/mailman/message/34460338/
  203. Nov 04 13:09:25 <bryce> I think the final step here is just that we need to fold in mention of the five levels we decided on for the web page
  204. Nov 04 13:10:22 <bryce> doctormon since that vote preceded your joining the board, I'd first like to get your thoughts
  205. Nov 04 13:11:30 <doctormon> We don't have a tracking mechanism/policy, so one year isn't something we';re going to be notified about.
  206. Nov 04 13:12:29 <bryce> doctormon, perhaps we could track it as part of the board action items for now?
  207. Nov 04 13:12:43 <bryce> to date we've had only one donation above $1000 and that was some years ago
  208. Nov 04 13:13:07 <tedg> Seems like something as simple as a shared google spreadsheet would work.
  209. Nov 04 13:13:39 <bryce> ScislaC had mentioned a potential $5,000 donation but I guess it never materialized.
  210. Nov 04 13:14:27 <bryce> tedg, no, it's not a matter of data recording, it's a matter of remembering down the road
  211. Nov 04 13:14:37 <doctormon> bryce: We can keep it in the action items for now then.
  212. Nov 04 13:15:13 <bryce> ok, works for me. We can just track it in the wiki with the agenda
  213. Nov 04 13:16:49 <bryce> I don't anticipate we're going to see an influx of donations at these levels, but you never know. And if we do we'll want this info on the site. Who knows maybe having it out there will generate some donor interest.
  214. Nov 04 13:17:30 <bryce> I don't think we want to literally cut and paste the text from the referendum though; it should be wordsmithed to be more presentable for donors
  215. Nov 04 13:17:41 <doctormon> I agree
  216. Nov 04 13:18:04 <bryce> doctormon, do you think this is something maren would be interested in working on designing? Or are there other web editors with good layout skills we could ask?
  217. Nov 04 13:18:19 <tedg> I think having the levels is good. It makes people feel like they have something to go for, and target. Instead of some random "donate something"
  218. Nov 04 13:18:45 <bryce> tedg, yeah and I especially like the names for the levels
  219. Nov 04 13:18:46 <doctormon> bryce: There are designers, Sylvain maybe, me perhaps. Depends on what and how fast.
  220. Nov 04 13:19:17 <doctormon> Do we have the website page explaining the levels with cute icons and example screenshots?
  221. Nov 04 13:19:24 <bryce> doctormon, there isn't anything driving an urgency to this other than that it's on our todo list
  222. Nov 04 13:19:57 <prkos> could we maybe get some descriptions from developers for each price tag, something inspiring about what a particular amount would do when applied to real problems being solved?
  223. Nov 04 13:20:16 <bryce> doctormon, creating that would be the next step. The levels definitely do suggest cute icons :-)
  224. Nov 04 13:21:15 <bryce> prkos, sure if that's something the web designer thinks would add to the page we can brainstorm something
  225. Nov 04 13:21:42 <prkos> like: one week of bug cracking frenzy by two mad scientists...
  226. Nov 04 13:21:53 <bryce> right now, the largest chunks of our cash go to hackfests and svg wg's and we have advocacy pages on the site for both of those, that could be linked to
  227. Nov 04 13:22:24 <bryce> prkos, that'd be awesome but we're not quite to that level yet ;-)
  228. Nov 04 13:22:47 <prkos> :-$
  229. Nov 04 13:23:10 <doctormon> We can save that one for the $100,000 level
  230. Nov 04 13:23:27 <bryce> doctormon, ok can you take the action item to find someone interested in working on scoping this out? You can have them pepper me with questions if they need direction.
  231. Nov 04 13:24:34 <bryce> prkos, actually hold that thought for next meeting; it fits with the funded development agenda item that we're going to have to postpone from this meeting...
  232. Nov 04 13:24:53 <bryce> alright, I think that covers sponsorship level stuff for now
  233. Nov 04 13:24:58 <bryce> any other business?
  234. Nov 04 13:25:13 <prkos> got it
  235. Nov 04 13:27:17 <bryce> alright, guess that's a wrap
  236. Nov 04 13:27:19 <bryce> thanks all!
  237. Nov 04 13:27:31 <bryce> ============== EOM ==============
  238. Nov 04 13:27:32 <Tavmjong> Good night all!
  239. Nov 04 13:27:40 <prkos> thank you! nite!
  240. Nov 04 13:27:50 <tedg> 'night folks!
  241. Nov 04 13:28:13 <fguimont> good night.
  242. Nov 04 13:28:40 <rindolf> night.
 
 

52

 

1072

Board Meeting - November 4, 2016

-

PasteBin

Zeilen
242
Wörter
4367
Größe
24,6 KB
Erstellt
Unterversionen
5
Typ
text/x-irclog
Creative Commons Attribution Share-Alike 3.0 (CC-BY-SA 3.0)
Bitte melde Dich an, um einen Kommentar zu verfassen!