Manual talk:Developing libraries

Automated style checks
"Automated style checks are STRONGLY encouraged..."

Can you point to a place where this is done? I'm using MediaWiki coding style for a lot of my libraries though do not have any style checking in place, so I'm curious on how to do this well.

--Jeroen De Dauw (talk) 18:36, 31 December 2014 (UTC)
 * We have a set of codesniffer rules that are run on the WMF Jenkins servers. The rules are in gerrit at tools/codesniffer. I have opened T85631 to track getting this package to include a composer.json and publishing to Packagist to make including it in local tests and via services like Travis easier. --BDavis (WMF) (talk) 18:50, 31 December 2014 (UTC)

Users
These 12 sections are important, thanks for compiling them. However, none of them is relevant to the only question users have: "will my wiki still work?". If we want guidelines, we need principles about the end result. For example: --Nemo 08:22, 8 January 2015 (UTC)
 * the tarball must just work;
 * an official packagist package needs to be made available (with ?) if it isn't yet;
 * packagers (e.g. Debian package maintainer) need to agree with the guidelines/continue providing the same level of service or higher;
 * no additional step(s) must be added to the installation process;
 * the list of requirements must always be complete, but should get shorter for the typical user and/or less relevant (e.g. we should support more platforms, not less, by including libraries);
 * the initial clone/install for a developer should not be longer than X (hours? no idea how to measure).