In T15056#3210, @golyalpha wrote:

Another example of broken dark theme

When an fatal exception is triggered :

Because there are more and more referenced issues and, because some of them may need further discussion in order to find the best solution, IMHO it may be a good idea to create a sub task for each issue reported isn't it ?

Another on when displaying a maniphest with a lot of comments :

Concerning the dashbord's big pannel :

In workboard, when a maniphest's is drag and dropped, available triggers information windows is broken.

In workboard, when maniphest's edit button style is broken on mouse over.

I'll do it next time, I always do my best to serve my master !

Yeah bob, feel free to add your nice screenshots in the Task description for more visibility. You are a good minion!

In workboard, empty column's drop zone is a little bit 'agressive' isn't it ?

Hi, I can also see this one that looks weird in big pannels available on dashboards

Also, I apologize for not completing this, hadn't had much spare time until recently. I will work on this soon.

Done.

Hi @Bukkit can you please publish F281219? thanks :)

I don't see file F281219

In T15129#11054, @Cigaryno wrote:

.. and vice versa

In T15129#10661, @aklapper wrote:

For archaeologists: canUninstall = false for Audit got set in rP11861265fe94fa97e4d0563c5bdb7b8cac27282d

Hoping to receive more feedback from the original author (without closing as invalid) I keep open but with a cute Clarification Needed

For archaeologists: canUninstall = false for Audit got set in rP11861265fe94fa97e4d0563c5bdb7b8cac27282d

I wonder if this is related to not being able to use the Diffusion repository file auto-complete when not logged in even though the repo is publicly accessible.

Hi @Cigaryno thanks for this bug report. Please attach more details than feel free to reopen

I have not checked that, but maybe exceptions should just be in monospace.

Yeah sorry, I mis-used Projects since I was not bold enough to mark more appropriately with #Milestones (that we know are a type of Project internally)

OK thanks, so I understand what was the last cleanup: you helped in removing some Projects where was related to Workboard and #Milestones but the last one does not exist.

I removed the tag from some tasks that are about Workboards and not about projects.

Projects isn't archived.

I'm still confused. I noticed that the Projects (archived) was archived since probably it was a sub-project, but why also Projects was emptied? It's a core component of Phorge, and it contained more than 3-4 Tasks inside (so, inside the avivey rule of thumb mentioned above). In this way I just feel like am I bothering you, just for trying to organize a massive work on a community project?

I'm done cleaning up Projects for now.

The old Chatlog data will be kept while removing Chatlog.

I'm ok with you creating a new Files tag for the Files app.

Avivey I understand your point of view, but please understand that it's really not feasible to look for "files" in the search engine, since we know in the IT everything is a file. Instead, just allowing people to click on a Tag and see some Tasks that are really related to what most looking is looking for (Files component), it's useful.

@avivey, @valerio.bozzolan this is not a place to discuss Files (archived).

We have a really good text-search system. Just go to maniphest and search for "files", you'll get everything that's related to it.

In T15130#5832, @avivey wrote:

I archived Files (archived) because there was nothing there.

In T15130#5832, @avivey wrote:

I archived Files (archived) because there was nothing there.
If it gets traffic, we can create a relevant tag.

There's no reason to create projects/tag on the off-case that "we might need this some day".

I archived Files (archived) because there was nothing there.
If it gets traffic, we can create a relevant tag.

In T15130#5813, @valerio.bozzolan wrote:

I disagree: I strongly suggest to keep the ability to use Projects as Tags. One problem is Mobile that affects mobile users, but it's not related to a particular area of interest like Diffusion. Also, Files (archived) , I don't agree on archiving it, since having that Tag dramatically simplifies searching for that specific topic on a search engine.

If one topic has multiple tags, is just easier to find it. Not less difficult. It's just a matter of having clear Projects for components) and Projects for topic Tags.

In T15130#5812, @avivey wrote:

For php, eg, having a column for "8.2" under "php 8" is plenty detailed enough.

I disagree: I strongly suggest to keep the ability to use Projects as Tags. One problem is Mobile that affects mobile users, but it's not related to a particular area of interest like Diffusion. Also, Files (archived) , I don't agree on archiving it, since having that Tag dramatically simplifies searching for that specific topic on a search engine.

For php, eg, having a column for "8.2" under "php 8" is plenty detailed enough.

Adding lots of projects makes it harder to find the right project for a given thing.

I'm also the author of the first table here in the Change Log:

In T15130#5798, @avivey wrote:

@Cigaryno Phorge was only part of "organize projects here" task.

@Cigaryno Phorge was only part of "organize projects here" task.

In T15130#5794, @avivey wrote:

ah

For our codebase, it's enough to have a single "8.x" tag. We have several millions lines of code less then wikimedia.

In T15130#5788, @avivey wrote:

@Cigaryno wtf?

For our codebase, it's enough to have a single "8.x" tag. We have several millions lines of code less then wikimedia.

In T15130#5784, @avivey wrote:

I'm starting on some of the top-level redundancies (such as ..., and at least 3 different projects for php 8 support!)

@valerio.bozzolan what?

Just a clarification:

@Cigaryno wtf?

I've killed all the stuff from under Phorge, and I'm starting on some of the top-level redundancies (such as Typeahead and typehead, and at least 3 different projects for php 8 support!)