As a team, we've decided to collapse them all back into the main project.

Hi, which underlying problem would you like to solve that made you come to this potential solution?

Right now, Parsoid has the main project and multiple mutually exclusive subprojects.

Subprojects at the same level can share tasks, hence they are not mutually exclusive. Could you elaborate? (Maybe I misinterpret / misunderstand words?)

For the records: As a side effect of the current proposal in this task, the Parsoid project will not have any members, because Projects that are parents of subprojects cannot specify members. Instead, the members of all its subprojects are treated as being is members.

In T245868#5909494, @Aklapper wrote:

As a team, we've decided to collapse them all back into the main project.

Hi, which underlying problem would you like to solve that made you come to this potential solution?

We wanted all Parsoid-codebase tickets in a single board instead for some of our workflows (searching, merging, full codebase view, etc.) ... the project mgmt workflow is captured via filtering the main board via tags and by other boards that track that.

Right now, Parsoid has the main project and multiple mutually exclusive subprojects.

Subprojects at the same level can share tasks, hence they are not mutually exclusive. Could you elaborate? (Maybe I misinterpret / misunderstand words?)

Sorry yes .. I meant: a task in a subproject isn't part of the main project board.

For the records: As a side effect of the current proposal in this task, the Parsoid project will not have any members, because Projects that are parents of subprojects cannot specify members. Instead, the members of all its subprojects are treated as being is members.

We right now have a number of subprojects already ( https://phabricator.wikimedia.org/project/subprojects/487/ ) and I am only asking the admins to remove 3 of the 5 subprojects. So, I don't understand why this changes anything.

In T245868#5910505, @ssastry wrote:

We right now have a number of subprojects already ( https://phabricator.wikimedia.org/project/subprojects/487/ ) and I am only asking the admins to remove 3 of the 5 subprojects. So, I don't understand why this changes anything.

Sorry, my fault! Didn't realize that you want to keep 2 subprojects as subprojects.

So if I understand correctly, this would mean:

• keep WikiPEG and Parsoid-PHP as subprojects of Parsoid (Question: What does that mean when it comes to use of the Parsoid workboard? That tasks in these two projects will be pretty much ignored?)
• Create separate top-level projects for Parsoid-Edit-Support (which has a milestone called Subtree Editing Support, Question: should that survive in a new parent project?), Parsoid-Read-Views, Parsoid-Linter
• Silently mass-move Parsoid-Edit-Support tasks, Parsoid-Read-Views tasks, Parsoid-Linter tasks to their new projects
• Update the side bar links on https://phabricator.wikimedia.org/tag/parsoid/
• Update the project description of Parsoid by adding these three new tags. That project description currently states that
  • its subcomponents are Parsoid-Web-API, Parsoid-DOM, Parsoid-Serializer, Parsoid-Tokenizer,
  • its tags are Parsoid-Nowiki, Parsoid-Rendering, Parsoid-Robustness, Parsoid-Tests, Parsoid-Token-Stream-Transforms,
  • its "Parent project" is Services (Question: which makes me wonder what Parsing-Team--ARCHIVED is actually used for, or which parts of Parsoid project tags fall under Services -team and which ones under Parsing-Team--ARCHIVED)
• Archive these three subprojects of Parsoid

In T245868#5912739, @Aklapper wrote:

So if I understand correctly, this would mean:

• keep WikiPEG and Parsoid-PHP as subprojects of Parsoid (Question: What does that mean when it comes to use of the Parsoid workboard? That tasks in these two projects will be pretty much ignored?)

WikiPEG might be ignored for a while yes unless we have spare capacity or some task in there becomes a blocker for some other work we are doing. As for Parsoid-PHP, that is ongoing work, and at the end of this quarter, we'll archive that subproject as well and move pending tasks into the main board.

• Create separate top-level projects for Parsoid-Edit-Support (which has a milestone called Subtree Editing Support, Question: should that survive in a new parent project?), Parsoid-Read-Views, Parsoid-Linter

No. They will NOT be top-level projects. Just tags like you indicated further below. We want all those tasks to just be tagged with Parsoid (the parent project).

• Silently mass-move Parsoid-Edit-Support tasks, Parsoid-Read-Views tasks, Parsoid-Linter tasks to their new projects

No, Move to Parsoid

• Update the side bar links on https://phabricator.wikimedia.org/tag/parsoid/
• Update the project description of Parsoid by adding these three new tags. That project description currently states that
  • its subcomponents are Parsoid-Web-API, Parsoid-DOM, Parsoid-Serializer, Parsoid-Tokenizer,
  • its tags are Parsoid-Nowiki, Parsoid-Rendering, Parsoid-Robustness, Parsoid-Tests, Parsoid-Token-Stream-Transforms,
  • its "Parent project" is Services (Question: which makes me wonder what Parsing-Team--ARCHIVED is actually used for, or which parts of Parsoid project tags fall under Services -team and which ones under Parsing-Team--ARCHIVED)

I don't think the Services applies any more for Parsoid since it is part of core. As for Parsing-Team--ARCHIVED we do occasionally look at it but we will figure out how to handle that board later.

• Archive these three subprojects of Parsoid

Yes.

In T245868#5913009, @ssastry wrote:

I don't think the Services applies any more for Parsoid since it is part of core.

@ssastry: Would you edit the project description to reflect the current situation?

As for Parsing-Team--ARCHIVED we do occasionally look at it but we will figure out how to handle that board later.

@ssastry: Is there a task to track defining how it is used or not? If not, would you create one?
Also see https://www.mediawiki.org/wiki/Phabricator/Project_management

Thanks! Can you bulk add "Parsoid-Rendering" tag to all tasks in the "Read Views" column on https://phabricator.wikimedia.org/project/board/487/ ? I tried doing it, but got warned that it will send emails and notifications.

@ssastry: Sure, done now.

@ssastry: Ping. Could you please fix the two remaining issues?

In T245868#5929537, @Aklapper wrote:

In T245868#5913009, @ssastry wrote:

I don't think the Services applies any more for Parsoid since it is part of core.

@ssastry: Would you edit the project description to reflect the current situation?

Done.

As for Parsing-Team--ARCHIVED we do occasionally look at it but we will figure out how to handle that board later.

@ssastry: Is there a task to track defining how it is used or not? If not, would you create one?
Also see https://www.mediawiki.org/wiki/Phabricator/Project_management

We occasionally look at that parsing-team board. But, most of the phab tasks that are Parsoid related get triaged as part of our existing workflow. But, we should remember to untag the parsing-team tag. In any case, I untagged about 20 tasks that had the Parsoid or Linter tags. There are 58 more tasks left there and we'll talk about how to handle this board in the future.

In T245868#5974406, @ssastry wrote:

We occasionally look at that parsing-team board. But, most of the phab tasks that are Parsoid related get triaged as part of our existing workflow. But, we should remember to untag the parsing-team tag. In any case, I untagged about 20 tasks that had the Parsoid or Linter tags. There are 58 more tasks left there and we'll talk about how to handle this board in the future.

@ssastry: Did that conversation take place?