First off, hello everyone.
In case you're lost about this whole affair.
As you might know, in recent months we’ve had Roll Thread creation problems, in particular with timing, or what some might call “sniping” or “hogging” threads weeks, months, and sometimes years in advance. As a result, the FGO Roll thread request thread became a thing, along with the policy of needing an official NA announcement to request and make a thread. Though, with the recent thread discussion over the last couple of days, some big (somewhat contentious) questions became apparent. We had some suggestions from various users and that boiled down to needing a poll. I made an original proposal-based poll (which will be linked below) but that didn’t really encompass all options and conflated two main questions. In addition to that, it really should have been its own main thread for accessibility concerns and all.
We are currently trying to get a democratic authority-decision on the Roll Thread procedures for FGO GP. As you might know, we’ve had procedure problems for a while. From what I gather from @Flower_Hermit, we make and follow our own system, and Flower/mods will essentially only intervene whenever a user ignores it intentionally. We have two options to make, a poll for each below. (0) Whether to give the same user the opportunity of making part 1 and part 2 threads of an event (“Righ of Continuation”), and (1) whether we want a “calling thread” or “planned sign up” system.
Quick Note for why this is a genuine problem.
There’s reason to believe that if we simply go back to the anarchy system the continuation of thread sniping will simply continue. Thread sniping not only disrupts the community and event experience (by being off-time) but also takes the opportunity away from other less public users to get a piece of the pie and share their own excitement on the event story and servants. If we don’t have a system it is very possible that it will simply continue, but* this is up for discussion (below)!
Now, the initial question (0) is motivated by a conversation that led to this proposal by @Fall-Moon:
The follow-up question (1) is motivated by the same conversation leading to this proposal by @OwlCafe:
Now, this last one requires someone to keep a Wiki/document up-to-date but I did not ask both of these users before posting their proposal in this thread (sorry about that!) so it can be anyone who is willing to help really, ideally with a backup.
There are two polls here that will be open indefinitely, but, say 3-days from now I (and others) will all check on the results and will implement whichever option has the highest approval rate. Please read both proposals and the current system carefully before voting. (Conversations from the FGO Roll thread request thread also have context for why there are certain rules/methods in those proposals in case you’re wondering about any of them so it might be worth a quick skin-read.)
Roll Thread Decision Poll.
Question 0. Implement “Right of Continuation”? (Currently we don’t have this.)
- Yes, users may have the opportunity to do both Part 1 and Part 2 threads.
- No, users may not do any consecutive threads.
Question 1. Should we have “Planned sign ups” or “Calling threads” as they are announced? (Currently, it’s the latter system.)
- Planned sign up and ranked on Wiki post/document.
- As announced. First come, first served basis.
- Neither, something else. (Explain below)
You can find the original (and now null) poll post I made here. That one was conflating the two questions and this kind of poll needed better accessibility so I have redone it here as an independent thread.
Important Note copied from the previous poll I made.
“It should be known that I’m not a mod and don’t have any particular authority over this. This whole thing is mostly done as a community collective so I’d figure the best way to go about this was to get a democratic authority-decision from everyone on this. All FGO GP peeps are free to help and discuss things equally, we just gotta decide on something first.”
Hope I didn’t miss anything. That’s all!