This month’s Faculty Meeting will occur on Tuesday 19:00 UTC for Americas/EMEA and Wednesday 05:00 UTC for APAC.
See the Training Team Faculty Member list for the list of current Faculty Members, and find out more about the Training Team Faculty Program in our handbook page.
The goal of the monthly Faculty Meeting is to discuss the Training Team’s goals, strategy, and how best Faculty Members can utilize their expertise within the group.
Notes from the calls will be posted as comments within this post.
Agenda
- Proposal to make Faculty meetings more public
- The team will continue working in the open
- everything that isn’t a privacy concern should go into a public channel of some sort.
- The private channel is intended for logins, incident concerns, etc.
- https://wordpress.slack.com/archives/C03B11FA16D/p1659098737136069?thread_ts=1658970512.900959&cid=C03B11FA16D
- announcing new channel joinees
- Is there a benefit in announcing these still to someone?
- Or are meeting facilitators (team reps) tracking these some other way anyway?
- Zoom disruptions
- turned a few more security features on in our shared Zoom account
- https://wordpress.slack.com/archives/C03B11FA16D/p1659733286494459
- Changed:
- Annotation to “Only the user who is sharing can annotate”
- Turned off:
- Whiteboard (Classic)
- Remote control
- Gesture Recognition
- Allow users to change their name when joining a meeting
- Allow participants to rename themselves
- Show participant profile cards in a meeting
- Turned on:
- Mute all participants when they join a meeting
- Hide participant profile pictures in a meeting
- requiring authentication to join a meeting.
- Faculty Meeting Calendar
- Hi, I was just wondering if we can edit link and add directly to calendar for Monthly call section, so that any faculty member can jump into this page and add this event into their calendar.
- I’m all for automation! Let me see how we could do this.
- Workflow (SME’s)
- difficult to jump in on things like reviewing new topics because the workflow may not be clear or simple enough to manage at the moment.
- https://wordpress.slack.com/archives/C03B11FA16D/p1660112243025129
- https://make.wordpress.org/training/handbook/getting-started/how-we-work-together/#development-workflows
- pull our GitHub issues into a spreadsheet to help SMEs better assess priority and “staleness
- My first guess would be to use the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.
- https://docs.github.com/en/rest/issues
- More specifically https://docs.github.com/en/rest/issues/issues#list-repository-issues
- I have secured a Crowdsignal premium account for us to use
- https://wordpress.slack.com/archives/C03B11FA16D/p1660872225211179
- you can create unlimited surveys and polls of all types with it
- Contributor badges
- Individual learn survey –
- Content Errors
- Hi @faculty! I’ve been looking at the slow but steady number of content error reports that come into Help Scout, and am considering how we can make these more “public” so that folks get the help they need sooner. Ideally, anybody (regardless of their access to Help Scout) should be able to help these folks out.…
- I’ve now updated the content error report page.
- https://wordpress.slack.com/archives/C02RW657Q/p1661580388948569
- In the thread above
It was suggested that we add additional info for folks who’d like to learn about GitHub to the error report page.
- While the SLS recording mentioned in the thread was good, it didn’t address reporting content errors specifically. Maybe we could make a quick video specifically about submitting error reports on GitHub, and add that instead? I’m happy to hear what @faculty-content-creators think about that.
- At the same time, another thought was adding more content before the error report form might discourage people from actually submitting their error report. The heading right now is pretty wordy as-is. I added a bit of color to break the text up a little.
- Faculty Meeting September 2022 – 5 weeks in September
- Also, can we make sure to include zoom links integrated with the meeting calendar event, so that any faculty member can join in the meeting by following the event and zoom link?