Can we please disable the ticket update module on plugins.trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.?
Since plugins.trac is mostly unusable, many plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party authors use Github GitHub is a website that offers online implementation of git repositories that 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/ and sync over changes. Unfortunately many of these include commit messages which includes “closes #123” or “fixes #123” which ends up with many people subscribed to tickets on trac, for example:
https://plugins.trac.wordpress.org/ticket/1 & https://plugins.trac.wordpress.org/ticket/2
It looks like we can simply disable the
Commit Ticket Updater trac module?
$ curl -I https://downloads.wordpress.org/release/wordpress-4.6.1.zip
HTTP/1.1 200 OK
Date: Thu, 24 Nov 2016 09:33:22 GMT
Content-Disposition: attachment; filename=wordpress-4.6.1.zip
Last-Modified: Wed, 07 Sep 2016 14:59:22 GMT
X-nc: HIT lax 189
The header The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. was added 5 years ago in [dotorg5308]. [dotorg7078] added
X-Accel-Redirect which may be the reason for the missing header now. To quote @dd32:
IIRC even when sent by PHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php., when it’s a X-Accel-Redirect it needs to be whitelisted in nginx NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/... I think we’ve enabled it and never pushed a change into nginx..
As reported in https://meta.trac.wordpress.org/ticket/1860 W.org is responding incorrectly for certain requests, I’m unsure what the cause is and whether it’s a nginx config or not.
Here’s a cURL command to reproduce:
$ curl -v 'https://wordpress.org/plugins/search.php?page=2&q=plugin'
* Trying 18.104.22.168...
* Connected to wordpress.org (127.0.0.1) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.wordpress.org
* Server certificate: Go Daddy Secure Certificate Authority - G2
* Server certificate: Go Daddy Root Certificate Authority - G2
> GET /plugins/search.php?page=2&q=plugin HTTP/1.1
> Host: wordpress.org
> User-Agent: curl/7.43.0
> Accept: */*
* Empty reply from server
* Connection #0 to host wordpress.org left intact
curl: (52) Empty reply from server
This is lowest of the low priorities, more as a FYI. The plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party directory will hopefully retire soon and this isn’t reproducible against the new directory, most likely due to the change from query variables to rewrites. If this is a
wontfix I don’t think anyone will mind.
Recently we started getting errors when trying to delete forwarders. For example:
Unable to locate the forwarder “email@example.com” for account “firstname.lastname@example.org” on domain “gmail.com”.
We can still add them, though.
I tried manually edited
/etc/valiases/wordcamp.org, but it just got overwritten a few minutes later with same contents it had before, so it seems like it’s not the canonical source for that data.
You can use the
iandunntest2 forwarder for
email@example.com as a test.
Can I please have commit access granted to buddypress.svn.wordpress.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/ for the following WordPress.org usernames:
Slaffik is our 2.8 release lead The community member ultimately responsible for the Release.. Netweb will be helping maintain BuddyPress’s build-tools. Offereins will be helping with some feature development.
Boone had the roles & responsibilities talk with them, and confirmed secure passwords for all.
The entire core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team is pumped for our new recruits to get started! <3
#buddypress, #commit, #prio2