Page MenuHomePhorge

Discussion NeededTag
ActivePublic

Members

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

Watchers

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

Details

Description

Tasks that require more thinking/input from community to reach an decision for the most suitable implementation.

Not to be confused with Clarification Needed - to be used when the general background is unclear or partially Invalid.

Recent Activity

Sat, Mar 22

valerio.bozzolan added a comment to T15081: Figure out if there are patches from Wikimedia's fork that are desirable to upstream in Phorge.

Another good simple candidate GDPR-friendly:

Sat, Mar 22, 21:31 · Discussion Needed, Affects-Wikimedia

Wed, Mar 19

avivey added a comment to T16007: Discuss the policy for contributing to prototype applications.

I'm not familiar with MediaWiki's packages - the model I'm copying is VSCode.
My thought is that in the install manual we'll say "now run ./bin/extensions install phorge-recommended-extensions" (near the ./bin/storage) step, and phorge-recommended-extensions would be the equivalent of "extension pack" hosted on the default Extension Store, which is hosted here.
(VSCode also has "bundled extensions", which I think doesn't work for us because we use "clone the repo" as the primary distribution system).

Wed, Mar 19, 09:10 · Discussion Needed, User-Cigaryno
Cigaryno added a comment to T16007: Discuss the policy for contributing to prototype applications.

Ideally, any current Prototype can be either promoted to Core, extracted to its own extension, or removed completely. Each extension/author can have their own policy on contributing.

Already, any new app that would be considered "Prototype" today should just go in its own extension, and we decided to remove a couple.

It depends on who on the wild (including large private companies developing closed-source software) is using prototype applications on Phorge. This should let us know if it should be promoted to core, separated into an extension, or removed completely if no one uses it (like Releeph and Phragments). Or even better, hold a Slowvote for each prototype application's future and possibly have Phorge's customers to vote (maybe notify as much as possible by creating a blog post about the vote to notify those who use the Atom feed).

I'm not sure that "usage" is really the best way to choose between "promote to core" and "extension"; The way I imagine it, in addition to the Core, we'll have a set of "highly recommended extensions" maintained, and a single step to install all of them when setting up a new machine. In that world, any app that can be separated out to an extension will be.
The prototypes can usually be curved out easily, without effecting the rest of the code.

Wed, Mar 19, 08:52 · Discussion Needed, User-Cigaryno
avivey added a comment to T16007: Discuss the policy for contributing to prototype applications.

The "Prototype" concept was a way for Phacility to experiment with things without committing - but we have a different model today.

Really!? Phacility SaaS instances do not allow enabling prototypes and self-hosted Support (from the Support application on admin.phacility.com that was oddly marked as Prototype) likely wasn't even available for prototype applications.

Wed, Mar 19, 07:54 · Discussion Needed, User-Cigaryno

Mon, Mar 17

aklapper added a comment to T16007: Discuss the policy for contributing to prototype applications.

It depends on who on the wild (including large private companies developing closed-source software) is using prototype applications on Phorge.

See T15501: Voluntary Usage Survey App basically.

Or even better, hold a Slowvote

Please no popularity contests (with even higher self-selection bias)...

Mon, Mar 17, 20:06 · Discussion Needed, User-Cigaryno
Cigaryno added a comment to T16007: Discuss the policy for contributing to prototype applications.

My thought on this is that long term, we'll remove the concept of "prototype" completely in favor of Extensions.

Prototypes that need a long way before being promoted to Core are those that should be separated into extensions.

Mon, Mar 17, 16:24 · Discussion Needed, User-Cigaryno
avivey updated the task description for T16007: Discuss the policy for contributing to prototype applications.
Mon, Mar 17, 07:39 · Discussion Needed, User-Cigaryno
avivey added a comment to T16007: Discuss the policy for contributing to prototype applications.

My thought on this is that long term, we'll remove the concept of "prototype" completely in favor of Extensions.
The "Prototype" concept was a way for Phacility to experiment with things without committing - but we have a different model today.

Mon, Mar 17, 07:39 · Discussion Needed, User-Cigaryno

Sun, Mar 16

aklapper added a revision to T16007: Discuss the policy for contributing to prototype applications: D25909: Diviner: Contributing Code: Update section on Prototype Changes.
Sun, Mar 16, 20:40 · Discussion Needed, User-Cigaryno
Cigaryno added a comment to T16007: Discuss the policy for contributing to prototype applications.

I do not think changes are necessarily needed, because it already says "With rare exceptions".

Bug fixes and security patches are indeed exceptions but not rare exceptions, assuming they fix problems with rough prototypes.

Sun, Mar 16, 16:29 · Discussion Needed, User-Cigaryno

Fri, Mar 7

aklapper added a comment to T16007: Discuss the policy for contributing to prototype applications.

I do not think changes are necessarily needed, because it already says "With rare exceptions".
Regarding the proposal, I do not believe that "prototype applications [...] are often subject to significant changes" either.

Fri, Mar 7, 16:46 · Discussion Needed, User-Cigaryno
Cigaryno created T16007: Discuss the policy for contributing to prototype applications.
Fri, Mar 7, 12:52 · Discussion Needed, User-Cigaryno

Feb 22 2025

amybones added a comment to T15961: Should we adopt modern PHP type hints in Phorge source code?.

I'd be very much in favor and I'd be happy to contribute changes for this. I've added type hints in my local fork to assist in development. Especially for core utility functions like idx and id which otherwise completely hide type information.

Feb 22 2025, 02:25 · Phorge Development Tools, Discussion Needed

Feb 7 2025

aklapper closed T15482: Conduit method for Legalpad signatures, a subtask of T15081: Figure out if there are patches from Wikimedia's fork that are desirable to upstream in Phorge, as Resolved.
Feb 7 2025, 12:48 · Discussion Needed, Affects-Wikimedia

Jan 17 2025

Cigaryno moved T15972: Add config option for maximum file size from Backlog to Feature Requests on the Discussion Needed board.
Jan 17 2025, 11:08 · Feature Requests, Config, Discussion Needed, Files
Cigaryno added a project to T15972: Add config option for maximum file size: Feature Requests.
Jan 17 2025, 11:08 · Feature Requests, Config, Discussion Needed, Files

Jan 15 2025

Cigaryno added a project to T15924: Commit feed body: it should probably show (part of) commit body: Feed.
Jan 15 2025, 19:48 · Feed, Discussion Needed, Diffusion

Jan 7 2025

valerio.bozzolan added a comment to T15961: Should we adopt modern PHP type hints in Phorge source code?.

Suggested meme for closing: "yesyes"

Jan 7 2025, 11:33 · Phorge Development Tools, Discussion Needed

Dec 31 2024

Cigaryno closed Q86: Policy lifecycle of security tasks as resolved.
Dec 31 2024, 10:56 · Discussion Needed

Dec 29 2024

Iniquity added a comment to T15100: [Feature request] Option to measure WIP limits based on card count instead of points, to more closely adhere to Kanban standards..

I'm not skilled enough to look into the bigger picture, however maybe the Edit Column dialog could have a third field apart from Name and Point Limit to also have Task Limit (or Card Limit?). Point Limit and Task Limit then must be mutually exclusive (do not allow to set both for a column, or even...board?), somehow.

Dec 29 2024, 21:28 · Feature Requests, Maniphest, Discussion Needed, Affects-Wikimedia, Workboard
Cigaryno moved T15081: Figure out if there are patches from Wikimedia's fork that are desirable to upstream in Phorge from Backlog to Wikimedia on the Discussion Needed board.
Dec 29 2024, 17:39 · Discussion Needed, Affects-Wikimedia
Cigaryno moved T15082: Consider allowing milestone columns to be ordered arbitrarily on workboards from Backlog to Wikimedia on the Discussion Needed board.
Dec 29 2024, 17:38 · Discussion Needed, Affects-Wikimedia, Workboard
Cigaryno moved T15924: Commit feed body: it should probably show (part of) commit body from Backlog to Discussion Needed on the Diffusion board.
Dec 29 2024, 17:36 · Feed, Discussion Needed, Diffusion
Cigaryno moved T15670: Diffusion repository commits: avoid to be a black hole for webcrawlers from Backlog to Discussion Needed on the Diffusion board.
Dec 29 2024, 17:34 · Diffusion, Discussion Needed
Cigaryno moved T15096: Discuss Arcanist as a barrier to adoption of Phorge and how to address the underlying issues. from Backlog to Discussion Needed on the Arcanist board.
Dec 29 2024, 17:08 · Discussion Needed, Arcanist

Dec 28 2024

Cigaryno moved T15892: Post-Commit Audit review: authors cannot "Raise Concern" from Backlog to Bug Reports on the Diffusion board.
Dec 28 2024, 19:26 · Discussion Needed, Bug Reports, Diffusion
Cigaryno added a project to T15670: Diffusion repository commits: avoid to be a black hole for webcrawlers: Diffusion.
Dec 28 2024, 18:40 · Diffusion, Discussion Needed
Cigaryno moved T15736: JavaScript modernization (umbrella task) from Backlog to Discussion Needed on the UX board.
Dec 28 2024, 11:47 · UX, Discussion Needed
Cigaryno moved T15082: Consider allowing milestone columns to be ordered arbitrarily on workboards from Backlog to Discussion Needed on the Workboard board.
Dec 28 2024, 10:58 · Discussion Needed, Affects-Wikimedia, Workboard
Cigaryno moved T15100: [Feature request] Option to measure WIP limits based on card count instead of points, to more closely adhere to Kanban standards. from Backlog to Feature Requests on the Maniphest board.
Dec 28 2024, 10:40 · Feature Requests, Maniphest, Discussion Needed, Affects-Wikimedia, Workboard

Dec 26 2024

Cigaryno added a project to T15972: Add config option for maximum file size: Config.
Dec 26 2024, 14:19 · Feature Requests, Config, Discussion Needed, Files

Dec 22 2024

Cigaryno moved T15082: Consider allowing milestone columns to be ordered arbitrarily on workboards from Backlog to Discussion Needed on the Affects-Wikimedia board.
Dec 22 2024, 07:07 · Discussion Needed, Affects-Wikimedia, Workboard

Dec 19 2024

Cigaryno moved T15892: Post-Commit Audit review: authors cannot "Raise Concern" from Backlog to Bug Reports on the Discussion Needed board.
Dec 19 2024, 07:33 · Discussion Needed, Bug Reports, Diffusion

Dec 17 2024

valerio.bozzolan added parent tasks for T15978: Phriction: evaluate real page move (breaking change): T15822: When a phriction page is moved, history should follow the page move, T15575: Moving a Phriction page does not move its Tags.
Dec 17 2024, 12:47 · Discussion Needed, Phriction
valerio.bozzolan created T15978: Phriction: evaluate real page move (breaking change).
Dec 17 2024, 12:46 · Discussion Needed, Phriction

Dec 11 2024

BlankEclair added a revision to T15972: Add config option for maximum file size: D25853: Add configuration option for maximum file size.
Dec 11 2024, 07:50 · Feature Requests, Config, Discussion Needed, Files
avivey added a comment to T15972: Add config option for maximum file size.

(we can probably keep this ticket open, so that we have the 2nd part on the backlog. I'm pretty sure we want it to happen "eventually".)

Dec 11 2024, 07:20 · Feature Requests, Config, Discussion Needed, Files
valerio.bozzolan added a comment to T15972: Add config option for maximum file size.

Feel free to show something early :) That would attract more attention than the Discussion Needed tag I bet

Dec 11 2024, 07:13 · Feature Requests, Config, Discussion Needed, Files
BlankEclair added a comment to T15972: Add config option for maximum file size.

Wrote the code for the first phase :p

Dec 11 2024, 07:01 · Feature Requests, Config, Discussion Needed, Files
BlankEclair added a comment to T15972: Add config option for maximum file size.

Sounds good to me :p

Dec 11 2024, 04:32 · Feature Requests, Config, Discussion Needed, Files

Dec 9 2024

valerio.bozzolan added a comment to T15972: Add config option for maximum file size.

We can also ship this feature in two phases, so, first, adding the option files.maximum-file-size, and then the second one when it's ready or requested lol

Dec 9 2024, 16:03 · Feature Requests, Config, Discussion Needed, Files
BlankEclair added a comment to T15972: Add config option for maximum file size.

Yeah, I agree, though I would then only work on implementing files.maximum-file-size because we don't really care that much about adding exceptions to the rule (as far as I know lol)

Dec 9 2024, 14:16 · Feature Requests, Config, Discussion Needed, Files
valerio.bozzolan added a comment to T15972: Add config option for maximum file size.

Uh, that would be so good. So you can say "When the moon is full".

Dec 9 2024, 08:36 · Feature Requests, Config, Discussion Needed, Files
avivey added a comment to T15972: Add config option for maximum file size.

Sounds reasonable.

Dec 9 2024, 08:12 · Feature Requests, Config, Discussion Needed, Files

Dec 8 2024

valerio.bozzolan added a project to T15972: Add config option for maximum file size: Discussion Needed.

I like your option names. I like to specify PHIDs and not numeric IDs so it's more portable against import/exports 👍 Let's add Discussion Needed to attract some +1 or nice suggestions.

Dec 8 2024, 18:11 · Feature Requests, Config, Discussion Needed, Files

Nov 28 2024

20after4 updated the task description for T15961: Should we adopt modern PHP type hints in Phorge source code?.
Nov 28 2024, 03:10 · Phorge Development Tools, Discussion Needed
20after4 created T15961: Should we adopt modern PHP type hints in Phorge source code?.
Nov 28 2024, 03:10 · Phorge Development Tools, Discussion Needed

Nov 26 2024

aklapper closed T15916: Conduit maniphest.gettasktransactions: include metadata and title, a subtask of T15081: Figure out if there are patches from Wikimedia's fork that are desirable to upstream in Phorge, as Resolved.
Nov 26 2024, 13:08 · Discussion Needed, Affects-Wikimedia

Oct 9 2024

20after4 updated subscribers of T15501: Voluntary Usage Survey App.

There is a significant amount of Phabricator dark matter out there - companies/people using the software, it works well enough, not really easy to know they exist or anything about their usage. I'm sure at least some of them have moved to Phorge. Automattic/wordpress.com have moved to Phorge and I wasn't even aware that they were using Phabricator before that. This is despite the fact that I did a pretty extensive amount of research to identify every company using Phabricator back in ~2019 as part of my work for Wikimedia, with the goal of reaching out and trying to organize an informal Phabricator users group. We had the idea that the various corporate users probably had good reasons to be collaborating and at least talking to each other since most of them were not active in the upstream project. Anyway, that never really panned out, although it did trigger a flurry of interest and some ongoing discussions via email (maybe even one video meeting but I can't remember the details now.)

Oct 9 2024, 07:16 · Discussion Needed

Sep 20 2024

valerio.bozzolan closed T15489: Diffusion commit feed: avoid to repeat the commit message twice, a subtask of T15924: Commit feed body: it should probably show (part of) commit body, as Resolved.
Sep 20 2024, 01:58 · Feed, Discussion Needed, Diffusion