Wikinews:Water cooler/policy

Page last updated: Tuesday 03 at 0516 UTC.      

Refresh   

Archive

---

Archives 2009  July 2009 August 2009 September 2009 October 2009 November 2009 December 2009 2010  January 2010 February 2010 March 2010 April 2010 May 2010 June 2010 July 2010 August 2010 September 2010 October 2010 November 2010 December 2010 2011  January 2011 February 2011 March 2011 April 2011 May 2011 June 2011 July 2011 August 2011 September 2011 October 2011 December 2011 2012  January 2012 February 2012 March 2012 April 2012 July 2012 August 2012 September 2012 October 2012 November 2012 December 2012 2013  January 2013 March 2013 April 2013 May 2013 July 2013 September 2013 October 2013 2014  January 2014 April 2014 May 2014 June 2014 July 2014 August 2014 September 2014 December 2014 2015  January 2015 February 2015 March 2015 June 2015 July 2015 August 2015 December 2015 2016  January 2016 February 2016 March 2016 July 2016 August 2016 December 2016 2017  January 2017 March 2017 May 2017 June 2017 July 2017 August 2017 September 2017 October 2017 November 2017 December 2017 2018  January 2018 May 2018 June 2018 July 2018 August 2018 October 2018 November 2018 2019  March 2019 April 2019 May 2019 July 2019 August 2019 December 2019 2020  February 2020 March 2020 April 2020 June 2020 2021  July 2021 August 2021 2022  March 2022 June 2022 November 2022 2023  May 2023 June 2023 July 2023 August 2023 September 2023 January 2024 March 2024 April 2024 May 2024 June 2024

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

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)

The goal was that Wikinews would be easy to share. That hasn't really happened, but that's the idea. :/ —Justin (koavf)❤T☮C☺M☯ 16:07, 9 November 2023 (UTC)

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)

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)

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)

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)❤T☮C☺M☯ 20:43, 11 November 2023 (UTC)

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)

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)❤T☮C☺M☯ 16:02, 1 December 2023 (UTC)

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

I vote yes to a vote. —Justin (koavf)❤T☮C☺M☯ 12:12, 14 December 2023 (UTC)

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)

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=history —Justin (koavf)❤T☮C☺M☯ 12:58, 14 December 2023 (UTC)

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)

Not from my perspective. Thanks. —Justin (koavf)❤T☮C☺M☯ 19:42, 14 December 2023 (UTC)

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)

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)❤T☮C☺M☯ 20:44, 14 December 2023 (UTC)
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)
3. I have a strong opposition to using the ShareAlike license, and I am disappointed in @MGA73 to open this discussion which has happened before; SA is not as free and liberal as BY license and instead of forcing us to go to a license we don't want, give a good reason why we should. I fail to see what problems we face when we have CC-BY 2.5 that the big brothers have to budge in and talk about changing the way things are happening.
   •–• 16:32, 26 August 2024 (UTC)

   User:Acagastya Thank you for your input but the idea was that you could vote for one of the three options: Change to cc-by-sa-4.0 (where you placed your vote), change to cc-by-4.0 or stay with cc-by-2.5. It is not force but asking what you prefer. If you prefer a free license then you could also suggest to go back to the original license (public domain). --MGA73 (talk) 16:45, 26 August 2024 (UTC)

   There wasn't a general consensus for 'SA' and we have recently been discussing closing this portion of the conversation based on the Sum up per march 2024, which indicates a consensus formed around Yes, WN upgrade to CC-BY-4.0 if the the other WN also upgrade. We have since moved forward with that as a general consensus—see discussions 1.8, 1.9, and 1.10 below.

   The goal of the upgrade is to take advantage of upgrades to the license itself, from 2.5 to 4.0. These benefits were discussed in December.[1] Should we hold off on closing this portion of the discussion to allow others to re-engage in it? If so, we would likely also need to move the roughly-agreed-upon date of upgrade to a later date. I believe other language projects are timing their upgrade dates based on ours.

   Since you are an administrator, we could also use your assistance in preparing pages for the upgrade. We have an open request for administrators at the following discussion: Wikinews_talk:Copyright#Pages_to_update_when_license_is_updated_from_2.5_to_4.0. There are details there of the edit-protected changes we need and myself or MGA73 could answer any specific questions about those changes. Alternatively, specific edit-protected pages could be temporarily unprotected and I can make the changes myself.

   Thank you in advance for any help you can provide. —Michael.C.Wright (^Talk/_Published) 17:41, 26 August 2024 (UTC)

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

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)

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)

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)

   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)

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)

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

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.[2] Previously unsigned comment by Michael.C.Wright (^Talk/_Published) 20:50, 24 February 2024‎ (UTC)[3]
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)
   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)
4. Support. A.S. Thawley (talk) (calendar) 03:10, 3 June 2024 (UTC)
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)

Comments

• "And I would advocate for using a separate license for spoken articles."

  Why is this, Xbspiro? And which license? —Justin (koavf)❤T☮C☺M☯ 12:28, 15 December 2023 (UTC)

  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)

  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)

• "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)

All notified. At least those not closed. --MGA73 (talk) 13:51, 15 December 2023 (UTC)

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)

• 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)

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)

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)

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)

• 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)
• 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)

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)

• 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)

  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)

  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)

  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)

  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)

  Is there no consensus? Or is the discussion not active?… Kitabc12345 (talk) 13:42, 1 January 2024 (UTC)

  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)

  I hope everyone will be active in the discussion. Kitabc12345 (talk) 11:59, 3 January 2024 (UTC)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

@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)

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)

@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)

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)

(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)

Do we have someone who knows how to do it? There could be as many as 4,600 articles in en.wikinews[4] 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)

@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)

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)

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)

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)

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)

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

@MGA73 Do you have any follow-up on this? I think this is also very important. Kitabc12345 (talk) 19:49, 25 August 2024 (UTC)

Kitabc12345 I have not checked this but I see no reason why it should not be possible. It should be no different than using files that can also have another license than the text. --MGA73 (talk) 04:26, 26 August 2024 (UTC)

@MGA73 The problem is that if the templates are part of the main text, but those templates have copyright agreements that are inconsistent with the rest of the content, it could create significant complications? Kitabc12345 (talk) 07:11, 26 August 2024 (UTC)

The key questions that need to be addressed are:

1. If a template is part of the main content, but the copyright license of the template is different from the rest of the content, how should this be handled?

2. How should the text within the template itself be treated in terms of licensing?

3. What is considered the "main content" versus "embedded templates"? Is the discussion page also part of the "main content"?

4. How can readers clearly differentiate between content under different licenses within the same page?

5. The person asking the questions suggests consulting the ENWN community to get their input on resolving these copyright and licensing challenges. Kitabc12345 (talk) 07:25, 26 August 2024 (UTC)

Other sites, including this one, typically use content released under more permissive licenses (e.g. CC0) and apply the terms of a more restrictive license (e.g. CC-BY-SA / CC-BY). Even if the more permissively licensed content is used in accordance with the stricter requirements, there would be no copyright issues. They say. Kitabc12345 (talk) 07:33, 26 August 2024 (UTC)

Kitabc12345 I doubt it is possible to give a clear and answer that will fit in all cases. But take a template like

Cry "Havoc," and let slip the dogs of war. —William Shakespeare, Julius Caesar, Act III, Scene I.

I think the code used on the page Template:Quote_box to generate the template can have one license and the text added on the article (Here: Cry "Havoc," and let slip the dogs of war.) will have another license. And templates like Template:NowCommons is not a part of the articles so I would say the code and the text there could be cc-by-sa-4.0. The problem is if someone make a template that include a lot of text and that template is included in articles. In those cases I think you have to judge if it is copyrightable text or not the same way you would if you were to copy the text from Wikipedia without including the actual template. --MGA73 (talk) 10:57, 26 August 2024 (UTC)

The issue is, if the templates are part of the article body but the copyright agreements of those templates are inconsistent with the rest of the main page content, what can be done in this situation? Kitabc12345 (talk) 12:26, 26 August 2024 (UTC)

@MGA73 It seems that the template source code may be licensed in other ways, but if it is used on a page, how would you want to indicate that? Kitabc12345 (talk) 12:37, 26 August 2024 (UTC)

Kitabc12345 I think that the text in MediaWiki:Copyright and Wikinews:Copyright can be updated but how is a good question. But perhaps just a short text saying “Copyright on other content than articles and images is generally cc-by-sa-4.0 unless otherwise specified.” I do not think we need to indicate that the code in the template is licensed differently from the article. Because if someone would go to India wins T20 men's cricket world cup against South Africa and click edit to copy the text then what they will get is for example {{cricket}} and that short text is probably ineligible for copyright. If they then go to Template:Cricket then they are no longer in the article name space but even if they do and the click edit then they just get a lot of code. If they copy paste the visible text from the template then I would say it is cc-by-2.5. But the worst thing that could happen is that someone think that it is cc-by-sa-4.0 and it would mean they get the SA part that they do not need. If needed there can be a longer text at Wikinews:Copyright illustrating the difference. --MGA73 (talk) 13:04, 26 August 2024 (UTC)

The Chinese Wikinews community wants to use more simple tools, scripts, and templates from Wikipedia to reduce our workload. Can we use templates licensed under CC BY-SA 4.0? If we switch to CC BY 4.0 on our website. Kitabc12345 (talk) 13:36, 26 August 2024 (UTC)

@Kitabc12345, It is my understanding that if you use content licensed as "SA," you must also license that content as "SA."

I agree with Kitabc12345 and MGA73's comments above, in which we understand the text of a template to be source code that can carry a different copyright license than the content it generates within the body of an article. However, I will also add that if it adds complication and further delays to the update project, maybe it's better to keep it simple in order to get it done. We currently don't have much admin support here at en.WN. Maybe keeping the update project as simple as possible will make it easier for an admin to step in and offer support or easier for us to get outside involvement from Meta. We could always revisit the topic later if-and-when we have better support. —The preceding unsigned comment was added by Michael.C.Wright (talk • contribs)

Yes if someone want to copy w:Module:Citation/CS1 here it would be a shame if the license prevented that. I guess you could add a message in the code that "This module is copied from English Wikipedia on <date> and it is licensed cc-by-sa-4.0. See edit history <link> on English Wikipedia for the authors." Same with Twinkle and all other tools etc. It should be possible to find a solution that does not prevent an update of the license to 4.0. So lets keep it simple :-) --MGA73 (talk) 14:43, 26 August 2024 (UTC)

I agree that we should first complete the work to upgrade all Wikinews language versions ( if they didn’t say to no) , including the English Wikinews, to the CC BY 4.0 license. But I hope we can continue to discuss this solution, as the Chinese Wikinews desperately needs the ability to cross-post content from the Chinese Wikipedia, including handling the conversion of traditional/simplified characters and regional terminology, as these evolve over time, but we have never been able to do this independently due to our small community and inability to maintain the different regional Chinese vocabulary conversions that people commonly use across the cross-strait and other regions. I believe this is also a reason why other language Wikinews projects hope to cross-post content from Wikipedia - their language communities are simply too small to independently write their own content, or even develop simple tools, scripts, and templates. This makes it very difficult for reporters. Kitabc12345 (talk) 15:20, 26 August 2024 (UTC)

Kitabc12345 I do not understand how the Chinese code/system works but I think that if Chinese Wikinews want to allow different licenses then you can do that indepently from what English Wikinews decide. It does however require that it is possible to explain to the reuser which license to use. --MGA73 (talk) 15:56, 26 August 2024 (UTC)

I know. Thanks. If Wikinews uses CC BY 4.0, even if the source code of simple tools, scripts, and templates like w:Module:Citation/CS1 in Wikinews states that it is published under CC BY SA 4.0, there may still be copyright concerns? If not, it seems that this issue could be resolved. I wonder if there are any professionals to ask about this. If we or other language versions of Wikinews upgrade to CC BY SA 4.0, can we use the content from the English Wikinews, which is under CC BY 4.0?Kitabc12345 (talk) 16:02, 26 August 2024 (UTC)

Kitabc12345 If you change to cc-by-sa-4.0 then you can still use text licensed cc-by-4.0 but wikis that use cc-by-4.0 can't use text licensed cc-by-sa-4.0 per https://wiki.creativecommons.org/wiki/ShareAlike_compatibility --MGA73 (talk) 16:38, 26 August 2024 (UTC)

However, I believe we just need to insert in the source code: “This module is copied from English Wikipedia on <date> and it is licensed cc-by-sa-4.0. See edit history <link> on English Wikipedia for the authors.” If that can be done, it’s quite simple and not too complicated. I’m not sure if it’s legal, but I know mixing different copyrights is allowed. I did check, and it seems to be legal, but I'm not completely certain. Kitabc12345 (talk) 19:04, 26 August 2024 (UTC)

But I don't know if it will affect its legality if the readers on the main page are unaware? Or not? I'm not sure if there are better ways to know how to update MediaWiki:Copyright and Wikinews:Copyright. I have some ideas for practical ways to do this. Just give me a bit of time to refine them. Kitabc12345 (talk) 19:18, 26 August 2024 (UTC)

It seems that template source code can adopt various licensing methods. Here are some suggestions for marking licenses on pages:

1. License Notice

Add a license notice at the top of the template source code, stating its license (e.g., "This template is licensed under CC BY-SA 4.0").

2. Comments in Source Code

Include comments in the template source code specifying the license for editors to view.

3. Template Parameter

Include a template parameter to output the license information, which can be embedded in pages:

{{license_info}}

Alternatively, use a parameter in the template for automatic embedding in page footers or MediaWiki:Copyright:

This page uses the template published under {{license_info}}.

4. Dedicated License Page

Create a dedicated page listing all templates and their corresponding licenses. This can be linked in copyright statements Wikinews:Copyright or MediaWiki:Copyright:

Copyright Notice

This site uses multiple templates, (Name 1), (Name 2), (Name 3)/ all following the CC BY-SA 4.0 license. For more details, see [Template License Page].

If we don't list them individually, I also provided other methods to directly link to a dedicated page that clarifies how readers can know which templates use which licensing methods. If we list them, it will be done automatically, and if tools, scripts, and code for templates aren't used, they shouldn't be displayed. Let’s license tools, scripts, and code for templates differently from article content.

Technological Solutions

With today's technology, tools should be available to automatically list the templates used and their licenses at the bottom of each page or in the footer copyright statement. If such tools aren’t available, the traditional method would involve modifying each page's footer to link to a dedicated page listing all template licenses.

Ideas for Implementation

1. Using Wiki Templates

Add a copyright/license template to the bottom or header of Wiki pages to dynamically populate license information for consistency.

2. Wiki Extensions/Plugins

Develop a Wiki extension or plugin to scan page content and generate copyright information, integrating this into the editing and publishing process. Existing extensions like "Pageinformation" and "Variables" may serve as references.

3. Dedicated Namespace

Create a "Copyright" or "License" namespace in the Wiki and link to these namespaces on relevant pages to centralize copyright information. Templates or Lua scripts can automate link generation.

Creating a Copyright Template Page

4. Template Structure

Create a page such as Template:Copyright to define the structure and content of the copyright statement template.

Template Content Design

Use Wiki template syntax to define the format, including information like copyright holder, license type, and effective date. Variables or template parameters can dynamically insert specific content.

Example Template:

{{Copyright2

|holder=Example Wiki

|license=Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)

|date=2024

}}

Referencing and Deployment

Template Usage: On Wiki pages needing a copyright statement, insert a call to the copyright template at the bottom or MediaWiki:Copyright:

{{Copyright2}}

Testing and Deployment / Maintenance and Updates:

Test the rendering of the template to ensure correct display of copyright information. Develop a process for deploying the copyright template to all relevant pages, considering automation for bulk updates. Regularly check and update the copyright template for accuracy regarding copyright holders and licenses. Ensure all relevant pages reference the latest copyright template and establish processes for any copyright policy changes. Kitabc12345 (talk) 19:41, 26 August 2024 (UTC)

I asked for clarification on the licensing differences between CC-BY-4.0 and CC-BY-SA-4.0 because some users wanted to understand it better, even though I had already grasped the concept a few years ago. I'm really sorry. Kitabc12345 (talk) 19:10, 26 August 2024 (UTC)

We do have a number of copyright templates already,[5] so your suggestion of placing a license template will work fine. Those can be used in template documentation when a template with a non-standard (to en.WN) is copied.

I think we can continue with our upgrade project under the assumption we're moving forward with CC-BY-4.0 and we can later tackle exactly how to designate templates licensed with a different CC version within their documentation.

At the moment, we're so thin in users that I don't see that being a problem any time soon. —Michael.C.Wright (^Talk/_Published) 13:35, 27 August 2024 (UTC)

Sum up per march 2024

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)

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)

Anyone? --MGA73 (talk) 14:04, 11 May 2024 (UTC)

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)

I can get behind an upgrade to by-4.0. A.S. Thawley (talk) (calendar) 19:13, 13 May 2024 (UTC)

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)

I have now written to all languages linked to d:Q16503. --MGA73 (talk) 15:56, 26 May 2024 (UTC)

I just became aware of this duscussion and will read it within next few days. Please note that Meta contributors do not govern Wikinews. Gryllida (talk) 12:26, 23 August 2024 (UTC)

Gryllida yes Wikinews decide not meta. But as far as I know the choice to change from PD to cc-by-2.5 was made based on a vote on meta. And if there is a wish that all WN have the same license then I can think of no better place to discuss than on meta. --MGA73 (talk) 14:03, 23 August 2024 (UTC)

I found m:Wikinews/Licensure Poll in case anyone is interessted in history :-) --MGA73 (talk) 17:18, 23 August 2024 (UTC)

As well as Wikinews/License straw poll with some additional explanations. Ankermast (talk) 17:25, 23 August 2024 (UTC)

@MGA73 where was it discussed on Meta, if it was? Gryllida (talk) 10:26, 25 August 2024 (UTC)

Gryllida At m:Wikinews/Licensure Poll there is a link to m:Wikinews/License and m:Wikinews/License straw poll. But I have not checked in details because I do not think it is important now as long as no vote is started on meta. --MGA73 (talk) 10:49, 25 August 2024 (UTC)

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)

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)

• 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)

@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)

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)

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)

@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)

@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)

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)

┌─────────────────────────────────┘
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)

I wanted to inform you that the Polish version has started voting on changing the version. We will have a stand on August 20. Kajtus von Rzywiec (talk) 02:40, 22 July 2024 (UTC)

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)

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)

Differences between 2.5 and 4.0 according to ChatGpt

@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)

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)

(прошу прощения за русский язык) Тема перехода на новую лицензию очень важно. И глупо обсуждать различия между лицензиями, опираясь на советы 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)

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)

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)

Hi Marek, MGA73, did WMF provide a clarification about difference between licenses version 2 and 4? I think based on above, it needs to stay without SA. Gryllida (talk) 12:32, 23 August 2024 (UTC)

Gryllida I have not asked WMF but they have supported upgrade from 2.5 to 3.0 and now to 4.0. Since it was done in 2 steps I do not think anyone have compared 2.5 vs 4.0 directly this time. --MGA73 (talk) 13:57, 23 August 2024 (UTC)

@MGA73 This was, to my surprise, discussed since January this year.

• It could be good to know the differences. I wrote somewhere that the voting was compromised by editing of vote section names. I don't know what was edited.
  • I think it would be fair to obtain this information and then run the poll again, properly this time, with sufficient information provided for each option impact.
  • Another option is to ignore the precise differences and follow up with each voted person and ask them to confirm that after the renaming of options they are comfortable with leaving their vote where it is.
• Someone mentioned it being discussed at Meta or possibly going to be discussed at Meta. It would be good to have details.

I am traveling and will check in more details when I am home in a few days. Gryllida (talk) 10:34, 25 August 2024 (UTC)

The discussion started in November 2023 so it has been almost a year. It was also announced on Wikinews:Admin_action_alerts/Archive_12#Closing_a_vote in July.

It is correct that there was a change shortly after the start: See Special:Diff/4759163 (17 December 2023). And I send a ping to User:Koavf, User:Xbspiro, User:Heavy Water and User:Base that were the only ones that had made a vote at that time.

I do not think we need a new vote. 2 of the users have edited since then so if they wanted they could change their vote. 2 other users have not edited since so if we make a new vote they are not likely to vote. They voted for an option that did not get most of the votes. So if they change their vote (or make no new vote) it will only make the concensus to change to 4.0 more clear. If they had voted on the willing choise I would agree that it could change the outcome with a new vote.

But if they see this it would be great if they would make a statement if they want to change their vote or not. --MGA73 (talk) 11:08, 25 August 2024 (UTC)

I have no change. —Justin (koavf)❤T☮C☺M☯ 11:18, 25 August 2024 (UTC)

Conclusion and implementation of upgrade to cc-by-4.0

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)

I got a reply on meta that what needs to be changed is a configuration change in https://phabricator.wikimedia.org/source/mediawiki-config/browse/master/wmf-config/InitialiseSettings.php$10828 and an edit to MediaWiki:Copyrightwarning. So now we have all info on what to change. --MGA73 (talk) 07:05, 25 June 2024 (UTC)

I've added both to our master list here: Wikinews_talk:Copyright#Pages_to_update_when_license_is_updated_from_2.5_to_4.0.

I am unsure who should edit the phabricator page. Do we request that once we're ready or is it our responsibility to maintain that page? —Michael.C.Wright (^Talk/_Published) 13:52, 25 June 2024 (UTC)

Michael.C.Wright We make a request in https://phabricator.wikimedia.org/ and ask them to fix. We just link to this discussion. --MGA73 (talk) 17:07, 25 June 2024 (UTC)

It would be great if you set a date for changing the license and announced it earlier. Our vote included the question "do you support changing the license if en.wikinews changes it?" and we stipulated that the change will enter into force simultaneously with your language version to maintain compatibility. Kajtus von Rzywiec (talk) 23:26, 24 July 2024 (UTC)

We'll need an admin to complete the migration as we have several pages that are edit-protected. We've made multiple requests, even directly in some cases. So we unfortunately are in a holding pattern. —Michael.C.Wright (^Talk/_Published) 13:35, 25 July 2024 (UTC)

To give other projects a chance I think the date should be September 1, 2024. Enwiki could do it to August 1 but since there have been no formal closure and no formal date set then it will be hard for other wikis to do it in time. --MGA73 (talk) 14:59, 25 July 2024 (UTC)

I still think it would be best if an admin make a formal conclusion with a date. Anyone? --MGA73 (talk) 16:26, 9 July 2024 (UTC)

I agree. To help; August 1 was floated above and is now only a few weeks away but easily doable. We've done a lot of the work upfront by identifying pages that need updated and prepping many for easier update. That list as well as instructions can be found here: Wikinews_talk:Copyright#Pages_to_update_when_license_is_updated_from_2.5_to_4.0.

Any admin who finalizes a date and closes this discussion, could do us a huge solid and go through the list and update any of the remaining, protected pages using the instructions at the link above. Many thanks @MGA73 for your help and perseverance and also many thanks to any admin who helps! —Michael.C.Wright (^Talk/_Published) 16:40, 9 July 2024 (UTC)

Since August 1 has passed thats no longer an option. I checked pl and it looks like support there too. If other wikis need 1 month to prepare perhaps October 1 is now the new target? --MGA73 (talk) 08:18, 4 August 2024 (UTC)

Hopefully @Cromium is indeed able to help. If so, I think they should set the date for when they can have the requested edits[6] completed and also be "on-hand" for any unforeseen problems after the cut-over.

I personally would prefer sooner rather than later; simply to git 'er done. I will be on-hand to help however I can to facilitate that. I anticipate being away from the project for much of late September and most of October, just FYI. —Michael.C.Wright (^Talk/_Published) 16:22, 4 August 2024 (UTC)

Ar.wikinews had a vote and they decided to upgrade to cc-by-sa-4.0. --MGA73 (talk) 08:33, 18 August 2024 (UTC)

Non-admin or non-bureaucrat closure?

Does it say anywhere that it has to be an admin or a bureaucrat that have to close a vote? If not perhaps another trusted user can close this vote?

Or should we just wait and see? Or perhaps just give up and maybe try on meta? What do you think? --MGA73 (talk) 16:23, 14 August 2024 (UTC)

I'm not sure about requirements for closing a general vote. I do know that it is implied that only admins should close a vote for Wikinews:Deletion_requests.

Either way, we need an admin to make the edits to edit-protected pages before we can proceed. Even if we vote on a date and close the vote, without an admin, we'll miss the date. —Michael.C.Wright (^Talk/_Published) 17:11, 14 August 2024 (UTC)

Yes an admin needs to edit the pages that are protected. But if a vote is closed in a valid way then I see no reasons why admins should not help make the changes. If the change has to happen on a specific time and date and no admins are active at that time then we could perhaps ask for help on meta. --MGA73 (talk) 17:42, 14 August 2024 (UTC)

I can find no explicit requirement that an admin must close polls and I have asked an admin.[7] We also don't have any active admin at the moment who are willing to engage in this project, despite requests by both myself and MGA73.[8], [9], [10], [11], [12]

This is not meant to 'call out' anyone or point fingers in blame. It is merely meant to demonstrate that we have done our due diligence seeking help locally before seeking help from Meta. It is understood that this is a project of volunteers.

I propose we close the polling/voting section tomorrow, August 22nd with the following conclusion:

A vote was used to guide discussion and gauge consensus, not to define it. Based on the Sum up per March, 2024,[13] there is general consensus for Yes, WN upgrade to CC-BY-4.0 if the the other WN also upgrade. After formally concluding the consensus-making process, a deadline for upgrading to CC-BY-4.0 is set for October 1, 2024.

I am willing to close sections 1.1 through 1.8 using the {{archive-top}} and {{archive-bottom}} convention, leaving section 1.9; "Comments from other wikis" open for continued project management.

Are there any objections or further feedback? —Michael.C.Wright (^Talk/_Published) 16:08, 21 August 2024 (UTC)

Thank you. I doubt it will be possible to make ALL the other WN to upgrade too because some are almost dead. It might help if we send out a final notice to all projects that "English WN have decided to change license per 1st xxx 2024 provided the at least x other WN also change license. So please leave a notice at <link to 1.9> if your WN will also change." --MGA73 (talk) 16:16, 21 August 2024 (UTC)

So is the requirement for enwikinews to change that the other languages change to CC-BY-4.0 or only that they update to the newest version and change to BY-SA-4.0? Best regards, --Ankermast (talk) 16:25, 21 August 2024 (UTC)

@Ankermast, I don't believe there is a strict requirement in either direction. En.WN can't mandate actions from other projects, and I don't think anyone is attempting to do so (at least I hope not). Hopefully other projects share that view. As I understand it, the goal is to ensure that content can be easily shared and/or translated between projects and beyond. There is general consensus that using SA is not compatible with projects that do not use SA. En.WN chose not to implement SA, as it was understood to create additional barriers to sharing. En.WN would like to make content as shareable as possible.

@MGA73, are you reading "Yes, WN upgrade to CC-BY-4.0 if the the other WN also upgrade" as a requirement for other WN to upgrade? I don't see where we discussed at any length what constitutes or satisfies 'other WN also upgrading.' In hindsight, maybe we should have. Should we clarify the closing conclusion to something like the following?

A vote was used to guide discussion and gauge consensus, not to define it. Based on the Sum up per March, 2024,[14] there is general consensus for Yes, WN upgrade to CC-BY-4.0 if the the other WN also upgrade. After formally concluding the consensus-making process, a deadline for upgrading English Wikinews to CC-BY-4.0 is set for October 1, 2024 to allow other active projects to determine how and what CC version to upgrade to.

—Michael.C.Wright (^Talk/_Published) 19:05, 21 August 2024 (UTC)

@Michael.C.Wright Could you please confirm if this conclusion is finalized? Kitabc12345 (talk) 20:04, 26 August 2024 (UTC)

I am now waiting for the two conversations that recently re-kindled in sections 1.2 and 1.4 to come to a conclusion. If @Acagastya is okay with where the conversation is in 1.2, then I think we can close sections 1.1 through 1.8 (which will effectively close the poll, even for additional comments). Acagastya is an administrator, so their input in both the conversation as well as the question of who and how to close the poll would be valuable. I don't want to jump the gun on closing it nor make a procedural error by closing it as a non-admin, though I don't see that as a requirement—I could be missing something. —Michael.C.Wright (^Talk/_Published) 13:50, 27 August 2024 (UTC)

Comments from other wikis

Note: I think it makes sense to collect all the comments from the other wikis here. --Ankermast (talk) 19:38, 20 August 2024 (UTC)

German: Hi everyone, I can tell you that there is interest in an update for German Wikinews, which has already been discussed. There are still some doubts about the documentation obligation, though. Best regards, --Ankermast (talk) 19:38, 20 August 2024 (UTC)

Thank you Ankermast. Can you link to the discussion? I thought of listing discussions/results on User:MGA73/Licenseupgrade but here is also fine. About documentation I do not know if m:Terms_of_use/Creative_Commons_4.0/Legal_note#Mechanism_for_the_upgrade can help? --MGA73 (talk) 19:48, 20 August 2024 (UTC)

The proposal is discussed below your message from May: n:de:Wikinews:Pressestammtisch#Update of license to cc-by-4.0. Ankermast (talk) 19:52, 20 August 2024 (UTC)

Arabic: Per the vote on ar:ويكي_الأخبار:الميدان#مقترح_تحديث_رخصة_ويكي_الأخبار They will change to Cc-by-sa-4.0. --MGA73 (talk) 19:57, 20 August 2024 (UTC)

The have changed per phab:T372730. --MGA73 (talk) 15:20, 21 August 2024 (UTC)

Does this mean that all articles are also licensed retroactively? Best regards, Ankermast (talk) 20:23, 21 August 2024 (UTC)

As I understand m:Terms_of_use/Creative_Commons_4.0/Legal_note#Mechanism_for_the_upgrade then only new edits are licensed 4.0. Existing text is still 2.5 (or PD if it is very old). --MGA73 (talk) 21:06, 21 August 2024 (UTC)

I asked because it is not shown that the earlier texts were contributed under 2.5. Ankermast (talk) 21:09, 21 August 2024 (UTC)

Polish: The poll on whether the license should be changed is going to end today. --Ankermast (talk) 20:01, 20 August 2024 (UTC)

We have it Kajtus von Rzywiec (talk) 01:08, 21 August 2024 (UTC)

Chinese: Seems to be positive about a change to cc-by-4.0. But perhaps User:Kitabc12345 can give an update? --MGA73 (talk) 20:14, 20 August 2024 (UTC)

Esperanto: ni estas por VladimirPF (talk) 21:11, 20 August 2024 (UTC)

Thank you VladimirPF! Do you have a link to the discussion? --MGA73 (talk) 05:11, 21 August 2024 (UTC)

La diskuto estis ekster vikinovaĵoj ĉar ĉe ni aktivas malmultaj personoj. Tamen, se estas bezonata mi povas organizi la diskuton kaj peti voĉdoni. VladimirPF (talk) 08:57, 21 August 2024 (UTC)

Thank you. I do not need a discussion but I do not know if it is needed for a change in phabricator. --MGA73 (talk) 11:42, 21 August 2024 (UTC)

VladimirPF Please check m:Requesting wiki configuration changes. I think the best is to start an on wiki discussion to meet the requirements. --MGA73 (talk) 15:24, 21 August 2024 (UTC)

Can we request a license change for other wikis?

I have noticed that on m:Requesting_wiki_configuration_changes#How_to_request_a_change #3 it says “In the case of a very small and low-activity community, it should be enough to show that you have tried to gain consensus, and that you have given an opportunity for objections.”

I have send messages to all wikis suggesting an update (see User:MGA73/Licenseupgrade) and on many wikis there were no response and therefore no objections. However I think before we can request a license update for other Wikinews there should at least be a more clear message in local language.

What do you think? Could that be an option to make sure that WN will have the same license after an upgrade?

In case any WN do not wish to upgrade they can very easily avoid that by simply saying "No". --MGA73 (talk) 17:51, 23 August 2024 (UTC)

We should point out that the hurdle to change is quite low for small communities (as this is the case for many Wikinews wikis). Ankermast (talk) 18:06, 23 August 2024 (UTC)

By the way: Would it be okay if I updated the list in your namespace? Ankermast (talk) 18:08, 23 August 2024 (UTC)

Yes please do! --MGA73 (talk) 18:09, 23 August 2024 (UTC)

I'm considering requesting modifications to the copyright agreements for different language versions of Wikinews that we have already given an opportunity to oppose. The challenge is how to indicate on their own Wikis that "previous articles were published under the old agreement" in their own language. Additionally, we have provided ample time for them to express any objections, but I believe we could use machine translation or AI translation to communicate this in their original language. After all, some of the non-responsive Wikinews versions likely have inactive communities. The worst-case scenario is that these projects could be closed by Meta-Wiki. Kitabc12345 (talk) 06:58, 26 August 2024 (UTC)

It is recommended that open a global RFC on metawiki and send a notification again. If there is no objection, then the global community can force an update of the license on these wikis. Thanks. SCP-2000 (talk) 08:39, 26 August 2024 (UTC)

Kitabc12345 and SCP-2000 Yes it may be the best way to do it on meta. I have not thought much of a wording of such an RFC but it could be something like "All Wikinews change to cc-by-4.0 on October 15, 2024 unless a wiki specifically choses otherwise. Vote will end at October 1." Any Wikinews that does not want to change to cc-by-4.0 can then just say "XX-Wikinews have decided to stay at cc-by-2.5 / change to cc-by-sa-4.0 per <link>." I do not know if 1 month to vote is enough and if 15 days after that is enough to change all Wikinews but whoever make the RFC can decide :-) --MGA73 (talk) 11:20, 26 August 2024 (UTC)

I support this proposal. Kitabc12345 (talk) 12:27, 26 August 2024 (UTC)

Comment from Gryllida

Comment Side note, I saw this and postponed it in my mind given the more urgent task of publishing. May take more than a day to resolve. Your help copyediting new submissions, helping others copyedit, and adding (and discussing) Reviewer nominations is welcome. I hope the licensing discussion can wait till then. Gryllida (talk) 12:05, 30 August 2024 (UTC)

Feedback on Pre-Review process

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, @Tom Morris:, @Heavy Water, 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)

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)

"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)

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)

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)

Yes, it has been very helpful to me, as a new contributor. Lejar (talk) 10:02, 16 June 2024 (UTC)

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)

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)

Thank you Me Da Wikipedian, for starting this conversation. —Michael.C.Wright (^Talk/_Published) 17:29, 16 June 2024 (UTC)

Your welcome. Me Da Wikipedian (talk) 19:43, 17 June 2024 (UTC)

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)

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)

"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)

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)

"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)

[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.[15] 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)

”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)

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)

"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)

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)

"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)

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)

I was persuaded by Michael.C.Wright's comment above that this could be a good thing. I looked to poke holes in it and it seems like a solid proposal, mostly. But I would prefer pre-reviewers to need to be a MediaWiki user group with formal approval, on further thought. That's the only way I can see to guard against situations where people completely ignorant of what they're talking about, even if well-meaning, give schlocky pre-reviews, reporters don't know that the advice is inaccurate or incomplete, and experienced users have to go in and explain what the pre-reviewer got wrong. Whereas if pre-reviewers are required to have at least some experience, they're less likely to give poor advice and cause further trouble, and if they do that — which they probably would, sometimes — there's a lot less they need to be corrected on. I think they shouldn't be able to pre-review articles they'd worked on significantly (judged by the same standards as for reviewers), for the reasons stated above of leaving choices up to the reporter and of the benefit of peer review, and also because reporters, to the extent possible, should learn by doing of having to fix problems with their articles. Heavy Water (talk) 06:10, 20 June 2024 (UTC)

" I would prefer pre-reviewers to need to be a MediaWiki user group with formal approval" I think that would be a bit difficult (anyone, please contradict me if I'm wrong) to get for 1 relatively inactive site. "the only way I can see to guard against situations where people completely ignorant of what they're talking about, even if well-meaning, give schlocky pre-reviews" - I think my idea of 5 articles including 1 in the last month and autoconfirmation, as well as a small bit of admin discretion (or however would give this should we make it more formalized).

I completely agree with you. I would say that it is optimal to have a formalized group, however it would not be by community consensus (as those are so hard to get around here), just the granting admin. Here is something else. So far, both of our pre-reviewers have made minimal errors, none of which caused too much damage. Allowing any autoconfirmed user to pre-review (which would through a bit of estimation be around 140,000 users or so) would result in the vast majority of pre-reviewers having no idea what they are doing. No pre-review would be better than this.@Heavy Water@Asheiou Me Da Wikipedian (talk) 10:07, 20 June 2024 (UTC)

After 1 week

After 1 week, here's what we have agreed on:

1. Unanimous consensus that a pre-review process should exist in some form
2. Unanimous consensus that pre-reviewers should be able give a recommend publish review
3. Unanimous consensus that pre-reviewers may not pre-review they're own articles.
4. Unanimous consensus that pre-reviewers must be auto-confirmed or confirmed

Here's what we have a disagreement on:

1. Can Pre-Reviewers give out Not-Ready pre-reviews?
2. Can Pre-Reviewers pre-review an article they have worked heavily on?
3. Should there be other requirements for pre-reviewer (other than confirmed/autoconfirmed) and if so what should they be?
4. Should Pre-Reviewer be a formalized group?

From this point forwards, pre-reviewers should follow the 4 statements above that we have agreed to. Me Da Wikipedian (talk) 11:33, 21 June 2024 (UTC)

@User:Heavy Water said But I would prefer pre-reviewers to need to be a MediaWiki user group with formal approval, on further thought. How do we make that group—who would we task to do so, an admin? If we are making a new group of pre-reviewers, should we attach 'patroller' privileges to that new group? See also: Wikinews:Water_cooler/policy/archives/2024/April#Additional_Checkusers_and_maybe_patrollers Patrolling new pages seems like a good fit for "pre-reviewers." Michael.C.Wright (^Talk/_Published) 14:23, 22 June 2024 (UTC)

Below are my responses to the open items listed above:

1. Can Pre-Reviewers give out Not-Ready pre-reviews?
   • I think a pre-reviewer's ability to recommend in both directions (publish/not ready) is vital.
2. Can Pre-Reviewers pre-review an article they have worked heavily on?
   • I think a pre-reviewer, as a peer reviewer, must maintain distance just as a reviewer must.
3. Should there be other requirements for pre-reviewer (other than confirmed/autoconfirmed) and if so what should they be?
   • We should make it very easy to give (and remove) pre-reviewer privileges. Otherwise we ultimately make it harder to give reviewer privileges. Therefore, in my opinion, fewer requirements are likely better than more.
4. Should Pre-Reviewer be a formalized group?
   • I feel like it adds a hurdle to require a collective decision to allow one to pre-review an article. But I see the potential damage a poor review can do. I (grudgingly) agree a formalized group would mitigate that risk.
   • Question Should all pre-reviews stop now that we are converging on consensus in favor of a formalized group?

Michael.C.Wright (^Talk/_Published) 14:39, 22 June 2024 (UTC)

"Should all pre-reviews stop now that we are converging on consensus in favor of a formalized group" - No. A few reasons:

1.Further pre-reviews are still providing benefit

2.More pre-reviews means more of a "sample" to know how well pre-review works

3.I believe that no one has suggested guidelines/requirements that any current pre-reviewer does not meet

Patroller actually seems like a great idea to add to the "pre-review package". I agree that fewer requirements is better. I'll explain why I think the 3 I gave are needed though.

Autoconfirmed:To allow them to be able to move the page, which sometimes does need to be done. Not a huge detail...but considered other requirements they'll probably have it anyways

5 articles:So that they will actually have knowledge about WikiNews. You can teach what you don't know yourself.

1 article in the past month:So that we only get people who are semi-active as pre-reviewers. Also to avoid someone who hasn't been here in 10 years getting pre-review and also probably not knowing what they're doing. And, of course, there are some people who could have gotten 5 articles even before peer-review was made. Keep in mind that we do have "rare cases" in there, and our admins can use common sense.

Here is actually another question:When review permissions are removed through PEP, are they automatically a pre-reviewer? Is there PEP for pre-reviewers?

@Michael.C.Wright Me Da Wikipedian (talk) 10:27, 23 June 2024 (UTC)

@Cromium as you have conducted the vast majority of reviews after a pre-review, do you have an opinion? Me Da Wikipedian (talk) 01:09, 28 June 2024 (UTC)

I'm just reading this and I don't understand why pre-review even exists as a separate category. I can always edit an article and leave a message on talk page. Why does it have to be marked as 'pre-review'? Gryllida (talk) 04:49, 21 August 2024 (UTC)

@Michael.C.Wright is honestly better at explaining it than I am, but basically pre-review has more goals than that which leaving a message or editing won't fulfill:

1.Improve the chances of the article passing review. Editing and talk page messages will help here, but a pre-review is more formalized in that the pre-reviewer approaches it like how one would review an article. This means that they will (hopefully) bring up everything needing fixing on the article, and will also pass any part (or everything) they think is already ready to be published. As well, a pre-review with all sections passed is more likely to, indeed, be passable, and would be (theoretically) reviewed first, since its more likely to be passed.

2.Identify good reviewer candiates:If someone consistently leaves good pre-reviews, then I can be reasonably confident that they will leave good reviews as well (as ultimately the main difference between pre-review and reviewer is that the pre-reviewer can't actually pass/fail the article). Also, if someone consistently leaves bad pre-reviews (outside of maybe asking them to not pre-review or teaching them), they are probably not a good reviewer candidate.

3.Prioritize reviewer time:There is virtually always tons good articles going stale due to lack of reviewers (as I side note, @Gryllida, I think you're a reviewer, could you review something?). If something was passed in pre-review it is more likely to actually pass review, and as such should be reviewed first (as the goal is to get the most publishable stuff published), and something failing pre-review should be reviewed later because it is much less likely to actually be passable. Me Da Wikipedian (talk) 10:49, 21 August 2024 (UTC)

This looks like a set of things that a talk page comment would do. It was explained that the difference is that a pre rreview can include an assessment of "everything", well a talk page comment can too and it can also include a note "I think this is ready to pass a full proper review".

On my user page there is a note about an utility that delivers notifications to users about new drafts, or new published stories, in categories of interest. It was running for a few months and then stopped. Please advise if you would like to help me maintain it. Gryllida (talk) 07:00, 22 August 2024 (UTC)

I believe what we really need is to maintain a steady output of published content. We've gone almost two full months now without a published article. It would really help if some reviewers re-engaged and reviewed some articles and sighted changes in the review queue. If we are unable to consistently publish news articles, I believe the project will qualify for being merged with another project (Wikipedia) or archived as part of the Procedure for Sibling Project Lifecycle, if/when it becomes active.[16]

Regarding the pre-review template, it's primarily meant to groom and identify potential, new reviewers. The intention is that in completing all the fields of the template, pre-reviewers systematically evaluate an article against the writing pillars. The template also produces a consistently formatted response that authors and reviewers both can quickly read and understand once they are familiar with it. In short, the {{pre-review}} is merely a comment on the talk page that is at least consistently formatted. The hope is that reviewers can identify users who are interested in becoming a reviewer and who have demonstrated potential through pre-reviews. The status quo is not working. We need to come up with a way to increase the number of active reviewers.

All three of the current article in the review queue have been pre-reviewed. You can take a look at them to see working examples of the results. I would say that in each case, the pre-review has provided useful feedback—useful to both the author and the reviewer. The output conveys feedback in an easily understood format and in many cases already, has resulted in corrections that would otherwise result in a failed review. There has been one article published after it "passed" a pre-review. [17]

We also need an admin's assistance with the license upgrade project.[18] We've been trying to get assistance with that project for several weeks.[19] We've done all the work we can without admin assistance and are now ready to ask Meta for outside assistance if we can't get local help. We've recently, as a project, chosen to become a global sysop wiki to get outside help with admin tasks such as speedy deletions and vandalism, because we don't have enough active admins to support day-to-day maintenance. I believe the project is circling the drain and is in serious need of re-engagement by reviewers and admins. The project fails at its core mission without them. —Michael.C.Wright (^Talk/_Published) 15:11, 22 August 2024 (UTC)

Thanks for the note. By my view pre reviews can be done by anyone. It would probably not misused for the next century or two while this is a small wiki. If it becomes misused and blocks do not help then maybe making a user right for it could make sense.

I didn't realize the gravity of the situation about two months with zero published articles. I have commitments for my health and family that prevent me from reviewing major stories. I usually do not and did not review stories on US politics. By the time I realized what their two major parties were I would already start thinking that this is deeply irrelevant to my existence (I am on a completely different continent). I can alleviate this situation by checking other submissions and by becoming more active as an author.

In my opinion it helps to also connect with contributors and reviewers through video chat and in person, then activity and collaboration may rapidly increase. I tried this on a Linux related group and it worked on multiple occasions. Having a stronger connection with another member of the group helped keep it prolific and inclusive. I can connect on matrix, sip, bigbluebutton, etc. My timezone is around utc+10. Gryllida (talk) 12:08, 23 August 2024 (UTC)

(Side note, on my user page it says my IRC nick, I would think email and irc would be first point of contact for admin help before Meta. I check itc every hour and email about 3 times a week. Other reviewers and admins may have some other contacts on their user pages.) Gryllida (talk) 12:34, 23 August 2024 (UTC)

About admin work I am surprised the software does not have a button to send email to all admins. I was not even aware of any of these tasks or globalsysop changes mentioned. It would have been nice if I was notified by email. I will try to check what needs to be done within next two days when I am back home and at my desktop. (I appreciate you writing abour them here now.) Gryllida (talk) 12:11, 23 August 2024 (UTC)

I checked and

• there is no clear description of differences between the licenses. I asked about it within that discussion.
• I did not understand why a change is needed, Wikimedia movement mission is to create freely licensed content and the current licence is free enough by their definition. This is my opinion. Consensus may be different.
• The voting section name was changed in middle of vote, perhaps another vote needs to occur here for the sake of clarity. I will need to read more thoroughly to understand whether this is needed. It is Friday evening and I am usually away on weekends but I will try to peioritise this.
• This is about licence change. It does not resolve question about articles publishing activity. We don't even have a WN:AAA-like page for reviewers...? More on this later.

Gryllida (talk) 12:39, 23 August 2024 (UTC)

@Gryllida you are commenting on a section about pre-review, not the license change. Me Da Wikipedian (talk) 21:48, 23 August 2024 (UTC)

Thanks @Me Da Wikipedian. You are welcome to move my comment, otherwise I will do it in a few days when I am on my desktop. Gryllida (talk) 10:25, 25 August 2024 (UTC)

There are many otherwise decent articles that are sitting in WN:ABAND because there wasn't any reviewer resource available in a timely manner. Flagged revisions was a policy enacted on Wikinews originally to satisfy a requirement for Google News syndication, but many years later I'm not sure such a policy is still sustainable. Instead of trying to create additional process, have we put thought into replacing the reviewer process with this lighter format entirely? Microchip08 (talk) 10:56, 29 August 2024 (UTC)

Hi @Microchip08 thank you for the notes, A few points

• I think it would be lighter if everyonne just agreed to write about my country and nothing else. I am poor at processing information about other places.
• Whatever is done, in my personal view the 5Ws in first paragraph is still a requirement. Would you agree?
• I can check the 5Ws were answered correctly, but if it is outside of my country or topic, I get stuck on verifying the second paragraph.
• Please review something now if you can, or have a look. Does it feel to you in the same way? That you can easily review first paragraph, but if topic is boring, you lack motivation to proceed? Or what is it that prevents you from completing a review?

Thanks, Gryllida (talk) 11:06, 29 August 2024 (UTC)

As a side note, one thing that tended to help me, and still does, is having someone available in real time when I am editing or reviewing. On wiki communication is good and transparent but is not real time. Even IRC level real time is nuts compared to a audio chat. (I am not suggesting audio chat for here; this is observation from elsewhere.) There were a few reviewers on irc, but now there is only one. This complicates things a bit. Another thing that complicates communication is slow typing on irc (rare, but happens). Thought it is best to share this here before I forget it. Gryllida (talk) 11:56, 29 August 2024 (UTC)

@Gryllida "it would be lighter if everyonne just agreed to write about my country and nothing else" - I don't really think thats a reasonable request.

I would agree with the second. Me Da Wikipedian (talk) 12:17, 29 August 2024 (UTC)

I didn't mean it as serious suggestion at time of writing. If seriously, I will reword it. It would be nice if there were one or two contributors who like to write about the topics that I like to review. Still thinking on that one, it was a bit of brainstorming... Gryllida (talk) 11:59, 30 August 2024 (UTC)

Ultimately, (my understanding is that) Wikinews was at one point on needing reviews for every article publishing a bunch of articles. That was because there were active reviewers. There are currently no reviewers who are active long-term, and haven't been in a long time. We need more active reviewers. However light you make a requirement, there is no point if there is no one to assess it.

What we need is more active reviewers. So, any user who feels they are ready to become a reviewer, please nominate yourself. That is the only way this problem will be fixed. @Microchip08 @Gryllida Me Da Wikipedian (talk) 12:22, 29 August 2024 (UTC)

The other way we can fix this is by removing the concept of formal review. The current approach is unique to Wikinews and significantly diverges from the way other Wikimedia projects approach the wiki way. Do we still believe the benefits of formal review outweighs the costs? It's difficult to recruit and retain reviewers if new contributors get their contributions staled out through no fault of their own, and people not reviewing quickly enough has been a problem for as long as I can remember. Microchip08 (talk) 12:34, 29 August 2024 (UTC)

@Microchip08 were you around when review didn't exist? Was anyone here around then? If so, do you think it was better? Me Da Wikipedian (talk) 21:03, 29 August 2024 (UTC)

Could the call for reviewers be put as a site notice or what was it called, at top of every page. Link to page that says "1. read CG and SG, 2. write five articles at the rate of one every three days and rejoice if one is published & use it as learning path, 3. edit others' drafts for a month to assist in preparing them to be publish ready 4. apply to be reviewer" ...? Gryllida (talk) 23:17, 29 August 2024 (UTC)

@Gryllida you can edit MediaWiki:Sitenotice if you wish. I would also advise that message I think you can't seriously learn to be a reviewer in 4/6 weeks, nor is reviewer based of how many articles you make/improve nor the time you have been here for. Me Da Wikipedian (talk) 23:52, 29 August 2024 (UTC)

It was meant as a wider pool, then we can select. Gryllida (talk) 00:20, 1 September 2024 (UTC)

@Gryllida, since it's a volunteer project, I don't think we should require a rate of writing articles such as X articles written every Y days.

Besides, if we don't have the reviewers to review articles at that same rate, writers will watch their articles go stale, which can be very frustrating. Without having all of their articles reviewed, we won't have good data on which to judge their understanding of what it takes to publish a good article. —Michael.C.Wright (^Talk/_Published) 14:29, 1 September 2024 (UTC)

I didn't mean the timing as a requirement, only as a guide to reduce risk of frustration with 'I thought I could get this all done in a day' from new participants who think that writing a story takes 10 minutes and no further work required. Gryllida (talk) 21:37, 1 September 2024 (UTC)

Who qualifies based on these? Wrote two or three articles which were successfully published, made 100+ edits in mainspace, is not a reviewer yet? Is there a list. Gryllida (talk) 23:30, 29 August 2024 (UTC)

@Gryllida I think that is way too low for reviewer...but some users who have made two/three published articles in the past year include and 100+ mainspace edits include myself, @Asheiou, @Michael.C.Wright (currently nominated for reviewer), @BigKrow, and @Виктор Пинчук. Me Da Wikipedian (talk) 23:55, 29 August 2024 (UTC)

Can you possibly leave each of them a message on talk page and ask whether they would like to nominate as reviewer? Ask to include preferred region(s) and topic(s) of interest in the application, and whether they can do one review a fortnight within their preferred topic area. Gryllida (talk) 11:55, 30 August 2024 (UTC)

@Gryllida Michael.C.Wright is nominated for reviewer, BigKrow has told me they have now wish to be one...Виктор Пинчук exclusively makes OR about stuff they do so I doubt they want to be one either...Asheiou has nominated themselves with no consensus...and as for myself would you really think that I am ready to be reviewer? Me Da Wikipedian (talk) 12:51, 30 August 2024 (UTC)

(You can link them to this discussion. I would ask myself, just late Friday evening,I am away on weekend, and if you can assist maybe we can get a reply sooner. Otherwise, I will message them a bit later in the week. Gryllida (talk) 11:57, 30 August 2024 (UTC)

Maybe also Kitabc12345

(This "reply" feature loses data half of the time I "paste" something into the textbox, and has ibadequate zoom on smartphone screen about 85% of the time, so annoying) Gryllida (talk) 12:08, 30 August 2024 (UTC)

Could you please also check the same for last five years, if it is not too much trouble, it would be legendary invaluable to know? Gryllida (talk) 12:09, 30 August 2024 (UTC)

@Gryllida Kitabc12345 doesnt have 2/3 published articles. Ill check the last 2 for you as anyone before that has been inactive so long that if they were a reviewer theyd qualify for PEP, ie.they have probably forgotten a lot. @CSJJ104, @JML1148, @Renamed user 2du13u4u8h, @Darkfrog24 and @Moondragon21 would be included by 2 years. Possibly more im nowhere near done yet.

However, other than Asheiou and maybe DarkFrog 24 if they were more active, I think all of these people aren't a great fit for being a reviewer. Writing 2-3 articles in 2 years is way too low a requirement. Me Da Wikipedian (talk) 14:51, 30 August 2024 (UTC)

Also @DRC-B5 but I'm done now...clearly none of these would ever gain consensus to be reviewer unless they do more stuff so.... Me Da Wikipedian (talk) 15:20, 30 August 2024 (UTC)

As one of the people pinged here (who has not created an article for over 18 months) it would be ridiculous for me to technically be eligible to be reviewer. Perhaps a 6-month threshold would make more sense. JML1148 (talk) 09:48, 2 September 2024 (UTC)

Pre-review process? I have two concerns. 1) Does the English Wikinews have enough people who are active enough that adding another step to article publication would be viable? When I was active here, it was normal for perfectly good articles to age out of WN:FRESH for no reason but that the reviewers didn't get around to reviewing them. The problem was not that the drafts had too many problems; it was that there weren't enough reviewer-hours to get them through the pipeline. Has that changed? 2) Was there some issue, like with the Gatwick article, where an article was published too quickly and there was some form of consequence? In other words, does the English Wikinews have a problem that a pre-review process would solve? Because if the answer to both of these is "no," then I'd have to tell you to change the above to "not unanimous." Darkfrog24 (talk) 16:05, 30 August 2024 (UTC) Readded after third party's apparent misunderstanding over identity. Heavy Water (talk) 20:08, 30 August 2024 (UTC)

You make a good point. To clarify; pre-review is not meant to be a requirement, an extra step to publication, or something reviewers do. Hopefully this clarifies a bit; pre-review is meant to eventually take some load off the reviewers by allowing trusted pre-reviewers to do some of the leg-work for them, should they volunteer to do so. For example; if I have established that I consistently give good advice in a pre-review, a reviewer could spend less time on an article I have pre-reviewed and more time on another that needs more attention. This saves reviewer-hours, which we don't have enough of, as you rightly pointed out. If there are two articles in the review queue and I as a trusted pre-reviewer have already worked with the author to correct identified problems and I recommend publishing the article, a reviewer could do a quicker/shorter evaluation of that article, maybe to ensure all facts are sourced and accurate, there is no bias of omission, etc. They can skip less-critical (but still important) things like looking for style and format issues, trusting that they were corrected in the pre-review process either directly by the pre-reviewer or afterwords by the original author. —Michael.C.Wright (^Talk/_Published) 20:53, 30 August 2024 (UTC)

In addition to @Michael.C.Wright's comments above, there are some other uses for pre-reviews. For example, if article X has issue Y that the reviewer couldn't solve without becoming involved, then the pre-reviewer can bring that up to the author, who will hopefully fix it before a review, thus reducing the chance that it goes stale/needs 2 reviews. As well, if you 2 articles in a review queue, one that passed pre-review and one that failed, and you trust the pre-reviewer, and you only have time to review 1, you would review the one that passed as its much more likely to actually be publishable. @Darkfrog24 Me Da Wikipedian (talk) 21:42, 30 August 2024 (UTC)

Okay, that's more or less what I thought. I think this makes everything too complicated. The minute the Wikinewsie who wrote the first draft hits "submit," the article immediately belongs to all of Wikinews. Anyone may edit it for any reason (and I have). Anyone may hit the review button and submit it to the reviewers. The reviewer only needs to see what the article looks like at the time it is submitted, not who made which edit. We don't need to create a pre-review system because we created one long ago. Perhaps Wikinews could benefit from people doing it more. I also think creating an official status could exacerbate unhealthy social patterns that I witnessed during my years of heavy activity here. Darkfrog24 (talk) 23:53, 30 August 2024 (UTC)

So I guess my answers to Gryllida's second set of questions are...

1) No, pre-reviewers should not give articles not-ready status.

2) Yes, pre-reviewers should indeed feel free to do more work more on articles that they have already worked heavily on.

3) No, there should be no requirements for pre-reviewership. This is partially because the community is small enough that reviewers can learn which other users they do and don't trust and partially because the kinds of skills we would require (professional-level English mechanics, etc.) are very difficult to assess by consensus. People tend to be annoyed when other people correct rule-based things like grammar, punctuation, flow of fact, and adherence to posted site guidelines and policies, but that's exactly what we want Wikinewsies to do before formal review.

4) No, this should not be a formalized group. Wikinewsies should jump in and edit articles whether they drafted them or someone else did, so long as there is no "edit in process" tag active. Whether drafters should be able to control who works on the draft, say, to request request no further edits before review, is a separate issue. Darkfrog24 (talk) 20:28, 31 August 2024 (UTC)

@Darkfrog24, yes any Wikinewsie can edit the article. Pre-review is a much more through process. The pre-reviewer is essentially suppossed to act like a reviewer in that they should fully look through everything, and then on the talk page post to the author what they did right and wrong. Done correctly, this can be very helpful for the author to learn. As well, the pre-reviewer can learn what they did right/wrong by comparing it to the actual review and hence learn how to review. As well, if someone consistently makes good pre-reviews then that is a great way to know if there a good reviewer candidate.

This can't be accomplished by everyday editing. The ability to give not-ready status and not being able to pre-review work they have made or heavily worked on is so that it is as best "practice" as it can be for actual review. The requirements and formalized group idea is mostly to prevent wrong or misleading advice, which, particularly when there may not be any other experienced user around to contradict them, can create problems. Me Da Wikipedian (talk) 01:25, 1 September 2024 (UTC)

That does not sound good to me. "Help the author learn"/"what they did right/wrong" presupposes that the reviewers/pre-reviewers are always or almost always right about what the drafter should do. That has not been my experience here on Wikinews. Wikinews is better off educating new users through published sources and formally established policies and guidelines. Darkfrog24 (talk) 18:36, 1 September 2024 (UTC)

@Darkfrog24 yes, that is the point of requirement for pre-reviewer, the hope that they are "almost always right about what the drafter should do". Fact is, reading every policy (or all the ones about article writing) is not something more first time contributors do. As well, there is a difference between saying "read the style guide" vs. "X over here is an issue with part Y of the style guide. You might want to consider changing it to Z". Me Da Wikipedian (talk) 18:42, 1 September 2024 (UTC)

I think we're on the same page about what the proposal is. In the interests of not dredging up old business (which could be bad habits long broken at this point), I'll leave you with "thanks." Darkfrog24 (talk) 18:50, 1 September 2024 (UTC)

Proposed Removal of the Reviewer Permission From William S. Saturn

After various reminders by George Ho with no response, I have requested the removal of the reviewer permission from William S. Saturn. Me Da Wikipedian (talk) 13:25, 21 August 2024 (UTC)