-
Notifications
You must be signed in to change notification settings - Fork 40
Ops Campaigns
Starting this August, we will be starting longer-term operations task management which we are calling campaigns. These will be conducted as needed, when there is a request from EGI, an ROC site or a user community, which requires coordinated action at most or all sites. The idea behind running a campaign is that will have a campaign leader, who is responsible for getting sites to stick to a schedule or taking action; campaigns are also time-limited, meaning that they have to have a start and an end.
While this is just another way of doing what we've always been doing, it will give some more visibility to important ROC-wide tasks and perhaps allow better delegation of tasks. Also, it will allow us to report better to supporting projects such as CHAIN-REDS and ei4Africa, as well as relying parties like EGI.eu. Ideally, campaigns should have
- A motivation
- a description of the work to be done.
- their own web page
- a calendar of actions and
- a hashtag.
Campaigns will be mostly documented on the Github wiki pages of the AAROC DevOps repo
for more information on what's going on, see the ROC webpage.