Lewis Goddard

I think a repository containing a stylesheet and a couple of test pages with plenty of elements is a good idea, but I don't think there's a need to version...

I mean I would like to pull in just 1 file, only when I choose, from another repository. That doesn't seem like it should need an entire new pattern when...

You wouldn't need to pull the repo, just download that one file, then file a merge request like we do for translations or chart updates. It seems unnecessary for us...

Ultimately, so long as updating is well documented, I'm not opposed to any method.

Seeing as we are now including the icons via a git submodule, and WebKit2 is in Epiphany (although we will need to support Freya for a while), this might be...

Does the `foreach ($res as $mail) {` that handles the result not require change?

I use services like Codacy or Code Climate to run PHPCodeSniffer or PHPMD, although adding it to the existing Travis CI builds would be nice. I have no major problems...

We would need to exclude things pulled in via composer, an potentially `docs/_mdr/Parsedown*` unless that is moved (messing with MDR).

I think the standard is open to discussion depending on how many changes need to be made. PSR2 might be easier to automatically lint for from where we are right...

We cleaned up languages that lacked a significant amount of translations, and since then the website doesn't appear to support Persian. https://l10n.elementary.io/projects/website/#languages We would need to generate new template files...