Page MenuHomePhorge

GovernanceProject
ActivePublic

Watchers

  • This project does not have any watchers.
  • View All

Recent Activity

Thu, Nov 25

Labricator added a comment to T15062: Introducing Phixator 2.

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

Thu, Nov 25, 17:41 · Phrequent, Phorge General/Unknown, Dashboards, Governance, Maniphest

Tue, Nov 23

Ekubischta added a comment to T15062: Introducing Phixator 2.

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

Tue, Nov 23, 20:06 · Phrequent, Phorge General/Unknown, Dashboards, Governance, Maniphest

Mon, Nov 22

motla updated subscribers of T15062: Introducing Phixator 2.
Mon, Nov 22, 15:15 · Phrequent, Phorge General/Unknown, Dashboards, Governance, Maniphest
motla created T15062: Introducing Phixator 2.
Mon, Nov 22, 15:15 · Phrequent, Phorge General/Unknown, Dashboards, Governance, Maniphest

Sat, Oct 30

chris changed the edit policy for T15004: Decide who has admin/commit/security access.
Sat, Oct 30, 16:26 · Governance, Phorge
chris renamed T15004: Decide who has admin/commit/security access from Nightster383Decide who has admin/commit/security access to Decide who has admin/commit/security access.
Sat, Oct 30, 16:20 · Governance, Phorge

Oct 24 2021

Labricator added a comment to T15004: Decide who has admin/commit/security access.

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.

Oct 24 2021, 19:37 · Governance, Phorge

Sep 22 2021

speck added a comment to T15010: Vision Statement.

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

Sep 22 2021, 00:52 · Phorge, Governance

Sep 17 2021

dcog added a comment to T15010: Vision Statement.

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

Sep 17 2021, 00:14 · Phorge, Governance
dcog added a comment to T15010: Vision Statement.

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.

Sep 17 2021, 00:11 · Phorge, Governance

Sep 16 2021

MikeCripps added a comment to T15010: Vision Statement.

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.

Sep 16 2021, 22:17 · Phorge, Governance

Aug 26 2021

avivey added a comment to T15038: Offer a custom neutral timezone.

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

Aug 26 2021, 17:32 · Phorge General/Unknown, Governance
MacFan4000 added a comment to T15038: Offer a custom neutral timezone.

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)

Aug 26 2021, 14:46 · Phorge General/Unknown, Governance

Aug 25 2021

dereckson created T15038: Offer a custom neutral timezone.
Aug 25 2021, 13:01 · Phorge General/Unknown, Governance

Aug 24 2021

speck added a comment to T15010: Vision Statement.

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.

Aug 24 2021, 18:54 · Phorge, Governance

Aug 19 2021

jmeador added a comment to T15010: Vision Statement.

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 :)

Aug 19 2021, 22:08 · Phorge, Governance
MacFan4000 added a comment to T15010: Vision Statement.

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

Aug 19 2021, 14:40 · Phorge, Governance
speck added a comment to T15010: Vision Statement.

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

Aug 19 2021, 01:38 · Phorge, Governance

Aug 18 2021

mydeveloperday added a comment to T15010: Vision Statement.

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,

Aug 18 2021, 17:08 · Phorge, Governance

Aug 11 2021

codemouse92 added a comment to T15010: Vision Statement.
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?

Aug 11 2021, 20:43 · Phorge, Governance
avivey updated the task description for T15010: Vision Statement.
Aug 11 2021, 20:04 · Phorge, Governance
avivey added a comment to T15010: Vision Statement.

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

Aug 11 2021, 20:03 · Phorge, Governance
codemouse92 added a comment to T15010: Vision Statement.

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.

Aug 11 2021, 16:55 · Phorge, Governance

Jul 26 2021

dcog added a comment to T15010: Vision Statement.

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

Jul 26 2021, 04:29 · Phorge, Governance

Jul 10 2021

speck added a comment to T15010: Vision Statement.

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.

Jul 10 2021, 18:19 · Phorge, Governance
avivey added a comment to T15010: Vision Statement.

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

Jul 10 2021, 17:24 · Phorge, Governance

Jul 9 2021

deadalnix added a comment to T15010: Vision Statement.

Are we supposed to make a similar lengthy statement?

Jul 9 2021, 21:48 · Phorge, Governance

Jul 8 2021

speck added a comment to T15010: Vision Statement.

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

Jul 8 2021, 01:17 · Phorge, Governance
speck added a comment to T15010: Vision Statement.

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

Jul 8 2021, 00:26 · Phorge, Governance

Jul 7 2021

jupe added a comment to T15010: Vision Statement.

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".

Jul 7 2021, 07:36 · Phorge, Governance
speck added a comment to T15010: Vision Statement.

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

Jul 7 2021, 02:39 · Phorge, Governance

Jul 2 2021

eax added a comment to T15010: Vision Statement.

I like it

Jul 2 2021, 03:55 · Phorge, Governance
Matthew added a comment to T15010: Vision Statement.

Ship it!

Jul 2 2021, 00:22 · Phorge, Governance

Jul 1 2021

avivey added a comment to T15010: Vision Statement.

I like the current version :)

Jul 1 2021, 19:26 · Phorge, Governance
jupe added a comment to T15010: Vision Statement.

Nothing to comment on: It’s great!

Jul 1 2021, 09:15 · Phorge, Governance

Jun 30 2021

speck added a comment to T15010: Vision Statement.

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

Jun 30 2021, 15:39 · Phorge, Governance
deadalnix added a comment to T15010: Vision Statement.

The vision statement really is fantastic.

Jun 30 2021, 13:52 · Phorge, Governance
speck added a comment to T15010: Vision Statement.

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.

Jun 30 2021, 03:35 · Phorge, Governance

Jun 27 2021

jupe added a comment to T15010: Vision Statement.

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

Jun 27 2021, 20:31 · Phorge, Governance
avivey added a comment to T15010: Vision Statement.

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

Jun 27 2021, 19:32 · Phorge, Governance

Jun 25 2021

eax added a comment to T15004: Decide who has admin/commit/security access.

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.

Jun 25 2021, 12:15 · Governance, Phorge
eax added a comment to T15004: Decide who has admin/commit/security access.
Jun 25 2021, 12:14 · Governance, Phorge

Jun 24 2021

deadalnix added a comment to T15004: Decide who has admin/commit/security access.

Great! Thanks @Matthew .

Jun 24 2021, 17:40 · Governance, Phorge
Matthew added a comment to T15004: Decide who has admin/commit/security access.
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.

Jun 24 2021, 17:30 · Governance, Phorge
speck added a comment to T15004: Decide who has admin/commit/security access.

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.

Jun 24 2021, 17:06 · Governance, Phorge
speck added a project to T15009: Foundation: Phorge.
Jun 24 2021, 03:49 · Phorge, Governance
speck added a project to T15004: Decide who has admin/commit/security access: Phorge.
Jun 24 2021, 03:49 · Governance, Phorge
speck added a project to T15010: Vision Statement: Phorge.
Jun 24 2021, 03:49 · Phorge, Governance
Matthew added a comment to T15004: Decide who has admin/commit/security access.
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

Jun 24 2021, 02:51 · Governance, Phorge
speck added a comment to T15004: Decide who has admin/commit/security access.

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

Jun 24 2021, 02:37 · Governance, Phorge