Vox Populi Congress Guide

Recursive

Already Looping
Moderator
Joined
Dec 19, 2017
Messages
3,880
Location
Antarctica
The Vox Populi Congress is a formal system to propose changes to the mod which will be run by me, Recursive (the Host) on a monthly basis. It began on October 1, 2022.

VP Congress Phases
Anyone who wishes to propose a change to the mod (even if they're just a player and not a coder!) can go through the following process.

First 15 days of the month: Proposal Phase
Days 16 – 18 of the month: Counterproposal Phase
Days 18 21 of the month: Sponsorship Phase
Remainder of the month: Voting Phase, including Ratification of Changes from previous releases

Each of these phases will be explained just below.

No Proposals Outside of VP Congress
Because we now have a formal system for proposing changes to the mod, it shall be forbidden to post proposals to make a change on the Community Patch Project forums outside of the VP Congress Process.

Other polls (for instance, to measure what people think of a current mechanic, or to consider potential options for a proposal) are permitted.

Posting discussion/feedback threads is still okay, of course.

Primary Developers
@Gazebo, @ilteroi, and @Recursive are the current "primary developers" of the mod, which have special abilities. Gazebo may select any other developer to be a “primary developer”.



Proposal Phase
Anyone can post a proposal for a change they’d like to see in Vox Populi in the Vox Populi Congress subforum. They must meet the requirements below:

Housekeeping Requirements
  • The proposal must be posted during the Proposal Phase.

  • The proposal must propose a change.

  • The proposal must explain its reasoning; the intended effect(s) of the change. This doesn’t need to be long, but it does need to be present, so the community understands your goal. If the proposal is complicated, such as the integration of a mod with many balance changes, you may be required to provide more detail (see the Other Requirements section below).

  • The proposal must not be a bugfix. All bugs should be reported on GitHub and nowhere else!

  • The proposal must be about game balance or other mechanics visible to the player. Proposals about internal changes such as performance improvements, modmod compatibility or database restructuring should not be made here – open an issue or submit a pull request on GitHub instead.

  • The proposal must not affect the same game mechanic as a proposal in the Proposal Queue (awaiting implementation into a release). See Proposal & Ratification Queues.

  • The proposal must not be identical to one that someone else has already made during this Proposal Phase.

  • The proposal thread title should have the correct format. This depends on the game mechanic that is being modified. The Host will correct any proposals with formatting issues, but try to follow this to put less work on the Host.
    - If the game mechanic being affected was modified recently and is awaiting ratification (see Proposal & Ratification Queues), the format is: (X-YY) Ratification Option: Thread Title

    - If it's not a ratification option, but there is an existing proposal to modify the same game mechanic, it's a Counterproposal and the format is: (X-YY) Counterproposal: Thread Title

    - If it's neither of these, it's simply a Proposal and the format is: (X-YYn) Proposal: Thread Title

    X = The number of the current VP Congress Session.
    YY = The proposal number, starting at 01. This is based on the timestamp for the first post in the thread. You can view the order in which threads were created by using the "First post > Ascending/Descending" forum filter.
    n = The counterproposal letter (only for Counterproposals). If the base proposal is (2-03), then the first Counterproposal would be (2-03a), the next would be (2-03b), etc.

  • If the proposal is a Ratification Option or a Counterproposal, you must link to the first proposal in your opening post. The only exception to this is a Ratification Option for a balance change that wasn't proposed, in which case simply describe the change. Descriptions of balance changes which weren't proposed are provided in the Proposal & Ratification Queues thread.

Formal Requirements
  • The proposal must be specific. Explain exactly what change you want to see and use exact numbers if possible. “Make Culture Victory less easy to achieve” will be rejected, while “Reduce the base Tourism on Great Works to 1” is a valid suggestion.

  • The proposal must be in scope for the mod. This will be generously interpreted given that this process is intended to empower the voices of the players, but if you’re asking for something which is impossible, would completely upend the game, or requires an infeasible amount of work, your proposal will be rejected. For example, a proposal for a 64-bit version of Vox Populi would be rejected.

  • The proposal must not be identical (or very similar to) a proposal that was rejected by the community in last month’s Voting Phase, or which was overturned during ratification within the past 30 days. A substantially changed proposal on the same game mechanic is allowed.

  • The proposal thread's opening post (OP) must contain all the elements of the proposal. Using multiple posts (or multiple threads!) to make the proposal is not permitted.

  • The proposal must contain no optional or "figure this out" elements. You are making a proposal, not bringing up possible options or asking for suggestions. If you want to do either of these, start a discussion thread in the main forum.

  • A proposer may only make one proposal per game mechanic. No counterproposals by the same person for the same game mechanic will be permitted.

Other Requirements
  • Proposals which modify bugged game mechanics might be vetoed until any bugs are fixed. This will be decided on a case-by-case basis.

  • A primary developer may require complicated proposals to provide more detail on the current state of the affected game mechanics and what will be changed, in the interests of making sure everyone understands the changes.

  • Proposals must contain accurate background information. Supporting facts (not opinions) made during a proposal post must be accurate. If a proposal contains misinformation as a basis for its approval, this is grounds for it to be vetoed or the vote count to be reset (see below).

  • The proposal must be safe for work and must not violate any CivFanatics site rules or applicable laws.

  • Proposals to integrate another mod's assets into Vox Populi require permission from that mod's creator.

  • Proposals should not modify the Community Patch only version's game balance.

  • The proposal should be serious. Spamming or trolling with your proposals will lead to your proposal proposing privileges being propositionally pillaged.

  • By making a proposal, you are providing an idea to the community and forfeit any kind of copyright-type claim to the idea. Even if you withdraw the proposal, you accept that the community may propose the idea again in the future, and you accept that your preferred implementation of the idea may not be the one that ends up being added to the mod.

A Note on "Game Mechanics"
This will generally be interpreted narrowly at the Host's discretion, but some examples:

Two proposals which modify the Granary will be considered to modify the same game mechanic.

Two proposals which modify the unit supply calculation will be considered to modify the same game mechanic.

Two proposals which add Founder beliefs will not be considered to modify the same game mechanic.

Two proposals which modify the amount of unit supply provided by different buildings will not be considered to modify the same game mechanic.


Withdrawing a Proposal
The proposal may withdraw their proposal. Please post in the thread and tag @Recursive (or send me a message by conversation) informing me that you would like to withdraw your proposal.

A proposal may not be withdrawn once the Counterproposal Phase has begun.

A withdrawn proposal may be resubmitted by anyone else.

A withdrawn proposal will be labelled as (Congress Session Number-WD) and moved to the Failed Proposals subforum.


Primary Developer Veto
Primary developers can veto a proposal if it does not meet the above requirements, with an explanation as to what requirements the proposal has failed to meet.

Proposals will not be vetoed for failing to follow the correct format or include a link to a main proposal, but the formatting will be corrected by the Host. Try to follow the correct format to reduce the amount of work the Host has to do.

If you’re unsure of whether your proposal is acceptable, you can always consult the Host or else submit the proposal well ahead of time to give yourself time to edit it in the case of a rejection.

A vetoed proposal will be labelled as (Congress Session Number-VT) and moved to the Failed Proposals subforum.


Counterproposals
Proposals which modify the same game mechanic (e.g., increase base Trade Route Gold to 2, increase base Trade Route Gold to 3) are allowed. During the Voting Phase, these will be displayed as separate options.

If you are submitting a proposal which conflicts with another proposal, it should be labeled as a “Counterproposal”, and you should link to the first proposal that was made on this subject.

There are two types of counterproposals:
- Ones which directly conflict with each other (e.g., +1 Food to Granary, +2 Food to Granary)
- Ones which affect the same game mechanic but could both be added (+1 Food to Granary, +1 Gold to Granary).

In the first case, the voting options would look like this:
  • Yea to +2 Food to Granary
  • Yea to +1 Food to Granary
  • Nay
In the second case, the Host may instead elect to allow multiple proposals to be added at once. For example:
  • Yea to +1 Food and +1 Gold to Granary
  • Yea to +1 Food to Granary
  • Yea to +1 Gold to Granary
  • Nay

Discussion and Debate
Discussion, debate and amendment of the proposals, as well as the submission of counterproposals, can begin right away once a proposal thread is made in the VP Congress subforum.

Discussion must remain civil; avoid personal attacks and accusations. If you don't like a proposal, then attack the proposal, not the proposer.

Avoid any off topic posts that don't contribute to the discussion. Bringing up irrelevant and controversial topics such as politics is a violation of CivFanatics site rules.

Don't make posts which serve only to upset or anger other users (flaming/trolling).


Making an Amendment
To make an amendment, the original proposer should:
  • Edit the original post of their thread to change the proposal.
  • Make a note in the original post to indicate that the proposal was amended and explaining how it was amended.
  • Make a new post in the thread to say that their proposal was amended (this alerts anyone watching the thread, so they can provide feedback or act accordingly).
There is no limit to how many times a proposal can be amended, but no further amendments can be made once the Sponsorship Phase begins.

If a proposal is amended, anyone who doesn't like the amended version can make a counterproposal with the pre-amended version of the proposal.

If a proposer amends a proposal by making it into something completely different (e.g. "+2 Food on Granary" to "Decrease unit maintenance costs by 25%", the proposal may be vetoed and the proposer told to create a new thread at any primary developer's discretion.



Counterproposal Phase
The Counterproposal Phase is intended to prevent:
  • Proposals with large amounts of changes being proposed at the last minute with no opportunity for anyone to make a counterproposal
  • Proposals being withdrawn at the last minute with no opportunity to resubmit it if someone else likes it
During the Counterproposal Phase:
  • No new proposals or Ratification Options may be submitted.
  • Proposals which were withdrawn can be resubmitted.
  • Amendments can still be made.*
  • New counterproposals may be made.*

* = However, unlike during the Proposal Phase, the Counterproposals and amendments made during this phase cannot greatly exceed the scope of the original proposal; the amount of things changed must be around the same amount or lower. If this rule is not followed, the change will be reverted and/or vetoed.



Sponsorship Phase
To advance to the Voting Phase, at least one coder must “sponsor” the proposal by making a post in the proposal thread. The proposer can sponsor their own proposal if they have the coding skills for it, and multiple coders can sponsor the same proposal. The main purpose of this phase is to ensure that the community does not vote on changes that have no chance of getting implemented due to lack of modder availability. Side purposes are to encourage communication between modders and players, to improve awareness of the development process, and to give anyone new who wants to contribute to the project opportunities to do so.

The Host will regularly review the forum during the Sponsorship Phase and add the [Sponsored] thread prefix to all sponsored proposals.

Sponsorship Rules
  • To sponsor a proposal, you must post in the thread to announce that you sponsor it. You must use the word "sponsor" in your announcement.

  • Anyone with the necessary skills, even if they have never previously contributed to Vox Populi, can sponsor a proposal.

  • By sponsoring the proposal, a coder confirms that they are able and willing to do the necessary coding changes by the end of next month's Voting Phase should the community approve the proposal.

  • The coder does not necessarily need to agree with the proposal, they only need to be capable and willing to do the work required to add it to the mod if the vote is Aye.

  • Sponsoring of a proposal can be done before the Sponsorship Phase; however, sponsors should be wary of sponsoring proposals during this time, because the proposal can still be amended until the Sponsorship Phase begins.

Sponsorship Deadline
The deadline to submit the changes for a sponsored proposal to the GitHub repository is the end of the next month's Voting Phase. For instance, a proposal passed during December 2022's Voting Phase must be implemented before February 1, 2023.

If a proposal is not implemented by that deadline, it will be dropped from the queue and fails automatically. Reaching out to other coders, etc. is all perfectly fine if you're having trouble meeting the deadline. There are no penalties for failing to meet the deadline, provided it is not intentional or repetitive on the sponsor's part. This is volunteer work and life happens.

Extensions to the deadline may be granted by Recursive if it appears likely the proposal will be implemented, and that it isn't a case of biting off more than can be chewed.


Partial Sponsorship
If two or more coders can cover different parts of a proposal (for example, one can handle SQL/XML changes and the other can handle DLL integration), this will be counted as valid sponsorship provided that all requirements of the proposal are met.


AI Must Be Able To Handle Changes
Implementing a balance change requires that the AI is able to handle the change. A sponsor must be able to modify the AI to be able to handle the balance change, if necessary.


High Impact Proposals
Primary developers may deem that a proposal is within the scope of the mod, but "high impact" (very complicated, requires a lot of new code, interacts with many existing mechanics, etc). If this determination is made through a post in the thread, the proposal must be sponsored by either two coders or a primary developer in order to proceed to the Voting Phase.

In the case of partial sponsorship, every element of the proposal must be covered by at least two sponsors or a primary developer sponsor.


Fast-Track Acceptance
If a primary developer decides to sponsor a proposal that they determine there is no reasonable objection to (e.g., a quality of life improvement that doesn't detract from anything), that proposal is immediately ratified and skips the Voting Phase. It will be marked as (Congress Session Number-A).


New Proposals and Amendments
No proposals (including counterproposals and ratification options) or amendments to existing proposals may be made during the Sponsorship Phase.


Proposals Not Sponsored
If a proposal is not sponsored by the end of the Sponsorship Phase, it will be marked as (Congress Session Number-NS) and moved to the Failed Proposals subforum.



Voting Phase
At the start of the Voting Phase, the Host will add a poll to all valid proposals in the Vox Populi Congress subforum.

The Host will create a new thread for ratification votes (including any Ratification Options) which links back to the original thread(s). If a proposal has counterproposals, they will be included as separate options in the poll, and a new thread will be created for those proposals, which links back to the original thread(s).

Discussion and debate can still continue.

All members of the community have one vote on each proposal thread. Voting will be publicly visible, and votes can be changed until the end of the month.

At the end of the month, the polls and threads will be closed and moved to the Passed or Failed Proposals subforums depending on the outcome.


Approval Voting
A voting poll will include the main proposal and all counterproposals as options, as well as an option for no changes. Everyone votes for all options they would be happy with, including contradictory options. This method is known as approval voting.

If an option receives at least 10 votes in favor and more votes than any other option, it will be selected. If "no changes" got the most votes, nothing happens. If an option for changes got the most votes, it will be added to the next release of Vox Populi once the coding work for it is complete. Ties will be broken by the Host.

If a proposal is voted down (Nay) during voting, that proposal and any counterproposals cannot be proposed during the next Proposal or Counterproposal Phase.


Vote Count Resets
If during the Voting Phase, a proposal's opening post needs to be edited to be made clear to voters, the vote count will be reset if the Host deems that it has likely had a substantial effect on the vote. This can only be done during the first three days of the Voting Phase. If the proposal text is deemed too unclear later on in the Voting Phase, the proposal will be vetoed and must be resubmitted.


Voting Thread Title Prefixes
The [Vote] and [Ratify] unique thread title prefixes will be added to Voting Phase and Ratification threads.


When does a Ratification Vote get added?
See the Ratification of Changes section just below. The date will also be listed in the Proposal & Ratification Queues thread.


New Proposals and Amendments
No proposals (including counterproposals and ratification options) or amendments to existing proposals may be made during the Voting Phase.


Creating Multiple Accounts to Vote
Don't do it. It's also against CivFanatics site rules. Anyone found to be doing this will have their votes disregarded and moderation action will be taken against their accounts.



Implementation of Changes
If it is discovered during the implementation of a proposal that it is unexpectedly difficult or impossible to implement, has gamebreaking effects, or the AI is unable to handle it:

1. If the proposal can be made feasible with small modifications which don't defeat the purpose of the proposal, it will be implemented in modified form. This will be noted at ratification time and in the Proposal & Ratification Queues thread.

2. If this cannot be done, the proposal will be vetoed.



Ratification of Changes
Once a new release is made including approved changes, a 30 day timer starts. After the players have had 30 days to playtest the changes, a review poll will be made during a following Voting Phase, where players will be asked to ratify (confirm) the changes.

A ratification vote will be held during a Voting Phase if there are at least 7 days of voting left on the 30th day after the changes were publicly released. Otherwise, the vote will be held on the following month.

An approval vote in favor (with at least 10 people voting in favor) confirms the changes. If the changes are not approved, they will be removed from the mod in the next release and cannot be proposed again for another 30 days after that.

Approved changes will be moved from the Passed Proposals subforum to the Ratified Proposals subforum, while unapproved changes will be moved to the Failed Proposals subforum.

There is one big exception to this rule, and that is if the original implementation of the changes is bugged. In this case, the 30 day timer starts after a hotfix is released which fixes the changes. Small problems such as a minor UI issue for a major overhaul do not count for this, as long as the bulk of the changes were able to be adequately playtested by the community.


Ratification Options
These will be presented as alternate options in the vote. If a Ratification Option also affects other game mechanics or is greater in scope than the original proposal, a second ratification vote will be held if the Option is voted for.


Proposals Without a Ratification Vote
If a proposal is passed which does not affect the game's balance in a meaningful way and isn't the integration of another mod, the proposal will be ratified immediately, without a ratification vote taking place. Changes to the UI or to diplomacy mechanics, for example, would not be subject to ratification.

Proposals which are accepted using Fast-Track Acceptance are also ratified immediately.




Balance Changes Outside the VP Congress
The VP Congress is intended to give the community more control over the changes they’d like to see in the mod, so it is ideal to run balance changes through the VP Congress process.

However, with the approval of a primary developer, a balance change can be made outside the VP Congress process by submitting a pull request or pushing code to GitHub. In this case, however, the changes will be ratified by the community after 30 days like a proposal, and the community can approve or reject the changes.

Primary developers do not have to give this approval if they don’t think the community will appreciate the change, instead directing the proposer to the VP Congress process.

This retains the ability for seasoned developers to contribute to the mod on their own time and schedule (which is necessary for us devs) but gives the community more power over whether they want to accept changes into the mod.


Early Integration of Proposals
This should only be done sparingly. If a developer pushes a change to the mod on GitHub which affects the same game mechanic as a current proposal (or a non-proposal change awaiting ratification), and a primary developer approves it:
  • If the changes integrate a proposal in its entirety: That proposal is "accepted", which gets the notation (Congress Session Number-A) and removed from voting. It is still subject to ratification, unless it was added through Fast-Track Acceptance (see above).

  • If the changes integrate part of a proposal, but don't conflict with it: The elements that are integrated will be removed from the proposal. A note about this will be added to the proposal's OP. This should not be done during the Voting Phase. If it nevertheless is done during the Voting Phase, the vote count is reset if this is the first three days of the Voting Phase, and the proposal is vetoed otherwise.

  • If the changes directly conflict with a proposal (Counterproposal): That proposal is vetoed. Developers should be cautious about this power in the interests of democracy.

  • If the changes affect the same game mechanic as a proposal, but don't directly conflict (also Counterproposal): A note about this will be added to the proposal's OP. This should not be done during the Voting Phase. If it nevertheless is done during the Voting Phase, the vote count is reset if this is the first three days of the Voting Phase, and the proposal is vetoed otherwise.

  • Changes which affect a proposal awaiting ratification will be treated as a Ratification Option. This should not be done during the Voting Phase. If it nevertheless is done during the Voting Phase, the vote count is reset if this is the first three days of the Voting Phase, and the proposal is vetoed otherwise.

  • Changes which modify existing non-proposal changes awaiting ratification: in this scenario, the changes will be modified and the 30 day ratification timer will be reset.

Changes Prior To October 1 Release
The VP Congress’s first session shall begin after the new release on October 1, 2022. All changes made prior to that date will not be subject to ratification, as they are part of the mod’s “base state”. They can still be changed through proposals, though!




Management of the VP Congress
The Host, Recursive, shall be in charge of managing the VP Congress using his moderator abilities, enforcing the rules for it and ensuring the entire process runs smoothly.

If there are edge cases or conflicts between VP Congress rules, the Host will adjudicate the situation and decide which rules will apply. This may involve a modification to this guide.

Please note that making mistakes about this new process will not lead to you getting in any trouble, I will simply explain/correct the error. Please don't take a proposal being vetoed personally; you are free to submit a corrected proposal immediately.

Feel free to contribute as many suggestions as you'd like!
 
Last edited:

Tekamthi

King
Joined
Aug 12, 2016
Messages
733
maybe consider deferring some proposals this first round. There are so many! Difficult to digest them all in one go
 

Stalker0

Baller Magnus
Joined
Dec 31, 2005
Messages
9,570
maybe consider deferring some proposals this first round. There are so many! Difficult to digest them all in one go
It is quite a few, but it will probably look a lot cleaner once Recursive makes them into polls, as all of the counterproposal threads would be condensed into just a few options. Also we need to keep in mind sponsorship, there are a number of proposals on the board right now that don't have one, if a dev doesn't commit to coding something, it just gets dropped.

So I share your concern that we did get quite a few out of the gate, but I don't think it will look as bad once its tidied up for the actual voting. We will see!
 

Recursive

Already Looping
Moderator
Joined
Dec 19, 2017
Messages
3,880
Location
Antarctica
maybe consider deferring some proposals this first round. There are so many! Difficult to digest them all in one go
It is quite a few, but it will probably look a lot cleaner once Recursive makes them into polls, as all of the counterproposal threads would be condensed into just a few options. Also we need to keep in mind sponsorship, there are a number of proposals on the board right now that don't have one, if a dev doesn't commit to coding something, it just gets dropped.

So I share your concern that we did get quite a few out of the gate, but I don't think it will look as bad once its tidied up for the actual voting. We will see!

I'd like to try one round of this before making changes to the system if need be.

Though I am making one important change: majority voting is replaced by approval voting, which is a fairer system for simple decisions like these and will stop multiple counterproposals from preventing a change that the majority desires from happening (so, more democracy).

Approval voting is simple: everyone votes for as many options in a set of proposals/counterproposals as they would be happy with (including contradictory options and "no changes"). The option with the most votes wins (I will break ties).

 
Last edited:

axatin

Warlord
Joined
Jul 24, 2022
Messages
116
Could we introduce the rule that proposal thread titles have to start with a number, and counterproposals start with the number of the proposal they're referring to? That way, by sorting the threads alphabetically, it would be easy to see all (counter)proposals to one topic:

(1) Proposal: Granaries should give more food
(1) Counterproposal: Granaries should ...
(2) Proposal: Nerf Songhai
...
 

Stalker0

Baller Magnus
Joined
Dec 31, 2005
Messages
9,570
Could we introduce the rule that proposal thread titles have to start with a number, and counterproposals start with the number of the proposal they're referring to? That way, by sorting the threads alphabetically, it would be easy to see all (counter)proposals to one topic:

(1) Proposal: Granaries should give more food
(1) Counterproposal: Granaries should ...
(2) Proposal: Nerf Songhai
...
Probably easier to do 1, then 1a, 1b for the counterproposals, as the numbers won't increase as fast. But I like the idea.
 

Recursive

Already Looping
Moderator
Joined
Dec 19, 2017
Messages
3,880
Location
Antarctica
Could we introduce the rule that proposal thread titles have to start with a number, and counterproposals start with the number of the proposal they're referring to? That way, by sorting the threads alphabetically, it would be easy to see all (counter)proposals to one topic:

(1) Proposal: Granaries should give more food
(1) Counterproposal: Granaries should ...
(2) Proposal: Nerf Songhai
...
Probably easier to do 1, then 1a, 1b for the counterproposals, as the numbers won't increase as fast. But I like the idea.
I have numbered the proposals as such.
 

Recursive

Already Looping
Moderator
Joined
Dec 19, 2017
Messages
3,880
Location
Antarctica

Recursive

Already Looping
Moderator
Joined
Dec 19, 2017
Messages
3,880
Location
Antarctica

usadefcon1

Prince
Joined
Sep 24, 2016
Messages
324
Are we going to have 50+ proposals on the main forum or should there be a different sub forum specifically for voting?
 

Recursive

Already Looping
Moderator
Joined
Dec 19, 2017
Messages
3,880
Location
Antarctica
Are we going to have 50+ proposals on the main forum or should there be a different sub forum specifically for voting?
The main forum, but by then I'll have moved all the old threads to the Archive subforum.
 

adan_eslavo

Archmage of all Pixels
Supporter
Joined
Apr 23, 2017
Messages
2,837
Location
Łódź, Poland
maybe consider deferring some proposals this first round. There are so many! Difficult to digest them all in one go
This is how it should work for those proposals, that didn't manage to get a Sponsor during the Sponsorship phase. It's not possible that all of them would get a Sponsor if we notice how many Developers VP has. Maybe next sesion someone will decide to support the project, and then it will go under the voting. Instant failure when the Proposal doesn't get the Sponsor might kill some good ideas.
 

Legen

Emperor
Joined
Sep 13, 2015
Messages
1,156
This is how it should work for those proposals, that didn't manage to get a Sponsor during the Sponsorship phase. It's not possible that all of them would get a Sponsor if we notice how many Developers VP has. Maybe next sesion someone will decide to support the project, and then it will go under the voting. Instant failure when the Proposal doesn't get the Sponsor might kill some good ideas.
Correct me if I'm wrong, but I assume that a proposal without a sponsor doesn't count as rejected for the purposes of the rule below:
The proposal must not be identical (or very similar to) a proposal that was rejected by the community in last month’s Voting Phase, or which was overturned during ratification within the past 30 days. A substantially changed proposal on the same topic is allowed.
A rejection requires it to go to the Voting Phase in the first place.

If someone's proposal doesn't get a sponsor this session, one can still propose it again next session.
 

Recursive

Already Looping
Moderator
Joined
Dec 19, 2017
Messages
3,880
Location
Antarctica
Correct me if I'm wrong, but I assume that a proposal without a sponsor doesn't count as rejected for the purposes of the rule below:

A rejection requires it to go to the Voting Phase in the first place.

If someone's proposal doesn't get a sponsor this session, one can still propose it again next session.
If a proposal fails because it lacked a sponsor, it can be proposed again next session. It's only changes that are voted down by the community that can't be proposed again for 30 days.

Does it need to be proposed separately for each session?
It could stay in the subforum for months if that was the case.
 

adan_eslavo

Archmage of all Pixels
Supporter
Joined
Apr 23, 2017
Messages
2,837
Location
Łódź, Poland
Correct me if I'm wrong, but I assume that a proposal without a sponsor doesn't count as rejected for the purposes of the rule below:

A rejection requires it to go to the Voting Phase in the first place.

If someone's proposal doesn't get a sponsor this session, one can still propose it again next session.
On Discord is written otherwise.
 

Stalker0

Baller Magnus
Joined
Dec 31, 2005
Messages
9,570
I think we should reconsider the policy on polls in the general forum. I think polls can still be a useful tools as people are crafting proposals and getting a toe in the water on what the community might like. they just won't have any "power" anymore except through teh voting phase.
 
Top Bottom