WordCamp Talk Proposals weekly slack chat recap 04/01/17

The last weekly 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/. chat took place Wednesday Jan 4, getting a false start at 4:30pm and off the ground and permanently moved to 5pm UTC. The archive starts here.

The agenda came about following a series of comments left by Ian Dunn on previous meeting notes 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/, requiring further discussion on:

  • the CPT debate, 1 CPT, 2 menu items?
  • Login, in or out of scope?
  • Both which touch on: general scope, how far ahead should we be thinking and is it slowing us down (i.e., global proposals, etc).
  • Code base: current fork or start over?

Present: Mathieu Viet, Tom Nowell, Andrea Middleton, myself.

The CPT debate

We agreed that using one single Post Type, but with two separate menu items, is a nice compromise and a clean approach to the problem. Rather than retain the Talk CPT, the 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 will be rewritten as an extension of the Session CPT.

Attendee rating tool

Not on the agenda, but a point that Ian brought up, is a parallel project being developed by Ptah Dunbar.

since this is highly relevant to the post-session attendee-rating tool you’re working on. It may make sense to integrate these two projects to some extent, rather than duplicating a lot of functionality.

After brief discussion about the front-end implications of where each tool would need to display information, we do not see any obvious conflicts. The Attendee rating tool seeks to display user feedback on 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. Sessions pages, which are not directly exploited/modified by WordCamp Talk Proposals. We agreed to contact the other team and invite them to the discussion and to mutually follow each other’s project.

Login and Speaker pages

This project has lead us to a larger project of creating a single sign on approach, using wp.org accounts as a basis for Speaker submissions.

Ian has suggested that this might be scope creep, and that we may want to focus on a per-site login method for now.

While we’re undecided on whether or not we agree that this is scope creep, enthusiasm did lead to some debate about whether or not the Speaker CPT still had purpose. And we did agree that would be scope creep, and that in the interest of backwards compatibility we would table such discussions for now.

Other questions raised around the idea of starting with wp.org user profiles:

  • How do we then populate the Speaker pages?

-> current thinking: some kind of prompt that allows admins to search a list of registered users and import their information.

  • When you click on a Speaker link from the site, where does it take you?

-> To the Speaker’s page on the WC site (not to wp.org)

  • How universal do we make the login? Will it require profiles to be the same? Or can profiles be modified on a per site basis after « import »?

-> We agreed that more discussion was needed around offering a simple sign up/workflow versus giving users and organizers some autonomy and choice.

Post Script

I was able to touch base with Ptah and briefly discuss his project with Daniel Iser (David Bisset is not longer participating). He provided us access to their working document.

We touched briefly on one potential commonality between the two projects: Speaker login. He will try and join us for our next chat to discuss further.


Further discussion was also had around the SSO implantation, with input from John James Jacoby, Otto and Sam Sidler.

From Sam,

Our goal was to get OAuth 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/ so that external sites (like wordcamp.org and bbpress.org) would use it to login to their respective sites.
But OAuth 2 is much harder to implement than we anticipated. Since something like it has to happen for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., we’ll hopefully be able to piggyback on that this year.

It’s clear that these are two separate projects, so our goal has to be to look at the overlap and come to an agreement on scope so that we can proceed with our main feature goal without being held up by dependencies.

Our next slack chat will take place this Wednesday, January 11 at 5pm UTC on #meta-wordcamp.