I also created a Jitsi meeting and put that in the description of {E1}.

I turned on prototypes and created {E1}, adding everyone currently (individually) cc'd on this task as an invitee.

In T15071#1840, @speck wrote:

should we enable prototypes on this install to try and use the calendar application for organizing this event?

Phabricator has a Calendar application but is prototype. I believe it's mostly functional -- should we enable prototypes on this install to try and use the calendar application for organizing this event?

4pm-8pm GMT (6-10pm GMT+2) sounds good to me - I can even go up to ~midnight and looks like I'm the east-most.

501(c)(3) is extremely easy to set up.

Time tracking is an interesting topic. At my company we addressed this by having a Herald WebHook hit our internal server whenever activity we're interested in tracking happens. Our internal server tracks these activities from multiple sources (not just Phab/Phorge) and users can go in to see all their activity linked up and input the approximate time spent on those activities.

I'd definitely love to see this later. I MIGHT be able to get to this later.

This looks pretty great! - I think T15030 is the general covering task for Extensions

Wouldn't this be a subtask of Legal? If admin has access to shell and/or PII, then this would be something for legal stuff.

@MikeCripps welcome aboard! I added you to trusted contributors group.

Any chance that anyone has insight on D25015? Specifically, a way to get l18n (internationalization/translation) information from PHP into JavaScript from a minimalist approach

In T15010#1272, @MikeCripps wrote:

Really glad to see Phabricator will live on - I've previously managed some bugfixes in an external repo and would love to try to get them into upstream. I've run Phabricator instances for 7 of the last 9 years (and was unable to convince my previous employer to switch) so I've got a bit of experience on the managing side as well.

Really glad to see Phabricator will live on - I've previously managed some bugfixes in an external repo and would love to try to get them into upstream. I've run Phabricator instances for 7 of the last 9 years (and was unable to convince my previous employer to switch) so I've got a bit of experience on the managing side as well.

I think I just set that via "Global Default": https://we.phorge.it/settings/builtin/global/

the only global config option I can find is the timezone, so either way changes to phorge core would be required. Timezone has no default value. (It's typically controlled by the php date.timezone setting)

I added you both as well! Welcome to the team. If anyone has pre-existing functionality that they feel would be good to include in the upstream feel free to submit the changes. There's ongoing work (unfortunately slowly) to rebrand the project, but that's not holding up other changes at this time.

I'd be happy to contribute. I currently maintain an installation with over 4,000 git repos and over 2,000 users since 2016. Our company apparently had the highest karma count by a wide margin with our Phacility Support Pact, for whatever that's worth :)

I would also love to contribute to Phorge. I have signed the legalpad doc.

I added @dcog @codemouse92 and @mydeveloperday to the trusted contributors group. Glad to have everyone involved!

Not sure if this is where to mention, I would definitely like to help develop/maintain/review Phorge (I have signed the doc), I currently maintain a 600+ user Phabricator instance housing 50+ git repos,

In T15010#1062, @avivey wrote:

Any user should be able to sign the doc at L1 Phorge Vision Statement - did you try it and got an error?

In T15010#1060, @codemouse92 wrote:

I agree with the doc, and would like to sign too.

Glad to see Phabricator continuing as Phorge. Not going to lie, I had a panic attack this morning when I found out that Phacility was winding down.

I would like to be a part of the core team, and I've signed the document.

Are we supposed to make a similar lengthy statement?

Heh, I wasn't really sure what people were expecting so just wrote up some stuff to explain who I am and what my role will probably end up being.

I would like to officially submit myself as a Core Team member.

Are we supposed to make a similar lengthy statement?

After agreeing and signing the document I submit myself here as a core team member, officially.

@jupe thanks for pointing out the typo, I've updated to fix that.

Did another pass on it: only thing I found is a typo (which I'm not allowed to fix): extra space after "Opinionated" and before to column in the list under "What is Phorge".

I've copied the contents into L1 Phorge Vision Statement which allows us to track signatures

I like it

Ship it!

I like the current version :)

Nothing to comment on: It’s great!

Thanks for the suggestions - I've updated the document to address them.

The vision statement really is fantastic.

I've made some updates to the vision statement document to try and bring it closer to completion. I've incorporated the rest of the outstanding notes and addressed the current comments.

Are we reasonably ok with what we have in the google doc?

Are we reasonably ok with what we have in the google doc?

I like the proposal above. Especially with having the core team "sign" a vision statement. The goal is less legalistic and more of ensuring we have a consistent view of the end product.

Great! Thanks @Matthew .

In T15004#672, @speck wrote:

I would say let’s go ahead and make those changes. I’ll be on later tonight from a workstation and can make those changes then (~8hrs) if needed.

I would say let’s go ahead and make those changes. I’ll be on later tonight from a workstation and can make those changes then (~8hrs) if needed.

In T15004#650, @speck wrote:

This is my understanding of the items in the description currently, please indicate if this is not correct

Security - I think this may have originally been intended for tagging items which are related to security issues that need addressed, such as vulnerabilities in the project. I think this is a tag that anyone could use when submitting issues.
Security Viewers - This is used to wall off items that should be restricted from public viewing, namely security reports, putting things into {S2}
Blessed Committers - The group of people who can push changes to the upstream

This is my understanding of the items in the description currently, please indicate if this is not correct

I would like to note that France has what the local law calls association loi 1901, which is very advantageous for a open source projects. In short it is an entity that can own stuff, accept donation, but cannot do for profit operations. Projects such as VLC and ffmpeg are using this. The requirement are very lax (you basically need to have an address somewhere in France for administrative bullshit) and have at least 3 founders. They don't need to be French or live in France, in fact, last time I checked, you could even do one as an illegal emigrant, which I found funny. I had a long chat with Jena Baptiste Kempf who created VLC about this for the last big open source project, but we ended up going for a structure in HK because we had Chinese users and donors and that was easier administratively this way. Chinese special case excluded, this was by far the best option we had.

In T15004#585, @Ekubischta wrote:

T15011 discusses some of this...

@willson556 built a container that works awesome - Just a few small things to work out - https://github.com/willson556/phorge-devcontainer

This container was easy enough for me to get up and running in like 4 steps (see the README)

I think once some of those issues are resolved, we should host the source for this container here at we.phorge.it

For the development environment this would probably be best in a diviner book/document instead of a wiki.

T15011 discusses some of this...

In T15004#100, @speck wrote:

On the topic of increasing community involvement we will also want to produce documentation for setting up development environments as well as the steps to submit changes upstream (like a quality checklist). To make development environments even easier we might want to consider supporting something like a vagrantfile so people can get started with very few steps.

hi, i'm the owner of a little sw Company based in Italy. I based it on phab and i would like to contribute to Phorge also with my employees.
If someone of admins is interested please contact me via email or in conpherence
Thank you everybody for your work, i hope the Phorge has a great future ahead

@eax I created O1 for that purpose.

In T15004#425, @speck wrote:

Currently rP and rARC only allow Blessed Committers to push - with those herald rules in place should we open that up?

Currently rP and rARC only allow Blessed Committers to push - with those herald rules in place should we open that up? Maybe we should have a separate group "Contributors" for anyone who wants to submit revisions for approval? Or should it be opened to any user?

Since we're planning to eventually host more-open/accessible community repositories I created these as separate object rules instead of as a global rule

I created H7 Guard Phorge Repo with Blessed Committers and H8 Guard Arcanist Repo with Blessed Committers to guard rP and rARC