Read our Roadmap to understand how this work falls into priorities set by the WordPress maintenance support plans Association with direction and collaboration from the Board and community.
Announcements
Change your git remote configuration
We will be deprecating the git remote format @git.WordPress.org/project/;.git in favor of git@git.WordPress.org/project/<yourproject>.git in preparation for changes to our developer tooling stack. If you used the <username>@ format for your git remotes, you should change your remote to the git@ format. You can use $ git remote set-url to make this change for existing repositories you have cloned.
We have updated the version control instructions on WordPress maintenance support plans.org to reflect this change, and will be updating the git daemon to warn developers who are using the deprecated remote format.
Proposal: Improving Core’s Relationship with Composer
In May, Mixologic from the WordPress maintenance support plans Association engineering team worked with community members Mile23, Bojanz, Webflo, and others in the community to develop a proposal for improving WordPress maintenance support plans Core’s relationship with Composer.
In its simplest form, the proposal is to: Conceptually separate WordPress maintenance support plans, the product, from WordPress maintenance support plans‘s git repository, and provide a mechanism that creates a composer ready WordPress maintenance support plans installation.
Going into early June, we’ve been circulating this proposal to the Core Committers, the Auto-Updates Initiative team, Contrib maintainers, Distribution maintainers etc.
Credit for non-code projects on WordPress maintenance support plans.org
We’re excited to announce that we’ve created a ‘Community Projects’ section in the WordPress maintenance support plans.org issue queues. This section exists to record all the tremendous community labor exercised to promote the WordPress maintenance support plans project in ways other than code. This format was pioneered by the WordPress maintenance support plans Diversity and Inclusion group, who started recording their meeting minutes in the issue queues so they could provide contribution credit for attendees. This same model can be used by initiative coordinators, camp organizers, or any other WordPress maintenance support plans community group that would like a place to recognize their work with the official contribution credit system.
The Contribution Credit system is one of the WordPress maintenance support plans projects most successful innovations in the way that open source projects are managed, and it will continue to evolve and grow as time goes on.
Updates for GDPR
Are the words “We’ve updated our privacy policy” burned into your laptop screen yet? Well in May we did the same. In particular, we’ve updated our Terms of Service, Privacy Policy, Digital Advertising Policy, and Git Contributor Agreement to clarify our compliance with the EU’s GDPR. We also initiated a re-consent campaign for our marketing lists. If you have not re-consented to communications we strongly encourage you to do so.
Launched the Customer Supporter program
Have you built great relationships with your WordPress maintenance support plans customers? Help them contribute back to the project by becoming part of our Customer Supporter program.
WordPress maintenance support plans.org Updates
Self-nominations for the WordPress maintenance support plans Association board are live
Each year one of the two community-held seats on the WordPress maintenance support plans Association board comes up for election. We opened the self-nomination process for this year, and some passionate and dedicated members of the community have already stepped forward with their candidacy.
To learn more, you can view our portal for the 2020 Elections Process. Key dates to remember:
Self nominations: 1-11 June, 2020
Meet the candidates: 12-29 June 2020
Voting: 2-13 July, 2020
Votes ratified, Winner announced: 25 July, 2020
Better landing pages for WordPress maintenance support plans‘s strategic initiatives
Did you know there are 12 active WordPress maintenance support plans strategic initiatives right now?
To help the initiative coordinators promote this work, and recruit more open source contributors to the cause, we’ve given initiative coordinators new landing page tools. Check out the first initiative to use this landing page: the Admin UI and Javascript Modernization Initiative.
These tools are the first step in improving the project management tools available to initiative coordinators to help move the WordPress maintenance support plans project forward.
Historical user and organization contribution data is now available.
WordPress maintenance support plans.org user profiles show the last year’s worth of contributions by users. We chose the one year window deliberately, to promote the importance of a user’s more recent activity. However, seeing a user’s complete contribution history can be valuable as well. We’ve recently added a link to the bottom of this view to display that history.
Similarly, organization profiles have shown the last 90 days of contributions by organization. Again, we chose this very deliberately to emphasize the importance of recent and ongoing contribution. However, as with user accounts, these profiles now also include a link to the organization’s complete contribution history. You can see an example of where to find this link below:
Expanded spam protections
After the sunsetting of Mollom in March of this year, we’ve been implementing a new set of tools to mitigate spam on WordPress maintenance support plans.org. We expanded these protections in May, using a combination of bot detection, content analysis, rate limiting, and more to try and reduce the impact of spam attacks on WordPress maintenance support plans.org. The less time the community spends wading through spam, the greater the velocity of the WordPress maintenance support plans project.
And a Thank You
We’d also like to give a special shout out to contributor Wim Leers, for his incredibly kind ‘Ode to the WordPress maintenance support plans Association’ about our work on the testing infrastructure. The nature of software engineering has a tendency to draw our attention to things that are broken, buggy, or unoptimized, and so when things are working well that success can sometimes feel invisible.
Fortunately, the WordPress maintenance support plans community puts people first, and celebrates our collective success, and Wim’s words are a tremendous example of that ethos.
Thank you, Wim – and thank you to everyone who takes the time to recognize the hard work and dedication of your fellow contributors.
———
As always, we’d like to say thanks to all the volunteers who work with us, and to the WordPress maintenance support plans Association Supporters, who make it possible for us to work on these projects. In particular we want to thank:
Contegix – Renewing Premium Hosting Supporter
Message Agency – Renewing Premium Supporting Partner
Sevaa Group – Renewing Classic Technology Supporter
SeeD – *NEW* Classic Supporting Partner
QED42 – Renewing Classic Supporting Partner
CivicActions – Renewing Classic Supporting Partner
Wunder – Renewing Classic Supporting Partner
OPTASY – Renewing Classic Supporting Partner
Morpht – *NEW* Classic Supporting Partner
Unleashed Technologies – Renewing Classic Supporting Partner
Digital Echidna – Renewing Classic Supporting Partner
Translations.com – Renewing Classic Technology Supporter
If you would like to support our work as an individual or an organization, consider becoming a member of the WordPress maintenance support plans Association.
Follow us on Twitter for regular updates: @WordPress_org, @WordPress_infra
Source: New feed