#spicerack would need to removed as a alt hashtag for #sre-tools

What are the options here in terms of tag vs project? Is a tag also a project anyway? Can all the tasks tagged show up in the existing SRE-tools workboard?

I'm asking because I'm not convinced that an additional project with its own dashboard would actually help.
Many spicerack-related tasks have cross-dependencies with other tasks related to other projects, most of which belongs to SRE-tools and having those in different dashboard would be confusing.
From what I've seen in the last few years usually people tend to merge multiple dashboards into one and not the opposite, to simplify the workflows.

So if this means just creating a dedicated tag that belongs to SRE-tools and the tasks will appear in the same dashboard, sure, why not.
But if this means that those tasks will not appear in SRE-tools then I don't think we should proceed as they will just spread fragmentation and not allow to have a single place where to look for SRE automation and tooling related tasks. That's why there are a lot of aliases for the SRE-tools project, so that all those confluence in the same place.

The experience with the homer tag has been mixed. But that one has much more sense because many tasks there are related to the configuration of the network, not the software itself. And still sometimes a task related to homer-the-software is opened with only the homer tag and not the sre-tools one and gets lost because not tracked in the sre-tools dashboard.

@crusnov, @jbond, @elukey, @faidon: do you have any thoughts on this?

Maybe as a subproject? According to the wiiki (https://www.mediawiki.org/wiki/Phabricator/Project_management#Parent_Projects,_Subprojects_and_Milestones) namespaced projects are allowed, but not sure if that's only for 'umbrella' projects.

Or maybe not xd

Tasks in subprojects will not show up on the workboard of the parent project.

Tags are projects are project tags.
Milestone could work but do see the "warnings" section first. Or Herald rule if all tasks tagged with #Spicerack should also be tagged with #SRE-Tools.

Hmm, so I think that a new project + a herald rule to add always the SRE-tools tag should do the trick then.

(thanks @Aklapper !)

I think that someone not familure with the sre process is more likley to try and find a spicerack tag then know to use the sre-tools tag. That said i think we should aim for the following

So if this means just creating a dedicated tag that belongs to SRE-tools and the tasks will appear in the same dashboard, sure, why not.

And sounds like @Aklapper has provider a solutions for that (thanks :)). i don't have a preference of if we should use a herald rule or milestone

In T275488#6853017, @jbond wrote:

I think that someone not familure with the sre process is more likley to try and find a spicerack tag then know to use the sre-tools tag.

@jbond fwiw if you type #spicerack Phabricator gives you: Spicerack , because it's already set since the start as an alias tag. Same if you search for spicerack in the search box, the autocomplete already gives you SRE-tools.

@jbond fwiw if you type Spicerack Phabricator gives you: SRE-tools

ack good to know thanks

Just to throw in opinion, having a separate tag makes sense, but also for organizational purposes having more workboards for sre-tools is too much, so the solution where sre-tools is automatically added seems like the best balance.

A bit of (maybe useful?) background, the idea is that me (and possible others) out of the SRE-tools project are going to actively work on spicerack (and cumin and related) project, so even for organizational purposes having the separated tag for spicerack itself helps, so people out of SRE-tools working on it can filter it and add it to other searches.

@dcaro: I'm not sure I get what is your proposal here with regard to the "related" part.
Because if we add also spicerack's "related" projects then we're more or less replicating SRE-tools, and it would be also misleading, why a cumin task should have a spicerack tag?
Or are you proposing to have one tag for each project?

I propose right now start with spicerack, then we'll see about others when they are needed, if the spicerack tag works well, then we can try to adopt a similar process for any other cross-team project, if it does not, then we can go another way.

Ok, but let's not add the spicerack tag also to tasks for other projects like cumin. That would just be confusing. IMHO.

Nono, that's only for spicerack, sorry if I confused you.

In T275488#6853154, @crusnov wrote:

having a separate tag makes sense, but also for organizational purposes having more workboards for sre-tools is too much

@crusnov: You don't have to create (or use) the workboard of a project tag.