3 replaced http://meta.english.stackexchange.com/ with https://english.meta.stackexchange.com/
source | link
2 replaced http://meta.english.stackexchange.com/ with https://english.meta.stackexchange.com/
source | link

Aside from the relevant place to track these discussionstrack these discussions, I believe we should decide the appropriate path for reaching a decision about a particular standard. Community run projects tend to get stuck debating; I want to avoid that.

Is there a solid SE path for adopting decisions that require input from the community? As in, something like this:

  1. Acknowledge a problem
  2. Propose solutions
  3. Vote on solutions
  4. Acknowledge a solution
  5. Propose migrations to solution
  6. Vote on migrations to solution
  7. Choose migration path
  8. Post a final summary somewhere people can find it

For something like a style guide, this could translate as such:

  1. Acknowledge a target for the style guide (i.e. block quoting)
  2. Propose solutions (i.e. > or codeblocks)
  3. Vote on solutions
  4. Acknowledge a solution
  5. Propose migrations to solution (i.e. this style should be enforced; or this style is merely a suggestion; or edit only if other edits are necessary)
  6. Vote on migrations to solution
  7. Choose migration path
  8. Post a final summary somewhere people can find it (i.e. update an "official" style guide and update all meta posts to point toward the resolution)

This is just a shot from the top of my head so please pick it apart. The goal here is to give us some way to bring resolution to some of these tough to resolve issues.

Aside from the relevant place to track these discussions, I believe we should decide the appropriate path for reaching a decision about a particular standard. Community run projects tend to get stuck debating; I want to avoid that.

Is there a solid SE path for adopting decisions that require input from the community? As in, something like this:

  1. Acknowledge a problem
  2. Propose solutions
  3. Vote on solutions
  4. Acknowledge a solution
  5. Propose migrations to solution
  6. Vote on migrations to solution
  7. Choose migration path
  8. Post a final summary somewhere people can find it

For something like a style guide, this could translate as such:

  1. Acknowledge a target for the style guide (i.e. block quoting)
  2. Propose solutions (i.e. > or codeblocks)
  3. Vote on solutions
  4. Acknowledge a solution
  5. Propose migrations to solution (i.e. this style should be enforced; or this style is merely a suggestion; or edit only if other edits are necessary)
  6. Vote on migrations to solution
  7. Choose migration path
  8. Post a final summary somewhere people can find it (i.e. update an "official" style guide and update all meta posts to point toward the resolution)

This is just a shot from the top of my head so please pick it apart. The goal here is to give us some way to bring resolution to some of these tough to resolve issues.

Aside from the relevant place to track these discussions, I believe we should decide the appropriate path for reaching a decision about a particular standard. Community run projects tend to get stuck debating; I want to avoid that.

Is there a solid SE path for adopting decisions that require input from the community? As in, something like this:

  1. Acknowledge a problem
  2. Propose solutions
  3. Vote on solutions
  4. Acknowledge a solution
  5. Propose migrations to solution
  6. Vote on migrations to solution
  7. Choose migration path
  8. Post a final summary somewhere people can find it

For something like a style guide, this could translate as such:

  1. Acknowledge a target for the style guide (i.e. block quoting)
  2. Propose solutions (i.e. > or codeblocks)
  3. Vote on solutions
  4. Acknowledge a solution
  5. Propose migrations to solution (i.e. this style should be enforced; or this style is merely a suggestion; or edit only if other edits are necessary)
  6. Vote on migrations to solution
  7. Choose migration path
  8. Post a final summary somewhere people can find it (i.e. update an "official" style guide and update all meta posts to point toward the resolution)

This is just a shot from the top of my head so please pick it apart. The goal here is to give us some way to bring resolution to some of these tough to resolve issues.

1
source | link

Path for adopting EL&U formatting standards

Aside from the relevant place to track these discussions, I believe we should decide the appropriate path for reaching a decision about a particular standard. Community run projects tend to get stuck debating; I want to avoid that.

Is there a solid SE path for adopting decisions that require input from the community? As in, something like this:

  1. Acknowledge a problem
  2. Propose solutions
  3. Vote on solutions
  4. Acknowledge a solution
  5. Propose migrations to solution
  6. Vote on migrations to solution
  7. Choose migration path
  8. Post a final summary somewhere people can find it

For something like a style guide, this could translate as such:

  1. Acknowledge a target for the style guide (i.e. block quoting)
  2. Propose solutions (i.e. > or codeblocks)
  3. Vote on solutions
  4. Acknowledge a solution
  5. Propose migrations to solution (i.e. this style should be enforced; or this style is merely a suggestion; or edit only if other edits are necessary)
  6. Vote on migrations to solution
  7. Choose migration path
  8. Post a final summary somewhere people can find it (i.e. update an "official" style guide and update all meta posts to point toward the resolution)

This is just a shot from the top of my head so please pick it apart. The goal here is to give us some way to bring resolution to some of these tough to resolve issues.