Skip to content

Meeting 2016 07 15

Jump to bottom Edit New page
larjona edited this page Jul 23, 2016 · 3 revisions

Call for meeting

Friday 2016/07/15 at 20:00 UTC Pumpit.info down :(

Meeting moved to Friday 2016/07/22 20:00 UTC Meeting moved 1h before, held in two phases, 19:00 to 19:30, and then 20:00 UTC.

Agenda

Feel free to add to this before the meeting!

  • Conservancy Application: last comments and send!
  • Pump.io code development
  • Release of 1.0, and Roadmap
  • Release procedure (e.g. signing?)
  • Anti-XSS
  • View partials (if we have time)
  • databank-disk is not on npm
  • Community governance and sustainability
  • Node adoption (sponsoring, administering)
  • Adoption of non-node related websites (e.g. OpenFarmGame, ih8.it)
  • Governance (non-profit status/application)
  • Funding
  • Other stuff

Summary

Log

[21:05:50] <larjona> #############################################################

[21:05:53] <larjona> BEGIN LOG

[21:05:53] <larjona> #############################################################

[21:06:04] <larjona> Dear all, welcome to this Publicity team meeting!

[21:06:04] <larjona> Agenda is here:

[21:06:25] <evanpro> Cool

[21:06:27] <larjona> https://github.com/e14n/pump.io/wiki/Meeting-2016-07-15

[21:07:01] <larjona> First, roll call,

[21:07:04] <larjona> who's here?

[21:07:09] <evanpro> me

[21:07:15] -*- larjona is here obviously

[21:07:21] <strugee> me

[21:09:48] <strugee> shall we talk about Conservancy first?

[21:10:04] <evanpro> Yes

[21:10:09] <evanpro> larjona: are you chairing the meeting?

[21:10:26] <evanpro> I assume

[21:10:55] -*- larjona just sent a note in pump about having the meeting now.

[21:10:55] <larjona> ok

[21:10:55] <larjona> yes

[21:11:02] <larjona> TOPIC: Conservancy application

[21:11:09] <evanpro> Ah great

[21:11:50] <strugee> cool

[21:11:56] <strugee> larjona: I think you know the most about this?

[21:12:29] <larjona> yes

[21:12:29] <larjona> I have quite a big lag, sorry

[21:12:47] <larjona> the application is here: https://github.com/e14n/pump.io/wiki/Conservancy-application

[21:12:53] <larjona> and IMO it's ready for sending

[21:13:04] <evanpro> larjona: I've looked it over

[21:13:26] <larjona> and? anything we need to fix/improve?

[21:13:44] <evanpro> It seems complete to me

[21:13:50] <strugee> \o/

[21:13:59] <evanpro> There are a couple of things I'd want to consider though

[21:14:00] <evanpro> In section 10

[21:14:18] <larjona> 10: how do you expect to spend funds

[21:14:18] <larjona> that you raise? etc etc

[21:14:35] <evanpro> We say that the funds would go to community infrastructure, developer time, and promotion

[21:14:35] <larjona> well, I'll copy the whole question

[21:14:40] <larjona> for the sake of the log:

[21:14:41] <larjona> 10 *** Going forward, once inside Conservancy, how do you expect to spend funds

[21:14:41] <larjona> that you raise? What types of activity do you want to ask Conservancy to

[21:14:41] <larjona> take on your behalf? Where geographically do you want those activities

[21:14:41] <larjona> to take place?

[21:14:42] <pumabot> http://i.imgur.com/e4BsPLu.jpg

[21:14:59] <evanpro> I wonder if we could change the order of that

[21:15:21] <evanpro> Running community servers is kind of an unusual thing for a FLOSS project to do

[21:15:54] <evanpro> Maybe instead say: fund developer time, promote project, cover costs of community infrastructure "as needed"

[21:16:15] <larjona> Sounds good to me

[21:16:19] <strugee> |1

[21:16:24] <evanpro> I think that's more typical of FLOSS project priorities

[21:16:26] <strugee> s/|1/+1/

[21:17:28] -*- strugee edits the wiki page

[21:17:29] <evanpro> Other than that...

[21:17:40] <larjona> done

[21:17:49] <evanpro> For #11, I am willing to participate in fundraising efforts

[21:17:49] <pumabot> [#11] Post image in Web UI https://github.com/e14n/pump.io/issues/11

[21:17:57] <strugee> heh. nvm

[21:18:00] <evanpro> ha ha

[21:18:13] <evanpro> Besides that, it seems pretty straightforward

[21:18:19] <evanpro> What is the next step? Should I send this in?

[21:18:25] <strugee> I'd like to add a +1 for participating in Conservancy fundraising

[21:18:29] <evanpro> Or would you do it, larjona?

[21:18:49] <larjona> wait

[21:19:29] <larjona> how should we word the answer for 11? "We are willing to participate in fundraising efforts" ?

[21:19:44] <evanpro> Yes

[21:19:47] <evanpro> That's probably good enough

[21:19:58] <evanpro> I don't think it has to be exactly who is willing to do it

[21:20:16] <larjona> Ok

[21:20:27] <larjona> We still need to add some more names in the question 24

[21:20:36] <strugee> ok

[21:20:52] <strugee> we can take care of that after this meeting, though, right?

[21:21:01] <strugee> I'd like to do code before evanpro has to go :)

[21:21:03] <evanpro> Good

[21:21:09] <evanpro> OK, great, let's do that

[21:21:16] <larjona> because we have more committers, but they are not active or they didn't do it themselves, so I'm a bit reluctant

[21:21:31] <larjona> I can add them later, no problem in doing the task

[21:21:36] <strugee> larjona: I can go through and reach out to them too

[21:21:37] <pumabot> http://i.imgur.com/9dNlOik.jpg

[21:21:43] <larjona> but I'm not sure if it's good to add somebody without their permission

[21:22:12] <strugee> we can probably get contact info from commit emails

[21:22:17] <larjona> (maybe add a note: old committer - we're not sure about their current involvement"

[21:22:46] <larjona> This is a social question. There is no problem in finding the data, I can find it in the git log

[21:22:57] <strugee> sounds good

[21:23:05] <strugee> so, can we move on to code?

[21:23:06] <evanpro> That's a great way to do it

[21:23:10] <evanpro> +1

[21:23:13] <larjona> ok, so

[21:23:29] <evanpro> Umm, can we say "larjona to do finishing touches and submit this application"?

[21:23:29] <larjona> I'll finish 24 and send to evanpro a "clean" copy, so he can send to conservancy

[21:23:35] <evanpro> I say yes

[21:23:38] <evanpro> OK, I will send it

[21:23:46] <larjona> I think you should send it, evanpro , because you applied

[21:23:51] <evanpro> Just send it to me by email when it's ready

[21:23:53] <larjona> ok

[21:23:56] <evanpro> larjona: fair point!

[21:23:57] <evanpro> OK let's talk code

[21:23:59] <larjona> so let's move

[21:24:16] <larjona> strugee your turn!

[21:24:27] <strugee> awesome!

[21:24:33] <strugee> so

[21:24:38] <larjona> TOPIC: Pump.io code development

[21:24:44] <strugee> we're very, very close to being able to release 1.0

[21:25:04] <strugee> there's just #1169

[21:25:04] <pumabot> [#1169] New HTML cleanup in post contents is too extreme https://github.com/e14n/pump.io/issues/1169

[21:25:14] <evanpro> OK

[21:25:26] <evanpro> So here's my thought on this matter

[21:26:09] <evanpro> I think it's unfair for the server to defer cleanup to the clients

[21:26:39] <evanpro> If you have multiple clients, the chance that one of them fails to do the sanitization correctly goes to 100% pretty quickly

[21:27:14] <evanpro> So I don't think that the API should serve unsanitized HTML

[21:27:34] <strugee> my feelings are the same although oshepherd suggested that that violates spec

[21:27:35] <strugee> https://github.com/e14n/pump.io/issues/1169#issuecomment-223550450

[21:28:17] <strugee> also, we can't allow <style> tags unless we embed a full-blown CSS parser in the scrubber

[21:28:38] <strugee> is that OK? note that existing clients, specifically Dianara (hi Jan!) use <style> pretty extensively

[21:30:37] <larjona> is embedding a full-blown CSS parser something possible+easy+elegant?

[21:30:38] <evanpro> Is there anything we can use to sanitize the <style> or style="..." ?

[21:30:58] <strugee> yes

[21:31:00] <strugee> a CSS parser

[21:31:22] <evanpro> https://www.npmjs.com/package/html-css-sanitizer

[21:31:29] <strugee> I think it should be ok but I wanted to double-check because it's a large new dependency

[21:31:58] <evanpro> https://www.npmjs.com/search?q=caja

[21:32:12] <evanpro> It seems like there are a lot of packages that re-package caja

[21:32:12] <strugee> evanpro: will look into that

[21:32:26] <strugee> but generally speaking is that the direction you want to go? allow <style> and sanitize its contents?

[21:33:08] <evanpro> Well, it's clearly important to at least one client developer

[21:33:35] <evanpro> if it's possible without too much hassle I'd prefer it

[21:33:50] <strugee> sounds good

[21:34:02] <strugee> so, I'll fix that up and then release 1.0.0 :)

[21:34:07] <strugee> also

[21:34:19] <strugee> #1170

[21:34:20] <pumabot> [#1170] Switch from utml to Jade https://github.com/e14n/pump.io/pull/1170

[21:34:35] <strugee> I switched over all the templates to Jade in a branch and basic web UI functionality is working

[21:34:36] <strugee> however

[21:34:52] <evanpro> strugee: oh cool

[21:35:03] <strugee> I haven't gotten it to work entirely because of all the logic in the web UI to handle utml partials

[21:35:05] <evanpro> Did you do the jade on the client too?

[21:35:10] <evanpro> Oh :(

[21:35:35] <strugee> yeah honestly I was going to ask you about this but I've forgotten the details so may email instead

[21:35:37] <evanpro> You mean how it compiles the UTML and re-uses it? Or how it re-uses components?

[21:35:39] <strugee> it's very, very close to working

[21:35:43] <evanpro> OK, sounds good

[21:35:43] <-- pacovila left (Read error: Connection reset by peer)

[21:36:08] <evanpro> I'd suggest maybe releasing 1.0.0 with utml and make changing to Jade the first thing to do after

[21:36:15] <evanpro> It'd be a pretty big change just before the release

[21:36:29] <strugee> basically this kind of stuff: https://github.com/e14n/pump.io/blob/master/public/javascript/pump/view.js#L275

[21:36:31] <strugee> evanpro: that's the plan

[21:36:39] <strugee> anyway, I'll email you

[21:36:55] <strugee> one more small thing: databank-disk isn't on npm

[21:37:22] <strugee> I installed via npm install e14n/databank-disk and it worked fine, so I think you should be fine just doing npm publish

[21:37:38] <evanpro> Oh, really?

[21:37:48] <evanpro> I think it was broken for 0.10 or 0.12

[21:37:56] <evanpro> The locking dependency didn't work

[21:38:05] <strugee> really? ok

[21:38:23] <strugee> if you don't mind me publishing it I'll check it out and then push it up

[21:38:28] <evanpro> OK, sounds good to me

[21:38:33] --> pacovila (~fravd@176.10.77.169) se ha unido a #pump.io

[21:38:39] <evanpro> Unfortunately I have to run

[21:38:44] <evanpro> See you all next month, thanks for everything

[21:38:48] <larjona> For the release we'll need to modify http://pump.io/

[21:38:48] <strugee> ok

[21:38:51] <strugee> evanpro: thanks!

[21:38:54] <larjona> thanks evanpro

[21:39:01] <strugee> larjona: I can take care of that

[21:39:02] <-- evanpro (~evan@modemcable098.74-70-69.static.videotron.ca) ha dejado #pump.io

[21:39:05] <larjona> ah, perfect

[21:39:41] <larjona> one small thing about that page: its mobile view does not show the "try it" button, so people in the mobile visit and then don't know what to do

[21:40:09] <strugee> ok

[21:40:18] <larjona> strugee, my proposal would be to create a "checklist" wiki page for the release

[21:40:24] <strugee> sounds good

[21:41:21] <strugee> I'll do that

[21:41:31] <larjona> Fine

[21:41:58] <larjona> anything else? Or do we finish here and we reopen meeting at 20:00UTC?

[21:42:06] <strugee> ah yeah I see what you're talking about re: Try It button

[21:42:08] <strugee> I'll fix that

[21:42:13] <strugee> I don't have anything else

[21:42:31] <larjona> Ok so I'll end the log now, and reopen later

[21:42:41] <strugee> sounds good. thanks for chairing, as always!

[21:42:43] <strugee> larjona++

[21:42:43] <pumabot> larjona has 9 points

[21:42:49] <larjona> #############################################################

[21:42:49] <larjona> END LOG

[21:42:49] <larjona> #############################################################

[22:01:45] <larjona> #############################################################

[22:01:47] <larjona> BEGIN LOG

[22:01:48] <larjona> #############################################################

[22:03:22] <larjona> Dear all, welcome to the second part of this Pump.io community meeting!

[22:03:22] <larjona> Agenda is here:

[22:03:22] <larjona> https://wiki.debian.org/Teams/Publicity/Meetings/2016-07-22

[22:03:47] <larjona> We had the first part of the meeting 1hour ago, because Evan could not attend now.

[22:04:11] <larjona> The log of that part is temporarily posted here: https://paste.debian.net/hidden/c393198e/

[22:04:45] <larjona> Basically, we discussed the pending small parts of the Conservancy Application, and the issues that are blocking releasing 1.0.0

[22:05:13] <larjona> So, is anybody here wanting to meet? Roll call!

[22:05:50] <strugee> o/

[22:05:59] <xmpp-pump> [marcel] \o

[22:06:23] <strugee> larjona: wrong agenda :P

[22:06:35] <strugee> https://github.com/e14n/pump.io/wiki/Meeting-2016-07-15

[22:06:37] <larjona> pardon!

[22:06:41] -*- Sazius is here

[22:06:41] <strugee> no worries!

[22:07:07] <larjona> I also chair there, and mix my cheatsheet :D

[22:07:14] <Sazius> I thought I just missed the meeting, didn't know there were two parts... will read backlog :-)

[22:08:27] <-- pacovila left (Read error: Connection reset by peer)

[22:08:34] <larjona> Sazius If you can add yourself to question 24 of Conservancy application (list the community members), it would be awesome

[22:08:35] <larjona> https://github.com/e14n/pump.io/wiki/Conservancy-application

[22:08:48] <larjona> (or tell me which info to put there about yourself).

[22:09:03] <larjona> If you prefer not to be in that list, please tell.

[22:09:52] <larjona> (note that this is being logged, too!)

[22:09:56] --> pacovila joined #pump.io

[22:18:35] <Sazius> larjona: sure, although I'm not a particularly active community member :-)

[22:18:54] <strugee> Sazius: you wrote Pumpa tho

[22:19:12] <strugee> that's important :P

[22:21:14] <Sazius> OK, I will add myself. Not sure since when I've been a community member... :-)

[22:23:27] <Sazius> larjona: done, feel free to edit as you see fit

[22:23:33] <pumabot> New Commit "Show "Try It" button on mobile" to e14n/pump.io by strugee: https://github.com/e14n/pump.io/commit/38514a6087582d589ae4012597e9efcd06532965

[22:23:41] <pumabot> strugee built e14n/pump.io pages at 38514a6087582d589ae4012597e9efcd06532965 in 3353ms.

[22:23:48] --> GitHub189 joined #pump.io

[22:23:48] <GitHub189> [pump.io] strugee pushed 1 new commit to gh-pages: https://git.io/vKD6p

[22:23:48] <GitHub189> pump.io/gh-pages 38514a6 Alex Jordan: Show "Try It" button on mobile

[22:23:48] <-- GitHub189 left #pump.io

[22:24:02] <larjona> thanks

[22:24:07] <larjona> Sazius++

[22:24:08] <pumabot> sazius has 1 point

[22:26:17] <larjona> Ok, so I'm here for anything you want to discuss, when silence, I'm adding more community members to the question 24

[22:39:59] <xmpp-pump> [JMobile] Hey, crazy pumpers

[22:41:34] <strugee> JMobile: heya!

[22:41:48] <strugee> in theory we're in the middle of the monthly meeting

[22:42:25] <xmpp-pump> [JMobile] Yep, larjona explained

[22:44:22] <larjona> so, strugee, if ((you have time now) and (not(you and others have any topic to discuss)) we can fire a collaborative pad to begin to write the release checklist

[22:44:39] <larjona> oh, I missed one ")"

[22:45:22] <strugee> sounds good

[22:45:27] <strugee> I do have time

[22:45:35] <larjona> ok, I'll post a link here

[22:46:40] <strugee> great

[22:46:48] <larjona> http://lacaja.larjona.net/shared/GZx4acq83kEXzFdkxfwHv1Z8MQR3lc2kWnr3n-JOqhH

[22:47:07] <larjona> (this is etherpad in my sandstorm.io box)

[22:50:37] -*- strugee 's web browser is hanging :/

[22:53:55] <xmpp-pump> [diane] Alas, I'm getting a 400 "Bad Request" when I try to post to my pump instance via the web UI.

[22:54:43] <strugee> diane: if you report a bug at https://github.com/e14n/pump.io/issues/new I'd be happy to take a look :)

[22:54:49] <larjona> ok, try this: https://titanpad.com/pumpioreleasechecklist

[22:55:03] -*- larjona forgot that her connection at home was very bad today :/

[22:55:26] <xmpp-pump> [diane] strugee: ok

[22:55:38] <larjona> diane: If you can add yourself to question 24 of Conservancy application (list the community members), it would be awesome

[22:55:38] <larjona> https://github.com/e14n/pump.io/wiki/Conservancy-application

[22:55:38] <larjona> (or tell me which info to put there about yourself).

[22:56:41] <larjona> If you don't want to be in that list, please tell, because I was going to add you as committer, bug reporter and selfhoster :)

[22:57:37] <xmpp-pump> [diane] :) ok

[22:57:37] <-- pacovila left (Read error: Connection reset by peer)

[22:58:41] <larjona> I have to go in 1-2 minutes

[22:59:39] --> pacovila (~fravd@176.10.77.169) se ha unido a #pump.io

[23:00:00] <strugee> larjona: do you mind if I move things from the brainstorming list into "before release", etc.?

[23:00:01] <pumabot> http://i.imgur.com/w0wuthi.jpg

[23:00:34] <strugee> I should turn off the business cat module

[23:00:36] <strugee> too chatty

[23:01:48] <xmpp-pump> [diane] (totally off topic but) the output of npm ls makes me sad.

[23:01:54] <strugee> diane: why?

[23:02:28] <xmpp-pump> [diane] http://dustycloud.org/blog/javascript-packaging-dystopia/

[23:02:34] <xmpp-pump> [diane] it goes on and on and on and on...

[23:02:41] <larjona> strugee: that's the intention, brainstorming should be empty eventually

[23:02:41] <pumabot> http://i.imgur.com/QyCmPGg.jpg

[23:02:43] <xmpp-pump> [diane] (filling out a bug report)

[23:02:50] <strugee> diane: ah yes I've read that

[23:03:11] <strugee> I'll be happy to explain why I think paroneayea is wrong, but I'll wait until the meeting is over :P

[23:03:16] <xmpp-pump> [diane] ok

[23:03:26] <xmpp-pump> [diane] i'd like to hear that

(end log)

Add a custom footer
Add a custom sidebar
Clone this wiki locally