I'm not sure what's the reason behind this task as this looks like it should be expressed via (sub)task inter-dependencies.
Also, please do not unsubscribe me from tasks. Thanks! :)

In T249676#6038829, @Aklapper wrote:

I'm not sure what's the reason behind this task

T242131#6025960

In T249676#6038829, @Aklapper wrote:

as this looks like it should be expressed via (sub)task inter-dependencies.

Please take a look at the immediate history above: T249676#6038590
That was the first approach and resulted in a 3-page-long task tree, which is unusable.
Also T242131#6038592
Also, the topology is different here from the task tree, serving the explorability of the tasks with patches and specifications.

Also, please do not unsubscribe me from tasks. Thanks! :)

Sure. In that case, please make well-informed, helpful comments. Thank you 😉

@Aklapper I'm not sure the title is expressive enough. Maybe you have a better title in mind for the ticket, which expresses that this is a resource for developers, not a "task" in the strict sense?

In T249676#6151496, @ovasileva wrote:

@Demian - I am also unsure of the purpose of this task - in terms of structuring the desktop improvements task we have the the separate board where work is separated by quarter, as well as the task trees of the per-feature items.

@ovasileva This question from Apr 3 preceding the creation of this ticket (I wouldn't call it a task) should answer yours:

In T242131#6025960, @Demian wrote:

@ovasileva It's very difficult to get an overview of the current progress in the DI timeline with the different parts tracked in disjunct trees of tasks which are like distinct islands.
It would be much easier if there was a common root for all DI development tasks. Could you please make one?
The current root tasks I'm aware of and often have to use the searchbox to navigate to are:

• T242131: [GOAL] Deploy new header to at least one test wiki
• T247032: [EPIC] Build collapsible sidebar and deploy to all test wikis

I've linked this comment above to answer Aklapper's similar question. Should I have been more explanatory?

For non-staff - who aren't up-to-date with the current progress and internal discussions (private slack, etc.) -, it is very hard to find the relevant discussions, decisions and patches of DI. This ticket catalogs the entry points for anyone without a detailed knowledge of the project. The workboard does not present this information. I understand this might not be an issue for the developers, or not important at all unfortunately.

It is my understanding that there are numerous tracking tasks on phab with similar purpose, therefore I wonder why this one is surprising.
Maybe the format? With that I'm not satisfied either, unfortunately this is what I could do within phab. I hoped to get some guidance to find a better format in response to T242131#6025960, but that did not happen.

In T249676#6151496, @ovasileva wrote:

I closing this for now. Let me know if you have concerns.

Closing the ticket is not an issue, it still serves as a catalog. My only concern is the general lack of communication and the lack of discover-ability of the tasks where the work is or was done for the purpose of onboarding, third-parties and for future reference.

@Demian - is the project board not sufficient for this purpose? All tasks related to the project are tagged there, which saves time from manually having to add them to this ticket.

In T249676#6157787, @ovasileva wrote:

@Demian - is the project board not sufficient for this purpose? All tasks related to the project are tagged there, which saves time from manually having to add them to this ticket.

It's very hard to find specific tasks, such as:

• Tasks where Alex documented the specifications
• Tasks with the patches linked
• The top-level (root) tasks

Without the task trees memorized, looking for a specific information in the tasks is typically a linear search. I recall spending a few hours altogether, looking for the exact values
to use in CSS. The categorization here intends to make these more discoverable.

I reckon now this ticket is not visible on the workboard and it does not need to be, as it's not a task. I think this is good as it is.

@ovasileva As this was my 3rd attempt to explain this ticket: was this a sufficient and understandable approach?

In T249676#6157984, @Demian wrote:

It's very hard to find specific tasks, such as:

• Tasks where Alex documented the specifications
• Tasks with the patches linked

I don't see anything in the desc here which somehow identifies tasks with patches.

• The top-level (root) tasks

I go to any task, look at the Task Graph, and usually see the top-level root tasks at the top of the task graph. I'm surprised by the term "very hard".

In T249676#6160554, @Aklapper wrote:

I don't see anything in the desc here which somehow identifies tasks with patches.

How is that possible? There are 12 patches in the "Patchwork" section. Is it possible the patches are not visible to you on those tickets?

Ah! That's possible because I had not realized which interesting quite literal meaning of "Patchwork" was used here.

In T249676#6179770, @Aklapper wrote:

which interesting quite literal meaning of "Patchwork"

I'm sorry, what does that mean?