Job graduation #554
Labels
No labels
dependencies
difficulty::high
difficulty::low
difficulty::medium
good first issue
help wanted
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
justin/makes#554
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In a large adoption of
makes, we would typically find a fork ofmakesthat 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'
./makesfolder and eventually graduate into themakesfork'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
statuslabeling 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.
I don't think (any more) this is particularly necessary at the moment. It is a neat idea. I'll close for now.