My two cents on the columns:

Documentation has the same issue, and milestones as well I think.

thanks. src/extensions works like a charm

The custom code is to be places under src/extensions folder. We already have custom apps for buildbot and documentation integration.

I am just a bit worried we might also loose a bit of reputation if we leave broken stuff alone for too long...

but for 2.81 the most important is to get started with 'new stuff'

I've gone ahead and tagged them all (the High Priority ones). More or less blindly as the priority decission has been made by core devs, so no use to mix in my own priority here again I think...
I might even add more High Priority ones the comming days (the more I go over - older - confirmed bugs, the more [pretty bad] regressions from 2.79 I find...)

We have previously been using high priority bugs as meaning "must be fixed before next release". So to me it makes sense to just tag all those with the Blender 2.81 milestone.

I think they should be considered as well, but for 2.81 the most important is to get started with 'new stuff'.

I still dont see any bugs tagged for this milestone.
Not even the High Priority regression ones.
https://developer.blender.org/maniphest/project/2/type/Bug/query/1BLyvlG786dk/#R

could this (setting the status) be automated when dragging a task from one column to the other? automated when committing?

Alright, everything properly tagged (with few exceptions). Closing now

regarding the workboard workflow:

FIrst, is this intended for any tasks or only bug reports?

Maybe this suggestion I'm about to make, someone won't like it, but it doesn't matter,
I have something to say that I think is important.

Hi, I have some feedback based on our current process, my previous experience with code quest, and personal opinion. Take with a grain of salt, I don't want to sound negative, just to present some counterpoints:

thanks. it works now
in order to have a new OAuth2 provider in Phabricator, i have to add a class also in lipphutil

I have a patch for the subproject tagging. Do we need the structure to show only during the moment you search for tags while typing in the edit box?

The Phabricator repository indeed doesn't have the arcanist and libphutil as submodule. You need to clone those repositories as per Phabricator installation guide, then checkout the following sha1s:

HI. i have couple of questions

Good morning Dalai! At the moment I m testing the OAuth2 login communication between Phabricator and Blender ID. It seems to be pretty straight forward as its well implemented on both side. I m actually spending more time setting things up.
In Phabricator, i m simply extending the PhabricatorOAuth2AuthProvider class, which handle all the work.
Right now, as Blender ID require an https return URI, i have to change my local phabricator to https.
Implementing the badge system will required more coding. I have still not had a look at it, thats why the OAuth2 login is a good warm up for me :)
at the moment, I can only work a couple hours a day for Blender.

Hi Frederic. Francesco has mentioned someone working on it. Could you give a bit more detail on that and how far you got already?

i have started to integrate the BlenderID OAuth2 for phabricator. you should be able to see something in the following days