Page MenuHomeDevCentral

architectureTag
ActivePublic

Members (1)

Watchers

  • This project does not have any watchers.

Details

Description

This tag identifies tasks where architectural decisions must be made.

Recent Activity

Jan 27 2017

dereckson moved T267: How are we building our webstack? from Next to Backlog on the Tasacora board.
Jan 27 2017, 23:36 · architecture, Tasacora

Jan 6 2017

dereckson moved T267: How are we building our webstack? from Working on to Next on the Tasacora board.
Jan 6 2017, 06:53 · architecture, Tasacora

Aug 24 2016

dereckson added a parent task for T984: Pick a format for Notifications::$rawContent property: T790: Publish a synthesis of Docker Images rebuilds on #nasqueron-ops.
Aug 24 2016, 03:07 · User-Dereckson, architecture, Technical debt, Notifications center
dereckson closed T984: Pick a format for Notifications::$rawContent property as Resolved.
Aug 24 2016, 03:06 · User-Dereckson, architecture, Technical debt, Notifications center
dereckson added a comment to T984: Pick a format for Notifications::$rawContent property.

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

Aug 24 2016, 03:01 · User-Dereckson, architecture, Technical debt, Notifications center
dereckson added a revision to T984: Pick a format for Notifications::$rawContent property: D635: Simplify PhabricatorNotification and allow to use notifications:payload.
Aug 24 2016, 03:00 · User-Dereckson, architecture, Technical debt, Notifications center

Aug 19 2016

dereckson moved T984: Pick a format for Notifications::$rawContent property from Backlog to Next on the User-Dereckson board.
Aug 19 2016, 13:48 · User-Dereckson, architecture, Technical debt, Notifications center
dereckson added a project to T984: Pick a format for Notifications::$rawContent property: User-Dereckson.
Aug 19 2016, 13:48 · User-Dereckson, architecture, Technical debt, Notifications center
dereckson updated subscribers of T984: Pick a format for Notifications::$rawContent property.
Aug 19 2016, 13:47 · User-Dereckson, architecture, Technical debt, Notifications center

Aug 18 2016

dereckson added a comment to T984: Pick a format for Notifications::$rawContent property.

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.

Aug 18 2016, 12:17 · User-Dereckson, architecture, Technical debt, Notifications center

Aug 17 2016

dereckson added a project to T984: Pick a format for Notifications::$rawContent property: architecture.
Aug 17 2016, 00:13 · User-Dereckson, architecture, Technical debt, Notifications center

Feb 14 2016

dereckson added a project to T620: Review and publish C code convention: discussion.
Feb 14 2016, 02:35 · discussion, architecture

Dec 11 2015

dereckson added a comment to T620: Review and publish C code convention.

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

Dec 11 2015, 01:02 · discussion, architecture

Dec 10 2015

xcombelle added a comment to T620: Review and publish C code convention.

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

Dec 10 2015, 12:29 · discussion, architecture

Dec 9 2015

dereckson added a comment to T620: Review and publish C code convention.

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

Dec 9 2015, 21:33 · discussion, architecture
xcombelle added a comment to T620: Review and publish C code convention.

Where is the llvm C code style guide ?

Dec 9 2015, 20:44 · discussion, architecture
dereckson added a comment to T620: Review and publish C code convention.

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

Dec 9 2015, 07:36 · discussion, architecture
dereckson updated subscribers of T620: Review and publish C code convention.

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

Dec 9 2015, 07:32 · discussion, architecture
dereckson created T620: Review and publish C code convention.
Dec 9 2015, 07:31 · discussion, architecture

Nov 30 2015

dereckson added a comment to T267: How are we building our webstack?.

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.

Nov 30 2015, 08:16 · architecture, Tasacora
xcombelle added a comment to T267: How are we building our webstack?.

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
Nov 30 2015, 07:09 · architecture, Tasacora
dereckson added a parent task for T267: How are we building our webstack?: T603: Establish a roadmap to reach a minimum viable product .
Nov 30 2015, 06:20 · architecture, Tasacora

Apr 8 2015

dereckson moved T267: How are we building our webstack? from Backlog to Working on on the Tasacora board.
Apr 8 2015, 10:28 · architecture, Tasacora

Mar 31 2015

dereckson added a comment to T267: How are we building our webstack?.

List of (front-end) JS frameworks to consider

Mar 31 2015, 23:19 · architecture, Tasacora

Mar 30 2015

Ash-Crow added a comment to T267: How are we building our webstack?.

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.

Mar 30 2015, 22:18 · architecture, Tasacora
dereckson added a project to T267: How are we building our webstack?: architecture.
Mar 30 2015, 15:11 · architecture, Tasacora