Removing Project-creators tag until we figure out if this is what we need, as part of a wider discussion that also involves T88468: Create Phabricator project to track noteworthy changes.

Updating title and description following the discussion in T24: Decide whether project reporting should be moved to Phabricator as well.

Name:
Being afraid of confusion (also because it's not the most simple thing to find a project's description in Phab when you have a tag), wondering if #status-summary is also acceptable here.

Process:
Definitely needs very clear instructions as we can only tag tasks but not specific comments in tasks.

e.g. that epic task about rewriting underlying system XYZ that just received an edit to its task description or just got comment 64 added which contains a summary of recent achievements, probably should not receive that tag.

While a dedicated task with

• summary = "2016-12-01" or "2016-12-monthly" (TODO: is more content wanted/needed in the summary already? Really depends on how you plan to view a list of these tasks, as a query result view would already list further associated projects)
• and
• description = "Last month we replace bar by foo" or "See T98765432#12345678" (TODO: is just linking to another comment or task acceptable or not?)
• and
• the associated tag = "#status-summary"
• and
• the associated tag = "#XYZ-Team" and/or "#XYZ-Rewrite"

should?

I like this idea A LOT, but since the aim is to move the reports from mediawiki.org to Phabricator, why not having an explicit Report tag? "Summary" sounds too vague and passive. A report is a summary with a purpose, a public communication.

About when to use this tag, the recommendation could be:

• If your project is running sprints, a Report is welcome at the end of the sprint.
• If your project is not running sprints, then you might consider a monthly or quarterly cadence, depending on the activity of the project.

In T88470#1049364, @Aklapper wrote:

Being afraid of confusion (also because it's not the most simple thing to find a project's description in Phab when you have a tag), wondering if #status-summary is also acceptable here.

In T88470#1049644, @Qgil wrote:

I like this idea A LOT, but since the aim is to move the reports from mediawiki.org to Phabricator, why not having an explicit Report tag? "Summary" sounds too vague and passive. A report is a summary with a purpose, a public communication.

My original proposal was to use #report but @Tbayer wasn't convinced and preferred #summary. I'm fine with whatever as long as we don't take forever to pick one :)

In T88470#1049364, @Aklapper wrote:

Definitely needs very clear instructions as we can only tag tasks but not specific comments in tasks.

e.g. that epic task about rewriting underlying system XYZ that just received an edit to its task description or just got comment 64 added which contains a summary of recent achievements, probably should not receive that tag.

Agreed. @bd808 proposed another approach in T24#1047982 but the more I think about it, the more I think that we should stick to the "1 update↔1 task" bijection.

In T88470#1049644, @Qgil wrote:

• If your project is running sprints, a Report is welcome at the end of the sprint.
• If your project is not running sprints, then you might consider a monthly or quarterly cadence, depending on the activity of the project.

Sounds good to me. As I mentioned earlier, each team is free to choose the frequency.

In T88470#1054289, @gpaumier wrote:

My original proposal was to use #report but @Tbayer wasn't convinced and preferred #summary. I'm fine with whatever as long as we don't take forever to pick one :)

I may have misunderstood this part. Let's use #report then, since people are more used to that term.

I think this task is ready to go and the tag can now be created!

In T88470#1054821, @gpaumier wrote:

In T88470#1054289, @gpaumier wrote:

My original proposal was to use #report but @Tbayer wasn't convinced and preferred #summary. I'm fine with whatever as long as we don't take forever to pick one :)

I may have misunderstood this part. Let's use #report then, since people are more used to that term.

I think this task is ready to go and the tag can now be created!

Yes, my point was rather that use of the tag should somehow carry the expectation that the team should not just tag a completed task as a "reporting level incident", but also add a brief summary text that provides some context. Otherwise it could become quite difficult for an uninvolved reader to get close to the level of understanding that the previous monthly reports / status updates provided. I understand @gpaumier will add some text to that effect to the description of the new project, now that it is live.

This wave of new tags (report, notice, roadmap... more?) should be documented somewhere at https://www.mediawiki.org/wiki/Phabricator/Project_management. I'm starting to feel a bit unsure/lost about what to use and when. I can be considered as a benchmark, this means that most of the target users of these tags will be even more unsure/lost.

@Qgil: T88468 is still open so things are still moving. I'll document the tags (in their description in Phabricator, and on the wiki) next week if possible.