Summary for Helphub Meeting 8 August 2017


@milana_cap @sergey @kenshino @atachibana @mapk @kafleg

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

@atachibana reports that editing remains at an even pace.


@mapk has been tasked to create issues on 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. for quick wins to getting the staging site to look…. proper. The whole ‘under construction’ look while backend work was being worked on and it was proving a distraction to those working on the project.

After the quick wins are covered, we will move on to proper UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. design.


Fixes were being held back due to a backlog of Travis issues. @clorith volunteered to fix them.

To get away from the style.css conflict, it’s been decided to keep 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 Plugin Directory or can be cost-based plugin from a third-party styles within plugins.

@kenshino is to update the collaborator list to more accurately reflect the people working on the project.

@milana_cap suggested we create a fixed date where we do a quick bug scrub weekly.

Update: Travis issues are fixed and we’re back on track and the bug scrub happened on Thursday.


We spent a little bit time discussing on how to increase the quality of our meetings and get more participation.

It was noted that the following would help

  • Proper meeting summary to be written always, possibly to have this task rotated every meeting
  • More interaction between meetings – a bug scrub was suggested as one of the things we could do
  • Tasks should be properly assigned and documented (Development and Editing progress to be updated on Github and TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the team uses for example: respectively)

Read the meeting transcript in the Slack archives.

The bug scrub transcript is available here.

(A Slack account is required)