We've sort of reached a status-quo:

• Trusted Contributors is basically "community members" - with a low bar for entry
• Blessed Committers is the next level up, and can basically push whatever code they want
• admin/root/security is basically "core team".

In T15206#5910, @valerio.bozzolan wrote:

In T15206#5663, @avivey wrote:

Looks like it's @chris that controls phorgelabs.

Also thank you @chris for setting yourself as a public user here https://github.com/orgs/phorgelabs/people so people can understand this

Whereas it would be nice for me to understand this duplication

In T15206#5663, @avivey wrote:

Looks like it's @chris that controls phorgelabs.

I think @Matthew could set the related user as a public one from https://github.com/orgs/phorgeit/people so it's more obvious to other people, and so we kill the need of extra/external team documentation

@avivey using your Google and GitHub accounts create OAuth supports. You first need to unlock Auth modifications to Auth.

Checked using Incognito window, the default time is UTC and 24 hours format.

Looks like it's @chris that controls phorgelabs.

Probably nobody.

Should we support oauth login via github/google/etc?

Right now, Trusted Contributors can land revisions that were accepted by Blessed Committers.

We need to support OAuth.

This mission is probably over as only Trusted Contributors may create tasks.

W5 has been set to editable by Blessed Communicators

We're around, just quiet :-)

@Matthew sorry for bothering

:(

The concept we're aiming for is "Extension Store" - Core to be minimal,. and everything else to be an optional install, with an "app store" somewhere here, and making installing extensions easy.

Isn't it possible to open a branch for that? who decide what feature can be integrated in Phorge? Just a remark, Phrequent *is* the application for time tracking, even quite empty by now

Looks great. I implemented a rough and simple logging feature over Phrequent, your extension looks more precise. I would think its better to merge/replace Phrequent rather than adding more implementations, though

Boldly closing, as L1 exists and is available to sign.

I think we're done here too? E13.

@speck Would it be totally unreasonable to instead do: