# [07:49] -gitbot:#testing- [web-platform-tests] zqzhang closed pull request #841: Put authorship information into IndexedDB test files (master...yunxiaoxie/IndexedDB-authorship) https://github.com/w3c/web-platform-tests/pull/841
# [14:46] <AutomatedTester> MikeSmith: could you email someone about finding the bugzilla REST endpoint. I have asked in #sysreq a few times at different times of the day and never get a response
# [14:47] <MikeSmith> AutomatedTester: yeah will do
# [17:58] <MikeSmith> plh: the "Testing Update" messages, I assume
# [17:59] <plh> ah, for anyone who is involved on #testing on a daily basis, I don't expect those messages to be useful
# [17:59] <plh> they're more targeted for folks who can't follow the PR or #testing on a daily basis
# [18:00] <MikeSmith> plh: then it would be good to also get some feedback from the people they're targeted to -- to hear if those people find them useful
# [18:00] <plh> and I do so everytime I have the opportunity
# [18:01] <MikeSmith> plh: but I think the fact that Ms2ger & jgraham don't find them useful is still worthwhile feedback
# [20:11] <plh> MikeSmith, I don't mean to exclude Ms2ger and jgraham, I just don't think they need to be told about what going in our github repo since they're always on top
# [20:12] <jgraham> plh: FWIW my objection is more that the email is a kind of wall of text that it's hard to learn anything from
# [20:12] <jgraham> Also, for people who aren't really reading, weekly might be too often. Monthly emails would work better, perhaps
# [20:13] <plh> re wall of text, Art suggested we use ... HTML for the text format
# [20:13] <plh> that would avoid all those visible links
# [20:13] <jgraham> That's not the problem, really
# [20:13] <plh> re weekly/monthly, it's possible that monthly would work better. I don't have enough data to judge yet
# [20:14] <plh> is it the wall of text or the wall of data then?
# [20:14] <jgraham> It feels like we don't really know what the use case here is, so we're just throwing everything at the wall in case something sticks
# [20:15] <plh> my use case is informning people who don't have the time to keep track of what's going on in github PR
# [20:19] <jgraham> Well a use case would probably mention specific information that people want, and what they are trying to do with it.
# [20:20] <jgraham> A sample use case would be something like "AutomatedTester wants to see how many PRs are being authored and reviewed by people in Mozilla each month so he can make sure they are doing their jobs"
# [20:20] <jgraham> (as it happens that would be a silly use case, but you get the general idea)
# [20:21] <plh> make senses. then, to be honest, I would say that we don't know enough about the use case yet
# [20:21] <plh> I see as an experiment at the moment
# [20:21] <jgraham> So why did we start doing this? Did people ask for it, ot did we just have the idea that it could be useful?
# [20:21] <plh> I started it because people didn't know what was going on in general
# [20:22] <Ms2ger> And we wanted to show them we weren't all slacking off?
# [20:23] <jgraham> So the use case is something like "The W3C wants to make its Members better informed about the current work that's happening in web-platform-tests so that (whatever you expect the benefits of awareness to be)"
# [20:24] <jgraham> In that case I would dramatically cut the amount of information
# [20:25] <jgraham> Like I don't think that anyone, at a high level, care that Ms2ger is doing code review that doesn't already know that to be the case
# [23:51] -gitbot:#testing- web-platform-tests/jgraham/manifest_no_git 735f38e James Graham: Ensure that just reading a manifest file doesn't require us to be in a git repo....
# [23:51] -gitbot:#testing- [web-platform-tests] jgraham opened pull request #1109: Ensure that just reading a manifest file doesn't require us to be in a g... (master...jgraham/manifest_no_git) https://github.com/w3c/web-platform-tests/pull/1109