Can we please enable SSL for lists.wordpress.org?

Currently the domain isn’t accessible over SSLSSL Secure Socket Layer - Encryption from the server to the browser and back. Prevents prying eyes from seeing what you are sending between your browser and the server., and it’s not uncommon for links to be SSL’d or for browsers to force SSL.

ref: https://meta.trac.wordpress.org/ticket/629

#prio3

Force SSL for https://planet.wordpress.org/ Can…

Force SSL for https://planet.wordpress.org/

Can we please enable forced SSL for https://planet.wordpress.org/ now that all the sites are SSL’d? Looks like the $maybe_force_ssl map just needs updating.

ref https://meta.trac.wordpress.org/ticket/634

#prio3

Disable plugins.trac.wordpress.org ticketing

The ticketing system on plugins.trac.wordpress.orgWordPress.org 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. https://wordpress.org/ 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.https://core.trac.wordpress.org/. 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.

#prio3

lists.wordpress.org unsubscription email not configured

According to #5134-meta the mailing lists include unsubscribe headers similar to this, but they don’t resolve to accounts:
List-Unsubscribe: ,

wp-svn-request@lists.wordpress.org: host lists.wordpress.org[198.143.164.108]
    said: 550 5.1.1 : Recipient address
    rejected: User unknown in local recipient table (in reply to RCPT TO
    command)

#prio3

#5134-meta

Clean up erroneous WordPress releases and branches

Over time, some erroneous WordPress releases or branches were accidentally created:

  • 5.4-RC3-47470. This should have been a nightly bump instead.
  • 4.9.8-beta1-43498. This too should have been a nightly bump.
  • 4.2.26 branch on git://develop.git.wordpress.org/ mirror. This should have been a tag instead, and is already deleted on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/., but still exists in the GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. mirror and shows up on 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. https://github.com/.

Would it be possible to clean them up to avoid confusion?

#prio3

Build SVN access for SergeyBiryukov

When WordPress is in RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. stage and a new version of Akismet is released, the svn:externals property has to be updated on the build repo (core.svn.wordpress.org).

For the upcoming WordPress 5.4 release this is already handled in https://core.trac.wordpress.org/ticket/49662#comment:2, so we’re good for now 🙂

Would it be possible for me (SergeyBiryukov) to get write access to core.svn.wordpress.org so I could help with these tasks in the future?

#prio3

Can I please have commit…

Can I please have commit access granted to bbpress.svn.wordpress.org for the WordPress.orgWordPress.org 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. https://wordpress.org/ username casiepa?

Pascal has been contributing to localizing bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. and moderating the forums for several years. He’ll be helping the rest of the team maintain strings going forward.

(He has secure passwords on his WordPress.org, 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/., and 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. https://github.com/ accounts.)

#bbpress, #commit, #prio3

Tighten the config block rules.

Currently the 403 LB blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. for config is being too greedy. Can we please tighten it up to allow legitimate urls such as these through?

https://wordpress.org/support/users/sconfig/, https://profiles.wordpress.org/sconfig/

Ref: #4776-meta

#prio3

#4776-meta

Remove old bbPress1 Search blocking

Currently requests to /support/search.php and /plugins/search.php are blocked for GoogleBot at the LB
Since neither of these URLs are in use today, can we remove these blocks?

Low-priority ref #4765-meta

#prio3

#4765-meta

Update some 302 redirects to 301s

Hi, as per #4630-meta can we update the following 302 redirects to 301’s?

  • chat.wordpress.orgWordPress.org 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. https://wordpress.org/
  • phpdoc.wordpress.org
  • wordpress.org/extend/

Additional ones via #4075-meta

  • wordpress.org/forums/
  • wordpress.org/tags/*

Here’s a diff that should apply to the web role:

Index: wporg-redirects.conf
===================================================================
--- wporg-redirects.conf	(revision 9066)
+++ wporg-redirects.conf	(working copy)
@@ -112 +112 @@
-	return 302 https://make.wordpress.org/chat/;
+	return 301 https://make.wordpress.org/chat/;
@@ -134 +134 @@
-	return 302 https://developer.wordpress.org/reference/;
+	return 301 https://developer.wordpress.org/reference/;
Index: wporg-wordpress.org
===================================================================
--- wporg-wordpress.org	(revision 9066)
+++ wporg-wordpress.org	(working copy)
@@ -36 +36 @@
-	rewrite ^/extend/?$ https://wordpress.org/ redirect;
+	rewrite ^/extend/?$ https://wordpress.org/ permanent;
@@ -88 +88 @@
-		rewrite ^ /support/ redirect;
+		rewrite ^ /support/ permanent;
@@ -91 +91 @@
-		rewrite ^ /support/ redirect;
+		rewrite ^ /support/ permanent;
@@ -99 +99 @@
-		rewrite ^/tags/(.*) /support/topic-tag/$1 redirect;
+		rewrite ^/tags/(.*) /support/topic-tag/$1/ permanent;

#prio3

#4075-meta, #4630-meta