Guide to proposing changes to the BoB Standard

Guide to proposing changes to the BoB Standard

This guide describes how a change proposal moves from a first idea to an approved change in the BoB standard. It covers what you do, when Samtrafiken gets involved and how the BoB Community contributes.

You prepare and drive your proposal yourself. Samtrafiken gives guidance when you need it and coordinates the formal part of the process, described in Change Management for the BoB Standard.

Steps

  1. Identify the need

  2. Discuss the idea

  3. Refine the proposal

  4. Create the technical contribution

  5. Create the Change Request

  6. Submit the Change Request

  7. Community review

  8. CAB review and decision

1. Identify the need

Responsible: You

Start by describing the need:

  • What problem are you trying to solve?

  • Who is affected?

  • Why is the current solution not sufficient?

  • What value would the change bring?

You do not need a complete solution at this stage. Focus on describing the problem.

2. Discuss the idea

Responsible: You

Before you write a formal Change Request, discuss the idea with the community. You can:

  • create a post in BoB Tech

  • present the idea at BoB Tech Live

  • talk directly with other participants

This gives you early feedback, shows consequences you may have missed and tells you whether others have the same need. No approval is needed at this stage.

Other participants give feedback and ideas. Samtrafiken takes part in the discussion and can give guidance.

3. Refine the proposal

Responsible: You

Use the feedback to improve the proposal. You may find:

  • a simpler solution

  • additional use cases

  • technical implications

  • a chance to combine your proposal with another initiative

There is no fixed point when a proposal is ready. Sometimes the Change Request itself becomes the basis for further discussion.

4. Create the technical contribution

Responsible: You

If the proposal affects the technical specification, prepare the changes by following the Technical contribution guide. This means:

  • creating a fork of the relevant repository

  • making the proposed changes

  • submitting a pull request with the changes

The technical contribution should be ready before Samtrafiken opens the proposal for community review in step 7. Smaller editorial changes may not need a separate technical contribution.

Samtrafiken can help with the contribution process and the repository structure.

5. Create the Change Request

Responsible: You

Describe in your Change Request:

  • the problem

  • the proposed solution

  • why the change is needed

  • the expected benefits

  • references to the technical contribution, if there is one

Use the Change Request template.

6. Submit the Change Request

Responsible: You submit, Samtrafiken registers

Send your Change Request through Samtrafiken's support portal.

Samtrafiken checks that it contains the information needed and may ask for clarifications. When the proposal is ready to move forward, Samtrafiken creates an issue in the BOBX backlog. The proposal is then part of the formal change management process and can go on to community review.

7. Community review

Responsible: Samtrafiken

Samtrafiken publishes the BOBX issue in the BoB Tech Forum, opens it for dialogue and coordinates the review.

The community comments, asks questions and suggests improvements in the forum. The aim is to resolve open questions and reach consensus before the proposal goes to the CAB.

You take part in the discussion, answer questions and update the proposal or the technical contribution when needed.

8. CAB review and decision

Responsible: Samtrafiken and the CAB

When the community review is done and the feedback has been handled, Samtrafiken presents the proposal and the outcome of the review to the Change Advisory Board (CAB).

CAB members review the proposal individually for about a month. The proposal is then discussed at the next CAB meeting, where the board makes its decision.

The CAB works by consensus. Since proposals have usually been discussed and refined along the way, it is uncommon for one to be rejected at this stage. A CAB member who cannot support a proposal is expected to give technical or business reasons and, where possible, suggest changes or alternatives.

The decision is one of:

  • GO

  • NO GO

  • Returned for revision

An approved change is planned for a future release of the BoB standard.

Need help?

If you have questions at any stage, contact Samtrafiken through the support portal.