Wikinews:Water cooler/policy

Latest comment: 1 day ago by Me Da Wikipedian in topic Feedback on Pre-Review process

Page last updated: Wednesday 19 at 1431 UTC     

Refresh Refresh this page  

Archive


Policies and guidelines and the Style guide contain or link to most of the current en.Wikinews policies and guidelines, however policy is based on the accepted practices of the day on Wikinews, often these might not be written down. This section of the Water cooler focuses on discussions regarding policy issues.

You may wish to check the archives to see if a subject has been raised previously.


Update of license

edit


This conversation has been marked for the community's attention. Please remove the {{flag}} when the discussion is complete or no longer important.


Some time ago there was a discussion on meta about how to implement the license update to CC BY-SA 4.0 on all wikis. See m:Meta:Babel/Archives/2023-06#Aftermath_of_ToU_updates.

Wikinews use the license CC BY 2.5. So it does not have the SA part and it is an older version.

I would like to ask why Wikinews does not follow WMF and most other wiki projects. Is there a good reason or is it simply because noone thought about updating the license?

Unless there is a good reason I suggest to update the license to follow WMF. --MGA73 (talk) 16:05, 9 November 2023 (UTC)Reply

The goal was that Wikinews would be easy to share. That hasn't really happened, but that's the idea. :/ —Justin (koavf)TCM 16:07, 9 November 2023 (UTC)Reply
Thank you, that makes sense because CC BY is less restrictive than CC BY-SA. However with the update of the Terms of Use users agree to license their contributions as CC BY-SA 4.0. So I think that at least all new content should be licensed under that license because I do not think that it is possible just to remove the "SA".
If the license do not make it easier to share then I do not think there are any good arguments to keep the less restrictive license for older text. Anyway if someone have allready legally shared the text they can continue to do so even if the license is changed so it should not give any problems to change license for older text too. --MGA73 (talk) 14:54, 10 November 2023 (UTC)Reply
But, "The only exception [to using CC BY-SA 4.0 or GFDL] is if the Project edition or feature requires a different license. In that case, you agree to license any text you contribute under the particular license prescribed by the Project edition or the feature." I'm struggling to see why we would voluntarily take on that load of work...to make it harder for people to reuse our content, as we want them to. Heavy Water (talk) 17:02, 10 November 2023 (UTC)Reply
Beause the mission of the wiki-family is to make knowledge free for everyone and make sure knowledge stays free. Wikipedia uses CC BY-SA 4.0 and that does not seems to be a problem. Wikipedia have grown and is one of the worlds most used websites.
One of the exceptions I know of is wikidata where the data is CC0. Then there is also fair use in some cases but that is not valid for wikimedians to use on own work only for work created by other. I do not know of any other exceptions and reasons.
I wonder if there are any known examples where someone said they would no re-use wikinews if the license was BY-SA instead of BY. Anyone have examples? --MGA73 (talk) 08:48, 11 November 2023 (UTC)Reply
Very unlikely, as Wikinews is very obscure. There have been times about 15 years ago when I saw Wikinews reproduced in the wild, but it's not common today, for sure. —Justin (koavf)TCM 20:43, 11 November 2023 (UTC)Reply
To me that sounds like there is no longer any real problem using BY-SA. Another question not yet discussed is why use 2.5 instead of 4.0. --MGA73 (talk) 15:40, 1 December 2023 (UTC)Reply
Agreed. I don't see any reason for us to use a different license than the other WMF projects and would support a change. I don't feel strongly enough that I would oppose the status quo, tho. —Justin (koavf)TCM 16:02, 1 December 2023 (UTC)Reply

┌─────────────────────────────────┘
So how to move forward? Should there be a formal vote? --MGA73 (talk) 11:54, 14 December 2023 (UTC)Reply

I vote yes to a vote. —Justin (koavf)TCM 12:12, 14 December 2023 (UTC)Reply
Thank you User:Koavf. I'm not very familiar with wikinews so I'm not sure how to do this. But I think I have to go to Wikinews:Polls and add a link to Wikinews:Update license poll and then make a suggestion at that page. Is that correct? If you would like to assist you are very welcome to make the proposal. --MGA73 (talk) 12:52, 14 December 2023 (UTC)Reply
I think just posting here would be sufficient, because as you can see, that page hasn't been edited in almost 15 years: https://en.wikinews.org/w/index.php?title=Wikinews:Polls&action=historyJustin (koavf)TCM 12:58, 14 December 2023 (UTC)Reply
User:Koavf, Okay I have prepared the poll below. I will add {{poll}} soon but perhaps you could have a look at it first? Is anything missing? --MGA73 (talk) 19:25, 14 December 2023 (UTC)Reply
Not from my perspective. Thanks. —Justin (koavf)TCM 19:42, 14 December 2023 (UTC)Reply


 
This is an open poll listed on the Water cooler and Wikinews:Polls. Please remove the {{poll}} flag when the poll closes.

Please discuss your poll ideas with the community before polling, and don't vote on everything as voting is evil.


Wikinews should follow the official license in wmf:Policy:Terms_of_Use (currently cc-by-sa-4.0)

edit
  1. Weak support It makes sense to be consistent and these terms on CC licenses have really improved and clarified them from v. 2.5 to today. —Justin (koavf)TCM 20:44, 14 December 2023 (UTC)Reply
  2. Weak support I can see the limitations of ShareAlike, but I think greater interoperability with other wiki projects is more important. As said above, the modern Creative Commons licenses are much better than the pretty ancient version we're currently using. Ash Thawley (talk) (calendar) 05:27, 29 January 2024 (UTC)Reply

Wikinews should keep the current license (cc-by-2.5)

edit
  1. keep the current license - a few of our articles got translated into other languages, and if we would be the only WN project to make the switch, that would kill the translation process. CC licenses are, as far as I know, forward-compatible (a translation of a 2.5 article could be published under 4.0), but not backwards-compatible (a translation of a 4.0 article could not be published under 2.5). (Sidenote: English is usually a source language on WN, but not the other way around because of en.wn's review process and its requirement to check all sources.) As Justin have said, our work had not been reused much lately, but SA would make that even harder. I would be happy to reconsider to transition from CC.BY 2.5 to CC-BY 4.0, if the vote would be simultaneous on all WN projects. - Xbspiro (talk) 12:12, 15 December 2023 (UTC)Reply
And I would advocate for using a separate license for spoken articles. I have raised that issue a while back during a Community Feedback period, but did not attract much attention. - Xbspiro (talk) 12:19, 15 December 2023 (UTC) Reply
  1. I said above, "I'm struggling to see why we would voluntarily take on that load of work [of migration]...to make it harder for people to reuse our content, as we want them to." Experienced Wikinewsies have repeatedly, over the years, defended the greater freedom offered by not imposing the SA restriction. Xbspiro makes a good point about translation, too. (I really don't care what license non-Wikinews projects use.) I'd welcome a discussion to study the idea of migration to CC BY 4.0. Heavy Water (talk) 15:56, 15 December 2023 (UTC)Reply
    I agree with your suggestion of 'studying the idea of migration.' One of things I'd like to better-understand before casting a vote is what can we glean from existing data, in order to understand the scope of any migration. Based on Xbspiro's point above regarding English as a source language, I've tried looking at Wikidata to see if any useful data can be had there. There may be better/existing ways to look at this data and I'm all ears if anyone can provide exmaples. Otherwise, I've started this page: Michael.C.Wright/TranslationAnalysis. Any and all thoughts are welcome. Michael.C.Wright (Talk/Published) 18:13, 8 February 2024 (UTC)Reply
  2. It is obvious that WMF is clueless about Wikinews, they barely have an idea about how Wikipedia functions. Using a more restrictive license, as all SA CC licenses are, makes any usage of Wikinews information more challenging. --Base (talk) 13:35, 16 December 2023 (UTC)Reply

New option: Wikinews should keep the BY but update to newest version (currently cc-by-4-0)

edit
  1. I support an upgrade to 4.0. As I mentioned below using two different licenses for various content; SA for internal tools, scripts, templates, etc and non-SA for article content might be a good compromise that allows us to duplicate Wikipedia tools, scripts, templates, etc. Otherwise, if we are limited to only one, I agree with Heavy Water that the least-restrictive option is the best. We also need to ensure that the other language projects upgrade to a compatible license to allow for translations. The number of English articles that get translated is significant.[1] Previously unsigned comment by Michael.C.Wright (Talk/Published) 20:50, 24 February 2024‎ (UTC)[2]Reply
  2.   Support All versions of BY should be supported and CC evolution should not be frozen in the ancient 2.5. version. Share-Alike (SA) should NOT be implemented as it causes obstacles in spreading information whether the main goal is to spread news maximally with minimum obstacles (just attribution, no extra efforts). --Ssr (talk)
  3. (прошу прощения за русский язык) я активный автор в разделе викиновостей на эсперанто. Считаю что переходн на cc-by-4.0 давно необходим. Я считаю не возможным переход на cc-by-sa-4.0 в связи с тем, что все предыдущие материалы викиновостей были опубликованы под лицензией cc-by-2.5, которая НЕ использует «Attribution-ShareAlike». VladimirPF (talk) 06:28, 28 May 2024 (UTC)Reply
    1. Translating @VladimirPF's   Support vote: "(sorry for using Russian) I am an active contributor to Wikinews in Esperanto. I think that the transition to cc-by-4.0 has long been necessary. I believe it is not possible to migrate to cc-by-sa-4.0 due to the fact that all previous Wikinews materials were published under the cc-by-2.5 license, which does NOT use Attribution-ShareAlike."
      @VladimirPF, я перевел ваши сообщения на английский. A.S. Thawley (talk) (calendar) 18:15, 2 June 2024 (UTC)Reply
  4.   Support. A.S. Thawley (talk) (calendar) 03:10, 3 June 2024 (UTC)Reply
  5.   Support – Of course, we'd be agreeing to either waive or not assert our own moral rights to the extent that the license allows. Nonetheless, a move to CC-BY 4.0 is long overdue, and we can't rescind the current license that we agreed to use in the first place, especially for older content. —George Ho (talk) 10:14, 16 June 2024 (UTC)Reply

Comments

edit
  • "And I would advocate for using a separate license for spoken articles."
    Why is this, Xbspiro? And which license? —Justin (koavf)TCM 12:28, 15 December 2023 (UTC)Reply
    Thanks for asking. The possibility of voice sampling bothers me a lot - CC licenses simply do not forbid that, but I can't name any licenses which would make me happy in this regard. Call me naïve, because a license will not keep bad actors back, but imagine a court proceeding where the sampler could argue that you have allowed your voice to be used for whatever purposes. Please, feel free to tell me, if you think this is not a valid point - even that would be better than no feedback at all. - Xbspiro (talk) 05:52, 16 December 2023 (UTC)Reply
    As long as it is a legal purpose then I think it would be hard to avoid. However the license require that reuser should "indicate if changes were made" so it would be clear that the voice was sampled to say something else. If the license is BY-SA then whatever they use it for should also be license BY-SA (which you think makes reuse harder). --MGA73 (talk) 21:26, 17 December 2023 (UTC)Reply
  • "if we would be the only WN project to make the switch". (Xbspiro)
I have made notes on some of the other WN projects too about license update. I can make a notice on all projects so all projects follow the latest license. --MGA73 (talk) 12:59, 15 December 2023 (UTC)Reply
All notified. At least those not closed. --MGA73 (talk) 13:51, 15 December 2023 (UTC)Reply
Thank you for the notification. We can proceed with a simultaneous transition in all languages for the entire project, ensuring consistency and applying the upgraded license uniformly across all language communities. Kitabc12345 (talk) 10:43, 25 December 2023 (UTC)Reply
  • Is this a straw poll? The poll system was only used, as far as I know, very early in en.wn's existence. I don't think it is consistent with modern project principles whereby decisions are reached by consensus rather than simple voting — experienced Wikinewsies' votes are given more weight (or others' aren't counted), because they have knowledge of the project and an accumulated reputation. Separately, I'm concerned about the "Yes" section title; I think it may mislead folks who haven't read the discussion above that precipitated this into thinking the Terms of Use require or at all encourage projects to use CC BY-SA 4.0. I'm not seeing either in the Terms of Use. How about "Yes, Wikinews should follow the typical license for Wikimedia projects, as defined by wmf:Policy:Terms_of_Use (currently cc-by-sa-4.0)"? The "No" section title would also read better with "should" before "keep". Heavy Water (talk) 15:56, 15 December 2023 (UTC)Reply
A vote is one way to find out if there is concensus or not. If 8 says yes and 2 says no then there is concensus. It would be a problem if the votes are 6 against 5 but if 6 prefer to change and 5 does not is it still not better to go with what most users prefer?
As for wmf:Policy:Terms_of_Use#7._Licensing_of_Content it says "When you submit text to which you hold the copyright, you agree to license it under: Creative Commons Attribution-ShareAlike 4.0 International License ("CC BY-SA 4.0"), ..." How can you read it any other way than CC BY-SA 4.0 is the preferred license?
As for the wording "should" I'm not a native English speaker so I do not see how it makes a difference if the word "should" is included or not. But if it is correct to write "Yes, Wikinews should..." and "No, Wikinews should..." then I do not mind.
As I understand your comment perhaps there should be one more option like "Update to CC BY 4.0" (not sure how that would fit in Yes/No). Do you have a suggestion? --MGA73 (talk) 21:14, 15 December 2023 (UTC)Reply
I asked on wmf:Policy_talk:Terms_of_Use#Does_ToU_require_that_Wikiprojects_update_license? and it was stated that ToU does not force a project to change license. --MGA73 (talk) 09:49, 17 December 2023 (UTC)Reply
Yeah, a vote can find out if there's consensus. But, for the example you gave, at en.wn it might vary based on who the users were, even if it was an 8–2 vote.
I figured that was what the ToU meant. Heavy Water (talk) 19:16, 18 December 2023 (UTC)Reply
  • I learnt about this discussion from the Water Cooler on Chinese Wikinews. The Chinese Wikinews community has discussed on the same matter a few months ago. Xbspiro's concern above is also one of the concern raised in our discussion. The Chinese Wikinews community generally supports to update the licence to CC-BY-SA 4.0 on condition that other Wikinews languages also follow as this enables translation and utilisation of contents from other Wikimedia projects. It seems not making much sense if only one or two Wikinews language editions update the licence while the others remain at CC-BY. --Waihorace (talk) 03:56, 16 December 2023 (UTC)Reply
  • Could somebody explain the benefits of switching 2.5 two 4 except the poor fact, that 4 > 2.5? --A1 (talk) 20:15, 16 December 2023 (UTC)Reply
A1 sadly no. But I can give it a try based on the links in https://wiki.creativecommons.org/wiki/License_Versions#License_Versioning_History under "Explanation of changes from prior version".
3.0 fixed some issues related to TPM / encryption and compability with MIT-licenses etc. Not sure how relevant that is for Wikinews.
But Internationalization seems more relevant as the new version "utilize the language of the international intellectual property treaties, in place of the language of US copyright law". Also there is a better coverage for Moral Rights.
BY-SA is more compatible with other licenses now.
4.0 is said to be even more global.
It should also be better to handle "Rights outside the scope of copyright".
It implement a "Common-sense attribution" that is better suited to reflect accepted practices (for example using a link) and also a "30-day window to correct license violations". It makes it harder for those that uses a tiny mistake to sue someone for copyright violation.
It also claims to have "Increased readability".
If anyone have a better reason you are very welcome to share it. --MGA73 (talk) 10:18, 17 December 2023 (UTC)Reply
  •   Comment I reworded the options as suggested and added a new option. I hope it is more clear now. Those that have allready woted are of courese welcome to move the vote if they prefer another option. --MGA73 (talk) 10:27, 17 December 2023 (UTC)Reply
    I support this. Updates are necessary because many new projects are now released in version 4.0. However, with Wikinews still on version 2.5, it becomes difficult to publish content from version 4.0 on the older version, causing some inconvenience to the Chinese wikinews community. Kitabc12345 (talk) 01:11, 25 December 2023 (UTC)Reply
    Kitabc12345 As I understand it the Chinese Wikinews will change to 4.0 if English Wikinews does. My guess is that other language versions would also be willing to change too. --MGA73 (talk) 09:59, 25 December 2023 (UTC)Reply
    Basically, only English, Russian, French, Japanese, Italian, Polish, Portuguese, Spanish, Chinese, German, Czech, Dutch, Swedish, Arabic, Serbian, Hebrew, and Esperanto are active communities. We have found that many news media outlets, although they publish under a free license, use the newer CC-BY-4.0 version, while our website operates on the older CC-BY-2.5 version. Consequently, we are unable to replicate their textual content under the newer CC-BY-4.0 license on our older CC-BY-2.5 website. Therefore, I am recommended to upgrade our license to the CC-BY-4.0 version. I agree to support the simultaneous upgrade to CC-BY-4.0 for other language versions, including the Chinese community. Insufficient local technical support personnel often lead us to rely on copying various Wiki templates, including countdown templates, from Wikipedia. We currently lack the knowledge and ability to create these templates independently without duplicating content from Wikipedia. Consequently, we are considering upgrading our license to align with other projects. However, this presents a significant dilemma as we frequently come across content that would be more beneficial to reproduce directly. However, Personally, I strongly support the direct upgrade of WikiNews' license to an independent one CC BY 4.0, not SA. This would preserve its distinct identity as a platform for original news content and prevent its assimilation with Wikipedia. Kitabc12345 (talk) 10:18, 25 December 2023 (UTC)Reply
    It seems that only we participate in this vote... What should we do to make this project improve the copyright in this 4.0 agreement, because there is a practical need. Kitabc12345 (talk) 01:59, 28 December 2023 (UTC)Reply
    Is there no consensus? Or is the discussion not active?… Kitabc12345 (talk) 13:42, 1 January 2024 (UTC)Reply
    So far only 4 users voted above. 3 thinks we should not upgrade to cc-by-sa-4.0. 1 would probably be willing to upgrade to cc-by-4.0 but it is not clear if the 2 others would accept cc-by-4.0. It would make things more clear if Xbspiro and Base would like to comment on the option to upgrade to cc-by-4.0 (but skip the SA).
    Some from other language versions would like to make sure that all language versions use the same version so they would only like to upgrade if it is a joined upgrade. Personally I think an upgrade is a good idea but I'm not really active except for trying to clean up files so I have not put a vote. --MGA73 (talk) 15:33, 1 January 2024 (UTC)Reply
    I hope everyone will be active in the discussion. Kitabc12345 (talk) 11:59, 3 January 2024 (UTC)Reply
However, Personally, I strongly support the direct upgrade of WikiNews' license to an independent one CC BY 4.0, not SA. This would preserve its distinct identity as a platform for original news content and prevent its assimilation with Wikipedia.
@Kitabc12345, I would like to hear more about this. What do you mean by 'assimilate?'
Wikipedia already performs a form of news service. Case in point: 2024 Kansas City Parade Shooting. Because of Wikipedia's editing process i.e., no review process, they can be more nimble and reactive than Wikinews. I'm not saying that is better—it's just the reality. In that way, I see Wikipedia already exceeding the abilities of Wikinews in providing timely and relevant news to readers (accuracy and bias notwithstanding). Based on that, I don't see a reason for Wikipedians to want to assimilate Wikinews. They already replace its news-providing function for their readers.
Aside from that, how does Wikinews not implementing a ShareAlike (SA) provision protect it from assimilation by Wikipedia?
Michael.C.Wright (Talk/Published) 17:18, 17 February 2024 (UTC)Reply
Suppose we are Wikinews; if the content of Wikinews were the same as Wikipedia's, would it still retain any unique characteristics? Kitabc12345 (talk) 08:15, 18 February 2024 (UTC)Reply
In the Chinese Wikinews community, some new users tend to directly republish articles from Wikipedia, which is inappropriate and leads to a loss of uniqueness for Wikinews. Due to differing copyright licenses, replicating content from Wikipedia on Wikinews is a violation of copyright, and such behavior is immediately prevented. Furthermore, Wikinews is subjected to a review process that typically ensures greater accuracy than Wikipedia. By this, I mean that while Creative Commons Share-Alike (CC-SA) might technically aid Wikinews in copying certain templates from Wikipedia and the like, it's not advisable for Wikinews to repurpose Wikipedia's content. Wikinews is capable of independently developing its own distinctive content over the years, thereby establishing a clear distinction from Wikipedia. If readers cannot obtain information on our Wikinews website that is not written on Wikipedia, then it is almost meaningless and devoid of any news value or relevance to the purpose of the Wikinews project. Kitabc12345 (talk) 08:22, 18 February 2024 (UTC)Reply
Your point is that by incorporating the SA provision, Wikinews would enable content duplication from Wikipedia. And that would eventually lead to Wikinews being assimilated by the larger Wikipedia because it essentially becomes the same content. It's an interesting point and an unintended consequence that warrants concern. There are though a number of key differences between the two platforms that are largely incompatible. For example, WP:AGF vs WN:Never_assume or WP:SYNTH vs WN:SYNTH. I would hope that those subtle and not-so-subtle differences would maintain a unique culture between the two that protects against assimilation.
I also think it is important for Wikinews to be able to generate and maintain the backend of the platform, i.e., the tools, scripts, templates, etc. In its current state, I don't see that en.Wikinews has the resources for that. The ability to adapt, remix, and transform those tools from Wikipedia might help with that problem.
For me, an important question to answer is: Can we utilize one or even two different licenses in a way that allow us to both discourage article content duplication across the various sister platforms while allowing for simple translations and also facilitating sharing of tools, scripts, templates, etc.? That may be an effective compromise and would allow us to move forward with an upgrade.
I posed the same question below (trying to keep track of multiple, similar, discussion threads).
Michael.C.Wright (Talk/Published) 15:23, 20 February 2024 (UTC)Reply

  Question It has always annoyed me that Wikinews is not on the same license as our bigger sibling, Wikipedia. It has, among other things, had the effect of us having to rewrite simple tools, scripts, code for templates, etc. which have already been created on WP. Whenever I have suggested that is just stupid, I've been told, well, that's just the way it's always been. As I am not a lawyer, my question is, what happens to our archives if we change? Is 4.0 in any way less restrictive than 2.5? If yes, it seems to me that the writers of the past would have their rights infringed. If so, do we run a bot and put a notice of CC-BY-2.5 on all articles published before the date we implement the proposed change? (And keep in mind, there are a number of articles which have already been specifically tagged as PD, probably what we would call CC0-1.0 today. --SVTCobra 21:58, 11 January 2024 (UTC)Reply

I don't think there is any harm in upgrading the agreement. There seems to be no problem between Wikipedia's upgrade from 3.0 to 4.0? All content is automatically upgraded, because we did not switch the copyright license to other restrictions, but only adopted the updated protocol. On the contrary, upgrading to 4.0 for news actually has great benefits because many free projects (other news agency website projects) have adopted the CC B Y4.0 guidelines. We can't copy the content of those free projects, which is quite annoying. Kitabc12345 (talk) 16:15, 12 January 2024 (UTC)Reply
I am trying to remember, but was the SA part perhaps the reason Wikinews was different than Wikipedia in the first place? I don't know who set these things up in the way-way-back days. SVTCobra 20:34, 12 January 2024 (UTC)Reply
In the comments above it is mostly the SA that some is against. So I think there is a chance for concensus to update to 4.0 without the SA. But it would be nice if those that woted against the update would clarify if they are against both the SA and the 4.0. --MGA73 (talk) 13:04, 13 January 2024 (UTC)Reply
I think after upgrading to version 4.0, everyone will have the opportunity to strive for SA space. We can start by handling it this way first. Kitabc12345 (talk) 16:31, 13 January 2024 (UTC)Reply
I agree with SVTCobra regarding the ability to copy tools, etc from Wikipedia. Wikinews does not have the resources necessary to correct even nit-noid issues such as template loops.
  Question My understanding of the difference between SA and non-SA is that reproduced SA content must carry the SA terms forward. A question I have is; can CC-BY-4.0 content be reproduced with credit but fully protected? In other words, is CC-BY-4.0 a possible dead-end route for free material? If so, I would be more in favor of the SA restriction because it preserves free access to the information.
Lastly, an aside; I'm not saying this is a waste of time. However, I think our energy would be better used in figuring out how to improve the publication and reviewing process. I'm not sure that the version of copyright license currently in use is impacting that to a great extent (though I am open to being convinced otherwise). A lack of timely, relevant content is the antithesis of the project and what I think will be the eventual death of en.wikinews. The copyright version becomes irrelevant when there isn't material being copied.
Michael.C.Wright (Talk/Published) 15:31, 5 February 2024 (UTC)Reply
Not sure what you mean fully protected. But it is possible to use CC-BY-4.0 text in another text and have that new text copyrighted so that no one else can use the new text (for example a book). But the original text is still CC-BY-4.0 so it is always possible to go back and use the original text.
I agree that it is relevant to get new articles. Someone wrote earlier that some news sites use CC-BY-4.0 and because Wikinews uses an old version that prevent editors from using text from those news sites. So I would not say its a waste to upgrade to a newer version. --MGA73 (talk) 18:10, 6 February 2024 (UTC)Reply
@MGA73 Yes, copyrighted is what I meant by 'fully protected' and you answered my question. Thanks.
  Question Regarding the statement 'our work has not been shared much recently,' do we have any stats on that? Wikimedia Stats can show things such as trends in articles read, but that doesn't indicate content copied or shared.
@Heavy Water makes a very good point we shouldn't take on extra work to make it more difficult to share our content. But I don't see that we know that BY-SA has or will hinder sharing (related to my question in this same reply). Do we even have enough committed admins/editors/users to undertake the upgrade project?
@Xbspiro makes another good point that it needs to be an all-or-nothing upgrade for various different Wikinews languges if en.wikinews is generally a 'source language' for others. Do we have any stats or data on how much en.wn content is a source for other languages?
For me, a vote would hinge on the following:
1. Do we have the manpower needed to proceed with the upgrade?
2. Do we have data on shared content?
3. Can and will the other languages follow suit?
As it currently stands, I may have time to volunteer to help with the upgrade, if needed.
Michael.C.Wright (Talk/Published) 15:13, 7 February 2024 (UTC)Reply
Coincidentally, today I logged in to find that one of my articles pending review has been translated and published by fr.wikinews. I was pinged regarding the creation of a wikidata item. I checked all of my published articles and found 50% (7 of 14) had wikidata linking to other languages. And that number could be higher if other other editors don't ensure they link to existing wikidata. Maybe wikidata could give us better insight into how much English content is being used among other wikinews platforms. Michael.C.Wright (Talk/Published) 15:02, 8 February 2024 (UTC)Reply
@Michael.C.Wright. I do not think it will take very long to update the relevant places from CC-BY-2.5 to CC-BY-4.0 or CC-BY-SA-4.0 if you know how to do it. Perhaps 1 hour? If other language versions want to change too then of course that will take some time too. --MGA73 (talk) 16:33, 8 February 2024 (UTC)Reply
Articles from English Wikinews are rarely translated into other languages. In fact, I find it uncommon to see numerous news reports that are sourced from English Wikinews—only a minor portion indeed. I do not agree with the claim that one's own language serves as the origin language. For example, some news reports on English Wikinews come from translations of articles from Russian Wikinews. However, I am in favor of other language editions of Wikinews upgrading to CC BY 4.0, in line with the English Wikinews. Kitabc12345 (talk) 08:33, 18 February 2024 (UTC)Reply
(see picture)
 
From my understanding, which was derived from the middle right panel of this illustration, content under, e.g., a CC-BY license just can't be copyrighted. Heavy Water (talk) 17:20, 8 February 2024 (UTC)Reply
Do we have someone who knows how to do it? There could be as many as 4,600 articles in en.wikinews[3] that exist as another language. Those licenses will need to align. Do we know how to identify all of those articles, contact someone on that language.wikinews and get the necessary changes made? Michael.C.Wright (Talk/Published) 16:50, 16 February 2024 (UTC)Reply
@Michael.C.Wright According to m:Terms_of_use/Creative_Commons_4.0/Legal_note#Mechanism_for_the_upgrade the way the WMF does it is that existing text stay under the old license and all new text is under the new license. So what should be changed is probably just the text you see on the bottom of each page saying:
All text created after September 25, 2005 available under the terms of the Creative Commons Attribution 2.5 License, unless otherwise specified. (Should there be the word "is" in "2005 is available"?)
If someone think it would perhaps also be possible to create a page somewhere that users can add their names to agree to relicense old text to the new version.
When editing there is a new text saying "Your work will be licensed under the Creative Commons Attribution 2.5 License and will be attributed to "Wikinews"." and that should of course also be updated.
There can be other places that needs to be updated too but I do not think we have to edit or do anything to all the excisting articles. --MGA73 (talk) 08:52, 17 February 2024 (UTC)Reply
Based on your response here, specifically regarding the upgrade of new content while leaving existing content as-is, I am ready to vote in favor of an upgrade. However, I would like to better understand the ramifications of implementing an SA provision. I have asked two specific questions in two different contexts: 1) Not using SA to protect from assimilation with other projects and 2) Using both SA and non-SA in different aspects of Wikinews content and processes. Michael.C.Wright (Talk/Published) 17:44, 17 February 2024 (UTC)Reply
I do not believe that such behavior is beneficial for Wikinews. Offering the same information as Wikipedia is pointless; it lacks uniqueness and does not differentiate from Wikipedia. Kitabc12345 (talk) 08:24, 18 February 2024 (UTC)Reply
Many free-license news sites do not employ SA (ShareAlike) as their licensing clause. If other media are also required to change to SA to be able to use content from Wikinews, this could strike a blow to the freedom of the press, affecting the dissemination of information and undermining the public good. Kitabc12345 (talk) 08:42, 18 February 2024 (UTC)Reply

  Question This question is related to User:SVTCobra's above (and I apologize if I'm breaking convention with the threading and {{question}} use. I am happy to reformat this entry to conform with norms).

It has always annoyed me that Wikinews is not on the same license as our bigger sibling, Wikipedia. It has, among other things, had the effect of us having to rewrite simple tools, scripts, code for templates, etc. which have already been created on WP.

Can we license tools, scripts, and code for templates different from article content? After all, the final, rendered product of a template for example, is not the template, but HTML formatting. Therefore a Wikinews article is not sharing any template. Based on this understanding, would it be an effective compromise to protect Wikinews articles with a less-restrictive CC-BY and internal tools, scripts, and templates with CC-BY-SA, in-line with Wikipedia?

Michael.C.Wright (Talk/Published) 17:36, 17 February 2024 (UTC)Reply

I concur with this viewpoint; this solution is very sound. Kitabc12345 (talk) 08:37, 18 February 2024 (UTC)Reply

Sum up per march 2024

edit

I have tried to sum up the wiews:

  • 2 users (3 if you include me) think Wikinews should follow the same license as the other Wiki-projects (Justin and Ash Thawley).
  • 5 users think that Wikinews should NOT change to BY-SA but stay with BY (Xbspiro, Heavy Water, Michael.C.Wright, Base and Kitabc12345)
  • 1 user is against the update from 2.5 to 4.0 (Base)
  • 4 users possibly 6 (or 7 if you include me) think Wikinews should (perhaps) upgrade to 4.0 (Michael.C.Wright said yes, Xbspiro and Kitabc12345 said yes if all WN update, Heavy Water said yes to study update, Justin and Ash Thawley said yes to 4.0 but also SA)

So does you agree that the result is "Yes, WN upgrade to CC-BY-4.0 if the the other WN also upgrade"?

If that is the result then next step is to find out if the other WN would also change license. That raises 2 questions:

  1. How do we find out if WN update - is it a vote on meta or is it a post on every WN?
  2. If it is a post on every WN should there be a yes on all WN or is it okay if one or a few smaller WN says no or ignore the post?

--MGA73 (talk) 14:57, 6 March 2024 (UTC)Reply

I think we need someone to conclude on this discussion. Can we agree that the result is WN should upgrade from cc-by-2.5 to cc-by-4.0 but it should be done on all versions of WN?
If yes how is it implemented? Do we need a vote on meta? --MGA73 (talk) 13:33, 22 April 2024 (UTC)Reply
Anyone? --MGA73 (talk) 14:04, 11 May 2024 (UTC)Reply
I agree we should upgrade from 2.5 to 4.0. However, I have no clue how to break the deadlock of inaction. We have a number of things we should be taking action on that we are instead endlessly mulling over.
I'm willing to help however I can. Michael.C.Wright (Talk/Published) 15:44, 11 May 2024 (UTC)Reply
I can get behind an upgrade to by-4.0. A.S. Thawley (talk) (calendar) 19:13, 13 May 2024 (UTC)Reply
Thank you for the latest comments. I see two ways. Either a coordinated action or that English Wikinews change and hopefully the other Wikinews follow.
I will try once more to write to the other versions and make them aware of the discussion here. --MGA73 (talk) 13:08, 26 May 2024 (UTC)Reply
I have now written to all languages linked to d:Q16503. --MGA73 (talk) 15:56, 26 May 2024 (UTC)Reply
As an administrator of Chinese Wikinews, I like that all versions of Wikinews adopt the same licensing with CC-BY-4.0. Kitabc12345 (talk) 10:32, 27 May 2024 (UTC)Reply

I have made a list of pages to change, when Wikinews is ready to update to 4.0. The list is here: Wikinews_talk:Copyright#Pages_to_update_when_license_is_updated_from_2.5_to_4.0. You are very welcome to add more pages if you find any.

Hopefully the list will make it easier for other languages of Wikinews to update too. --MGA73 (talk) 15:56, 26 May 2024 (UTC)Reply

  • I would like all versions of wikinews to be under the same license. Do we have to do a poll on pl-Wikinews? Will there be one joint (for ol versions of wikinews) voting on meta-wiki? (sorry-automatic translator) Marek Mazurkiewicz (talk) 20:13, 26 May 2024 (UTC)Reply
@Marek Mazurkiewicz: I think each Wikinews have to decide to change. If it is possible to make a vote on meta for all that would be great but I'm not sure it is possible to force all to follow the result.
In order to make the change at all or as many WN languages as possible we could set a date for the change that will give everyone time to vote. For example August 1, 2024. --MGA73 (talk) 20:22, 26 May 2024 (UTC)Reply
Do we have an accessible summary of the differences between licenses somewhere? I'm not a lawyer. I think August 1st is not enough time. Maybe January 1, 2025? Marek Mazurkiewicz (talk) 20:36, 26 May 2024 (UTC)Reply
I don't think all Wikinews communities have the capacity to hold votes on their local community pages, as some Wikinews languages are not very active. Kitabc12345 (talk) 10:36, 27 May 2024 (UTC)Reply
@Marek Mazurkiewicz: There are more info about changes at this link. But I can't claim that it is super easy to understand.
I think that 7 months sound like a long time. What needs to be done? If there are 30 days for community to confirm the change and 30 days to find out where to change is that not time enough? I'm not against giving more time I just wonder what is needed? Am I missing something?
@Kitabc12345: If a small wiki do not wish to hold a vote then perhaps there are a few active users that can decide? --MGA73 (talk) 16:27, 27 May 2024 (UTC)Reply
@Marek Mazurkiewicz: You said earlier that August 1, 2024 were not enough time. Did you notice my question about it? --MGA73 (talk) 17:30, 7 June 2024 (UTC)Reply
So far, no one in our water_cooler has commented. I don't know if we can make such a decision. Marek Mazurkiewicz (talk) 22:36, 7 June 2024 (UTC)Reply

┌─────────────────────────────────┘
I made a new comment on your water cooler. Does anyone know how things are going on other wikinews languages? --MGA73 (talk) 15:56, 14 June 2024 (UTC)Reply

Just to add my 5c here as I got the message on BS Wikinews and I would be up for upgrade of 2.5 to 4.0 licence, while remaining flexible on Share Alike (as I am still not certain what would be desired by whom in my own region/language spectrum). --Zblace (talk) 08:59, 16 June 2024 (UTC)Reply

Zblace Thank you! I think the best way to find out is to reply on your wiki as you just did and then perhaps others will reply too. But if a formal vote is required maybe you could create one? --MGA73 (talk) 09:12, 16 June 2024 (UTC)Reply

Differences between 2.5 and 4.0 according to ChatGpt

edit

@Marek Mazurkiewicz: and other asked what the differences are. Between cc-by-2.5 and 4.0. Earlier I wrote that:

A1 sadly no. But I can give it a try based on the links in https://wiki.creativecommons.org/wiki/License_Versions#License_Versioning_History under "Explanation of changes from prior version".
3.0 fixed some issues related to TPM / encryption and compability with MIT-licenses etc. Not sure how relevant that is for Wikinews.
But Internationalization seems more relevant as the new version "utilize the language of the international intellectual property treaties, in place of the language of US copyright law". Also there is a better coverage for Moral Rights.
BY-SA is more compatible with other licenses now.
4.0 is said to be even more global.
It should also be better to handle "Rights outside the scope of copyright".
It implement a "Common-sense attribution" that is better suited to reflect accepted practices (for example using a link) and also a "30-day window to correct license violations". It makes it harder for those that uses a tiny mistake to sue someone for copyright violation.
It also claims to have "Increased readability".
If anyone have a better reason you are very welcome to share it. --MGA73 (talk) 10:18, 17 December 2023 (UTC)Reply

Today I asked ChatGpt if it could explain the differences and is said (format changed by me):

[Start]

Sure! The Creative Commons (CC) licenses have different versions, and each version may have slight variations in the terms and conditions. Here are the main differences between the Creative Commons Attribution 2.5 (CC BY 2.5) and Creative Commons Attribution 4.0 (CC BY 4.0) licenses:

1. Internationalization and Legal Code Updates
  • CC BY 2.5: The 2.5 license is not as thoroughly internationalized. It was mainly designed with the legal frameworks of a few specific jurisdictions in mind.
  • CC BY 4.0: This version is fully internationalized, meaning it's designed to be universally applicable across different legal systems worldwide. The legal language and terms have been refined to accommodate various legal traditions and interpretations globally.
2. Terminology and Clarity
  • CC BY 2.5: Uses older terminology and might be less clear in some areas compared to newer versions.
  • CC BY 4.0: Introduces more precise language and definitions to reduce ambiguity and increase clarity for international users.
3. Moral Rights and Database Rights
  • CC BY 2.5: The handling of moral rights and database rights is less explicitly addressed.
  • CC BY 4.0: Specifically addresses moral rights (rights of attribution and integrity) and database rights, providing more comprehensive and clear guidelines on how these rights are managed under the license.
4. Additional Terms and License Interpretation
  • CC BY 2.5: Includes fewer provisions related to additional terms.
  • CC BY 4.0: Allows licensors to add specific terms and conditions as long as they don't contradict the license. It also includes more guidance on the interpretation and enforcement of the license.
5. Attribution Requirements
  • CC BY 2.5: Attribution requirements are somewhat less detailed.
  • CC BY 4.0: Provides more detailed requirements for attribution, making it clearer what users need to do to properly attribute the original creator.
6. Adaptation and ShareAlike Compatibility
  • CC BY 2.5: Adaptation terms are present but less developed.
  • CC BY 4.0: Has clearer terms on what constitutes an adaptation and how adaptations should be handled, ensuring better compatibility with other licenses, including more detailed terms on share alike and compatibility with other licenses.
7. Technical Protection Measures (TPM)
  • CC BY 2.5: The stance on technical protection measures (such as DRM) is less detailed.
  • CC BY 4.0: Clearly prohibits the application of TPMs to licensed works in a way that restricts others from exercising the licensed rights.
8. General Provisions and Warranties
  • CC BY 2.5: Contains fewer general provisions.
  • CC BY 4.0: Includes updated general provisions and disclaimers, such as a more detailed disclaimer of warranties and liability, which offers better legal protection to licensors.

In summary, CC BY 4.0 is more detailed, clearer, and better adapted to international use than CC BY 2.5. It also includes improved provisions for handling moral and database rights, attribution requirements, and additional terms, making it a more robust and versatile licensing option.

[End]

I hope this will make it easier if/when other language versions discuss the change of license. --MGA73 (talk) 05:48, 28 May 2024 (UTC)Reply

(прошу прощения за русский язык) Тема перехода на новую лицензию очень важно. И глупо обсуждать различия между лицензиями, опираясь на советы ChatGpt. Я настоятельно рекомендую обратиться в Фонд для получения чёткого ответа на вопрос: в чём различия между CC BY 2.5 и CC BY 4.0. В конце концов, именно Фонд несёт юридическую ответственность за реализацию условий различных лицензий в наших проектах.
ps: лично я поддерживаю переход на CC BY 4.0. Отимени викиноновтей на языке эсперанто могу сказать, что с нашей точки зрения переход на новую лицензию нужен: мы используем ряд материалов и источников, которые распространяются по лицензии CC BY 4.0. VladimirPF (talk) 06:08, 28 May 2024 (UTC)Reply
Translating @VladimirPF's comment: "(I apologise for using Russian) The topic of transition to a new license is very important. And it is stupid to discuss the differences between licenses based on the advice of ChatGPT. I strongly recommend contacting the Foundation to get a clear answer to the question of what the differences are between CC BY-2.5 and CC BY-4.0. In the end, it is the Foundation that is legally responsible for implementing the terms of various licenses in our projects.
PS: I personally support the transition to CC BY- 4.0. In addition to Wikinews in Esperanto, I can say that from our point of view, the transition to a new license is necessary: ​​we use a number of materials and sources that are distributed under the CC BY-4.0 license." A.S. Thawley (talk) (calendar) 18:10, 2 June 2024 (UTC)Reply
GPT chat can't help us here. This is too delicate a matter. Wikipedia is on version 4.0, so a change will probably be necessary sooner or later. But our community is small. No one has commented on pl.Wikinews yet. Marek Mazurkiewicz (talk) 17:04, 28 May 2024 (UTC)Reply

Conclusion and implementation of upgrade to cc-by-4.0

edit

I see support to upgrade to cc-by-4.0 but perhaps an administrator or a bureaucrat should formally close the vote and set a date for the upgrade. I suggested August 1, 2024 but someone from another language suggested that it was a bit too soon. So it could also be September 1, 2024 for example.

I also think it would be helpful to cummunicate the date to the other language versions that English Wikinews will change the license on <this date>. It will make it easier for each wiki to coordinate.

I have created User:MGA73/Licenseupgrade with a list of all wikis. It is not complete yet but I hope it can make it easier for all languages to upgrade. Everyone are welcome to help update and expand. And I can also move it outside my name space if thats better. --MGA73 (talk) 12:47, 16 June 2024 (UTC)Reply

Review and Admin fast track, to reinvigorate English Wikinews

edit

There was discussion about the review process being broken, over at Wikinews:Flagged revisions/Requests for permissions. The suggestion was made to split the conversation off elsewhere, and I see no evidence that this was done, so I'm doing it.

When I was a high schooler, I had first period off one year. I would kill time in the library, and so I asked for sysops privileges. I received them, almost instantly. The thinking at the time was that being an admin was no big deal. If you were wrong in your judgements, another sysops could revert you, and if needed, your special status could always be revoked.

I became an early contributor to Wikinews, with my first article dated to November 16, 2004, just eight days after the project's launch. For years, things would be published almost instantly after they were submitted, unless they had substantial issues. But increasingly things I'd submit would get lost in a jumble, and marked stale. This included original reporting, enough so that I substantially left the project.

I feel Wikinews needs to add five admins and five reviewers, minimum, in the hopes that one remains active over the medium term. If the people chosen end up making bad calls, that's the learning process. If they end up making really bad calls, okay, we remove the status. This is a wiki, everything is revertable. But more than likely, the people given these extra responsibilities will be a-okay.

Thoughts? -- Zanimum (talk) 01:18, 22 April 2024 (UTC)Reply

I have to agree. There's a major personnel shortage here, and it's not going to get better with the current system. Handing out admin and reviewer like the titles are irreversible and made of solid gold isn't going to do anything to improve the mess this place has found itself in. Anyone able to help out should be vetted, sure, but then they should be allowed to help. The situation as-is is entirely unsustainable, as the last few months have proven. A.S. Thawley (talk) (calendar) 09:44, 22 April 2024 (UTC)Reply

Tagging in Asheiou (t · c · b), MathXplore (t · c · b), Habst (t · c · b), Heavy Water (t · c · b), Michael.C.Wright (t · c · b), Bawolff (t · c · b), who all commented on the previous thread. -- Zanimum (talk) 01:21, 22 April 2024 (UTC)Reply

I agree. This wiki has become silly. A bunch of rules with no one left for the rules to be enforced against. Somewhere along the way we've lost the path. Bawolff 02:40, 22 April 2024 (UTC)Reply
'Too few reviewers' has been a complaint for years. 2022,2020 This is the chronic problem I referred to recently.[4]
I propose the following scheme:
  • No immediate approval for elevated privileges
  • A new {{pre-review}} template that has three possible statuses:    In progress (default),    Recommend publish, or    Not ready. The only parameters for this template can be 1, 2, or 3
  • Anyone can perform pre-review by starting a new section in the article's collaboration page titled "Pre-review" followed by {{pre-review}}
    • Articles that have the status    Recommend publish can be more-quickly reviewed by an existing reviewer
    • Reviewers will learn which pre-reviewers leave good notes for them and demonstrate the ability to improve articles prior to publication.
    • Articles that have the status    Not ready will have the {{review}} template changed by the pre-reviewer to {{develop}} for changes to be made (saving reviewers time)
    • Authors are thus incentivized to do more of their own copy editing if their articles contain obvious and easy-to-fix errors that cause them to fail pre-review.
  • Pre-reviewers are required to use the {{tasks}} template as well as clear notes in the collaboration page.
    • Links to policy with explanations indicate a proficient pre-reviewer.
    • Links to previous precedent and examples indicate a proficient pre-reviewer.
    • This also informs new authors/users of our policies.
Existing reviewers and admins can at any time initiate a vote for elevated privileges for a pre-reviewer based on their demonstrated ability to pre-review. The voting process has a defined time-limit, after which only a simple majority out of ≥ 3 admin and/or reviewers is needed to grant elevated privileges.
Any reviewer or admin can at any time initiate a vote of "no confidence" in the scheme itself. That process too has a defined time-limit, after which only a simple majority out of ≥ 3 admin and/or reviewers is needed to end the scheme.
Michael.C.Wright (Talk/Published) 16:41, 22 April 2024 (UTC)Reply
I do not entirely disagree with everything I'm reading here. The 'pre-review' idea might have a pinch of merit. But:once again, we find ourselves quacking about over things that matter little, while spending minimal time on things that REALLY matter, namely: Getting the news, submitting the news, editing the news and publishing the news. That is what we are supposed to be about at this place. Let's try not to move too speedily on this just yet. We need a period of contemplation on this -- but I like the discussion on-the-whole. So, quite seriously: Who wants to become a Reviewer in the near future?--Bddpaux (talk) 19:29, 22 April 2024 (UTC)Reply
I would volunteer to help. There needs to be some sort of plan or system in place to help on-board people and make the process as smooth and effective as possible. A scheme like the one I've proposed could serve dual purposes: assisting current reviewers in evaluating aspiring reviewers and offering aspiring reviewers an opportunity to immerse themselves in the intricacies of the role. In a way saying to new reviewers; if you want it, this is what it takes. Are you still interested? I think the review process is completely different from writing a good article. Though it requires that ability as a foundation.
I guess I'm trying to err on the side of fewer reviewers to prevent too many who just want the title and a new userbox. I also see little value in retreading discussions that have been had for years. A news provider needs to be both nimble and thoughtful, intentional, and deliberate. -- Michael.C.Wright (Talk/Published) 13:05, 23 April 2024 (UTC)Reply
As stated in my review request, I'd be happy to help out. I'm just coming out of my health slump so I should be around more soon. I'm starting on en-wiki with small edits to get my footing again and build up a bit. I'm going to reapproach AILSHA to ask some questions about some of the more recent things she's been doing since Eurovision. A.S. Thawley (talk) (calendar) 16:07, 23 April 2024 (UTC)Reply
I would totally support this, however I think there should be some requirements for pre-review, if for nothing other than preventing vandalism, nonsense, and people with absolutely no idea what they are doing. Maybe something like:
1.5 published articles. This would be so that they have at last some idea of what passes a review, and some idea of our policies on how to write articles.
2.Autoconfirmed. To prevent vandalism, and users who don't know anything about Wikinews. In reality most people meeting the first requirement would meet the second.
I think maybe would could have it so that these people could review pending changes as well. Me Da Wikipedian (talk) 18:50, 19 May 2024 (UTC)Reply
I have created the template {{Pre-review}} based on my comments above. I am interested in feedback about the template itself as well as any thoughts on its effectiveness in getting good, early evaluations of content. It is ready to be carefully used now. I think using it would be a good way for any aspiring reviewer to get a feel for the basics of reviewing (the basics = reviewing against the pillars).
I've used it once on an article and I think I will change the pass/fail verbiage to something else. The goal being not to discourage or offend authors, but to provide legitimate, understandable, and actionable feed-back with an ultimate goal of getting more quality articles published.
If there is feedback strictly based on the template—such as format, layout, etc—that feedback is best placed on the template talk page so we don't lose the focus here.
Current reviewers; if you went to review an article that already had a {{pre-review}} on it and the pre-review was done by someone you trusted, with a track record of good articles and good work with other authors, would that help you? --Michael.C.Wright (Talk/Published) 13:12, 30 May 2024 (UTC)Reply
I have made a proposal for a pre-reviewing page Me Da Wikipedian (talk) 00:52, 31 May 2024 (UTC)Reply
Given that @Bddpaux has left for 6 months it seems (and Asheiou for a week), we will need all the reviewer time we can get. I think pre-reviews are a great way to so. I would like to ping people who are, under the proposal, eligible for pre-review, and ask that they consider it.
Users eligible (I am pinging Michael.C.Wright because they would have been eligible when they started doing it) @Asheiou, Michael.C.Wright, BigKrow, Виктор Пинчук:. Thank you.
P.S. Let me know if I missed anyone. Me Da Wikipedian (talk) 11:05, 2 June 2024 (UTC)Reply
Idea:Make it such that the review category is sorted by assessed ready at the top, non-pre reviewed in the middle, and assessed not ready at the bottom@Michael.C.Wright Me Da Wikipedian (talk) 11:06, 2 June 2024 (UTC)Reply
I made a first-pass attempt at this but it isn't working yet. It's tricky because the {{pre-review}} is applied to the talk page. But the article is what is in the category 'Review' and thus gets listed in the review queue. I do like the idea and would like to see if it can be done. But I'm also trying to ensure the {{pre-review}} is least-impacting right now, as it's not an officially approved process. Michael.C.Wright (Talk/Published) 18:45, 3 June 2024 (UTC)Reply
Is it possible to apply pre-review to the main page? It so far has silent consensus, but if anyone complains we can always undo it.@Michael.C.Wright Me Da Wikipedian (talk) 20:22, 3 June 2024 (UTC)Reply
Me Da Wikipedian: What exactly do you mean? And also, hell no (I hope it's not what I think it is, but I can't think of any alternative interpretations). There isn't even a consensus for pre-review to be implemented (silent consensus is an absurd idea, particularly for a small wiki like en.wn, and actually means there is no consensus). I thought the one done for the article about Putin allegedly being open to ceasefire talks was just a beta version intended to get feedback, so I didn't object. Now there's been another, and it is apparently being treated like it's a feature of policy, even though it still is only acknowledged by a proposed policy.
Speaking of which, I have questions about the pre-review process, and especially about that proposed policy. I see two different people basically presenting two radically different ideas of what this would be.
Michael.C.Wright, from what I can gather from the pre-reviews you've done and your April 22 comment above, your framework involves pre-reviewers recommending actions to reporters and reviewers. You asked whether those recommendations, from someone reviewers trust, would help reviewers. Just speaking for myself obviously, though I hope other reviewers would feel the same, I would only trust them to point out issues, not to ensure an article, or a facet of it (e.g. neutrality) is pass-worthy. Unless they're trusted enought to be reviewers, and I wouldn't want to rely solely on my own judgement of that. The consensus resulting from an FR/RFP has the benefit of showing us the entire community's opinion of that. If they are just being trusted to point out issues, I don't understand why this needs to be a formal thing with the complications of such, because non-reviewers have been doing a similar sort of thing for years (you among them).
Me Da Wikipedian, pre-review as I gather you envision it also sounds redundant...to, um, review. According to the proposed policy, we would be giving full reviewer rights — plus autosight, which tells me you probably don't understand how the current system works — to people with possibly very little experience here. Am I wrong about how your proposal is supposed to work? Again, why wouldn't these people just run for reviewer, then? Heavy Water (talk) 21:53, 3 June 2024 (UTC)Reply
@Heavy Water, what I mean by "silent consensus" is that a few users want it and no one has said they don't, so until then it is reasonable to think there are no complaints. And yes, unless and until someone has an issue its being treated as such, it's reasonable to think that...no one has any issue with it being used. Obviously, the point of pre-review would not be to be the same as review. It would exist to allow a more open discussion between the pre-reviewer and the author, someone who can fix the issues with being worried about being too involved in writing the article, training for potential reviewers, helping to prioritize the work of actual reviewers, and helping with more minor stuff like rollback and pending changes. Their judgement has no effect at all on whether or not an article is published. The main thing they can't do is the really hard part about reviewers jobs, you know being solely responsible to make sure something is of quality and if so publish it to the main page. At least how I meant the autosight was similar to the pending changes right on enwiki, to allow them to review pending changes, not new articles. Again, at least with my requirements, these people would have a reasonable amount of experience. People wouldn't just run for reviewer...because well the level of trust and confidence needed for someone to give a recommendation and help a new user out is much different than the power to publish something to the main page.
I completely concur with @Michael.C.Wright's comment below as well. Me Da Wikipedian (talk) 23:43, 3 June 2024 (UTC)Reply

┌───────────────────┘
I thought the one done for the article about Putin allegedly being open to ceasefire talks was just a beta version intended to get feedback...

Correct

Now there's been another, and it is apparently being treated like it's a feature of policy, even though it still is only acknowledged by a proposed policy.

The template is not intended as a policy feature. The disclaimer at the end clarifies: "This is a pre-review only and is not part of the official review process." If it evolves into a policy, that's fine, but its purpose is to provide a consistent, predictable format for evaluations by another user.

from what I can gather from the pre-reviews you've done and your April 22 comment above, your framework involves pre-reviewers recommending actions to reporters and reviewers.

Correct

I would only trust them to point out issues, not to ensure an article, or a facet of it (e.g. neutrality) is pass-worthy.

Correct

Unless they're trusted enought to be reviewers, and I wouldn't want to rely solely on my own judgement of that. The consensus resulting from an FR/RFP has the benefit of showing us the entire community's opinion of that.

I made the template in the context of my comment above, in which I proposed a process for grooming and identifying potential reviewers. In this process, any user can evaluate an un-reviewed article and provide feedback, ranging from a simple second opinion to an in-depth evaluation that helps get an article published. To reiterate what I said above, "Reviewers will learn which pre-reviewers leave good notes for them and demonstrate the ability to improve articles prior to publication." In this way, a good pre-reviewer (this is just a name to discuss them, not meant to be a unique group, with status, etc.) can be identified by reviewers as someone who could be nominated or supported as a potential reviewer.

If they are just being trusted to point out issues, I don't understand why this needs to be a formal thing with the complications of such, because non-reviewers have been doing a similar sort of thing for years (you among them).

One of the benefits I see in the easyPeerReview gadget is that it forces a reviewer to at least acknowledge the pillars one-by-one, implying each was checked by the reviewer as part of a (hopefully) structured, rigorous, thorough review. I think the template {{Pre-review}} could do the same for potential reviewers. I don't expect it to train people on how to review, nor do I expect it to signal a potentially good reviewer. But over time, a bunch of pre-reviews by someone could do both.
As Bawolff intimated at Water cooler/Miscellaneous, we need to change the way en.wn is perceived. By my count, one could potentially argue we meet three of the proposed criteria to shutter a project:
  1. Lack of impact on other Wikimedia projects and wider Internet infrastructure
  2. Severe lack of community activity
  3. Strong external project to merge with (Wikipedia)
We need more reviewers. My goal with this template is to help groom and identify those individuals more quickly and easily. Sorry for the long post. I'm trying to make things more clear. Michael.C.Wright (Talk/Published) 23:10, 3 June 2024 (UTC)Reply

Opt in global sysops?

edit

Although this wiki will soon meet the automatic criteria to opt in global sysops, I would like to propose that the English Wikinews becomes a global sysop wiki.

As a steward dealing with anti-abuse I've noticed that this wiki gets a lot of vandalism, spam etc., but has little admin support to deal with it. Out of fifteen administrators on this wiki, only four of them have edited in the last month, and out of those four, only two have taken admin actions this month, and only one in the last week.

Looking in Category:Speedy deletion, there are 320 (!) pages nominated for speedy deletion, and many vandalism/spam pages which have been sitting undeleted for months. With the current situation here, having global sysops being able to help would be a benefit. We have many active global sysops in multiple different time zones who are active and able to quickly act when needed.

Keep in mind that global sysops are only allowed to use their tools for anti-vandalism/anti-spam purposes; other actions are outside of global sysops' scope, and global sysops do not interfere with the content side or other unrelated areas of the project. EPIC (talk) 16:50, 24 May 2024 (UTC)Reply

Yes please. —Justin (koavf)TCM 16:53, 24 May 2024 (UTC)Reply
  •   Support I often work with EPIC and have found they respond quickly and effectively to cross-wiki abuse. Their help (and other's) for local vandals would be greatly appreciated. Speaking of vandalism, have you see your user page here @EPIC? ツ —Michael.C.Wright (Talk/Published) 17:45, 24 May 2024 (UTC)Reply
    I have actually not, but I'm surprised it's been up for over a month now. Well, you see my point here. EPIC (talk) 18:28, 24 May 2024 (UTC)Reply
  •   Support 100%! I am SO EXHAUSTED dealing with vandalism... it drags this project down! Silly question, though: Global sysops will know/learn/understand what constitutes vandalism here, right? ...not just someone who is off to a rocky start on what may be a good news article.--Bddpaux (talk) 19:39, 24 May 2024 (UTC)Reply
    It's a reasonable question actually, but yes - it shouldn't be a problem for global sysops to tell what is obvious vandalism and what is just a new user unfamiliar with local practices, especially since this is an English wiki and language barriers aren't as much of an issue here, unlike with other GS wikis. And like mentioned, global sysops should not be using their tools to get around the local procedures for becoming a local administrator, but should be following what is allowed within GS scope. EPIC (talk) 21:22, 24 May 2024 (UTC)Reply
    I generally agree that global sysops can be trusted, but please note that not all global sysops have experiences at Wikinews, and not all languages have their own Wikinews edition. I would like to welcome the global sysops, but I also believe that borderline cases should be handled by our local admins/reviewers or a global sysop who has sufficient experience in any version of Wikinews. MathXplore (talk) 01:32, 25 May 2024 (UTC)Reply
    +1 to this one, I have no problems trusting global sysops to clean up vandalism and spam, but like mentioned, other maintenance work outside of that scope, and, like you mentioned, borderline cases, should be left to local administrators. EPIC (talk) 03:16, 25 May 2024 (UTC)Reply
  •   Support but can you clarify the automatic criteria to opt in the global sysops? Where is the documentation? MathXplore (talk) 23:53, 24 May 2024 (UTC)Reply
    Yes, I absolutely can; as per m:Global sysops#Scope, if the wiki has fewer than ten admins or fewer than three admins having taken an admin action in the past two months, it will be eligible to become a GS wiki. Of course there can be exceptions to this, such as if the wiki has previously voted to opt out global sysops, in which case an opt-in discussion will be required. This is not the case for enwikinews (it was automatically opted out when the GS wiki set was created), but I opened the discussion here anyway to see the community's opinion. EPIC (talk) 00:54, 25 May 2024 (UTC)Reply
    I think I have read that documentation before, but I didn't notice that it means the automatic criteria to opt in the global sysops. Thank you for the information. MathXplore (talk) 01:26, 25 May 2024 (UTC)Reply
  • Support pretty strongly. This wiki has an odd history of rejecting similar (past) help; nice to see that isn't the case now. Leaderboard (talk) 11:11, 25 May 2024 (UTC)Reply
  • Oppose because most global sysops have very little experience of this wiki. I don't think many of them will understand the subtle difference between a newbie article and real vandalism. I admit I've been absent for a few months but I've had to decline multiple speedy deletion requests, which I don't think a global sysop would have recognised. I don't doubt their abilities elsewhere (particularly the very small wikis) but out of 27 global sysops...
sixteen haven't edited here in more than a year including one that has never edited here.
seventeen have fewer than 100 edits on this wiki (14 with fewer than 50 edits and 1 with zero edits).
the majority of edits by the others are due to global renaming (done elsewhere).
We should not be trusting these administrative tools to users who would not yet qualify as local administrators. I can see only one user (DannyS712) who has both a large number of edits here and recent editing experience. Since we can't pick and choose amongst them, we should not accept global sysops.
The solution to the problems of vandalism lies partly with having more local administrators. I'd suggest inviting some of the more active recent contributors above to put forward their names for the admin hat. [24Cr][talk] 19:12, 28 May 2024 (UTC)Reply
I'd probably have opposed global sysops as well had the admin/functionary situation been better - but the problem on this wiki has mostly been that local administrators have not been able to act in a timely manner when needed and traces of vandalism have been undeleted for months, especially now that there is an LTA (ACV) who has been taking advantage of that and created vandalism here for a few months now (a lot of which is still not deleted). I've seen multiple users request steward action for this reason - mainly global blocks/locks, but now more recently also CU requests and SRP requests for removal (as bureaucrats/CUs had not been editing here before I emailed the crats recently to forward some requests we have gotten). I do agree that this wiki has a slightly different profile than wikis where GSes/stewards mainly act, but should there be a consensus here, I would suggest making it clear in Wikinews:Global rights usage what global sysops/stewards can and cannot be doing here. EPIC (talk) 19:49, 28 May 2024 (UTC)Reply
I agree that vandalism should have been dealt with much earlier but it is nothing new here or on many wikis. I was a steward (until ill health pushed me to resign in 2023) and saw plenty of LTAs targeting smaller wikis over several years. No amount of admin actions will prevent a determined vandal. Long before I became active here, I was very active on English Wikipedia, where the presence of hundreds of active administrators has not solved vandalism in the 20+ years since it became a phenomenon. As I said above, part of the solution is to recruit local administrators but a major part of the solution lies in removing the one thing that drives vandals. Many of them do it because they think their vandalism will be visible to the general public and because it will annoy some editors. The fact that many wikis allow anonymous IPs to edit mainspace pages makes the vandals bolder. The fact that user pages are soft targets is what helps vandals. We can play whack-a-mole all day but it won't stop them. We can block huge swathes of IPs but it won't stop most vandals because they can swap IPs. Part of the solution is for us to implement a Draft namespace (like the ENWP one) for all new articles and to prevent anonymous IPs and new accounts from editing mainspace pages. That would eliminate the motivation to vandalise pages they think the public will see. Another part of the solution is to prevent user pages from being edited or moved by anonymous or new accounts. A final piece of the solution is to improve tools like the abuse filter (which is responsible for preventing numerous bad edits and blocking many potential vandals). Allowing the global sysops to act against vandals will not prevent the vandalism. The other issue of CU is nothing new either. Myself and Acagastya stood for CU in 2021 precisely because stewards were slow to act on our requests (and as a steward I couldn't use the tool here). I do understand the frustration of not having someone act on a request quickly but if you look at the history of WN:RFCU, there have been two requests in April and May this year. One request was retracted by the requesting user and the other was acted on after 12 days. Before that there were no requests locally for almost three years. I honestly cannot see how this is being construed as a track record of local CU requests not being acted on. On the contrary, the two of us have performed almost 500 CU checks in the 2+ years between being appointed and October 2023. Yes, we've both been less active for a few months but I don't feel it's fair to characterise us as being completely inactive. [24Cr][talk] 21:12, 28 May 2024 (UTC)Reply
I find your and @Heavy Water:'s stance rather frustrating, and I've had this issue with Agastya in the past as well. I've been around for a while and I can't recall of a time where I thought that this wiki was well-managed in terms of routine housekeeping (regarding "The solution to the problems of vandalism lies partly with having more local administrators" in fact I tried to be admin unsuccessfully and was opposed because I did not have the reviewing experience and whatnot even though my sole purpose of applying was because I was tired of seeing the spam). "I think the GSes or stewards would need to learn so much about this project and how it works that they'd practically have the experience to become admins locally" - sorry I don't agree with that. You say things like "play whack-a-mole" but my experience (at least on my wiki) is that global sysops do a very good job of removing nonsense. "because stewards were slow to act on our requests" is unfortunate though if true.
Instead of being so dismissive, how about write a short guide on how global sysops are to operate on this wiki? They tend to be conservative anyway. GS making a mistake? Just tell them; they tend to be pretty good at learning from it. Leaderboard (talk) 12:27, 30 May 2024 (UTC)Reply
  •   Oppose: Cromium makes a very convincing argument here, and I trust their expertise. I just have a few things to add. I think the GSes or stewards would need to learn so much about this project and how it works that they'd practically have the experience to become admins locally. The statistic EPIC uses (current at that time) was from around the end, and therefore culmination, of an approximately two-month stretch with an unusually low rate of admin speedy deletions — particularly early on, which created such a backlog of speedy deletions that it would take a significantly above-average amount of effort to clear it, and so admins ended up just containing its growth (Cromium has since made that effort and cleared most of the backlog). And, I don't think removing the vandalism we get here is as urgent as it is for, say, a lot of the vandalism at en.wp, because the published content of the project is by default protected by the combined effects of FlaggedRevisions and the archive policy — published, unarchived articles are supposed to be protected upon publication so they can only be moved by admins and edited by autoconfirmed users, with any edits still subject to review by a reviewer, archived articles (nearly all published articles) are only editable or movable by admins, and nothing can be published without a review. Heavy Water (talk) 16:06, 29 May 2024 (UTC)Reply
    Maybe it's enough to allow global stewards to respond to WN:AAA requests. Those are normally completed by Wikinews editors who are likely more aware of what is actual disruption here. I also don't think it takes much experience here to know what constitutes abuse. There are good give-aways that an experienced steward would recognize, regardless of their experience here, such as 1) posted by a new account, 2) new page created, 3) contains an external link, 4) contains offensive language, etc. The vandalism we see normally fits many of those descriptions.
    They also theoretically have the benefit of seeing global disruption and may recognize sooner a specific, cross-wiki LTA.
    Besides, what would be the downside? A false-positive deletion of genuine content running off what might otherwise become a long-term wikinewsie? We are already struggling to review articles we're getting from existing users. To me, that is the real problem we should be working on. Michael.C.Wright (Talk/Published) 16:30, 29 May 2024 (UTC)Reply
  Support Although I think we should say something along the lines of generally speaking just use it for
A.Blocking/Unblocking
B.Deletion
C.Anything else urgent Me Da Wikipedian (talk) 21:33, 29 May 2024 (UTC)Reply
  •   Support I appreciate Cromium's and Heavy Water's concerns about giving global sysops access to this local wiki. However, I'm worried about the state of this project without allowing global sysops. Furthermore, IMO, the project's autonomy isn't strong enough to withstand any more vandals and sockpuppets and LTAs. I can see one of admins being burned out from such common incidents. To allow ourselves being relaxed from work, maybe global sysops should see the workload and be burdened instead? George Ho (talk) 21:32, 31 May 2024 (UTC)Reply
  Support per @George Ho. I would like to see global sysops taking the most conservative stance possible, only removing obvious vandalism. If there is any doubt, they should leave it up and defer to our local admin team. I recognise the concerns of @Cromium and gsysops editing here need to look at what we consider vandalism before touching anything. A lot of the vandalism tedium could be effectively handled by gsysops though. @Michael.C.Wright's shout about WN:AAA requests may be a good start, and we could see how effective it is from there. A.S. Thawley (talk) (calendar) 18:25, 2 June 2024 (UTC)Reply

  Done This has been open for a while, and after checking with some other stewards beforehand, we have determined that there is a consensus to give global sysops access, with caveat that they will only use their access for clear cut cases, such as clear vandalism and spam. As I am not a regular at this project, I will let another user update Wikinews:Global rights usage accordingly, with clear mentions of the allowed use cases above. EPIC (talk) 13:03, 3 June 2024 (UTC)Reply

Gopher65's reviewer tools under review

edit

I have just now requested removal of Gopher65's reviewer tools. Your inputs there are welcome: Wikinews:Flagged revisions/Requests for permissions/Removal/Gopher65. George Ho (talk) 21:20, 31 May 2024 (UTC)Reply

Global sysop restrictions

edit

So, since we've opted into global sysops, now comes the time to define some more precise limits for what they are allowed to do here. @Leaderboard and I have added a bit that reflects the basics of what was said in the original discussion, but I feel what we've written so far is a bit short and vague for a policy that affects what people who have nothing to do with this project can do.

As a first note, I'd like to copy the "Any English Wikinews administrator can ask a global [sysop] to stop [using their permission] if what they deem to be misuse occurs, and the global [sysop] must comply with such a request." general rule that we apply to global rollbackers into the policy. I thought I'd bring it up here because I'm hesitant to just go and write out an entire policy myself, and people who have been here for longer will probably be able to write it in a better way than I could.

If anyone has any thoughts or policy suggestions in this regard, please share them here and we can reach a consensus on what to put in the final policy. A.S. Thawley (talk) (calendar) 19:28, 3 June 2024 (UTC)Reply

I don't see a problem with adding that. Beyond this, I don't see the need to expand on this further. Your linking to Wikinews policies should be enough for global sysops to understand what's going on, and should any clarification be needed, it should be OK to update it then. Put it this way: a global sysop should be able to easily figure out what they can (or cannot) do on this wiki, and the policy as written does that. Leaderboard (talk) 20:08, 3 June 2024 (UTC)Reply
That's a fair point. I'm just wary that the opt-in didn't pass unanimously, with some quite high profile (@Cromium, @Heavy Water) oppose votes. I'd be interested to hear their opinions on if we should add anything else to the policy page, given that they opposed the opt-in — something to help address some of their specific concerns, perhaps. A.S. Thawley (talk) (calendar) 21:48, 3 June 2024 (UTC)Reply
Thank you for starting this discussion and making those changes to the policy page. I am still unsure about letting global sysops do these tasks but I'm willing to see what it produces. I'd like their remit to be limited to obvious vandalism and cross-wiki abuse. We have already had one global sysop action today by a user who had only made 15 edits here (mostly reverting vandalism or requesting deletion), which deleted a page that had random letters as a title BUT the content was the basic layout of new articles, as might happen if a new user used the system on WN:Writing an article. The deletion happened five minutes after page creation. I checked on the global user contributions page and this was the IP users only edit, so it did not seem an obvious vandal although there may have been deleted contributions elsewhere. Although it most likely was a test page, my personal inclination would have been to leave it a while in case the new user tried further edits. For me, it wasn't a clear case of speedy deletion being needed. My feeling on restrictions is that global sysops should only delete pages that clearly fall under criteria A3, A6 or R4 on Wikinews:Criteria for speedy deletion. I will keep observing these deletions and may comment further. [24Cr][talk] 23:18, 3 June 2024 (UTC)Reply
Outside of some of the later CSD's for articles I don't see why they can't do everything else. If there trusted enough to be a global sysop, I'd imagine there trusted to use common sense and not do anything if they have no idea what their doing.@Cromium Me Da Wikipedian (talk) 23:45, 3 June 2024 (UTC)Reply
Cromium's concern is valid for the reason that Wikinews operates so differently to any other WMF project. Common sense that works on other wikis doesn't necessarily work here. I was hesitant to opt in too, honestly, but I feel with clear enough guidelines we can limit false positives on the global sysop side. I'm not entirely sure myself of the final restrictions we should impose on global sysops, so I feel this discussion is important to have so we don't argue about it in 3 months time if someone messes up because we didn't provide them any guidance. A.S. Thawley (talk) (calendar) 23:57, 3 June 2024 (UTC)Reply
Agreed. What I am trying to say is that global sysops should know this is a different wiki, and if there not used to it, either they don't do things here or they look around and learn.@Asheiou Me Da Wikipedian (talk) 23:58, 3 June 2024 (UTC)Reply
That being said: I've updated the policy with information for meta:GIE and meta:AFH (which wikis cannot opt-out of, so in essence codifying what already happens). Also I moved the "can ask to remove" part to a single place so that it's clear that it applies to all rights. Leaderboard (talk) 20:30, 3 June 2024 (UTC)Reply
I agree with that first note for sure. I think that, maybe, we should have a restriction on the more controversial things, but I think were mostly okay. Me Da Wikipedian (talk) 21:18, 3 June 2024 (UTC)Reply

Feedback on Pre-Review process

edit


This conversation has been marked for the community's attention. Please remove the {{flag}} when the discussion is complete or no longer important.


We have now had at least 17 pre-reviews on at least 15 articles and counting over the past 2 weeks or so, including at least 8 done by me. As such, I think we have a basic idea of how this process is working. How is it? Authors who have recieved a pre-review (@BigKrow:, @Asheiou:, myself, @Lejar:, @Uju4Ever:, and @Professor Penguino:), is it helpful? Pre-reviewers (@Michael.C.Wright:, myself, and hopefully Asheiou at some point), how is it for you? Reviewers who have reviewed after a pre-review (Asheiou and @Cromium:), was the pre-review helpful to you? Generally, is this process helpful and should it continue?

If you support the continuation of the pre-review process, do you support any changes to the pre-review proposal policy or is it good to go? Should we decide to adopt it, how should we enforce the requirements and how should we grant the permission? Will users be allowed to decide to opt out of pre-review?

Please share any and all feedback about the process. Me Da Wikipedian (talk) 21:07, 14 June 2024 (UTC)Reply

I think the only requirement for pre-review should be auto-confirmation. If the point of a pre-review is to have it open to more people, just creating a tiered pre-reviewer permission is counterintuitive, especially if a permission would have to be applied for. A.S. Thawley (talk) (calendar) 22:07, 14 June 2024 (UTC)Reply
"I think the only requirement for pre-review should be auto-confirmation" - The idea, at least my idea, of pre-review is that people with some idea of what they are doing can help out new users. A user can be autoconfirmed from doing something totally unrelated to writing an article and will likely have no idea what they are talking about. The other requirements were made so that someone at least has a basic understanding of policy, has had articles actually pass review before (you can't review someone elses work on something if you can't do the work yourself), and there recommendations will do more good than harm. The idea of application is just because I think it would be annoying to try to get it granted automatically, but the proposal states that it should be granted to anyone meeting the requirements except in rare cases. @Asheiou Me Da Wikipedian (talk) 22:12, 14 June 2024 (UTC)Reply
My idea of the pre-review "role" was less of a formalized role and more of semi-formalized process anyone could follow, even if they do a poor job of it (at least the first time or two). The goal is to create a pipeline for new reviewers. I think we need as little friction as possible in creating new reviewers without compromising the quality of reviewers.
Having said that, I'm not against a formalized role. I would like to see how consensus develops around it. —Michael.C.Wright (Talk/Published) 17:13, 16 June 2024 (UTC)Reply
I agree. I do think that a bad pre-review can be confusing thought as many people will find up following the incorrect recommendation. As well, at least for myself, by first 10 or so edits were adding punctuation (to a now deleted article). Would you have really thought I would do anything but give useless/harmful recommendations at that point? 5 articles and you’ll at least know enough to be helpful. Activity is avoid pre-reviewers who don’t respond in a reasonable timeframe and given how pre-review is pretty new and changing so they will keep up. @Michael.C.Wright, Asheiou: Me Da Wikipedian (talk) 19:43, 17 June 2024 (UTC)Reply
Yes, it has been very helpful to me, as a new contributor. Lejar (talk) 10:02, 16 June 2024 (UTC)Reply
Awesome. Thanks for the feedback. For me that is a primary mark of success; assisting new contributors understand how things work here, especially given our approach of limited documentation and policies and higher dependence on institutional knowledge. —Michael.C.Wright (Talk/Published) 17:15, 16 June 2024 (UTC)Reply
Totally agree with @Michael.C.Wright:. Honestly, despite all the debate over details of the proposed policy, so far this has been implemented and the people getting pre-reviews, the pre-reviewers, and the reviewers all find it helpful. That is point, lets remember that. @Lejar, Asheiou: Me Da Wikipedian (talk) 19:43, 17 June 2024 (UTC)Reply
Thank you Me Da Wikipedian, for starting this conversation. —Michael.C.Wright (Talk/Published) 17:29, 16 June 2024 (UTC)Reply
Your welcome. Me Da Wikipedian (talk) 19:43, 17 June 2024 (UTC)Reply

NOTE:Asheiou was granted preview status when they should not have been by @Bddpaux: and made 1 review before the status was removed. Me Da Wikipedian (talk) 21:07, 14 June 2024 (UTC)Reply

I can say that in the one review I did, I found the issues highlighted by the pre-review useful for informing my review outcome. I agree with @Heavy Water that pre-review just by its nature can never be used to assure the publishability of a piece, but it can be used to point out things to work on.
My continued hesitancy with pre-review is that all the time spent pre-reviewing could be spent fixing the article to a standard where it can be published. A.S. Thawley (talk) (calendar) 22:05, 14 June 2024 (UTC)Reply
"pre-review just by its nature can never be used to assure the publishability of a piece" - which is why the pre is there. "all the time spent pre-reviewing could be spent fixing the article to a standard where it can be published" - this actually brings up some other interesting questions. Can you pre-review your own article. Also, is can pre-reviewers pre-review an article they fixed up heavily, like I have done at IDF missile strikes UN school and Last civilian hospital closes in Darfur, Sudan? @Asheiou Me Da Wikipedian (talk) 22:08, 14 June 2024 (UTC)Reply
I don't think anyone can effectively review their own work, that's why we do peer-review.
Pre-reviewing something you did lots of work on should be okay, because it's a *pre*-review. An uninvolved editor will still go through and work out any issues a pre-reviewer may have inadvertently introduced. A.S. Thawley (talk) (calendar) 22:17, 14 June 2024 (UTC)Reply
"I don't think anyone can effectively review their own work" and "Pre-reviewing something you did lots of work on should be okay," are sort of contradictory, as if you did a lot of work on it you are kind of reviewing (partially) your own work.@Asheiou Me Da Wikipedian (talk) 22:36, 14 June 2024 (UTC)Reply
[A]ll the time spent pre-reviewing could be spent fixing the article I agree with the general principle. However, a reviewer is limited to how involved they can be in producing an article. There are bright lines such as adding sources that disqualify a reviewer.[5] I think pre-reviews are most valuable when they are done in the context of an actual review. Therefore any recommendation to not publish should mirror why the same article would otherwise fail review, such as WN:Source problems, extensive copyright problems, etc.
A.S. Thawley, you raised that point before and after reading and agreeing with it, I updated the template's documentation by recommending pre-reviewers first "Perform any desired edits to the article to help improve it..." The ultimate goal of a pre-review is to get articles published easily and quickly and therefore correcting as many problems as possible before review is helpful. Maybe I should update the proposed policy (that could also just become a guideline) to reflect that, because it is a very good point. —Michael.C.Wright (Talk/Published) 17:24, 16 June 2024 (UTC)Reply
”I should update the proposed policy” - Please don’t until we can reach a consensus, just so that we have a thing that exists (and stays the same) that we can propose changes to and then make only changes we agree on. @Michael.C.Wright: Me Da Wikipedian (talk) 19:43, 17 June 2024 (UTC)Reply
I also meant to add that pre-reviewing one's own work goes against the spirit of peer review, in my opinion. Authors often read their own words as they intended, not as others might interpret them. An uninvolved reviewer is more likely to spot errors. —Michael.C.Wright (Talk/Published) 17:26, 16 June 2024 (UTC)Reply
"all the time spent pre-reviewing could be spent fixing the article to a standard where it can be published" - by this logic, provided there is another reviewer who could review, reviewers shouldn't give not ready reviews, just fix it. And yet they do.@Asheiou Me Da Wikipedian (talk) 22:49, 14 June 2024 (UTC)Reply
There's no guarantee that another reviewer will actually be available or willing to review something. Not ready reviews given out by actual reviewers are essential to ensure that reviewers don't lock themselves out of reviewing. The difference with pre-review is that a pre-reviewer has no ability to actually publish a piece, so their ready assessment isn't binding. The roles are different. A.S. Thawley (talk) (calendar) 23:08, 14 June 2024 (UTC)Reply
"There's no guarantee that another reviewer will actually be available or willing to review something" - there are certain times you can be reasonably certain. Again, I think that whether or not pre-reviewers can lock themselves out of pre-reviewing does make a difference here and a large one. The other value of a not ready review is if the pre-reviewer doesn't have the time, interest, expertise, to fix it. As well, some choices can be up to the author (problem X can be solved by Y or Z). Furthermore, a not ready review allows the pre-reviewer to give recommendations to the author and reviewer, allowing the reviewer to check if the issue was fixed quickly rather than needing to find it. As well, part of pre-review is to help users gain experience with reviewing, and for reviewers to know how well a job they did. @Asheiou Me Da Wikipedian (talk) 23:16, 14 June 2024 (UTC)Reply
I agree. The pre-review process benefits everyone: reviewers, reporters, and potential reviewers. For example, it helps identify uncertain issues. By using {{pre-review}}, questions can be raised, and observing how reviewers address them provides valuable feedback. This helps reporters avoid future issues and allows reviewers to understand pre-reviewers' capabilities. Ideally, the original author can address potential issues before review, making the reviewer's job easier and faster and hopefully lead to more published articles. —Michael.C.Wright (Talk/Published) 17:28, 16 June 2024 (UTC)Reply

Removal of Microchip08's reviewer tools proposed

edit

After notifications and invites toward the user, I have just now proposed the removal of Microchip08's reviewer tools: Wikinews:Flagged revisions/Requests for permissions/Removal/Microchip08. George Ho (talk) 02:49, 16 June 2024 (UTC)Reply