12

Is there a way to block a proposal, essentially launching a counter vote to not add another topic?

Laravel for instance has their main documentation at /laravel, a second one for a minor version and is now voting to bring in yet another minor version.

The original documentation spans from 5.0 to 5.3. I tried extending some topics to include 5.4. However, my changes were repeatedly denied (all I wanted to change was the version that is noted at the top of each topic for example, this one has 5.0-5.3 when it should be up to 5.4. I digress).

Is there a way to counter vote as it isn't good to spread the documentation so far and wide? Along with that, can you burninate topics or is that just tags?

6
  • 2
    If I'm not mistaken all the minor version should be rolled into the main tag and you just use versioning on the examples to show the differences. I believe CM's have merged theses on other tags. Commented Apr 27, 2017 at 12:15
  • Hi @NathanOliver, I'm not too used to the meta side of SO, how would you go about starting that process? And yes you are correct they should be all rolled into one. Commented Apr 27, 2017 at 12:18
  • The meta post should start the process. Might need a mod flag but I'm not 100% certain. Commented Apr 27, 2017 at 12:18
  • See also the Bash, sh, shell, command-line and command-line-interface mess. Commented Apr 27, 2017 at 15:43
  • 1
    @JonEricson This is nowhere near status-completed. The question asks about countering a Docs proposal that happens to be about Laravel, while all that's done so far is merging laravel-version tags into laravel. Commented Apr 27, 2017 at 18:48
  • @dorukayhan: Correct. That's why I closed it as a duplicate of the other question which is still open. As far as I know, the immediate support portion of the question is complete. Commented Apr 27, 2017 at 19:25

1 Answer 1

Reset to default
2

I already merged a bunch of Laravel tags. Today, I merged and into . (Please go over the topics in Laravel to make sure they are all needed and there aren't duplicate topics.) I also merged in under the assumption that it will eventually get enough questions for people to start proposing it.

Did I miss any?

2
  • Nope they look good, however you bring up an interesting point as Laravel 4 is completely different to Laravel 5, I would say 4 should have it's own docs, hopefully there won't be enough questions to warrant it due to being superseded by 5. Commented Apr 27, 2017 at 18:45
  • 1
    I don't really know the difference between various versions of Laravel. However, Docs is designed to handle divergent versions such as Python 3.x and 2.x. Commented Apr 27, 2017 at 19:28

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.