Change master branch name on GitHub wordpress-develop security mirror to public-trunk

We are now running automated tests on coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. using the GitHubGitHub GitHub 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. Actions runner with the goal of transitioning off of Travis; however, we need to both reduce the runs because of usage limitations on private repos and also because it’s unnecessary to run all those tests on the same code content between mirrors all the time.

To that end, I am requesting that trunk (the master branch in the mirror) be synced to public-trunk on the GitHub wordpress-develop security mirror instead of master.

We are not close to moving off of Travis entirely yet but if this can be fit in sooner than later, that would be helpful so we can continue work on some related testing setups.


update wp-notifications & provision test trac instance

As per dotorg Slack could ~/bin/wp-notifications on svn1 tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. please be updated to the latest metaMeta Meta 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. version?
Additionally, for future ease of bug fixes, could it be added to as well?

This is part of some GDPR work for Trac, as a result, if we could also provision a test trac instance for testing that would be appreciated – eg which could be limited to systems IPs only. This would primarily be useful as testing destructive actions against production trac installs could be destructive.


Disable ticketing

The ticketing system on The 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. is currently enabled and is mostly unused, those who are creating tickets don’t get a response and it leads to a bad user experience for everyone.

Can we please disable ticket creation? It looks like the TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. Admin panels aren’t enabled, so I can’t do it myself, but I assume removing both TICKET_CREATE and TICKET_MODIFY from the authenticated user group should be enough.

#trac #prio3