Highlights

5 clips · select lines in any transcript to make one

0:59
User testing shows that recipients cannot reliably tell whether a welcome message…
Editor engagement roundtable · Sat, Jun 22, 2013 · 1:18
“we ask them do they think that the welcome message was left by a human or a robot, and it's 50/50. Yeah. Same message. They can't tell. They can't tell. And I actually think personally that we should just basically just do it automatically and make sure that you know it's happened automatically, like welcome with Here's some places where you should start learning what to do. Here's some things to do based on your interests that you described to us. These are the types of things that we would like you to get involved with. Don't worry, you can't break it. Betsy, you had something. I wanted to share 2 stories about user page interactions that I think were important to my wiki career. 2 things. When I first started And I tried it again. It felt weird, but I made an edit and I added a word to the slide that wasn't there before.”
Public link on
0:41
The automated testing framework developed by Peter has been merged into the…
CiviWiki weekly sync — 2018-02-19 · Mon, Feb 19, 2018 · 2:06
“Awesome. So that was the main amount of work that was kind of merged in, in the past week. Oh, I'm sorry, there was one other pull request that's noteworthy. We have now merged the test framework. So that was quite a bit of effort. Do you want to comment on that, Mitchell? Peter has been in communication with you. Yeah, I'll jump in real quick. So yeah, this was— we brought in a developer, Peter, from— I think he was somewhere in Eastern Europe.”
Public link on
0:39
Pull requests should remain focused on a single type of task rather…
CiviWiki weekly sync — 2018-05-14 · Mon, May 14, 2018 · 2:41
“Cool. So that's good work. One thing I'd like to encourage is that every pull request should be really focused in doing one kind of thing, and it can close multiple issues if those issues are related, if there's some kind of cluster of bugs or a couple of features that might be touching the same part of the code. The issues that are marked as being fixed by pull request number 193, they are not so closely related, so I would urge you to open 3 or 4 pull requests.”
Public link on
0:39
The approved Django REST Framework pull request will be merged once conflict…
CiviWiki weekly sync — 2018-05-28 · Mon, May 28, 2018 · 3:37
“All right. But yeah, so for what you said— back to what you said, Islaya— let's go ahead and merge this initial work on the Django REST Framework. This is really good. And then keep on the componentization. As an aside, I was just reading on Hacker News that Shadow DOM has— I think they're going to— in Mozilla, they're going to have it as a standard feature. It's been behind, I guess, a flag for a while that you had to enable or disable. Since about 2015 or 2016, I don't know. But basically, that's part of this Web Components standard that's pretty much fully fledged except a crucial part called HTML imports.”
Public link on
0:51
The Board approved the trustee evaluation rubric by a 9 to 1…
Community Board seats — call for feedback · Sat, Feb 20, 2021 · 1:19
“Yep, sure, sure, Andrew. So, you know, I, of course, didn't vote in support of adopting the, the rubric you know, the vote was 9 to 1 with me being the opposing vote exactly because of the reasons that you mentioned. I don't see enough clarity at this point in time with respect to how that rubric is gonna be used to feel comfortable supporting it being rolled out. So at this point in time, how it's gonna be used is still to be defined. And maybe this is just a question that's your opinion But is it— do you see a path for it being better specified to be usable, or is it kind of a— I don't want to say dead end, but is it somewhat— is it too amorphous to be useful, or can it be clarified?”
Public link on