IRC log of browserext on 2016-10-06

Timestamps are in UTC.

01:27:29 [RRSAgent]
RRSAgent has joined #browserext
01:27:30 [RRSAgent]
logging to
01:27:36 [Zakim]
Zakim has joined #browserext
01:28:13 [Florian]
Meeting: Browser Extension CG teleconf
01:28:21 [Florian]
ScribeNick: Florian
01:28:29 [Florian]
Chair: Florian
01:28:56 [Florian]
01:30:27 [mikepie]
mikepie has joined #browserext
01:30:38 [mikepie]
present+ mikepie
01:32:24 [Florian]
present+ Florian
01:32:43 [kmag]
present+ kmag
01:33:29 [kmag]
mikepie: Are you having trouble joining the hangout?
01:34:28 [mikepie]
Yeah. I have to reinstall Chrome. Sorry
01:34:44 [kmag]
01:34:50 [mikepie]
Almost there...
01:36:01 [Florian]
TOPIC: Agenda
01:36:28 [Florian]
Florian: Anything else to add to the agenda?
01:37:18 [Florian]
kmag: I'd like to talk about standardizing IDs.
01:38:33 [Florian]
mikepie: let's talk about extended attributes as well
01:39:18 [Florian]
TOPIC: extended attribute
01:39:48 [Florian]
mikepie: we have some direct contacts what should help get the ball rolling by lightly prodding the right people.
01:40:44 [Florian]
TOPIC: Joint statement on native messaging
01:41:27 [Florian]
01:42:46 [Florian]
Florian: This is a first incomplete draft of the join statement we mentioned during TPAC
01:42:54 [Florian]
kmag: I am not sure this is really necessary
01:43:46 [Florian]
Florian: Not sure either, but I think it's not wrong to ping people who worry about the whole web platform if we're doing something that might matter to more than to just ourselves
01:44:04 [Florian]
mikepie: looks like a good start, will ping people at MS
01:44:18 [Florian]
mikepie: what do we do once we have this?
01:44:29 [Florian]
Florian: I'll ping the TAG and see what they think of it
01:44:42 [Florian]
TOPIC: Status update on
01:45:51 [Florian]
Florian: Anything to speak about without aswan on the call
01:45:55 [Florian]
mikepie: not really
01:46:09 [Florian]
TOPIC: standardizing IDs
01:48:11 [Florian]
Florian: Have we though about using URLs (as in including a domain name in there) for IDs? You'd still have to map the ID to the application, but at least we'd get a clean space without too much colision problems
01:48:53 [Florian]
kmag: we'd need a way to verify you own the domain, and some way to associate the ID with the application... Seems complicated
01:49:12 [Florian]
kmag: Maybe we could instead share our ID database from the respective vendor stores
01:49:43 [Florian]
kmag: and allow registration on each store, but stores would check with the other stores that the ID is free
01:53:26 [Florian]
Florian: doesn't that lock us out of native messaging when not using app stores for distribution? Like private extensions, or enterprise distribution
01:54:08 [Florian]
kmag: I think it's ok. Enterprise works with its own rules anyway, and the single developer use case doesn't really involve distribution, so it is ok.
01:54:51 [Florian]
mikepie: how about having 2 ids? a shared one that is unique across stores and one that is unique in your own store?
01:54:57 [Florian]
mikepie: I guess that doesn't help
01:55:58 [Florian]
Florian: Has our various companies already solved a similar problem, and can we talk to the people who did that?
01:56:41 [Florian]
mikepie: there's globaly unique, which deals with avoiding collisions, but it doesn't help with central registration
01:58:09 [Florian]
mikepie: how about : when I submit to the FF store, and it generates a unique ID for me. Then I use that ID to register in the MS store
01:59:03 [Florian]
Florian: but that allows for spoofing
01:59:12 [Florian]
kmag: only if the end user can do it, so we shouldn't allow
01:59:25 [Florian]
mikepie: Can we combine that with the domain name id?
02:00:01 [Florian]
kmag: I don't see how
02:00:58 [Florian]
Florian: Should we ping crypto / security / ssl / ssh / etc people? They should be more familiar than us with this kind of issues
02:01:07 [Florian]
mikepie: Let's do that, I know some folks.
02:01:26 [Florian]
02:01:32 [Florian]
02:01:39 [mikepie]
02:04:46 [Florian]
mikepie: number 2 is unfinished, it will read ext instead of cxt
02:05:00 [Florian]
mikepie: 1 and 6 may not work at small sizes
02:05:08 [Florian]
Florian I like 2 4 and 8
02:05:20 [Florian]
mikepie: 4 looks like XML
02:06:18 [Florian]
kmag: I like 4 5 and 8
02:06:29 [Florian]
mikepie: I'll clean up 2 4 5 and 8
02:06:40 [Florian]
kmag: I'll also try to involve our designers.
02:07:11 [Florian]
TOPIC: Reviewing / resolving issues in
02:08:01 [mikepie]
02:08:05 [Florian]
Florian: Any particular issue you want feedback / discussion on?
02:08:22 [Florian]
mikepie: not sure, let's just start with giving you an update
02:08:29 [Florian]
mikepie: I merged webdriver
02:08:49 [Florian]
mikepie: I do have a question about something needing to be a POST instead of a GET
02:09:29 [Florian]
mikepie: I also changed the naming convension, so that everything starts with BrowserExt, and unified Info/etc into Details
02:10:10 [Florian]
mikepie: I added a script to facilitate navigating through issues.
02:12:06 [Florian]
mikepie: so the thing I want input on is Issue 35
02:12:23 [Florian]
kmag: there are two methods that need to be POST, because they have side effects:
02:12:51 [mikepie]
Get Browser Extension Context Menu Items
02:13:01 [mikepie]
Select Browser Extension Context Menu Item
02:14:08 [Florian]
mikepie: I'll be doing a new iteration on this tomorrow, and then the section should be ready for review
02:15:11 [Florian]
Florian: Skipping the issues that are TODOs to yourself, it would be nice to register the issue that need discussions into github
02:15:14 [Florian]
mikepie: Will do
02:15:33 [Florian]
kmag: should we provide regex for comment removal?
02:15:42 [Florian]
kmag: I'll register than into github, OK?
02:15:47 [Florian]
mikepie: Sounds good.
02:16:51 [Florian]
TOPIC: Community involvement
02:17:18 [Florian]
Florian: A while back we talked about trying to reach out to more people and try to get them involved, to comment on the spec
02:17:53 [Florian]
Florian: As we're starting to have a spec with issues to discuss, are we at that point, or would it still be a waste of time for most people to come at this point
02:18:32 [Florian]
mikepie: I'd like to look at some usage data to check first that we have the key APIs that people will want to look at to avoid disapointing them, but other than that yes, we should be able to now
02:20:00 [Florian]
mikepie: I can look for extension vendors that can already use the stuff we have
02:20:27 [Florian]
mikepie: If andrey had some specific vendors in mind, that let's us look at it from the other direction and ask them what they think is missing.
02:26:58 [Florian]
TOPIC: meeting
02:27:05 [Florian]
mikepie: Let's try in two weeks
02:27:16 [Florian]
Florian: Should we try and adjust the time for aswan?
02:27:22 [Florian]
mikepie: Yes, and for Shwetank as well
02:28:08 [Florian]
Florian: Let's book the same time for now, and in parallel try and talk to them. We can adjust if they propose something that works better.
02:28:23 [Florian]
RRSAgent, make log public
02:28:29 [Florian]
RRSAgent, draft minutes
02:28:29 [RRSAgent]
I have made the request to generate Florian
02:34:11 [Florian]
RRSAgent, bye
02:34:11 [RRSAgent]
I see no action items