Summary for HelpHub Meeting 9 September 2019

@kenshino @milana_cap @leogermani @kafleg @aion @softservenet @Pieter @audrasjb @estelaris @bph @joyously


Development of HelpHub was blocked for 2 things and discussed:

  • design is being revised by @estelaris
  • 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. 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 released code are all centrally managed through SVN. workflow is being set by @netweb

@estelaris commented for HelpHub design:
This is the document to gather all the requirements docs team has.

Design team review

They reviewed two things:

  1. mobile view
    They agreed that it needs to change, so they are working on a template to be used by the entire ecosystem.
  2. anchor symbol
    They are thinking about using a similar treatment to 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 be the repository owner. It will be global as well.

#needs-desing keywords for tickets

@estelaris added needs-design keyword to 3 tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. tickets:

@estelaris will look into those 3 this week and will add screenshots

Improbements for archives

Docs Team did make some decisions on previous meeting that should improve usability of them

  1. Team agreed to use custom excerpts for each article – this is extra work for content but we can all help perhaps we can add another column to @atachibana ‘s document.
  2. Order of posts will be set manually because we want to make it contextual/complexity/step-by-step order
    This can’t really be automated and applicable to every categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. so we’ll use the order functionality in Post Attributes and @felipeelia already created patch for it.

Dev flow setup

@kenshino will catch up with @netweb.
@leogermani will test the documentation to get the dev environment up.

HelpHub rosetta release

Now, there are two releases: Serbian and Japanese.
Serbian team had HelpHub enabled on wrong site. It was disabled then and enabled on /support/ so they are ready to go.
Japanese team shared guide for getting started with this.

French, Brazil, Russia and some other countries are in the line for that activation.

HelpHub contents migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.

@leogermani migrated content and hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.. Top 3 actions and filters (total of 6) were done and @millana_cap reviewed.

Open floor

@milana_cap suggested to have different people leading the meetings, Like rotating but more volunteering. We can call it a facilitator rather than “leading”. The agenda already mentions people sho will “lead” each topic.

@leogermani volunteered to lead the next HelpHub meeting, and @softservenet follows.