irc_meeting_2011-09-03.txt 26 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564
  1. <paroneayea> ****** Meeting logging now! ******
  2. <nyergler> lol
  3. <schendje> gmgbot` has no regard for schendje's feelings [11:02]
  4. <gmgbot`> schendje: Error: "has" is not a valid command.
  5. <paroneayea> we'll just have to use the copy-pasta route since I don't know
  6. what I'm doing
  7. <nyergler> gmgbot`: help
  8. <gmgbot`> nyergler: (help [<plugin>] [<command>]) -- This command gives a
  9. useful description of what <command> does. <plugin> is only
  10. necessary if the command is in more than one plugin.
  11. <paroneayea> gmgbot`: commands
  12. <nyergler> awesome
  13. <gmgbot`> paroneayea: Error: "commands" is not a valid command.
  14. <paroneayea> haha
  15. <paroneayea> ok
  16. <nyergler> ok, faking it
  17. <paroneayea> so
  18. <paroneayea> first of all [11:03]
  19. <paroneayea> nice, or should I say *amazing* job everyone on this release
  20. <paroneayea> I honestly do think it was our best month yet. It was certainly
  21. the month with the most fun screenshots in the press release at
  22. least
  23. * schendje claps
  24. <paroneayea> so
  25. <paroneayea> everyone pat themselves on the bat and feel good about themselves
  26. :) [11:04]
  27. <paroneayea> and then stop so we can continue with the meeting :)
  28. <paroneayea> so! this next month
  29. <paroneayea> I'm going to ramble for a second then open the floor [11:05]
  30. <paroneayea> basically we intend to try and get 0.1.0 out this month, and
  31. http://mediagoblin.com as a real example site next month, so
  32. <paroneayea> we need to wrap things up, though I feel like I've said "wrap
  33. things up" the last couple of meetings :)
  34. <paroneayea> I wrote out a vague outline of things that I knew I wanted to
  35. discuss to the list:
  36. <paroneayea> - Licensing support! [11:06]
  37. <paroneayea> - Wrap up 0.0.5 stragglers
  38. <paroneayea> - RDFa integration
  39. <paroneayea> - Caching integration
  40. <paroneayea> - More user experience testing and feedback integration!
  41. <paroneayea> - A new and updated website look and feel!
  42. <paroneayea> - Starting to work on multi-media support in the processing
  43. backend, if there's time?
  44. <paroneayea> - What else?!
  45. <paroneayea> - Surely there are things.
  46. <paroneayea> - ... http://mediagoblin.org/ redesign
  47. <paroneayea> oh
  48. <paroneayea> documentation is surely a thing
  49. <paroneayea> so I don't know where we want to start specifically
  50. <paroneayea> so I say let's do the website first :) [11:07]
  51. <paroneayea> schendje: ping! Presumably you're here
  52. <paroneayea> http://bugs.foocorp.net/issues/543 I just wrote this up, which
  53. includes ascii art mockups of the site
  54. <paroneayea> based on conversations in here last night
  55. <paroneayea> so I guess the big thing is, how do we intend to execute on this
  56. :) [11:08]
  57. <paroneayea> I'm opening the floor here btw
  58. <paroneayea> I'm also going to be traveling a bunch for work this month, so I
  59. think I'll need a lot of help directing this one [11:09]
  60. <paroneayea> no comments? :)
  61. <wctype_t> are the bills paid? :p [11:10]
  62. <paroneayea> wctype_t: the bills are paid :)
  63. <paroneayea> for mediagoblin.org at least
  64. <paroneayea> that's to speak nothing of mediagoblin.com ;) [11:11]
  65. <paroneayea> okay, so no serious comments, so I guess I hope we'll iterate on
  66. mockups on the ticket and jsut start pushing it forward
  67. <tychoish> in general my preference is for simpler, easier to read websites
  68. that aren't fussy. I think it's probably better to start with a
  69. list of what needs to be on mg.org that isn't there... and I'll put
  70. this in the ticket.
  71. <gullydwarf> Csrf needs attention
  72. <paroneayea> tychoish: ok great, that feedback is appreciated [11:12]
  73. <paroneayea> gullydwarf: yes, that's true
  74. <paroneayea> though that csrf ticket has turned from being "CSRF ticket" to
  75. "everything and the kitchen sink security" ticket
  76. <paroneayea> without any action items
  77. <gullydwarf> Don't want to get diaspora*-ed
  78. <nyergler> is the .org site static HTML? it's own python app? (sorry for the
  79. n00b question)
  80. <paroneayea> nyergler: not a n00b question
  81. <paroneayea> it's pyblosxom :)
  82. <paroneayea> rendering to static HTML [11:13]
  83. <nyergler> ok, cool
  84. <paroneayea> for ultimate laziness
  85. <paroneayea> I actually wrote up a wiki page on how to mess with it
  86. <schendje> oh, sorry, my client doesn't ping me :(
  87. <paroneayea> http://wiki.mediagoblin.org/Update_the_website
  88. <paroneayea> np schendje :)
  89. <nyergler> (i assume we'll loop back around to CSRF, since that sounds
  90. important for an 0.1
  91. <nyergler> )
  92. <paroneayea> nyergler: yes let's get to that in a second :) [11:14]
  93. <paroneayea> schendje: so, transforming my ascii art shittiness into real
  94. mockups
  95. <paroneayea> iirc school's starting for you so you're getting busy but
  96. <schendje> paroneayea: I think I can handle that :)
  97. <paroneayea> cool, I've been thinking maybe the design could actually be more
  98. like your original mediagoblin mockups
  99. <paroneayea> still dark themed, similar to what we have, but more assertive
  100. <paroneayea> as it's marketing materials [11:15]
  101. <paroneayea> cool
  102. <schendje> well we've certainly got a lot more freedom, so that's fun
  103. <paroneayea> look forward to seeing those then :)
  104. <paroneayea> yeah
  105. <paroneayea> great
  106. <schendje> will it be translated, btw?
  107. <schendje> or English only?
  108. <paroneayea> schendje: unfortunately likely not
  109. <paroneayea> we might handle that at a future time
  110. <paroneayea> for now static html that we barely have to maintain is best
  111. <schendje> paroneayea: well for the design that's actually a lot easier ;)
  112. <paroneayea> yeah
  113. <paroneayea> ok :)
  114. <paroneayea> schendje: I'm assigning the ticket to you then
  115. <schendje> sounds good! [11:16]
  116. <paroneayea> comments in the ticket from people generally are welcome
  117. <schendje> yeah so I think I'll just keep updating that one
  118. <paroneayea> great
  119. <schendje> and everyone can comment on mockups when they want
  120. <paroneayea> assigned :)
  121. <paroneayea> sounds perfect
  122. <paroneayea> ok!
  123. <paroneayea> so CSRF :)
  124. <paroneayea> gullydwarf: ^^
  125. <gullydwarf> Present
  126. <paroneayea> so honestly I think we should probably split out a new ticket
  127. that's actually CSRF only since the old one is confusing maybe?
  128. [11:17]
  129. <paroneayea> regardless, someone should take the lead on actually acting on
  130. *csrf* this month.
  131. <nyergler> what's the existing ticket?
  132. <paroneayea> volunteers? I'd love to see something like the lazy-csrf stuff
  133. django has
  134. <nyergler> found it, 361
  135. <paroneayea> yes good question
  136. <paroneayea> oh it's not as bad as I remember the ticket being :) [11:18]
  137. <paroneayea> still a lot of non-csrf-activity :)
  138. <paroneayea> so I haven't used it since it was after I stopped really using
  139. django but
  140. <paroneayea> I hear https://docs.djangoproject.com/en/dev/ref/contrib/csrf/ is
  141. really great and easy to use
  142. <nyergler> i think it'll take a bit for me to dig through this, but i'm happy
  143. to work on CSRF-ness
  144. <paroneayea> nyergler: great!
  145. <gullydwarf> Sweet!
  146. <nyergler> i've done some of it for ye-olde-daye-jobe
  147. <nyergler> and we're dealing with both Django and non-Django there [11:19]
  148. <paroneayea> I obviously don't want to use django's but just an idea of doing
  149. something similarly easy
  150. <gullydwarf> Even better
  151. <paroneayea> got it
  152. <paroneayea> great
  153. <paroneayea> nyergler: could you register on the tracker and I'll mark you in
  154. the hacker group
  155. <paroneayea> then I can assign it to you
  156. <paroneayea> nyergler: thanks :)
  157. <nyergler> i suspect i'll have stupid questions, but i think paroneayea is
  158. probably used to answering those from me :)
  159. <nyergler> i just registered (nyergler, naturally)
  160. <paroneayea> nyergler: it'll be payback for ~2 years of dumb questions from me
  161. when you were my boss [11:20]
  162. <nyergler> i was thinking i was the one asking dumb questions then ;)
  163. <paroneayea> we'll make it even, we were both dumb
  164. <nyergler> sweet
  165. <gullydwarf> K, driving home now
  166. <paroneayea> ok, assigned to you [11:21]
  167. <tychoish> everyone's dumb. the world goes on.
  168. <paroneayea> gullydwarf: don't IRC an drive! :)
  169. <paroneayea> gullydwarf: we can talk more later if there are things you want
  170. to follow up on
  171. <paroneayea> okay, so other things
  172. <paroneayea> docs!
  173. <paroneayea> that's a big one
  174. <paroneayea> tychoish: ^^^^
  175. <paroneayea> :)
  176. <paroneayea> unfortunately willkg is not here :(
  177. <paroneayea> I really wanted him to be part of this meeting for that, but
  178. <paroneayea> oh well [11:22]
  179. <Elrond> Evening!
  180. <paroneayea> tychoish: a pretty clear first action item for the docs is
  181. homogenizing all the "hacking howto" type pages
  182. <paroneayea> or at leas splitting them up and making them clear
  183. <paroneayea> tychoish: presumably I should write up a ticket on that and
  184. assign to you?
  185. <paroneayea> hiya Elrond :) [11:23]
  186. <paroneayea> everyone's favorite elvenlord has joined the party.
  187. <tychoish> those are the pages in the wiki about how to get started with the
  188. hacking?
  189. <paroneayea> yes
  190. <tychoish> ok. yeah.
  191. <paroneayea> tychoish: there's even an old .rst version of it back in the git
  192. history :)
  193. <paroneayea> even a version still un-deleted from the site ;)
  194. <Elrond> paroneayea - :-))) Except only few people bow. ;o) [11:24]
  195. <paroneayea> http://docs.mediagoblin.org/hackinghowto.html
  196. <tychoish> lightweight markup is fungable
  197. <paroneayea> tychoish: great, you want to write up the ticket for that or
  198. should I?
  199. <paroneayea> tychoish: I also wonder about other things that should be done
  200. docs-wise. Are there things you need from me to plow ahead?
  201. <tychoish> is the version in rst different from the ones in the wiki?
  202. <paroneayea> tychoish: the wiki ones have been updated a bit [11:25]
  203. <tychoish> ok,
  204. <paroneayea> OSX and distro instructions improvements, possibly some other
  205. stuff
  206. <nyergler> tangential question: if i'm getting started with dev, and find
  207. things that are out of date, should i edit the wiki? email the
  208. devel list?
  209. <tychoish> depends on which things, I guess.
  210. <paroneayea> nyergler: editing is good, and pinging on IRC is great
  211. <nyergler> great, thanks
  212. <paroneayea> usually we can coordinate... I always seem to not be far away
  213. from my desktop :P [11:26]
  214. <tychoish> if people can tell me what's up and what needs to be changed, I'll
  215. make tickets.
  216. <tychoish> I'm not always here, but logging happens, email's good too.
  217. <tychoish> my main questions are: 1) how does the docs.mediagoblin get
  218. published
  219. <paroneayea> tychoish: cronjob :) [11:27]
  220. <tychoish> the poor man's daemon
  221. <paroneayea> every half hour or so, git pull and sphinx make
  222. <tychoish> awesome.
  223. <paroneayea> yup
  224. <paroneayea> it runs whatever's in master presently
  225. <tychoish> 2. are we still comfortable with docs/ being in the source code
  226. repo?
  227. <paroneayea> tychoish: I'm comfortable with it, yes [11:28]
  228. <tychoish> sweet.
  229. <paroneayea> we can consider moving it, but if so let's do it at a later time
  230. when willkg is also here
  231. <paroneayea> I think it's fine there for now though
  232. <tychoish> of course, I don't mind, but I don't want it to irritate you/other
  233. people
  234. <tychoish> so just tracking that.
  235. <paroneayea> I'm happy with it where it is.
  236. <paroneayea> is there a 3) ? :)
  237. <tychoish> yeah, just everyone should open tickets and assign them to me for
  238. documentation bugs, or things that they think needs to be
  239. documented or better documented. [11:29]
  240. <Elrond> Is the meeting already over or are we currently at the "docs" topic?
  241. <paroneayea> Elrond: on "docs"
  242. <paroneayea> tychoish: ok, I'll try to review things and send more issues your
  243. way later today [11:30]
  244. <paroneayea> and you write up the hacking howto ticket
  245. <paroneayea> sounds good?
  246. <tychoish> until I get more up to speed I kinda need to depend on folks to set
  247. my agenda :)
  248. <tychoish> yep
  249. <tychoish> sounds good.
  250. <Elrond> Okay, I'll wait for the next topic then. :)
  251. <paroneayea> ok
  252. <tychoish> i'm done. :)
  253. <paroneayea> next topic! :)
  254. <paroneayea> caching
  255. <paroneayea> well this one's on my plate
  256. <paroneayea> Elrond says I should just merge it now without tests ;)
  257. <paroneayea> though honestly we're not far away from that
  258. <paroneayea> it should be done this weekend
  259. <paroneayea> I'm not sure there's more to say about it [11:31]
  260. <paroneayea> unless people have questions, let's move on
  261. <paroneayea> - More user experience testing and feedback integration!
  262. <Elrond> paroneayea - IF it doesn't break anything. That's on the "doesn't
  263. hurt, might even help. Maybe someone else will write tests. Or
  264. someone else will start using it and find issues".
  265. <paroneayea> Elrond: it doesn't break anything
  266. <paroneayea> it just sits on the side [11:32]
  267. <paroneayea> minding its own business
  268. <paroneayea> twiddling its thumbs
  269. <Elrond> merge it. leave ticket open for tests.
  270. * nyergler wonders what the test coverage is like right now as a whole
  271. <Elrond> next topic.
  272. <paroneayea> nyergler: good question ;)
  273. <paroneayea> nyergler: probably not great
  274. <nyergler> ok, fair enough
  275. <paroneayea> nyergler: we have tests for submission (including evil
  276. submissions) and auth stuff and most of the components
  277. <paroneayea> config stuff, storage system, etc [11:33]
  278. <paroneayea> most of the components have test
  279. <nyergler> sounds like a great start
  280. <paroneayea> but not all
  281. <paroneayea> plenty of views don't have tests
  282. <paroneayea> but most of the ones that worry me about evil things happening
  283. <paroneayea> do
  284. <Elrond> I think, test coverage is fine currently.
  285. <paroneayea> it could always be better ;) [11:34]
  286. <paroneayea> but yeah not bad for now
  287. <Elrond> non user facing things need tests! And the most important ones have.
  288. <paroneayea> true
  289. <paroneayea> okay
  290. <paroneayea> - Licensing support!
  291. <Elrond> user facing stuff... is tested by users. ;o)
  292. <paroneayea> So actually I'm prototyping a tool at work-ish about this
  293. <paroneayea> I'd actually like to discuss it with nyergler later more
  294. <paroneayea> I don't know if I'll have time to finish it by this release :(
  295. <paroneayea> but I'll try
  296. <nyergler> this is a tool for license selection? [11:35]
  297. <paroneayea> nyergler: yes
  298. <paroneayea> we could do it the cheap way for now :)
  299. <Elrond> Does that also include the selection of harmless-ness?
  300. <paroneayea> Elrond: whaa
  301. <nyergler> right -- i was going to ask if we had schema support for license
  302. <Elrond> (good for everyone, not good for children, bad for everyone)
  303. <nyergler> i suspect the answer is "yes" since we're mongo and the answer is
  304. always yes
  305. <nyergler> :)
  306. <nyergler> Elrond: that seems like a different flag
  307. <paroneayea> nyergler: yeah we just need to add a field to the MediaEntry
  308. thing that has 'license' [11:36]
  309. <paroneayea> and have it point at URLs.
  310. <Elrond> nyergler - It is.
  311. <paroneayea> I think generally the solution mlinksva and I have been
  312. discussing is the value of the license field is actually the URL,
  313. and maybe somewhere else in the application is info about that
  314. license based on its url
  315. <nyergler> of course
  316. <nyergler> we could probably get the field into MediaEntry and add static
  317. support for the core 6 [11:37]
  318. <paroneayea> and the tool I'm talking about is just auto-jsonifying it using
  319. rdfa profiles
  320. <paroneayea> but yeah
  321. <nyergler> iterate on that for adding support for all variants, etc
  322. <paroneayea> we don't need that tool for 0.1.0 yet
  323. <paroneayea> we could just do it manually
  324. <paroneayea> that makes no sense what I just said without context maybe
  325. <nyergler> :)
  326. <nyergler> is there a ticket for license support? [11:38]
  327. <paroneayea> nyergler: I don't think so
  328. <paroneayea> nyergler: do you want to write one up maybe?
  329. <paroneayea> :)
  330. <paroneayea> or I can after the meeting.
  331. <paroneayea> and you can comment on it
  332. <nyergler> happy to do it
  333. <paroneayea> great
  334. <paroneayea> I also have as an issue for this meeting
  335. <paroneayea> - RDFa integration
  336. <paroneayea> and now that nyergler is here I might be not the only
  337. #mediagoblin participant who cares about that anymore ;) [11:39]
  338. <Elrond> I would like to add "- database schema (I have some feelings there!)"
  339. to the end of the topic list, either for public discussion or private
  340. discussion after the meeting.
  341. <paroneayea> Elrond: is this about non-mongodb support :)
  342. <Elrond> paroneayea - No.
  343. <paroneayea> Elrond: oh, what is it then?
  344. <paroneayea> I'm curious
  345. <nyergler> paroneayea: i definitely care about it, not sure i know enough
  346. about GMG to comment at the moment [11:40]
  347. <Elrond> paroneayea - Let's postpone this until that topic is there. :-)
  348. Don't want to disturb now.
  349. <paroneayea> okay
  350. <paroneayea> nyergler: honestly I care about it but it's pretty low priority
  351. for 0.1.0 maybe comparatively
  352. <nyergler> i suggest we create a ticket for basics
  353. <paroneayea> nyergler: yeah
  354. <paroneayea> though honestly
  355. <nyergler> title, creator, pub date
  356. <paroneayea> it's pretty easy.
  357. <paroneayea> yup
  358. <nyergler> right
  359. <paroneayea> nyergler: could you make that ticket too ;) [11:41]
  360. <paroneayea> haha
  361. <nyergler> this is payback, isn't it
  362. <nyergler> sure
  363. <nyergler> ;)
  364. <paroneayea> :)
  365. <paroneayea> great
  366. <paroneayea> - More user experience testing and feedback integration!
  367. <paroneayea> this is a thing I really care about but none of the people who
  368. have been working on it are present at this meeting I think.
  369. <paroneayea> but basically we need to turn those UX testing reports into real
  370. bugs [11:42]
  371. *** gullydwarf_ (~vdfc@50.15.244.85) has joined channel #mediagoblin
  372. <paroneayea> heya gullydwarf_
  373. <gullydwarf> Home :)
  374. <paroneayea> horray
  375. <Elrond> paroneayea - I have some private UX testing going on omgmg.*. I will
  376. try to make bugs from this.
  377. <paroneayea> I just brought up user experience testing
  378. <gullydwarf_> sweet home
  379. <Elrond> Two gullydwarf? One isn't enough? ;) [11:43]
  380. <paroneayea> people have started writing things on the wiki, we should turn
  381. them into bugs, but I'm not sure if there should be a process for
  382. that
  383. <paroneayea> Elrond: :)
  384. <gullydwarf_> Elrond: :-))
  385. <schendje> we should probably read Jan's paper ;)
  386. * paroneayea wonders if joar is lurking :)
  387. <paroneayea> schendje: yes I think so
  388. <paroneayea> schendje: I'll talk to him about how to go about transforming
  389. those reports into bugs
  390. <paroneayea> he would know if anyone would.
  391. <schendje> yep
  392. * paroneayea files into orgmode [11:44]
  393. <paroneayea> ok :)
  394. <paroneayea> will do.
  395. <paroneayea> also, thank you thank you gullydwarf_ for starting omgmg :)
  396. <Elrond> paroneayea - I would at least say: If someone went over one report
  397. and turned it into bugs, that someone should put links to the bugs at
  398. the end of the report, so that one can follow, what happens, etc.
  399. <gullydwarf_> paroneayea: you bet
  400. <gullydwarf_> I feel bad about yesterday
  401. <paroneayea> gullydwarf_: don't.
  402. <gullydwarf_> and well compensated for my time, btw :)
  403. <paroneayea> gullydwarf_: it was a good lesson and experience :) [11:45]
  404. <gullydwarf_> it always sucks when someone has to come in and clean up your
  405. own mess :/
  406. *** mlinksva (~mlinksva@adsl-76-200-160-216.dsl.pltn13.sbcglobal.net) has
  407. joined channel #mediagoblin
  408. <paroneayea> gullydwarf_: don't apologize, thanks for working with me on it
  409. <gullydwarf_> but I am using it as a learning exp, you're correct
  410. <paroneayea> oh hey mlinksva !
  411. <paroneayea> now there are 3 people who care about the rdfa issue :)
  412. <nyergler> wow, i'm feeling all nostalgic
  413. <paroneayea> :)
  414. <Elrond> nyergler - Why do you feel nostalgic? [11:46]
  415. <paroneayea> mlinksva: was nyergler's boss/coworker, is mine
  416. <paroneayea>
  417. <nyergler> paroneayea, mlinksva, and I used to work together at CC
  418. <paroneayea> yeah
  419. <Elrond> Ahh.
  420. <paroneayea> and nyergler used to be my boss ;)
  421. <paroneayea> okay [11:47]
  422. <paroneayea> - Starting to work on multi-media support in the processing
  423. backend, if there's time?
  424. <paroneayea> I'm not sure I'll get to this [11:48]
  425. <paroneayea> probably realistically post-0.1.0
  426. <nyergler> i suggest we punt
  427. *** gullydwarf (~AndChat@173-147-118-171.pools.spcsdns.net) has quit: Quit:
  428. Bye
  429. <Elrond> I'd vote for post-0.1 too.
  430. <paroneayea> but we're getting close to an infrastructure that we will support
  431. that
  432. <paroneayea> yeah
  433. <paroneayea> ok :)
  434. <paroneayea> let's ignore that entirely
  435. <paroneayea> ignoreeed!
  436. <paroneayea> I guess all tehre is to talk about then is 0.0.5 stragglers, or
  437. anything else people intend to raise!
  438. * paroneayea links http://bugs.foocorp.net/projects/mediagoblin/roadmap
  439. [11:49]
  440. <paroneayea> oh, I'd really like to wrap up http://bugs.foocorp.net/issues/296
  441. <paroneayea> because i think it's risky with this not working as-is
  442. <paroneayea> it makes dumb assumptions
  443. <paroneayea> for example, it would totally do the wrong thing on joar's site.
  444. <paroneayea> most of the rest of the things on that list I'm not sure I care
  445. to comment on [11:50]
  446. <paroneayea> except that things like tag clouds and etc are maybe not so easy
  447. to do until we figure out if we want to outsource those tasks to
  448. celery or mapreduce
  449. * paroneayea hates using mapreduce unless necessary
  450. <paroneayea> in this case, probably necessary
  451. <paroneayea> but I don't think it's a critical 0.0.5 feature [11:51]
  452. <paroneayea> okay I'm done bringing things up
  453. <paroneayea> anyone else have things?
  454. * gullydwarf_ is looking through the roadmap
  455. <nyergler> is willkg working on 296?
  456. <gmgbot`> *NEWS* issues: Feature #544 (New): Basic content license support
  457. <paroneayea> nyergler: realistically I think no :\
  458. <paroneayea> he's swamped with migrating the bug tracker off of foocorp onto
  459. redmine
  460. <paroneayea> and a bunch of other things
  461. <paroneayea> we don't have a db dump so he wrote an html scraping library
  462. [11:52]
  463. <nyergler> foocorp isn't running redmine? (can't tell what it is)
  464. <nyergler> w.t.f.?
  465. <gullydwarf_> paroneayea: what do you think about me claiming
  466. http://bugs.foocorp.net/issues/357 for refactoring?
  467. <nyergler> can not wait to hear this story :)
  468. <paroneayea> nyergler: yes we can discuss later ;)
  469. <paroneayea> gullydwarf_: claim it!
  470. <paroneayea> please! [11:53]
  471. <gullydwarf_> done :)
  472. <paroneayea> ok
  473. <paroneayea> so after I wrap up the caching thing, I wonder if I have major
  474. things to do this month
  475. <paroneayea> besides a lot of triaging and management and site redesign and
  476. etc :) [11:54]
  477. <nyergler> sounds like you have major things to do this month :)
  478. <Elrond> - buy mediagoblin.com
  479. <Elrond> - Make business plan. ;o)
  480. <paroneayea> Elrond: already bought it
  481. <paroneayea> Elrond: for $200 :p
  482. <paroneayea> someone had it.
  483. <Elrond> Oh, yuck. [11:55]
  484. <paroneayea> Elrond: well anyway, yes, we're working on that also.
  485. <Elrond> - Add features to GMG for mediagoblin.com business plan. ;)
  486. <paroneayea> oh!
  487. <paroneayea> there is one!
  488. <paroneayea> I can't believe I forgot
  489. <paroneayea> captchas.
  490. <schendje> - Gather and sell people's data to advertisers
  491. <paroneayea> or similar.
  492. <gullydwarf_> schendje: :)
  493. <paroneayea> schendje: hehe [11:56]
  494. <Elrond> schendje - Oh, yeah. ;)
  495. <Elrond> proper freemium plan.
  496. <Elrond> (or whatever that is spelled)
  497. <paroneayea> well
  498. <paroneayea> captchas though for serious.
  499. <paroneayea> I don't know what to do about this
  500. <nyergler> paroneayea: captchas for the signup page?
  501. <paroneayea> yes
  502. <paroneayea> just for registration
  503. <paroneayea> we'll likely need them
  504. <paroneayea> I hate using recaptcha because of the centralization aspect
  505. [11:57]
  506. <paroneayea> but honestly all existing captcha solutions suck :\
  507. <paroneayea> for python
  508. <Elrond> recaptcha is easy, I think. It's just a very good mind mood testing
  509. thing.
  510. <paroneayea> we could probably integrate a "shitty recaptcha hack" into
  511. mediagoblin for now
  512. <paroneayea> and have an open ticket for non-evil-centralized captchas.
  513. <paroneayea> and maybe make a library for it. [11:58]
  514. <Elrond> Hmm, yeah.
  515. <nyergler> right -- just make sure you can yank it out once we know what the
  516. decentralized version is :)
  517. <paroneayea> yeah
  518. <Elrond> Just ask people a math question. ;o)
  519. <paroneayea> Elrond: computers will never solve those!
  520. <Elrond> Like "integrate ln(x) from 1 to x" ;o)
  521. <nyergler> ok, i need to drop off shortly, anything else i can help with at
  522. the moment, paroneayea?
  523. <gullydwarf_> +1 math, something you can plug into wolfram alpha
  524. <paroneayea> nyergler: I think you've volunteered for plenty, and excited
  525. about you jumping on board :) [11:59]
  526. <gullydwarf_> hrm, maybe not
  527. * paulproteus waves to nyergler!
  528. <paroneayea> gullydwarf_: that would be a great solution if we wanted a
  529. bot-only site
  530. <Elrond> We could also do chemistry questions. ;o)
  531. <paroneayea> keep the humans out!
  532. * gullydwarf_ bye nyergler!
  533. <nyergler> wow, it is old home day on #mediagoblin
  534. <gullydwarf_> paroneayea: indeed
  535. <nyergler> tty soon
  536. <paroneayea> later :)
  537. <paroneayea> okay :) [12:00]
  538. <paroneayea> looks like we've wrapped up then with some good action items for
  539. the month :)
  540. <Elrond> :-)
  541. <gullydwarf_> paroneayea: oh [12:01]
  542. <gullydwarf_> any new thoughts on federation?
  543. <gullydwarf_> we seem to be about where we were last month
  544. <paroneayea> gullydwarf_: my thoughts are "we work out a plan first thing
  545. after 0.1.0 is out the door" :)
  546. <gmgbot`> *NEWS* issues: Feature #545 (New): Add RDFa to HTML output ||
  547. Feature #357: "Lost password?" functionality ("Change password"
  548. functionality possibly embedded i...
  549. <gullydwarf_> and the month before ...
  550. <Elrond> - db schema: I feel MediaEntry gets added fields like mad. "Oh, we
  551. need x, it has something vaguely to do with some MediaEntey, add it
  552. there." I don't like that. Lately the processing errors. They're in
  553. every entry, but only needed *while* processing or for error cases.
  554. <paroneayea> 0.1.0 is supposed to be "the last pre-federation-work" branch
  555. <gullydwarf_> paroneayea: sounds good
  556. <paroneayea> that's one reason why I said this month's should be 0.0.5 instead
  557. of 0.1.0
  558. <paroneayea> ok :) [12:02]
  559. <paroneayea> I'm going to go press my french press
  560. <paroneayea> and drink some coffee
  561. <paroneayea> thanks all
  562. <paroneayea> great meeting!
  563. <paroneayea> ******* END LOGGING! ********