Request For Comment [RFC] Framework

An RFC can be created once a Moderator approves a Proposal Idea for progression. Your RFC must take into account all the relevant feedback presented by the community in response to your Proposal Idea. The process and format for an RFC is outlined below.

After submitting an RFC, you should post the link to your new RFC at the top of your original Proposal Idea, then change the label on your Proposal Idea to progressed, and move it to the Proposal Archive subcategory.

The RFC phase is aimed at building out your proposal to finally advance into a Formal Proposal. Your RFC should respect the following guidelines:

1. Posted in the Hubble Improvement Proposal: RFC section

2. Tagged with the rfc tag, and have the [RFC] prefix.

3. Include a link to your original Proposal Idea

When creating an RFC, the link to the related Proposal Idea should be added at the top of the RFC post. If your RFC does not link to the original Proposal Idea, it will be removed by a Moderator.

4. Include all the relevant information raised in your Proposal Idea

5. Facilitate the discussion and update your RFC

The goal of an RFC is to collect as much community feedback as possible, as well as reflect all new insights brought forward. After your RFC is posted, you should engage with community members in the comment section, facilitating the conversations and doing so as neutrally as is possible.

As the discussion unfolds, you should add any relevant information to the body of your RFC. If you are referencing a specific comment, insert the link to the related comment. Your RFC should remain up to date with new information at all times. If you have posted an RFC, you are responsible for keeping it updated, and for driving the community to engage with it.

6. Include a poll

The goal of your RFC is to gather comprehensive feedback on your proposal, and a poll is an accurate representation of community feedback.

Once your RFC is completed, scroll to the bottom and insert a poll:

  1. Select the cog on the far right of the menu, then select Build Poll

  1. Select Multiple Choice poll unless your poll only has “Yes”, “No” and “Abstain” as options.

Note: All polls should include “Abstain” as an option.

  1. Select the cog in the bottom right corner to open the poll-setup options.

  2. Type a neutral poll title that aligns with the content of your RFC.

  3. Type in all the relevant options according to the content of your RFC.

Note: Each voting option should consist of a single, clear option.

  1. Set Min Choices to 1 and Max Choices to the number of polling options, excluding the “Abstain” option.

  2. Set Limit voting to these groups to Trust_level_2

  3. Set Show results... to Only after voting

  4. Enable the Show who voted option.

  5. Ensure the Automatically close this poll option is disabled.

In the end, your poll setup should look more or less as follows:

Why it’s necessary for polls to follow the standard:

  • Uniformity enables ease of use and interaction across the board, regardless of topic.
  • Including the “Abstain” option allows for neutral or disinterested users to indicate their neutrality, and may also serve as a means of protest against the topic.
  • Allowing for multiple options to be selected allows users to indicate interest in as many options as they see fit.
  • trust_level_2 prevents voting from being manipulated or spammed by new or untrustworthy accounts.
  • Revealing results only once the vote is complete prevents confirmation bias, where users might be swayed in favor of a certain option upon seeing the majority vote.
  • Polls need to remain open as long as the RFC remains open, which is not limited to a specific time period, but instead is dependent on the amount of engagement and feedback on your RFC.