Template:QEMU PRIP Process

From PRPL
Jump to: navigation, search

PRIPs process overview[edit]

NOTE: This isn't a hard set of rules; nor do you have to do them in that order serially. You could finish coding your change before writing one word in a PRIP, for example. The risk in doing so is that you miss out on feedback when you could incorporate it at relatively low cost -- that is, relatively little rework. It's better to overcommunicate and overdiscuss.

The following list describes one approach for improving prpl QEMU using a PRIP:

Have an idea for improving prpl QEMU[edit]

Every new improvement comes from a community member having an idea. If you have an idea for prpl QEMU, start the PRIP process.

Sometimes, even though you have a good idea, you want to bounce the idea off some members of the community before you begin working on it. In that case, email the QEMU PEG mailing list with your idea and see if anyone has any thoughts.

Break it down, if necessary, to discrete ideas.[edit]

We don't want to lose the big picture but breaking down big ideas helps ensure you've thought through all the steps and helps others better understand your proposal.

Open a feature request[edit]

Add a feature request via Github Issues on the prpl QEMU issue tracker. Provide enough detail about what the improvement does and how it makes prpl QEMU better; that allows the triage team and attendees to offer feedback and, if all goes well, schedule the feature in an appropriate release.

Draft your PRIP[edit]

Get the ideas "down on paper." Use the Create A New PRIP tool to start creating your PRIP on the wiki. All you'll need is the issue number from the issue your created in the last step.

Get public feedback[edit]

You have many options for feedback: E-mail the prpl QEMU mailing list describing the proposed change. Blog posts. Tweets. Discussions at online meetings.

Capture the feedback[edit]

Use the feedback to improve your PRIP. Add useful suggestions. Address weaknesses. List alternatives. Consider what it means if you're getting lots of negative feedback. (But don't let the haters get to you.)

Update your PRIP[edit]

Complete all the sections of the PRIP. Keep discussing on the mailing list. When you're done, email the prpl QEMU mailing list and ask for final approval of the PRIP. Don't worry about a formal vote, just get a general sense of whether the community supports creating a PRIP branch.

Feature branch is added[edit]

If your PRIP is approved, a feature branch named for your PRIP will be added to the prpl QEMU Github repository. The feature branch name uses the formula PRIPn where n is the PRIP number.

Collaborate on the feature[edit]

Now that your feature branch has been added, collaborate with others on the feature using the Merge-then-review workflow.

Workflow diagram of PRIP Process[edit]

Feature Creation.png

The content of this page is licensed under the Microsoft Reciprocal License

The content of this page is a derivative work of [1], Copyright (c) 2004, Outercurve Foundation.