Job graduation #554

Closed
opened 2021-09-17 04:43:23 +02:00 by blaggacao · 1 comment
blaggacao commented 2021-09-17 04:43:23 +02:00 (Migrated from github.com)

In a large adoption of makes, we would typically find a fork of makes that holds domain specific module adaptions on one hand and end-user repositories on the other hand.

Typically, the flow of standardization is bottom up rather than top down. That means that new ideas germinate in end-user repositories' ./makes folder and eventually graduate into the makes fork's module system.

To support this process, we would need to provide a sort of metadata field on scripts which help organize the process and make it both, obvious & transparent.

For example, a simple status labeling scheme, as is common metadata in many simplified workflow implementations, could suffice:

  • status = "wip"
  • status = "documented"
  • status = "upstream candidate"

We could then have a special command to filter jobs based on their maturity, so that cross-orga devops people can relatively easily get a general view on the state of job affairs across several repositories and spot upstreamable candidates more easily. Or support with general chore / imp.

In a large adoption of `makes`, we would typically find a fork of `makes` that holds domain specific module adaptions on one hand and end-user repositories on the other hand. Typically, the flow of standardization is bottom up rather than top down. That means that new ideas germinate in end-user repositories' `./makes` folder and eventually graduate into the `makes` fork's module system. To support this process, we would need to provide a sort of metadata field on scripts which help organize the process and make it both, obvious & transparent. For example, a simple `status` labeling scheme, as is common metadata in many simplified workflow implementations, could suffice: - `status = "wip"` - `status = "documented"` - `status = "upstream candidate"` We could then have a special command to filter jobs based on their maturity, so that cross-orga devops people can relatively easily get a general view on the state of job affairs across several repositories and spot upstreamable candidates more easily. Or support with general chore / imp.
blaggacao commented 2021-09-30 05:05:54 +02:00 (Migrated from github.com)

I don't think (any more) this is particularly necessary at the moment. It is a neat idea. I'll close for now.

I don't think (any more) this is particularly necessary at the moment. It is a neat idea. I'll close for now.
This discussion has been locked. Commenting is limited to contributors.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
justin/makes#554
No description provided.