This meta question arises from the closure of my question. I am not going to try to reopen the question, because I am not a close/reopen button lover. Just let the question be part of the silent history of TeX.SE site. What I want to know are the guidelines of TeX.SE about the relations between accepatble questions and user opinions.
Please read first all the comments below the closed question and its answers before reading forwards. Thank you.
From the closed question, I find two general questions that I want to asked here.
The First Question
Queston 1: Are questions of "how to do something with some package" acceptable on this site, if the asker knows with 90% certainty some feature is not supported in some package?
For this queston, I think the answer is YES. In general, an asker gets the certainty of whether or not some feature is supported by searching in the web or in the documentation. Sometimes, there are undocumented features in some package (for example, some months ago, an user ever asked how to break from
\int_step_inline loop). Also, if the feature is really not supported, other users could still answer the question, providing some workarounds or hacks of the dirty code, which may be useful to the asker and others.
The Second Question
Queston 2: Are his/her questions acceptable on this site, if the asker believe the vote and bookmark numbers of every question are positively correlated to how many users need some feature of some package?
For this queston, I also think the answer is YES.
(1) On TeX.SE main site, users can not open polls. So every post is either question or answer, and "a disguised poll" is a meaningless statement.
(2) I will not change the above belief. So If the answer is NO, then all of my questions can be closed for this reason, which I think is ridiculous.
(3) My belief is for all questions, not only for my questions. For example, when writing my package, I sorted by votes all questions with
[tables] tag. And the first three questions are
819 votes: How to add a forced line break inside a table cell 421 votes: Column and row padding in tables 289 votes: How to create fixed width table columns with text raggedright/centered/raggedleft?
So I decided these features in tables are mostly wanted by users and implemented them in my package. Everyone has his/her right to disagree with me. But I don't think it is the proper reason to close my questions.
I will add two answers below as polls for these two questions. Please upvote or downvote them.