Maintain other implementations under the same GitHub organisation

[Krinkle]

How would you feel about moving the PHP port (from MediaWiki) and original (now abandoned) implementation in Python (from Google) to this repository. We could implement (partially?) shared test cases and other things, and a nice common versioning and release notes scheme.

The nodejs implementation can continue to be published on npm. We could consider publishing the PHP implementation on Composer.

[trevorparscal]

Let's do this thing!

/me awaits pull request

[GaryJones]

How about moving all of them to a new organisation e.g. https://github.com/cssjanus ?

[Krinkle]

@GaryJones I like that (at least moving it to an organisation, including nicer github.io domain).

Separate repositories does make it harder to share data and enforce API parity. E.g. if we maintain the test cases centrally and fetch 'em in the unit tests, it could cause one of the implementations to have a broken build without it having changed anything. Whereas when in the same repo, we can require that interface changes update all implementations at once. But that also shows the obvious drawback (having to update all at once). Separate repositories certainly has more benefits than overhead I think. Thanks!

[jdforrester]

Seeing that the organisation exists, is this just waiting for the repos to be imported?

[Krinkle]

https://github.com/cssjanus/php-cssjanus