Corey McKrill 9:16 pm on August 2, 2017
Tags: 2100-meta, , 2934-meta, 3003-meta, 574-meta, 859-meta, , ,   

Recap of WordCamp.org Ticket Scrub for the week of July 31st

Great attendance for our first-ever WordCamp.org ticket scrub!

The next WordCamp.org Ticket Scrub meeting will be in two weeks, 2017-08-15 19:00 UTC, in #meta-wordcamp.

Here is a summary of this week’s discussion:

#2907-meta

This patch makes some significant changes to the Instagram source in the Tagregator pluginPlugin 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. to accommodate changes to the Instagram APIAPI An 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.. The current patch submitted by @xkon uses raw cURL commands, which is not ideal for compatibility. The suggested change was to try using `wp_remote_get` or `wp_remote_post` instead. @ryelle volunteered to help test this and other Tagregator patches. (#2100-meta, #3003-meta)

#2934-meta

This ticket has a patch from @rmarks that partially addresses the issue. @coreymckrill said he would try to get that patch committed, and suggested fixes for other parts of the issue should go in a separate patch.

#859-meta

We discussed the patch for this ticket recently submitted by @grappleulrich. One aspect of the patch was to prevent users from publishing posts while Coming Soon mode is enabled, so that site subscribers wouldn’t get an email notification of a new post that might be incomplete and that they wouldn’t actually be able to access. As a group, we agreed that disabling the Publish button would actually be confusing and that there are times when you might want to publish a post while still in Coming Soon mode. Instead, we decided to change the approach so that email notifications are disabled in Coming Soon mode, and there is a warning near the Publish button to notify users that their post won’t be emailed to subscribers if they publish while still in Coming Soon mode.

#574-meta

This is an old ticket with an old patch. We agreed that the feature described would still be useful, but the patch probably needs to be updated before it will be compatible with the current version of CampTix. @coreymckrill said he would move the ticket over to the CampTix GitHubGitHub 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 by the repository owner. https://github.com/ repo.

If you were unable to attend this meeting but have feedback, please share your thoughts in the comments on this post. In case there’s a need for further discussion we will ensure to make time for it in the next meeting. See you next time!

#recap #ticket-scrub #wordcamp

#2100-meta, #2907-meta, #2934-meta, #3003-meta

Corey McKrill 9:04 pm on July 31, 2017
Tags: , ,   

WordCamp.org Ticket Scrub for the week of July 31st

This is the agenda for our first bi-weekly WordCamp.org ticket scrub, which will happen at 2017-08-01 19:00 UTC in #meta-wordcamp.

  • The main goal for this first meeting is to start going through the list of WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.-related good-first-bug tickets, review their status, and adjust status/keywords as necessary.

If you have some thoughts beforehand or would like something related to be part of the agenda, feel free to share your ideas in the comments for this post. See you in the chat!

cc @sergeybiryukov @grapplerulrich @ryelle

#agenda #ticket-scrub #wordcamp

+make.wordpress.org/community

Corey McKrill 9:10 pm on July 26, 2017
Tags:   

Experiment: WordCamp.org bug scrubs

There are a lot of open WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.-related tickets in 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. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. that don’t get much attention. Some of them even have patches ready to go. The problem is that each ticket requires discussion and testing before it can be resolved, and we don’t currently have the bandwidth to keep up with it all.

Here’s what I think an ideal ticket workflow looks like:

  1. Ticket is opened
  2. Ticket issue is confirmed and the ticket is accepted
  3. Patch(es) added to the ticket
  4. Patch code is reviewed
  5. Patch is tested against issue’s reproduction steps
  6. Patch is confirmed and committed
  7. Ticket is closed

When multiple people collaborate on tickets, getting through these steps is much faster. I’d like to propose that we try having scheduled meetings in the meta-wordcamp 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/ channel to work through tickets together. We could model this after CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. bug scrubs, and with at least 3-5 people attending, we might be able to make progress on several tickets each time.

I’d like to try doing them every two weeks. My preference would be *every other Tuesday at* 17:00 UTC, but I’m open to other time slots if they can accommodate more people.

Leave a comment here if you’re interested in participating, and whether that time and date would work for you.

cc @grapplerulrich @sergey @miss_jwo @brashrebel @iandunn @shadyvb

+make.wordpress.org/community

#wordcamp

Jenny Wong 10:26 am on May 30, 2017  

X-posting Proposal: WordPress Community Conduct…

X-posting Proposal: WordPress Community Conduct Project
Please read + comment on the original post.

Proposal: WordPress Community Conduct Project

Corey McKrill 12:29 am on May 24, 2017  

Finalizing Meta topics for the Community Summit

I just popped in here and realized that there isn’t a post yet for discussing 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.’s community summit topics. I’ll couch off of @hlashbrooke‘s post to get things started.

The Community Summit is going to be hosted in Paris just a few days before WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe, on 13 & 14 June 2017. We are at the stage now where all contribution teams are being asked to finalize their topics for the Summit. The deadline for final topics is 9 June 2017.

The currently proposed topics for all teams are listed here, and these are the ones for the Meta Team:

  • Translation of documentation on 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/, including developer hub and (the future) help hub – (Polyglots, Docs, Support)
  • Participate in other team’s discussions to see how the Meta team can help them

Are there any additional topics that you feel are important for us to discuss at the Summit?

While answering that question, please bear the following from the Summit announcement post in mind:

The main purpose of the summit is to move the project forward before and after the event, with the event being a milestone in a larger set of work.

With this main goal in mind, we’ll touch base with all team reps to figure out which of the topics proposed can be handled beforehand, and come up with topics that would be:

1) of importance to the project as a whole
2) would benefit from cross-team collaboration
3) will leave us in a better position than when we started

Tellyworth 3:00 pm on March 30, 2017
Tags:   

Announcing the new WordPress Plugin Directory

The 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. team is very happy to announce the launch of the all-new WordPress PluginPlugin 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!

First announced as an Open BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. at WordCamp Europe 2016 , this latest evolution features a range of improvements, both internal and tangible:

  • A new back-end based on WordPress, to replace the old bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org engine.
  • Refactored APIAPI An 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. code, also open sourceOpen Source Open 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..
  • A complete visual redesign and open-source theme.
  • A completely open-source codebase.
  • A vastly improved search engine.

Developers and testers running early versions of WordPress 4.8 have already been using the new API for a while now, and many in the #meta community have been testing and contributing to the new directory’s development.

For those of you seeing the new directory for the first time, here are some of its features in detail that will interest both plugin developers and users:

The search engine has been totally replaced. Searches now return the most relevant results based on a combination of many factors including version compatibility, recency, and popularity, in conjunction with text relevancy. This means that obsolete and unsupported plugins – while still available – are less prominent in search results than those in active development and use.

Search results in the old directory, left, and the new directory, right.

The most important information about each plugin is shown up front, rather than on separate tabs. The description, screenshots, and FAQs are all visible together, with a simple scroll, without flipping to a separate tab. Important metadata like versions and ratings are shown in a sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme., much like before, but we’ve simplified the page with a 2-column layout, removing extraneous navigation from the old 3rd column.

Plugin details in the old directory, left, and the new page, right.

We have also revised accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) across the new design, with improved text sizes and contrast, and better markup for screen readers. The new design is responsive and works well on mobile and desktop devices with a wide range of sizes.

Behind the scenes, the entire back end of the web site and API has been replaced with an open source WordPress plugin. The old directory was built on bbPress with a collection of ageing, closed-source plugins. It was antiquated and difficult to maintain. The new directory uses the best practices of modern WordPress development; and, since it’s entirely open source, can be maintained and improved by a much wider community.

It’s been a long road, so it’s very exciting to finally launch the new Plugin Directory. Thanks to everyone who has contributed their time and energy to the project, especially @obenland, @mapk, @dd32, and @gibrown, whose enthusiastic efforts made everything look easy.

The new directory has been built with future maintainability and iterative enhancement in mind. We’re looking forward to hearing feedback from the whole WordPress community, and making regular improvements and additions. Bug reports and specific enhancement requests can be made in Trac. The best place for questions and general discussion is the #meta channel on 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/.

Ian Dunn 12:08 am on March 23, 2017
Tags: ,   

X-post: Showing upcoming local events in wp-admin

X-post from +make.wordpress.org/community: Showing upcoming local events in wp-admin

Tellyworth 12:19 pm on February 15, 2017
Tags: ,   

Plugin directory chat 2017-02-15

Join us at 22:00 2017-02-15 UTC in #meta for our first regular pluginPlugin 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 chat in a while.

#plugin-directory #meta

Samuel Sidler 1:27 am on February 11, 2017
Tags: make.wordpress.org/hosting,   

X-post: Building a Machine-Readable List of WordPress Events

X-comment from +make.wordpress.org/hosting: Comment on Building a Machine-Readable List of WordPress Events

Mark Uraine 1:59 am on January 21, 2017
Tags: ,   

Handbook Redesign

The Handbooks are slowly being updated to the o2 theme (Breathe). With this upgrade, I’ve been thinking about how we present our documentation, reference materials, etc. While Breathe was definitely refreshing, there’s still some experience issues I need to work through.

CURRENT ITERATION

Right now, the amount of floating menus on the page is too many. When navigating to a Handbook page there’s a floating menu on the left side, and possibly another floating menu on the right side for in-page navigation. This compresses the initial intro of the document a user might be reading causing some confusion with its odd flow of characters.

Current Handbook

 

PROPOSED ITERATION

I believe we could alleviate some of this by anchoring the left side menu a bit better and structuring these pages to appear more like a true documentation portal. I made a few changes in Inspector within the browser and came up with something like this (b/c of this there’s no mobile version yet):

Handbook

 

Some PROS and CONS are mentioned in a conversation here: https://meta.trac.wordpress.org/ticket/2389

FEEDBACK

Please leave some feedback here in the comments or on the actual ticket. Everything is helpful. I’m personally struggling with the floating right-side menu. There’s been some good ideas for solutions, what’s yours? If you have a few minutes to take a brief survey regarding the Handbook usage, please do! Handbook Usage Survey

 

#design, #make