0MQ Requests for Comments

Why fork a specification?

You can fork any specification at any point. You do this by copying the existing text, and creating a new specification with the same name and content, but a new number. The reasons you might need to fork include:

1. To change the responsible editor for a specification, with or without the cooperation of the current responsible editor.
2. To rejuvenate a specification that is stable but needs functional changes. This is the proper way to make a new version of a specification that is in stable or deprecated status.
3. To resolve disputes between different technical opinions.
4. To allow new raw versions of existing specifications.

A fork is a different specification, even if it carries the same name. Forks have no special status except that accorded by the community.

The right to fork

While conventional standards-setting processes frown on forking, because it tends to reduce interoperability, we consider the right to fork to be an essential freedom, and it is one that the intellectual property policy of this site enshrines. Forking gives better designs a chance to emerge and it places the burden of choice on the Community, especially implementors and users, rather than on top-down processes.

Naming conventions

When you fork a specification, if you intend to design a new version of the same specification, give it the same name. If you intend to make a knock-off that has radical improvements, feel free to invent a new name.

Prerequisites

Forking a specification means creating a new spec. Before you can create a new spec, you must be registered as an editor. You have to read and agree with the terms of use and intellectual property policy of this site. You must first be registered as a Wikidot user. And you should join the mailing list.

It's your baby

If you start a new specification, you're responsible for it. That means you are the editor, and the only editor of the page. If this is too much responsibility for you, ask the public mailing list for help. The only way to change the editor of an existing specification is to fork it and delete the old one. "Delete" means "tag with the deleted tag". No specs are actually deleted.

Copy the existing spec

On the existing spec page, click the Source action at the top right. If you don't see a Source action, you are either not logged in, or not registered as editor.

Abuse and sanctions

Forking is a tool, and the operators of the site may suspend or ban people who abuse it. We don't define "abuse" but basically if a fork creates more argument than it solves, that's a bad thing.

Go for it

Choose a good name for your spec, and enter the "<abbreviation> - <name>" below. You can change the name later. When you click "Create", you'll get a template for the new spec. Paste the source of the old spec, change the state to "Raw" and save the page. Remove all tags. And then tell the public list what you've done and why.

All specifications