| 01:50 | <heycam> | tobie: I don't think that's possible for a non-org owned repo. let me know what hook url to add and I'll add it. (though I realise you might still want to click that "send a test hook message" button and won't be able to.) |
| 06:05 | <jyasskin> | heycam: Would it make sense to transfer the repository to an org? |
| 07:47 | <pycat> | Hello World!My name is Katerina. |
| 07:47 | <pycat> | I am applying to the Outreachy internship for this program. |
| 07:47 | <pycat> | I have strong experience on HTML and am interested on contributing to HTML standard. |
| 07:47 | <pycat> | I could work on issue #1429 (https://github.com/whatwg/html/issues/1429) as my first |
| 07:47 | <pycat> | contribution. |
| 07:48 | <pycat> | I would also like to know what additional programming skills are required :) |
| 07:48 | <pycat> | Thanks :) |
| 07:58 | <annevk> | pycat: we don't currently participate in Outreachy I believe; where did you read that we were? |
| 07:59 | <annevk> | pycat: you're welcome to nevertheless contribute though 😊 |
| 08:05 | <pycat> | annevk: Yes, just noticed that i was in Outreachy round 12 section, but i am interesting anyway :) |
| 08:07 | <pycat> | annevk: could you tell me more about the required skills |
| 08:10 | <annevk> | pycat: some knowledge about algorithms and programming, not really any particular language since it's mostly English (unless you want to work on tooling/tests); bit of experience with making web sites would also help |
| 08:15 | <pycat> | annevk: great, i have some experience on making custom web sites with python django framework |
| 08:16 | <pycat> | annevk: i would like to know some more about tooling/tests |
| 08:17 | <annevk> | pycat: and to solve the more involved issues you'll have to figure out what browsers do |
| 08:18 | <annevk> | pycat: through some combination of using JavaScript APIs, maybe reading source code, and observing behavior |
| 08:19 | <pycat> | annevk: this will be my very fist time contributing to open source so any help and information will be more than welcome :) |
| 08:20 | <annevk> | pycat: quite a lot of what we do is document existing JS APIs better, and try to get all browsers to implement them in the same way |
| 08:27 | <annevk> | pycat: the other thing I suppose is that you need to learn GitHub a bit |
| 08:27 | <annevk> | pycat: how to make a pull request and such |
| 08:28 | <annevk> | pycat: I believe README/CONTRIBUTING files have guidance there |
| 08:30 | <pycat> | annevk: i already have some experience on git and github, mostly working individually |
| 08:30 | <annevk> | pycat: great |
| 08:31 | <pycat> | annevek: great, i will proceed on README/CONTRIBUTING. I hope i'l have my first pr soon :) |
| 08:36 | <pycat> | annevk: Thanks a lot for the guidance!!!I hope well talk soon! |
| 09:21 | <annevk> | pycat: thank you! |
| 11:16 | <gsnedders> | slightlyoff: where's the Google document giving the different levels of DRM? My Google-fu isn't good enough, seemingly |
| 12:34 | <MikeSmith> | annevk: https://stackoverflow.com/questions/39878142/redirect-failing-on-cors-request if you have time to answer there |
| 12:45 | <annevk> | MikeSmith: answered half |
| 12:46 | <MikeSmith> | thanks |
| 12:49 | <MikeSmith> | I wonder if there are browser bugs open to implement the preflight-redirect change |
| 12:50 | <MikeSmith> | in general it seems like we should have more systematic way of getting browser bugs filed for changes like this |
| 12:57 | <annevk> | Yeah, maybe I should reopen that issue to get bugs filed and fix tests |
| 12:58 | <annevk> | Too tired to get much done atm |
| 17:29 | <smaug> | ++Domenic |
| 17:29 | <Domenic> | because the whatwg⊙wo response? |
| 17:31 | <smaug> | yes |
| 17:31 | <smaug> | thanks |
| 17:32 | <Domenic> | I feel sad for that list :-/. It has a lot of high-powered subscribers but I'm afraid we're just wasting their time. |
| 17:33 | <TabAtkins> | It probably makes sense to convert it over to being manually filtered. |
| 17:33 | <TabAtkins> | (I think we should do the same to the csswg list.) |
| 17:34 | <Domenic> | interesting |
| 17:36 | <smaug> | TabAtkins: ah, yes. Given that the mailing list is low-traffic these days, filtering would make sense. |
| 17:36 | <smaug> | and shouldn't take too much anyone's time |
| 17:36 | <TabAtkins> | Exactly. And it lets you head off these sorts of emails with a quick reply pointing them to the guidelines. |
| 17:36 | <Domenic> | You could even apply filtering only for first-time posters |
| 17:37 | <TabAtkins> | Domenic is already having his time wasted by these; it wouldn't increase his burden at all, and would save other people. ^_^ |
| 17:37 | <TabAtkins> | Yeah, that's pretty typical. |
| 19:18 | <jyasskin> | tobie: Do you have sample code for Generic Sensors if a page wants to start watching a sensor's changes, but also use its current value as the first of those changes? |
| 19:28 | <tobie> | jyasskin: On a spotty mobile connection in a fast train for the foreseeable future. |
| 19:28 | <tobie> | jyasskin: yes this is the default behavior |
| 21:55 | <TabAtkins> | jyasskin: That's the "ReactiveValue" I talk about in http://www.xanthir.com/b4PV0 if Domenic or whoever would hurry up and standardize Observers. ^_^ |
| 21:57 | <jyasskin> | TabAtkins: There it is! I knew you'd sent me that link before, but couldn't find it. |