Attendees

• Soumya "Having Sucky Internet" Deb
• Leo "WIP" McArdle
• Tomer "WordPress" Cohen
• Jan Bambach
• Tara Shahian

Agenda

• Welcome and introduction
• MCS Theme
  • Timescale?
  • Public vs Private
  • Subtheme vs Start From Scratch
  • Organisation (decentralization/delegation)
  • Ping WebDev team to take the repo to github.com/mozilla/mcs
  • MCS Themes Vs. Community Customization Packs [CCP]
• We need a slogan, a vision, a goal!
• What will we do with the wiki?
• Meeting Schedule
• Coding Style

Meeting Notes

Welcome and introduction

• We have the aid of Tara from creative, huzzah!

MCS Theme

Timescale?

• Will be done as part of the whole update of the visual style of mozilla.org/firefox and mozilla.org
• Huge effort which won't happen till next year
• Needs a lot of discussion to ensure we have a strong theme
• Leo's mockups https://github.com/leomca/mcs
• What should we do until the visual update?
  • Sort out the wiki

Public vs Private

• Public being in the CMS's theme repo
• Private being on our own site
• Let's discuss this further when we know more about what the theme is going to look like

Subtheme vs Start From Scratch

• The debate rages on...

Organisation (decentralization/delegation)

• Mozilla generally works by delegation
  • This is where someone is given power over a sub-section of a project

Ping WebDev team to take the repo to github.com/mozilla/mcs

• Let's not atm, since we're not making any official MCS theme

MCS Themes Vs. Community Customization Packs [CCP]

• The CCP is, er, what it says on the tin - different things that allow communities to change the look 'n' feel of their website, slides, etc.
• The theme is part of the CCP, so there's not really any 'vs' here
• Let's discuss further on the mailing lists

We need a slogan, a vision, a goal!

• Let's discuss on mailing lists

What will we do with the wiki?

• Make it our homepage, much like what remo does
• Start afresh and backport any articles we need to

Meeting Schedule

• Weekly meeting
• Let's discuss time on mailing lists

Coding Style

• let's put this on wiki and discuss at a later date
• 4-spaces tab indentation (and use spaces, instead of \t)
• Don't leave unnecessary spaces in a blank-line or end of a line's code
• Leave a blank-line at the end of each files (& always use Linux newline \n [LF])
• Define variables at the 1st line of it's scope-block, as much possible
• Preferably, use camelCase for variable names, in JS
• Start branches from committing readme & then touch the files you need
• Only commit the files immediately necesary, not the ones probably required for future
• Never commit a massive ammount of code in one commit
• Add/fix features & commit only that much (one commit per fix)
• ...even if it's one character manipulation
• Before committing code check the DIFF *very* carefully
• Remove unnecessary modifications in line not related to that FIX
• If you've done multiple fix, preferably remove others for next commit & do one commit per fix
• Put *really* meaningful commit-messages (ever written a Telegram? ;)

Things to discuss on mailing lists

• CCP
• Slogan/vision/goal
• Our meeting schedule