We'll start with inline JSON and we'll advise when new formats pop. JSON is more and more universal.

JSON makes a lot of sense, there is no need to parse twice a JSON payload, once for our notification format, once for the source payload.

In T620#5505, @xcombelle wrote:

Le llvm style guide, c'est un style guide pour c++ par pour le c ?

Le llvm style guide, c'est un style guide pour c++ par pour le c ?

http://llvm.org/docs/CodingStandards.html

Where is the llvm C code style guide ?

For the remaining, we should also document an cross-languages set of recommendations, at least for C family.

Adding people having write some code in C in their life as bug CCs.

Note: I'm only going to speak about the front-end, as the fact we code the back-end in Node.js or in Python doesn't matter a lot to this question.

About the browser stack, two questions (more or less related)

• Does a framework bring a lot comparing to vanilla javascript for the use ?
• Which browser we intend to support. A good target would be in my opinion Grade A support by mediawiki

List of (front-end) JS frameworks to consider

If we don't rely on a PHP back-end, let's go for Django. For easy JS manipulation of .svg files, we should try and see if raphael.js suits our needs.