• Development
• Blueprints
• no-pythonpath

Summary

Don't require inclusion of ~/.wns/wnsrc.py . The most common use of wnsrc is to locate a working sandbox. This code should be moved to the individual scripts that make use of this piece of code.

Release Note

This section should include a paragraph describing the end-user impact of this change.

Rationale

This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

Use Cases

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

API Changes

Should cover changes required to the API, or specific API that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

• changes in configuration files

• backward compatibility if API changes

• how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working.

This need not be added or completed until the specification is nearing beta.

Open Issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF ¹; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

• CategoryBlueprint