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.

\o/

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.

<3

WordCamp Talks (Talk Proposals) weekly slack chat recap

Our 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 happened last week, Wednesday Dec 21 (5:30pm UTC+1). The archive starts here.

No set agenda as it was right before the holiday and attendance was low.
Present: Andrea Middleton, Tom Nowell, and myself, with participation from Josh Levinson.

We covered the following points and came to a few agreements:

  • We’ve validated the 2 CPT approach as the most effective, stating definitively that each has its own separate and unique purpose, giving us far more advantages.
  • We debated the name 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. Talks, and have decided, barring better ideas, that WordCamp Talk Proposals would be more apt and will be reflected in the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. if not 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 namespaces.
  • This brought up further discussion on the use of such a plugin for other types of proposals and WordCamp decision-making where upvoting could be useful. We decided that the direction we’re taking with WordCamp Talk Proposals is very specific to the Call for Speakers process and related post types and taxonomies, and that other types of proposals could use the basic WP Idea Stream plugin if desired.
  • We briefly discussed the single sign-on approach, and agreed that it should be contained in a separate plugin for development and maintenance purposes, as well as to eventually make it available for other usage. But we will focus on it being useful for WordCamp Talk Proposals first and foremost to not slow down the integration of this valuable feature.
  • Tom brought up the idea of rebuilding the code base from scratch; we decided that this foundation was well enough advanced that it was best to continue on the current fork.
  • Tom and Josh were given commit access.

Our next slack chat is scheduled for Wednesday January 4 at 5:30pm UTC+1 on #meta-wordcamp.
Reminder that the plugin can be found here 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/.

Comments welcome. Thanks to all!

\o/

WCEU17 design team is building improved and more flexible WordCamp theme

In the Summer of 2015, a survey on WordCamp.org tools has brought up some great ideas and suggestions for a new default WordCamp.org theme. We, the growing design team of WordCamp Europe 2017, this year 6 people strong, want to help create such a new default theme for WordCamps. The ideas voiced in the survey were pretty much in line with our vision for a new theme.

We currently use the “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. Base Redux” theme for WCEU17 which is based on a very old version of _s, lacking some of the newer features. The Redux theme also has some major A11yAccessibility 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) issues we’d like to tackle.

The suggestions from the survey we felt most strongly about were “serve the many, not the few“, “flexible starter theme“, and “be a theme only“. Using a current version of _s would solve a lot of these wishes voiced by the community.

The status quo

To tackle this, we compared the Base Redux theme with a current version of _s. We wanted to identify feature that were added and might need to be implemented in a new WordCamp base theme. Many added functions in Base Redux are legacy code, including older versions of the custom post types for speakers, session, etc. As those features are now handled by plugins, they are no longer needed in a new theme.

After stripping out all old and unused functions, we identified only some additional widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. areas used:

  • Two additional widget areas after the headerHeader 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.: after-header and after-header-homepage (only on the front_page)
  • Two additional widget before the content: before-content and before-content-homepage (only on the front_page)
  • A second 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.: sidebar-2
  • 5 footer widget areas: footer-widget-1 … footer-widget-5
  • A credit action in the footer (which was never really used)

We do see the need for some additional widget areas and will decide which widget areas make sense to add to the new default theme to add additional flexibility. Having special page templates with no sidebars (full width) or other layout options, could also be very useful additions.

In the comments to the survey, Josh Leuze came up with some ideas for a new default theme. He wanted to introduce a theme with a basic design, so any WordCamp organizing team, with limited design resources, has a good starting point for a nice WordCamp theme. Josh included some of his ideas in the GitHub repo with additional assets for visual design ideas.

A new theme without a bundled design

The Base Redux theme is a starter theme and doesn’t really include any design. When using it you basically have three options, to create a design:

  1. Clone the design of a current WordCamp also using Base Redux
  2. Adding styles to Base Redux using the “Custom CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site.” functionality from Jetpack
  3. Adding styles to Base Redux using the “Remote CSS” functionality bundles in a WordCamp.org 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. 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

For the new WordCamp theme we envision to:

  1. Have a solid technical framework with improved A11y using the latest version of _s
  2. Provide more flexibility and ease in setting up the WordCamp site by providing more layout options, page templates, and additional widget areas
  3. Provide modular CSS and style guide (provided separately / not included in theme – more info below)

Other theme improvements

We’re still working on the full list of theme improvements and features we’d like to include in the new WordCamp theme, but here are some of our ideas so far:

  • More flexible homepage options to share timely announcements, calls for sponsor/speaker/volunteers throughout the life span of an event
  • Page templates for speakers, sponsors, etc
  • Paginated archives for post types
  • Improved A11y

Sneak Peek: Theme CSS and a living style guide

Designing a WordCamp website can be challenging since we can’t modify HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. or JS so it’s important to have a good CSS starting point and documentation to speed things up. Separate from the new WordCamp theme, we’re also creating modular CSS and a living style guide as a convenient starting point for WordCamp organizers to use.

We’ll be releasing it 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. for anyone to use, edit, and fork to create and share new versions. The styles can easily be applied to a WordCamp site using the “Remote CSS” plugin.

We’re hoping this to be a starting point and that the style guide will evolve over time. This will give others the opportunity to release more versions of it for the community to choose from. We understand that not every WordCamp team has design resources, so we want to help with some of the heavy-lifting providing this style guide.

We’ll be publishing more info about this soon. But for now, we’d like to share a few screenshots of what such a style guide would look like:

Style Guide: Color variables and values

Style Guide: Example of components

Big thanks to my team members @kau-boy and @lucijanblagonic who helped me kick this off.

Dear community

We’re very excited about this project and we’d love to hear your feedback! Also read our intro post on WCEU.

#campsite-theme, #meta-wordcamp, #wordcamp-sites

WordCamp Talks weekly slack chat recap

We had our first 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 on Wednesday (5:30pm UTC+1) to discuss the 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. Talks 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. The archive starts here.

On our agenda:

  • One CPT or two? balancing the existing with the incoming.
  • User profiles & login
  • Automation: workload? And should we aim for v1, or can it wait? (dependant on above discussion)
  • Questions, getting everyone up to speed
  • Reporting: how should discussion during these chats be archived?

Present: Mathieu Viet, Andrea Middleton, Josh Levinson, Veselin Nikolov, Kelly Dwan & myself, with input from Tom Nowell, Dominik Shilling & John James Jacoby.

1. The Custom Post TypeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. debate

The WordCamp Talks plugin introduces a new CPT, on top of the existing Sessions, currently called “Talks”. The debate centered around the pros and the cons of having two separate CPTs, versus combining them into one (ie, rewriting the Talks plugin to utilize the existing Sessions CPT).

Consensus was reached that leaving them as two separate CPTs was more advantageous.

  • The two CPTs have different purposes: Talks is for receiving, upvoting/commenting and selecting talks privately; whereas Sessions is for displaying talks and full schedules publicly.
  • Each has taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. and/or 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. data not used by the other. (although it could be interesting to integrate categorization into Sessions, a separate debate :)).
  • Large WordCamps can receive over 200 applications, whereas the final selection is usually no more than 60. From a UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. standpoint, it would be much easier for organizers to manage this reduced final selection than having to scroll through a list of both selected and rejected talks.
  • The workload to automate the process of selecting from Talks to publish to Sessions is minimal. So whereas it does create some redundancy, it does not significantly increase the workload for organizers (check boxes, push a button).
  • This also means that Talks remains optional, it doesn’t have to be a requirement for organizers to work this way (didn’t come up in discussion, me adding it now :)).

Barring veto from @iandunn 😀 or additional arguments against this approach, we’ll continue development in this direction. Tom Nowell said he would have an alternative proposal – so we’ll discuss it at the next meeting if he’s ready.

2. User profiles & login

The ultimate goal of this plugin is streamlining the entire Call for Papers process for WordCamps. One of its key features is allowing applicants to log on to the site, creating a user profile account, from which they submit multiple talks, edit their talks (time frame defined by organizers), edit their profile at any time and view the ensemble of their submissions.

After much discussion about the best way to integrate and conform to the existing WordCamp sites and Speaker CPT, we are looking to create a single login based on wp.org user profiles. This will have the additional advantage of not only allowing users to submit more than one talk from a single profile, but effectively submit multiple talks to any WordCamp from their single wp.org profile. Brilliant!

What if an applicant doesn’t want to sign up to wp.org? Will this be excluding some people outside of our community from participating?

This question was raised during our work session at Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. during WCUS. After further discussion we concluded the following:

  • In either case, the applicant will have to sign up somewhere, creating an account on one or the other website. They are required to provide us with a certain amount of personal information.
  • In the same way that speakers are required to sign waivers, allowing organizers to film them and publish their talks to WordPress.tv, this will become a requirement of participating in an official WordCamp.

Unless strong arguments can be made against a universal login, we will proceed with development in this direction.

How to go about it? We were pointed to the following (thanks, Dom!):

  • https://meta.trac.wordpress.org/ticket/721
  • https://meta.trac.wordpress.org/browser/sites/trunk/common/includes/wporg-sso
  • https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-login

3. Automation and feature roadmap

We solved this pretty quickly: no need to wait, automation can be achieved for the v1. This was mainly regarding publishing from Talks to Sessions, but also regarding the Speaker CPT, which we’ll be digging into as we move forward on the login.

4. Reporting

We agreed that this was the best spot to post full reports of our meetings 🙂
If you have comments, ideas, opinions on any of this, please weigh in!
Or if I left anything out or reported sideways, let me know! 🙂

Our next slack chat is schedule Wednesday, December 21 at 5:30pm UTC+1 (Paris time) on the #meta-wordcamp channel. I’ll post a proposed agenda a few minutes before we get started.

The plugin is on github if you want to contribute https://github.com/imath/wordcamp-talks

WordCamp Talks – weekly slack chat

Hey folks! We’re starting a weekly chat on the #meta-wordcamp Make 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, beginning this Wednesday, December 14 at 5:30pm UTC+1.

The goal of the meetings will be to advance discussions around the features of 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 and the specificities of integrating it into 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. sites, as well as to organize and distribute the work load. We had some great conversations during WCUS, and I’d like to keep that momentum going!

Currently on board: @imath @joshlevinson @dzver @tomjn (and maybe @tacoverdo).

If you’re interested in getting involved, please feel free to join us.
First, catch up on the conversation:

WP Idea Stream for the WordCamp admin toolbox

WordCamp Talks Beta


https://github.com/imath/wordcamp-talks