Page MenuHomePhorge
Feed Advanced Search

Today

Bukkit created T15063: Change Letter PFP Upon Rename.
Sun, Nov 28, 00:50 · Phorge

Wed, Nov 3

MacFan4000 added projects to T15060: Better Pirate English: Phorge, Localization.
Wed, Nov 3, 15:24 · Localization, Phorge

Tue, Nov 2

dbn added a comment to T15059: Phabricator doesn't email @outlook.com addresses.

We had a similar issue with Microsoft email on our own custom mail server. Microsoft delivers mail for several domains from the same email service, so this similarly affects email from outlook.com, hotmail.com, live.com and msn.com. See https://postmaster.live.com/pm/policies.aspx for details.

Tue, Nov 2, 15:47 · Phorge
codemouse92 added a comment to T15059: Phabricator doesn't email @outlook.com addresses.

This is likely related more to the configuration of the email server. Outlook is very picky, and as far as I know, checks the headers for all of the following:

Tue, Nov 2, 14:02 · Phorge

Sun, Oct 31

Ekubischta added a comment to T15059: Phabricator doesn't email @outlook.com addresses.

I can confirm as well that I have never received an email from phorge / phabricator on my email which isn't "outlook.com" but is an office 365 email account

Sun, Oct 31, 02:09 · Phorge

Sat, Oct 30

chris added a comment to T15059: Phabricator doesn't email @outlook.com addresses.

Do you have any additional repro steps? Mail config will be specific to the Phab/Phorge install. If this is specific to our Phorge installation, yeah... it's sucky. We self-host our email server and that means we're subject to all of the arcane and mystic requirements there. As far as we can tell, it's set up as correctly as is possible (SPF, DKIM, DMARC all configured correctly; domain is old enough that it doesn't negatively impact our trust scores; etc.). (A current spam test result for reference.)

Sat, Oct 30, 22:42 · Phorge
Labricator added a comment to T15054: Improve Feed search filters to hide "minor activities".

@valerio.bozzolan Fancy seeing you here. I'm Void from your phabricator instance.

Sat, Oct 30, 22:27 · Phorge
Labricator created T15059: Phabricator doesn't email @outlook.com addresses.
Sat, Oct 30, 22:26 · Phorge
chris changed the edit policy for T15004: Decide who has admin/commit/security access.
Sat, Oct 30, 16:26 · Governance, Phorge
Labricator added a comment to T15033: Add option for GDPR Warning Suggestion.

Yes, that's why I'm saying "yeah, great idea, let's do this, but let's also create a config toggle so that it can be disabled for people and orgs who don't need it".

Sat, Oct 30, 16:21 · 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 29 2021

golyalpha added a comment to T15033: Add option for GDPR Warning Suggestion.

@golyalpha As my current employer is one of the largish companies, (50,000+ international employees), but not primarily software focused we have all been given GDPR awareness training but do not have a general, all employees, GDPR statement available nor a standard text or set of texts to use.
When I was deploying a Phabricator instance I actually had to come up with the wording myself and then get it approved by the legal & compliance team - my biggest hurdle was convincing them of the required data retention period - they were much more used to systems such as payroll & HR where records are only retained for a fixed number of years after the period of employment as demanded by things like the local tax regulations and the idea that due to legal liability, etc., we needed to retain the information for the full life of the product being developed and possibly beyond if components were reused.

Oct 29 2021, 08:04 · Phorge
gadgetsteve added a comment to T15033: Add option for GDPR Warning Suggestion.

@dcog Just:

Oct 29 2021, 07:17 · Phorge
dcog added a comment to T15033: Add option for GDPR Warning Suggestion.

@golyalpha As my current employer is one of the largish companies, (50,000+ international employees), but not primarily software focused we have all been given GDPR awareness training but do not have a general, all employees, GDPR statement available nor a standard text or set of texts to use.
When I was deploying a Phabricator instance I actually had to come up with the wording myself and then get it approved by the legal & compliance team - my biggest hurdle was convincing them of the required data retention period - they were much more used to systems such as payroll & HR where records are only retained for a fixed number of years after the period of employment as demanded by things like the local tax regulations and the idea that due to legal liability, etc., we needed to retain the information for the full life of the product being developed and possibly beyond if components were reused.

Oct 29 2021, 06:55 · Phorge
gadgetsteve added a comment to T15033: Add option for GDPR Warning Suggestion.

@golyalpha As my current employer is one of the largish companies, (50,000+ international employees), but not primarily software focused we have all been given GDPR awareness training but do not have a general, all employees, GDPR statement available nor a standard text or set of texts to use.
When I was deploying a Phabricator instance I actually had to come up with the wording myself and then get it approved by the legal & compliance team - my biggest hurdle was convincing them of the required data retention period - they were much more used to systems such as payroll & HR where records are only retained for a fixed number of years after the period of employment as demanded by things like the local tax regulations and the idea that due to legal liability, etc., we needed to retain the information for the full life of the product being developed and possibly beyond if components were reused.

Oct 29 2021, 06:07 · Phorge
golyalpha added a comment to T15033: Add option for GDPR Warning Suggestion.

I18n is also fairly important from the point of view that citizens in certain jurisdictions are basically legally immune against documents written in a language different from the official language of their jurisdiction, so, +1 on that.

Oct 29 2021, 05:30 · Phorge
gadgetsteve added a comment to T15033: Add option for GDPR Warning Suggestion.

Would it worth considering having multiple versions available with which is displayed determined by locale & language selection, (I18n & I10n). Then places with specific legislation could display the boilerplate or customised version and places without could, potentially, mention it with a link rather than having a specific sign-off and also linguistic problems could be addressed by the instance maintainer(s).

Oct 29 2021, 05:27 · Phorge
gadgetsteve added a comment to T15033: Add option for GDPR Warning Suggestion.

@Labricator Definitely - as potentially contributors can be from anywhere in the world, including places with GDPR or equivalent legislation. (Note that I am In Wales, UK so would be covered). I am reasonably sure, not a lawyer remember, the legislation is written in such a way that you can't get away with things like "the data is stored somewhere without DGPR so it doesn't apply", etc.

Oct 29 2021, 05:22 · Phorge
golyalpha added a comment to T15033: Add option for GDPR Warning Suggestion.

Yes, that's why I'm saying "yeah, great idea, let's do this, but let's also create a config toggle so that it can be disabled for people and orgs who don't need it".

Oct 29 2021, 05:20 · Phorge

Oct 28 2021

Labricator added a comment to T15033: Add option for GDPR Warning Suggestion.

What about the public versions? It still should have a GDPR notification.

Oct 28 2021, 23:46 · Phorge
golyalpha added a comment to T15033: Add option for GDPR Warning Suggestion.

Yes, the GDPR notice must inform about each and every purpose specifically. But it must do so only once - that can be at sign up.

Oct 28 2021, 06:11 · Phorge
gadgetsteve added a comment to T15033: Add option for GDPR Warning Suggestion.

The EU & UK GDPR provisions are very specific that each data gathering application must inform the user:

Oct 28 2021, 04:49 · Phorge

Oct 27 2021

golyalpha added a comment to T15033: Add option for GDPR Warning Suggestion.

Definitely a good idea for anyone who wants to run Phorge in EU/UK or work with EU/UK contributors. Though it really is only necessary for the signup page - individual repositories really only have to worry about CLAs (if relevant).

Oct 27 2021, 12:32 · 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
Labricator added a comment to T15033: Add option for GDPR Warning Suggestion.

I'd definitely recommend this change. Although I am not the best with legal mumbo jumbo, this would definitely be a must-have.

Oct 24 2021, 19:35 · Phorge
Labricator added a watcher for Phorge: Labricator.
Oct 24 2021, 19:31

Oct 21 2021

io added a comment to T15026: Create a migration guide to move from Phabricator to Phorge.

Great, thanks for the info.

Oct 21 2021, 09:31 · Phorge

Oct 20 2021

MacFan4000 added a comment to T15026: Create a migration guide to move from Phabricator to Phorge.

@io for GitHub we have a task (T15046)

Oct 20 2021, 22:59 · Phorge

Oct 19 2021

io added a comment to T15026: Create a migration guide to move from Phabricator to Phorge.

Hi all,

Oct 19 2021, 16:54 · Phorge

Oct 17 2021

dcog added a comment to T15006: Re-brand Phorge.
In T15006#1429, @speck wrote:

I can provide more information later this weekend but I think it would help if we set up a virtual meeting with anyone interested in helping to get this done.

Oct 17 2021, 17:13 · Phorge
avivey added a comment to T15006: Re-brand Phorge.
In T15006#1429, @speck wrote:

I can provide more information later this weekend but I think it would help if we set up a virtual meeting with anyone interested in helping to get this done.

Oct 17 2021, 06:39 · Phorge

Oct 16 2021

dcog added a comment to T15006: Re-brand Phorge.

Also this Vagrant pattern should work first-run with vagrant up: https://we.phorge.it/T15027#852

Oct 16 2021, 04:08 · Phorge
Ekubischta added a comment to T15006: Re-brand Phorge.
In T15006#1429, @speck wrote:

I can provide more information later this weekend but I think it would help if we set up a virtual meeting with anyone interested in helping to get this done.

Yes - I could have some availability - Normally evenings (US Central Time) -

Oct 16 2021, 02:11 · Phorge

Oct 15 2021

speck added a comment to T15006: Re-brand Phorge.

I can provide more information later this weekend but I think it would help if we set up a virtual meeting with anyone interested in helping to get this done.

Oct 15 2021, 22:31 · Phorge
Ekubischta added a comment to T15006: Re-brand Phorge.

@speck What can I help with here? - Are we waiting on upstream for anything currently?

Oct 15 2021, 22:09 · Phorge
speck added a comment to T15055: Import translations from translatewiki.net.

The effort to rebrand Phabricator is going to result in changes to a lot of text which would likely invalidate a large number of translation entries.

Oct 15 2021, 17:39 · Phorge
20after4 renamed T15055: Import translations from translatewiki.net from Import translations from translate wiki.net to Import translations from translatewiki.net.
Oct 15 2021, 17:11 · Phorge
20after4 created T15055: Import translations from translatewiki.net.
Oct 15 2021, 17:11 · Phorge
speck added a comment to T15054: Improve Feed search filters to hide "minor activities".

At my company we have a similar situation however our management system is something we also actively develop. We solved this problem by configuring a web hook to hit an endpoint for the activities we are interested in having people track. The endpoint receives the transactions, pulls some additional info, and creates time-tracked activities for them in an aggregated list. Employees review the list and update time for each activity. It works pretty well and is not limited to activities from Phab allowing other systems to post activity to report, and for employees it’s nice because we can present the activity they’ve done and only require they estimate time spent as all other context is linked up.

Oct 15 2021, 16:12 · Phorge
valerio.bozzolan updated the task description for T15054: Improve Feed search filters to hide "minor activities".
Oct 15 2021, 15:58 · Phorge
valerio.bozzolan triaged T15054: Improve Feed search filters to hide "minor activities" as Low priority.
Oct 15 2021, 15:43 · Phorge
valerio.bozzolan updated the task description for T15054: Improve Feed search filters to hide "minor activities".
Oct 15 2021, 15:31 · Phorge
valerio.bozzolan added a cover image to T15054: Improve Feed search filters to hide "minor activities".
Oct 15 2021, 15:30 · Phorge
valerio.bozzolan created T15054: Improve Feed search filters to hide "minor activities".
Oct 15 2021, 15:30 · Phorge

Sep 22 2021

pasik added a comment to T15047: Officially raise minimum required PHP version to 7.2.

and yes, I'm also running phabricator on top of CentOS 7 (using PHP 7.x via SCL).

Sep 22 2021, 20:55 · Phorge
pasik added a comment to T15047: Officially raise minimum required PHP version to 7.2.

Isn't Centos End of Life soon?

Sep 22 2021, 20:55 · Phorge
speck renamed T15047: Officially raise minimum required PHP version to 7.2 from Oficially raise minimum required PHP version to 7.2 to Officially raise minimum required PHP version to 7.2.
Sep 22 2021, 19:44 · Phorge
speck added a comment to T15047: Officially raise minimum required PHP version to 7.2.

Is it possible to pick a branching off point?

Yep I think this makes sense and is why I think our first release should still support PHP 5.4 but we can move off it after that.

Sep 22 2021, 19:43 · Phorge
Ekubischta added a comment to T15047: Officially raise minimum required PHP version to 7.2.

Is it possible to pick a branching off point?

Sep 22 2021, 19:35 · Phorge
avivey added a comment to T15047: Officially raise minimum required PHP version to 7.2.

Also, https://secure.phabricator.com/T7413 for the phone-home feature.

Sep 22 2021, 19:02 · Phorge
avivey added a comment to T15047: Officially raise minimum required PHP version to 7.2.

The kind of teams that use Centos/Redhat are very conservative - they're exactly the teams that would not install PHP from an "alternative" source (or from source code). They also tend to keep to older OS versions, as long as they are supported, and would not be happy with a single machine being different from the rest.
All that to say, it would make these teams sad to require an upgrade.

Sep 22 2021, 19:02 · Phorge
taavi added a comment to T15047: Officially raise minimum required PHP version to 7.2.

I'm mostly a Debian person (so I'm not aware of CentOS specifics) but my understanding is that CentOS 7 shipped with PHP 5.4 and has newer versions available via alternative repositories (not sure if official or not), while CentOS 8 (and Rocky Linux 8, if that matters) had PHP 7.2 by default and shipped a few years back. Is there a reason we're not basing our PHP support on latest distro releases (plus something like a year or two for a transition buffer), especially if newer PHP versions are available for older distro versions available as backports? I don't think requiring PHP / distro upgrades every few years is unreasonable.

Sep 22 2021, 18:38 · Phorge
Ekubischta added a comment to T15047: Officially raise minimum required PHP version to 7.2.

Isn't Centos End of Life soon?

Sep 22 2021, 18:23 · Phorge
avivey added a comment to T15047: Officially raise minimum required PHP version to 7.2.

+1 for CentOS 7.

Sep 22 2021, 16:04 · Phorge
eax added a comment to T15047: Officially raise minimum required PHP version to 7.2.

Agreed. We should aim to follow some specific conservative release. CentOS 7 seems reasonable.

Sep 22 2021, 04:23 · Phorge
speck added a comment to T15012: Update Diviner documentation to reference Phorge.

We should include the Diviner and tech docs generation as part of the upgrade process of this server, that should ensure it's always up to date.

Sep 22 2021, 01:09 · Phorge
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
speck added a comment to T15047: Officially raise minimum required PHP version to 7.2.

I think our general strategy here should be focused around the versions of PHP available from the default/common package repositories for major server-based Linux distributions. There might be some situations where those package repositories only support very old versions (e.g. CentOS 7) which we should only plan to provide documentation for how to get the required version of PHP installed.

Sep 22 2021, 00:49 · Phorge

Sep 18 2021

MacFan4000 added a comment to T15012: Update Diviner documentation to reference Phorge.

I will note that also the tech docs aren’t fully generated since there should be docs for most of the phorge/phabricator classes. Also the arcanist docs aren’t generated at all.

Sep 18 2021, 18:11 · Phorge
Leon95 added a comment to T15012: Update Diviner documentation to reference Phorge.

The Server also needs to periodically rebuild the Diviner Books to keep them in sync with Source Code. Eg. just set up a crontab entry. Or later, if more traffic is on the page: rebuild it once a commit affecting the Docs is committed.

Sep 18 2021, 14:53 · Phorge

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
TitanNano updated the task description for T15047: Officially raise minimum required PHP version to 7.2.
Sep 16 2021, 15:59 · Phorge
TitanNano created T15047: Officially raise minimum required PHP version to 7.2.
Sep 16 2021, 15:58 · Phorge

Sep 4 2021

speck added a comment to T15042: Easier landing of revisions.

Automated Landing should be what adds the "Land Revision" button to revisions -- so not fully automated but allows someone to land without needing a local clone to manage.

Sep 4 2021, 21:03 · Phorge
MacFan4000 added a comment to T15042: Easier landing of revisions.

Also when I look at a diff on upstream phabricator i see a land revision button - but I don’t see that for diffs on this instance.

Sep 4 2021, 19:15 · Phorge
MacFan4000 added a comment to T15042: Easier landing of revisions.

@speck for rARC Trusted Contributors can land but rP is restricted to Blessed Committers

Sep 4 2021, 19:06 · Phorge
speck updated the task description for T15042: Easier landing of revisions.
Sep 4 2021, 18:24 · Phorge
CSharp added a comment to T15041: Starmap.

I'd suggest starting of the starmap by shedding some/most of the applications that were not part of the core of Phabricator or have been in the Prototype phase for a long time, allowing the project to regain focus and improve on the things that make Phorge unique. This would provide a number of advantages:

Sep 4 2021, 18:05 · Phorge
speck updated subscribers of T15042: Easier landing of revisions.
Sep 4 2021, 17:45 · Phorge
speck created T15042: Easier landing of revisions.
Sep 4 2021, 17:41 · Phorge
speck updated subscribers of T15041: Starmap.
Sep 4 2021, 17:32 · Phorge
speck updated the task description for T15041: Starmap.
Sep 4 2021, 17:32 · Phorge
speck updated the task description for T15041: Starmap.
Sep 4 2021, 17:31 · Phorge
speck created T15041: Starmap.
Sep 4 2021, 17:30 · Phorge

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 29 2021

20after4 added a comment to T15014: Develop a Phorge Release Process.

I can help out with upstream merges. I've been doing it on a regular basis for Wikimedia for a long time now. It's rarely been a problem but I'm been careful to make sure that Wikimedia's fork doesn't drift too far away from upstream.

Jul 29 2021, 21:33 · Phorge

Jul 28 2021

speck added a comment to T15014: Develop a Phorge Release Process.

Handling of merging upstream changes will probably lead to some challenging merges done by people who did not author the original changes in Phorge. I don't know what the best way is to work around this. Maybe if we regularly (daily?) pull in changes from upstream, merge into our own master branch which everyone lands onto that should mostly catch merge issues?

Jul 28 2021, 20:46 · Phorge
avivey added a comment to T15014: Develop a Phorge Release Process.

There already are a bunch of worthwhile changes in Phabricator we should pick up; @Matthew - want to load them to check out the procedure? I can do that otherwise.

Jul 28 2021, 07:08 · Phorge

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 20 2021

MacFan4000 added a comment to T15030: Support a Phorge Extensions ecosystem.

regarding a monorepo, I'm not sure if there is an advantage to that, I'm fine with individual repos. I currently maintain most of Wikimedia's extensions in a single monorepo but I'd consider splitting them out into individual repos if any one them were candidates for upstreaming.

Jul 20 2021, 14:52 · Phorge

Jul 19 2021

20after4 added a comment to T15030: Support a Phorge Extensions ecosystem.

regarding a monorepo, I'm not sure if there is an advantage to that, I'm fine with individual repos. I currently maintain most of Wikimedia's extensions in a single monorepo but I'd consider splitting them out into individual repos if any one them were candidates for upstreaming.

Jul 19 2021, 03:57 · Phorge
20after4 added a comment to T15030: Support a Phorge Extensions ecosystem.

I'd like to host https://github.com/wikimedia/phabricator-antivandalism here, perhaps under a new name.

Jul 19 2021, 03:55 · Phorge

Jul 18 2021

dcog added a comment to T15030: Support a Phorge Extensions ecosystem.
In T15030#972, @avivey wrote:

A space-zombie game that can report high-scores to IRC, Slack and Phorge.

Jul 18 2021, 07:06 · Phorge

Jul 17 2021

avivey added a comment to T15030: Support a Phorge Extensions ecosystem.

Here's the terms I've been thinking of for accepting a project to Phactory:

  1. Directly related to Phorge in a significant way:

Good: Module for integration with some other system; New Phorge app that does something reasonable; scripts for administration work.
Bad: A space-zombie game that can report high-scores to IRC, Slack and Phorge.

Jul 17 2021, 07:23 · Phorge
avivey updated the task description for T15022: Legal stuff.
Jul 17 2021, 06:50 · Phorge
gadgetsteve added a comment to T15033: Add option for GDPR Warning Suggestion.

Checking the Wikipedia entry for GDPR at https://en.wikipedia.org/wiki/General_Data_Protection_Regulation it mentions that this regulation or other similar ones have been enacted in:

Jul 17 2021, 06:08 · Phorge
gadgetsteve added a comment to T15033: Add option for GDPR Warning Suggestion.

Of course since Phorge itself is a public project with, potentially, UK/EU contributors the signup/login page should really display such a warning.

Jul 17 2021, 05:53 · Phorge
gadgetsteve created T15033: Add option for GDPR Warning Suggestion.
Jul 17 2021, 05:51 · Phorge

Jul 16 2021

dcog added a comment to T15014: Develop a Phorge Release Process.
In T15014#929, @avivey wrote:

nit-pick: maybe name them phabricator/master and phabricator/stable

Jul 16 2021, 01:21 · Phorge
dcog added a comment to T15030: Support a Phorge Extensions ecosystem.
In T15030#949, @0 wrote:

There are some projects listed on the Phabricator Community Resources page. Would all of those be eligible for hosting here, or would there be some criteria to limit the number of external projects?

Jul 16 2021, 01:17 · Phorge