Please see https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects for required info.

@Aklapper - I think we don't want a project - I thought phabricator has the concept of tags that are not necessarily projects. Let me know if this is not the case. We only want to ensure if they tagged PageviewsAPI, we'd also add the Analytics project.

See https://www.mediawiki.org/wiki/Phabricator/Project_management#Types_of_Projects

@Aklapper, Thanks, I updated the ticket description.

I personally don't see how this is a tag but I'd be happy to create a project.
If this should be a tag, someone else can create it and I won't complain. :)

I don't know how "tags behave differently from projects" - feel feel to elaborate.

@Aklapper - We're not tied to it being a tag - I thought tags imply that this doesn't have a full workboard, and is just an indicator that this task is categorized as a Pageviews-API task. They will all be part of our Analytics project anyway. The purpose is mostly for grouping all Pageview api tasks in one place for someone to keep track of. This was requested in feedback from community. I understand that phabricator treats tags as projects too currently, so the difference is merely visual. So project/tag - whatever is fine.

Alright. Please see https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects for required information (project description etc).

@Aklapper, thanks - edited description with all details.

@madhuvishy: Please clarify, do you want a tag (yellow), or a component (blue)? The description says "project" (which means mostly the type "component"), and another part says "tag". So which one should I create?

I don't think this should be a tag.

@Luke081515 - I think Project(component) is fine.