Welcome to the MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Team!
The Meta team is responsible for maintaining and managing WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ websites. Our work is mostly done on the meta trac. If you see a bug, file a ticket!
The WordPress Photo Directory recently hit 1,317 photos, and continues to grow very quickly! As volunteer moderators have reviewed numerous submissions, there have been growing realizations and many thoughts around how to best support the longevity of the Photo Directory. To work through these next steps, I’d like to request the following:
A new site on the Make network, `make.wordpress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//photos/`
Two handbooks: one public, and one private*
The current volunteer moderators are very excited to expand the team and grow the Photo Directory into a vast, high-quality resource for the WordPress community! Please join us in the new Slack channel once available.
*The private handbook will be made available to photo directory moderators. While it is unlikely that WordPress community members will submit inappropriate content, curators of user-submitted content do need to have certain processes in place in the event that happens.
6:17 pm on January 13, 2022 Tags: photo-directory
As announced in State of the WordState of the WordThis is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. 2021, WordPress now has a Photo Directory! The Photo Directory is both a curated source for high-quality images and a new submission tool for Openverse, powered by the WordPress community.
How you can help
The Photo Directory hasn’t fully launched yet. However there are already three ways you can help!
The first way is to contribute your photos. Do you own some exceptional, blog-worthy photos you’d like to offer to the community? You can submit those photos here.
The second way is to report issues. The Photo Directory is new and will continue to be built. If you run into any issues when using it, you can log an issue.
Contributing photos and reporting issues can be a one time contribution or as many as you’d like.
The third way is to become a Photo Directory Moderator. To help maintain and grow the Photo Directory, Moderators are needed to help review and approve submitted photos. Moderators will also be able to inform and refine the moderation process.
If you are interested in becoming a Photo Directory Moderator, this is a great time to do so, as moderation practices and tools are being discussed and developed. Anyone is welcome to contribute in this way, although it is particularly helpful if you already have experience with:
Excellent communication in open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. communities
Moderation best practices
Photo Directory Moderators can expect to spend 1-2 hours in coming weeks learning about the Photo Directory and current moderation tools, and discussing future best practices. To keep the Photo Directory a thriving resource, Moderators are needed for the foreseeable future, perhaps dedicating up to an hour of their time each week.
In the last Meta chat of 2021, we reviewed our use of component focuses in 2021, and discussed some alternatives.
To recap briefly, in 2021 we chose a different Meta component on which to focus attention for the two weeks between biweekly [fortnightly] chats. That had mixed results; in some cases we were successful in cleaning up tickets in those components, and starting or refreshing work on various tasks. In other cases, no notable progress was made.
Some of what we learned through the process:
Components vary widely in their size, complexity, and access limitations.
Focusing attention on a component doesn’t mean anyone is available to work on it.
It is a good way to uncover forgotten tickets and low-hanging fruit.
It’s not always clear what to do with tickets that aren’t immediately actionable.
Two weeks is not very long!
If we’re going to continue with the idea of focuses, let’s discuss ways of improving the process. For example:
Are there other focus groupings we should try, besides components?
What goals should we set?
Are there ways we can improve our chances of success and progress?
The next metaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. chat is 2022-01-12 21:00:00 UTC. That gives us roughly a week to discuss ideas and come up with a plan for the first focus of 2022. Discussion and suggestions are welcome in comments on this post, or in the #meta channel on SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
Update: This week’s meeting is cancelled; we’ll discuss it next time.
Since Learn WordPress was launched in December 2020, one of the focuses of the platform has been to enable live, synchronous learning experiences. These were initially formalised as discussion groups, but have since evolved to the more general name “social learning”. More info here: https://learn.wordpress.org/social-learning/
The events, known as social learning spaces, are live sessions where people learn together in multiple formats – discussions, workshops, webinars, ride-alongs, work-alongs, etc. These are currently been done over Zoom, which is fine for the most part, but in order to be more accessible and available, it would be great if text-based spaces could be run too. The most logical place for those would be the WordPress SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., so I’d like to request that we add a new Slack channel named #social-learning.
This new channel would be reserved for these live, synchronous events and nothing else – it means that all attendees would need to join Slack in order to take part.
For some context, when discussion groups were still relatively new, some were initially done in this text-based format using the #community-events channel. However, since the Training team has now taken ownership of this side of the project, it makes more sense to break them into a separate place and have their own dedicated space.
I’ll leave this request open for feedback until Friday, 19 November @ 2am UTC, after which feedback will be collated and, if there are no objections or issues, the new channel can be created.
From 11-Nov-2021 03:56:39 UTC to 11-Nov-2021 05:57:33 UTC there was an outage affecting some requests to wordpress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ sites including api.wordpress.org. That caused an error response to some APIAPIAn 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. calls.
The root cause was a failure to properly deployDeployLaunching code from a local development environment to the production web server, so that it's available to visitors. root files during a deploy. That was my mistake, and I apologize for causing the outage. The systems team was able to fix the problem.
With the help of the systems team we’ve identified some deficiencies in the deployment process, and will add some extra safeguards and monitoring to reduce the chance of similar failures in future.
From last Friday, WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profiles have started to show activity from the WordPress GitHubGitHubGitHub is a website that offers online implementation of git repositories that can 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 be the repository owner. https://github.com/ organization. This is shown when your WordPress.org & GitHub accounts are linked together. You can do this through your WordPress.org profile.
Currently we’re tracking New Issues submitted (by you), Closed Issues (by you), Pull requests submitted (by you), Pull requests merged (by you, and additionally the PR submitter gets a ‘PR Merged’ event), and finally Pushes to default branches.
There are a few limitations. We’re not currently accounting for PRs where commits are pushed to the PR by someone other than the submitter/merger. Similarly, if you push code from someone else then it may not be handled appropriately.
The code to display it on profiles.wordpress.org is unfortunately not yet open-sourced. It’s nothing overly special, but we realise this does limit the ability for submitting patches to that part of the code. MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tickets detailing a requested change including the Text/CSSCSSCSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. required will be prioritised.
Most repositories activity items will display the team logo, but if it’s not known it’ll default to the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. code logo. If you find activity on a repository is tracked with the incorrect logo, create a meta ticket in the Profiles component or comment below.
Why doesn’t it list my Issues & Pull Requests?
That might be expected. We only have data for Friday onwards cached on WordPress.org. Importing all previous issues and pull requests is possible, an importer simply just hasn’t been written yet.
If you haven’t linked your GitHub account to WordPress.org, it won’t show then either. Good News! Once you link your account, it’ll show up immediately for any data that we have.
Some people who linked their GitHub account when that feature was first launched have since had their account link expire. This has since been fixed – they no longer expire. So if you thought you had linked it, but find it now not-linked, that’s likely why.
Are we showing too much information?
Should we combine events? For example; Today I submit a PR for review, later today I merge it, that’s two activity entries. Should it be merged together if within x hours? “Submitted & Merged PR #123 to WordPress/example-repo”
Are there any events you wish to see shown? Pull Request Reviews perhaps? Props for those who were commenters on the Issues/PRs?