Items covered and discussed in the Support Team Meeting include:
For the full experience of a support meeting summary, including calls for comment and good tunes, please read the full make/support meeting summary post.
Items covered and discussed in the Support Team Meeting include:
For the full experience of a support meeting summary, including calls for comment and good tunes, please read the full make/support meeting summary post.
Items covered and discussed in the Support Team Meeting include:
For the full experience of a support meeting summary, including calls for comment and good tunes, please read the full make/support meeting summary post.
Items covered and discussed in the Support Team Meeting include:
For the full experience of a support meeting summary, including calls for comment and good tunes, please read the full make/support meeting summary post.
Items covered and discussed in the Support Team Meeting include:
For the full experience of a support meeting summary, including calls for comment and good tunes, please read the full make/support meeting summary post.
Items covered and discussed in the Support Team Meeting include:
For the full experience of a support meeting summary, including calls for comment and good tunes, please read the full make/support meeting summary post.
Items covered and discussed in the Support Team Meeting include:
For the full experience of a support meeting summary, including calls for comment and good tunes, please read the full make/support meeting summary post.
Items covered at today’s Support Team meeting:
Items covered at today’s Support Team Meeting:
WordPress 5.9-beta1 has been delayed, a new date for the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process., and consequently a new release schedule, is not yet announced, but will be posted once it is finalized by the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team.
Team representative nominations are over, and with only one nominee, we have no need to hold a vote. The nominee is @sterndata, and instead of the vote which would have ensured if there were multiple nominees, we will instead have a ~2 week period in which any concerns can be raised, this can also be done privately to @clorith. If no concerns are raised, or they’re all worked out, the final announcement of the new representative will be done after December 1st, and we will prepare a handover period with some onboarding and similar at that time.
Next weeks meeting (November 25th), will be a very informal office hours, due to major holidays being celebrated in parts of the world, and other social events elsewhere, there are not a lot of regular contributors available at the time, so this feels like a good approach.
A note was made that often folks join the channel after an incident, quite often relating to something unfortunate happening on for example the forums, and that the users may not feel very well received.
This is in part by nature of guidelines helping us enforce directives, but we can probably also be better at providing a more welcoming surrounding in such cases.
We, as volunteers in the #forums channel, should avoid “piling on” when someone has concerns. Letting one individual handle the case, of course another person may be asked to chime in, but it should then ideally happen at the original attendees request, to avoid giving users a feeling of being outnumbered and of a lesser voice, or may lead to confusion and frustration.
That’s not to say things do not some times escalate, and we know that not everyone wants to accept the answers that are given. If things escalate, and users do not wish to listen, it becomes an unwelcome environment for other participants on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., so please escalate such cases to a Slack admin, and they can deal with it from there.
Read, or comment on, the complete original post on make/support.
