Jump to content

Proposal talk:Stable Release Tab

From Strategic Planning
Latest comment: 14 years ago by Philippe in topic Impact?

In what ways does this proposal differ from flagged revisions versions of Wikipedia? Dedalus 13:02, 22 August 2009 (UTC)Reply

  • Flagged revision is, by itself, merely a mechanism that adds an approval layer to wiki editing; wiki editing goes on as normal, but occasionally an admin comes along and updates the article to the latest non-vandalism revision. On the other hand, the process I propose--which could be implemented with flagged revisions--is a system of branching and releases, with (up to three) completely disconnected versions of an article developing independently. And through the processes I describe, "releases" would be subject to far more scrutiny than a flagged revision. --Estemi 14:30, 22 August 2009 (UTC)Reply


Some proposals will have massive impact on end-users, including non-editors. Some will have minimal impact. What will be the impact of this proposal on our end-users? -- Philippe 00:16, 3 September 2009 (UTC)Reply

Possible impact #1: Consider this scenario: A professor wishes to assign his class to read a certain Wikipedia page. Before he makes the assignment, he wants to get the page into good shape. If this professor's changes will not be posted immediately, do you think he will even bother revising the page?
Possible impact #2: It's not much fun to submit changes that may never make it to the end users. If we make editing Wikipedia less fun, this will certainly have a significant negative impact. Editors will always want their changes to be in the most prominent place possible. If there is a "stable release" page, therefore, it must not be the default. If the default is not the newest page, the incentive to edit is lost.