- See the page history to retrieve old threads.
Tried to email you re IP Block Exemption
[edit]You requested IP block exemption, and it has been granted. Please note that the email address you provided with your request is listed as not valid. Should you wish to have IPBE extended, please send a brand new email with a current email account. Risker (talk) 01:23, 5 July 2024 (UTC)
Draft:Constrained minimum criterion
[edit]You seem to think that Draft:Constrained minimum criterion should be deleted because the topic does not seem to merit an inclusion in Wikipedia, since the criterion seems too recently introduced. In other words, there is no need to develop this draft
. If you think that you should use the process at Wikipedia:Miscellany for deletion. If you do not want to do that, you could always ignore the draft, and if nobody edits it for six months it will get deleted anyway.
Attempting to turn the draft article into a redirect is the wrong thing to do.-- Toddy1 (talk) 12:37, 5 July 2024 (UTC)
- @Toddy1: It was actually already deleted before by G13. I requested it to be undeleted to see if the topic is notable or if the draft contains some materials that need to be merged into the existing articles. As it turned out, the topic seems to be too recent so it probably doesn’t pass the notability but the notion was already mentioned in an existing article so I simply redirected it to that article. In my opinion, the redirect is preferable since anyone who disagrees with my editorial judgement can undo the redirect and develops the draft. Also, if the draft is deleted, to revisit the notability question later, we need to undelete it first: undoing the redirect is simpler and thus is more productive. What do you think? —- Taku (talk) 13:16, 5 July 2024 (UTC)
- The logic that you are using would apply if you moved the draft into mainspace. But if you did that, it would be sensible to copy some sort of talk page discussion into the redirect-page's talk-page.
- But the logic you are using does not work in draft-space. This is because in draft-space, Draft:Constrained minimum criterion will be deleted if it goes for a 6-month period with no edits. If the thing is going to remain in draft-space, then it should stay as an article (not as a redirect intended to mask an article).
- Having redirects in draft-space works when you have two draft-space articles on identical subjects, and you merge them, and turn one into a redirect to the other. It is also works as a temporary thing when you move an draft from draft-space to main-space; but in that case, sooner or later, the draft-space redirect gets deleted.-- Toddy1 (talk) 16:56, 5 July 2024 (UTC)
- @Toddy1: Sorry but I don’t think I quite follow. For example, it’s actually quite common that a draft turns out to cover a topic that is already covered in mainspace articles. In that case, the best course of action is to merge the draft into the existing articles (and I do that a lot). The case of this draft is actually quite similar to such a case: the notion this draft is about is already mentioned in one mainspace article. It is a common and preferable practice to leave a redirect after the merger instead of deleting the article since it would be easier to undo the merger if needed afterward. The "logic" of leaving the redirect instead of deletion is exactly the same: my editorial judgment was the topic is not notable but if some other editor thought differently, it would be easier to undo the redirect, develop the draft and then move it to the mainspace. By the way, I am very familiar with G13 but it doesn’t mean we must use G13 to handle drafts; redirecting is fine too. —- Taku (talk) 17:12, 5 July 2024 (UTC)
- If you want the draft deleted, go through a deletion process.
- If you want the draft preserved but hidden behind a redirect, move the draft to mainspace immediately after changing it to a redirect.
- Or leave it as a draft article, and see what happens.
- -- Toddy1 (talk) 19:16, 6 July 2024 (UTC)
- @Toddy1: Or just leave the redirect. Basically, you seem to think that is not an opinion, but it is an opinion since for example we leave a redirect when we merge drafts into the existing articles. I am not going to insist (not too important for me) but I just want to point out that a redirect is an option in addition to G13. —- Taku (talk) 19:45, 6 July 2024 (UTC)
- @Toddy1: So, do you still believe a redirect cannot be an option? (It’s just that from your non-response response, I cannot tell if you actually read and understand what I wrote above). —- Taku (talk) 08:00, 8 July 2024 (UTC)
- Yes I read it. But it does not make sense. And your following it up with the 8 July message suggests that this is important to you, even though on 6 July you said the opposite. That does not make sense either. If you do not want to develop the draft into an article, then please just leave it as a draft and maybe someone else will. -- Toddy1 (talk) 15:14, 8 July 2024 (UTC)
- @Toddy1: I don’t understand why you respond with non-repose again. I asked "do you still believe a redirect cannot be an option?" You can say yes or no and preferably with some reasoning. Like I said, a draft in question isn’t too important for me but I would like to know why you think what you think. I am quite active on the draftspace. So, what is important for me is to know what other editors think about the draftspace. That’s why I was interested in knowing why you insist on G13 instead of a redirect. At least, I explained why leaving a redirect is preferable in some instances; if you think it didn’t make sense, again you can tell why, that’s a response. Taku (talk) 17:27, 8 July 2024 (UTC)
- If the draft article is left as a draft article, a number of things may happen:
- Someone will read it and find it useful.
- Someone will improve it.
- Nobody will do anything, and eventually it will get deleted.
- If the draft article is left as a draft article, a number of things may happen:
- @Toddy1: I don’t understand why you respond with non-repose again. I asked "do you still believe a redirect cannot be an option?" You can say yes or no and preferably with some reasoning. Like I said, a draft in question isn’t too important for me but I would like to know why you think what you think. I am quite active on the draftspace. So, what is important for me is to know what other editors think about the draftspace. That’s why I was interested in knowing why you insist on G13 instead of a redirect. At least, I explained why leaving a redirect is preferable in some instances; if you think it didn’t make sense, again you can tell why, that’s a response. Taku (talk) 17:27, 8 July 2024 (UTC)
- Yes I read it. But it does not make sense. And your following it up with the 8 July message suggests that this is important to you, even though on 6 July you said the opposite. That does not make sense either. If you do not want to develop the draft into an article, then please just leave it as a draft and maybe someone else will. -- Toddy1 (talk) 15:14, 8 July 2024 (UTC)
- @Toddy1: Sorry but I don’t think I quite follow. For example, it’s actually quite common that a draft turns out to cover a topic that is already covered in mainspace articles. In that case, the best course of action is to merge the draft into the existing articles (and I do that a lot). The case of this draft is actually quite similar to such a case: the notion this draft is about is already mentioned in one mainspace article. It is a common and preferable practice to leave a redirect after the merger instead of deleting the article since it would be easier to undo the merger if needed afterward. The "logic" of leaving the redirect instead of deletion is exactly the same: my editorial judgment was the topic is not notable but if some other editor thought differently, it would be easier to undo the redirect, develop the draft and then move it to the mainspace. By the way, I am very familiar with G13 but it doesn’t mean we must use G13 to handle drafts; redirecting is fine too. —- Taku (talk) 17:12, 5 July 2024 (UTC)
- There is no valid reason to turn the draft into a redirect. And if it were turned into a redirect, it would be appropriate to delete the redirect after 6 months. The policy at WP:RDRAFT is not applicable, since the draft has not been moved to mainspace.-- Toddy1 (talk) 22:46, 8 July 2024 (UTC)
- @Toddy1: Thank you for the reply. I would say the logic doesn’t apply some instances. Besides the merger case mentioned above, another would be a case when a draft is a duplicate of an existing one in the mainspace; in that case, it is a common and preferable to redirect the draft. Just to confirm, you do agree there are some instances when redirecting is appropriate, right? You said “ There is no valid reason to turn the draft into a redirect. And if it were turned into a redirect, it would be appropriate to delete the redirect after 6 months”. This is plainly false. There is no such policy and is contrary to standard practices in the draftspace. —- Taku (talk) 10:12, 9 July 2024 (UTC)
- We do not agree. User talk:Arjayay#Draft:Constrained minimum criterion shows that I am not the only person to disagree with you on this point. There is no value to Wikipedia in continuing this conversation. There comes a point in every debate where the debate itself has come to a natural end. -- Toddy1 (talk) 17:42, 9 July 2024 (UTC)
- @Toddy1: Good. You finally answered my question. You are wrong (there is no prohibition on redirects as you seem to believe) but I agree we don’t need to continue the conversation. —- Taku (talk) 19:27, 9 July 2024 (UTC)
- We do not agree. User talk:Arjayay#Draft:Constrained minimum criterion shows that I am not the only person to disagree with you on this point. There is no value to Wikipedia in continuing this conversation. There comes a point in every debate where the debate itself has come to a natural end. -- Toddy1 (talk) 17:42, 9 July 2024 (UTC)
- @Toddy1: Thank you for the reply. I would say the logic doesn’t apply some instances. Besides the merger case mentioned above, another would be a case when a draft is a duplicate of an existing one in the mainspace; in that case, it is a common and preferable to redirect the draft. Just to confirm, you do agree there are some instances when redirecting is appropriate, right? You said “ There is no valid reason to turn the draft into a redirect. And if it were turned into a redirect, it would be appropriate to delete the redirect after 6 months”. This is plainly false. There is no such policy and is contrary to standard practices in the draftspace. —- Taku (talk) 10:12, 9 July 2024 (UTC)
- There is no valid reason to turn the draft into a redirect. And if it were turned into a redirect, it would be appropriate to delete the redirect after 6 months. The policy at WP:RDRAFT is not applicable, since the draft has not been moved to mainspace.-- Toddy1 (talk) 22:46, 8 July 2024 (UTC)
Merging
[edit]Just a reminder that when proposing a merge, the justification goes on the talk page of the preferred target (not in the edit summary). That way, people can respond to your comment and hence allow a discussion. See Step 1 in WP:MERGEPROP. For the relevant merge, I've started on for you at Talk:Riesz's lemma. Klbrain (talk) 05:31, 3 August 2024 (UTC)
- @Klbrain: I don’t think it’s necessary mandatory. Sometimes the rationale for the merger is clear enough and the discussion is not needed. In fact, you can just go ahead and do the merger without putting a merger tag. Putting a merger tag and if no one opposes to it after several days passed, that would be a good enough indication that there is no opposition. (Unlike an afd, you don’t need sufficient support votes to do merger.) —- Taku (talk) 06:33, 3 August 2024 (UTC)
- I absolutely agree that discussion isn't always needed; the issue is that you recognised the need for an argument (hence in the edit summary), but put it a non-standard location. It was also in one edit summary, but not the other. If the case for a merge is clear (that two pages are clearly about the same subject), then I agree that a case isn't needed. I didn't think that this was the case here, as there are many theorms or lemmas named after people that look similar, but in fact are distinct. While I've done some maths in the past, it wasn't obvious to me, and therefore I suspect to many other readers. Klbrain (talk) 07:36, 3 August 2024 (UTC)
- @Klbrain: when you put a cleanup tag, it is often enough to put a reason in the edit summary since the expectation is that other editors would be reading edit summaries. I don’t think a merger tag is much different. Of course, it really depends on cases, though. —- Taku (talk) 08:35, 3 August 2024 (UTC)
- I absolutely agree that discussion isn't always needed; the issue is that you recognised the need for an argument (hence in the edit summary), but put it a non-standard location. It was also in one edit summary, but not the other. If the case for a merge is clear (that two pages are clearly about the same subject), then I agree that a case isn't needed. I didn't think that this was the case here, as there are many theorms or lemmas named after people that look similar, but in fact are distinct. While I've done some maths in the past, it wasn't obvious to me, and therefore I suspect to many other readers. Klbrain (talk) 07:36, 3 August 2024 (UTC)