Page MenuHomePhabricator

Create a service-deployment-requests project in Phabricator
Closed, ResolvedPublic

Description

See T97031 for the reasoning behind this.

TL;DR Allow people to request the new service process to run for their new service.

Event Timeline

akosiaris created this task.Jun 8 2015, 3:19 PM
akosiaris raised the priority of this task from to Needs Triage.
akosiaris updated the task description. (Show Details)
akosiaris added a project: Project-Admins.
akosiaris added a subscriber: akosiaris.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 8 2015, 3:19 PM

See https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects for required information (description; project type)

I admit I'm still lost how to come up with a description for this project (or some link to some wikipage) that an outsider might be able to understand what the project is about. :-/

Ah yes, sorry.

Description: When a developer or engineer has developed a new service and would like to see it in production, he should file a request in this project in order to provide services and ops teams with the requested information and kick off the process of putting the service in production.

project type: tag

Additional hashtags: none

Policy:

Visible To Public (no login required)
Editable By All Users
Joinable By All Users

When a developer or engineer has developed a new service and would like to see it in production, he should file a request in this project in order to provide Services and Operations teams with the requested information and kick off the process of putting the service in production.

Thanks. Last two questions (sorry, but want to do things right):
If I get it correctly, I am tempted to call this "service-deployment-requests" instead, if you're fine with that?
(Because "service-requests" without lazy /me reading project descriptions could mean asking someone else to provide service by doing random $stuff that I want to see, to differentiate from e.g. Wikimedia-Site-requests or such :)

Also wondering if any of the Services or Operations projects should be automatically associated to tasks (via Herald) under that new project to be created?

Aklapper triaged this task as Medium priority.Jun 10 2015, 3:12 PM

When a developer or engineer has developed a new service and would like to see it in production, he should file a request in this project in order to provide Services and Operations teams with the requested information and kick off the process of putting the service in production.

Thanks. Last two questions (sorry, but want to do things right).

Good that you asked.

If I get it correctly, I am tempted to call this "service-deployment-requests" instead, if you're fine with that?
(Because "service-requests" without lazy /me reading project descriptions could mean asking someone else to provide service by doing random $stuff that I want to see, to differentiate from e.g. Wikimedia-Site-requests or such :)

Sounds fine to me. service-deployment-requests it is.

Also wondering if any of the Services or Operations projects should be automatically associated to tasks (via Herald) under that new project to be created?

Yes, you are right. It would be useful. I assume I should have answered that in Additional Hashtags: but it did not occur to me.

Aklapper closed this task as Resolved.Jun 10 2015, 5:55 PM
Aklapper claimed this task.

Requested project has been created: Service-deployment-requests

Please encourage interested people to visit the project and to join the project as members, and to subscribe themselves to the project in order to receive updates!

Recommended practices for project and workboard management in Phabricator are available.

And if for some reason you ever want to rename the project, please check the guidelines first.

Herald rule H34 created:

Enjoy!

Aklapper renamed this task from Requesting a service-requests project to Create a service-deployment-requests project in Phabricator.Jun 10 2015, 5:55 PM
Aklapper set Security to None.