text:
Quark (kernel)

In computing, Quark is an operating system kernel used in MorphOS. It is a microkernel designed to run fully virtualized computers, called boxes (see sandbox). , only one box is available, the ABox, that lets users run extant AmigaOS software compiled for Motorola 68000 series (MC680x0 or 68k) and PowerPC central processing units (CPUs).

Design goals
The Quark microkernel is not a member of the L4 microkernel family, but borrows concepts from it, including: the clan (group of tasks), ID concept, and recursive address mapping. Quark also has an asynchronous/synchronous message interface similar to Amiga's Exec kernel but adapted to an environment with memory protection.

Other Quark features include:
 * High super/usermode switch speed
 * Low interrupt latency
 * Interrupt threads (IntThreads) and Int P-code abstraction
 * Symmetric multiprocessing (SMP)
 * Models task/thread and clan/chief
 * Resource tracking
 * Virtual memory (optional)
 * Distributed computing
 * No access to kernel structures
 * Clean design with an elegant application programming interface (API)
 * Micro/pico kernel mix

For this new kernel, a hardware abstraction layer is used which provides the needed hardware resource information like scanning all Amiga Zorro II bus boards, Peripheral Component Interconnect (PCI) boards, and local hardware resources.

Functions

 * SYS_AddLinkMessage
 * SYS_AttemptSemaphore
 * SYS_AttemptSemaphoreShared
 * SYS_CopyCPUHalConfig
 * SYS_CreateMemList
 * SYS_CreateTask
 * SYS_DeletePort
 * SYS_DeleteSemaphore
 * SYS_DumpMemHeader
 * SYS_FindFreeMemArea
 * SYS_FindSkipSize
 * SYS_GetLinkMessage
 * SYS_GetMessageAttr
 * SYS_GetNextCPU
 * SYS_Init
 * SYS_InsideClan
 * SYS_IsClanMember
 * SYS_MMUAddPage
 * SYS_MMUGetEntry
 * SYS_MoveRomModuleToMemoryEnd
 * SYS_ObtainPort
 * SYS_ObtainSemaphore
 * SYS_ObtainSemaphoreShared
 * SYS_ReleaseSemaphore
 * SYS_ReplyMessage
 * SYS_SendMessage
 * SYS_SetMessageAttr
 * SYS_SetupPageTable
 * SYS_ShowExceptionThreads
 * SYS_ShowForbidThreads
 * SYS_ShowIntThreads
 * SYS_ShowQuarkState
 * SYS_ShowReadyThreads
 * SYS_ShowRunThreads
 * SYS_ShowThreads
 * SYS_ShowWaitIntThreads
 * SYS_ShowWaitThreads
 * SYS_Start
 * SYS_StartNextThread
 * SYS_StartThread
 * SYS_WaitPort

Trance JIT
Trance JIT is a MorphOS just-in-time (JIT) compiler, or code translator, for running 68k applications within the MorphOS environment. It has been part of the MorphOS operating system since MorphOS 1.4.

MorphOS has a fully integrated 68k emulator to run many Amiga applications, which were almost exclusively compiled for the 68k processor, though MorphOS runs on PowerPC. Trance supplements this function by adding JIT compiling, increasing the speed of the emulation. It does not interfere with the full integration of 68k and PowerPC tasks MorphOS provides.

Trance exists in the form of an executable, run during boot, and a shared library. Although it is not technically part of the kernel, and MorphOS can be run without it, Trance is considered a fundamental part of MorphOS and one of its most powerful features.

Compatibility of Trance is considered to be very high and there are few to no 68k instruction sequences or applications which cause it any problems. It is also considered to be very fast, with users noticing few differences between 68k programs and native PowerPC code.

Trance was developed by Ralph Schmidt and Teemu Suikki, with minor support from other MorphOS team members, Mark Olsen, Sigbjørn Skjæret, and Harry Sintonen.

ABox
Under the Quark kernel, a PowerPC native reimplementation of the OS known from the Commodore International A1000, A500(+), A600, A2000, A1200, A3000(T), and A4000(T) systems runs as a mix of a virtual emulation and a driver. This OS driver is called an ABox.

The 68k emulation is written in C and uses GNU Compiler Collection (GCC) assembly language macros where needed to speed up some complex instructions.

A JIT engine named Trance is also available for MorphOS, to speed up old 68k programs beyond the current state of the traditional emulation.

The PPC native Exec supports the PowerPC register model which means there is no difference for this Exec if it runs 68k or PowerPC code. PowerPC code does not block multitasking inside the OS box like in emulations where the 68k code is just emulated in some host system's task (then every access outside this environment would stop the multitasking in the emulated environment).

For applications running under this new PowerPC ABox kernel 68k code runs as subroutines inside PowerPC tasks. For 68k or PowerPC applications it's fully transparent if some library, hook, interrupt is still 68k or already using PowerPC code.

title: Quark (kernel)


text:
Arabian Plate

The Arabian Plate is a minor tectonic plate in the Northern and Eastern Hemispheres.

It is one of the three continental plates (along with the African and Indian plates) that have been moving northward in geological history and colliding with the Eurasian Plate. This collision is resulting in a mingling of plate pieces and mountain ranges extending in the west from the Pyrenees, crossing Southern Europe to Iranian plateau, forming the Alborz and the Zagros Mountains, to the Himalayas and ranges of Southeast Asia.

Lexicology
The Arabian Plate is a designation of the region, and it is also sometimes referred to as the Arab Plate.

Borders

The Arabian Plate consists mostly of the Arabian Peninsula; it extends westward to the Sinai Peninsula and the Red Sea and northward to the Levant. The plate borders are:

 * East, with the Indo-Australian plate, at the Owen Fracture Zone
 * South, with the African Plate to the west and the Somali Plate and the Indo-Australian Plate to the east
 * West, a left lateral fault boundary with the African Plate called the Dead Sea Transform (DST), and a divergent boundary with the African Plate called the Red Sea Rift which runs the length of the Red Sea;
 * North, convergent boundary with the Anatolian Plate and Eurasian Plate, including the East Anatolian Fault, Zagros fold and thrust belt, and Makran Trench.

History
The Arabian Plate was part of the African Plate during most of the Phanerozoic Eon (Paleozoic–Cenozoic), until the Oligocene Epoch of the Cenozoic Era. The Red Sea rifting began in the Eocene, and the separation of Africa and Arabia occurred approximately in the Oligocene, and since then the Arabian Plate has been moving toward the Eurasian Plate. The opening of the Red Sea rift led to volcanic activity. There are volcanic fields called the Older Harrats, such as Harrat Khaybar and Harrat Rahat, cover parts of the western Arabian Plate. Some activity still continues especially around Medina, and there are regular eruptions within the Red Sea.

The collision between the Arabian Plate and Eurasia is pushing up the Zagros Mountains of Iran. Because the Arabian Plate and Eurasian Plate collide, some cities such as those in southeastern Turkey (which is on the Arabian Plate) may undergo earthquakes, tsunamis, and volcanoes.

Countries and regions
Countries within the plate include Bahrain, Djibouti, Iraq, Jordan, Kuwait, Oman, Qatar, Saudi Arabia, Syria, United Arab Emirates and Yemen. Regions include the Anti-Lebanon Mountains (Lebanon), parts of Awdal (Somalia/Somaliland), the Khuzestan Province (Iran), the Southeastern Anatolia Region (Turkey), and the Southern Denkalya Subregion (Eritrea).

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Arabian Plate


text:
Dwight Yorke

Dwight Eversley Yorke CM (born 3 November 1971) is a Trinidadian and Tobagonian professional football coach and former player who was most recently in charge of Australian A-League club Macarthur FC. Throughout his club career, he played for Aston Villa, Manchester United, Blackburn Rovers, Birmingham City, Sydney FC and Sunderland, mainly as a forward, between 1998 and 2009. Yorke formed a prolific strike partnership with Andy Cole at Manchester United, where he won numerous honours including several Premier League titles and the Treble of the Premier League, FA Cup and UEFA Champions League in 1999. Yorke scored 123 goals in the Premier League, a record for a non-European which was not broken until Sergio Agüero in 2017.

At international level, Yorke represented Trinidad and Tobago on 74 occasions between 1989 and 2009, scoring 19 goals. He helped his nation reach the semi-finals of the 2000 CONCACAF Gold Cup, and later qualify for the FIFA World Cup for the first time in its history, representing his country in the 2006 tournament. After retiring from playing in 2009, Yorke became assistant manager of the Trinidad and Tobago national team, a position he held until the completion of the qualifying matches for the 2010 FIFA World Cup.

Aston Villa
Yorke was first discovered by Graham Taylor, at the time the Aston Villa manager, on a tour of the West Indies in 1989. Yorke, aged 17, appeared in a team that played a friendly against Aston Villa. Taylor was impressed and offered Yorke a trial at Villa. Yorke was subsequently given a permanent contract and played for the Villa Reserve and Youth sides for the majority of the 1989–90 season, making his First Division debut for Aston Villa against Crystal Palace on 24 March 1990: Crystal Palace won the game 1–0. During his time with Aston Villa, from 1989 to 1998, Yorke played initially as a right winger until the 1995–96 season, he then switched to centre forward and established himself as one of the Premier League's top strikers.

Yorke was an integral member of the Villa team that reached the League Cup Final in 1996. Villa won 3–0 against Leeds United with Yorke getting on the scoresheet. On 30 September 1996 he scored a hat-trick against Newcastle United in a 4–3 defeat. Yorke appeared for Aston Villa on 284 occasions, scoring 97 times.

The circumstances of his departure from Aston Villa were controversial. John Gregory, Aston Villa's manager at that time, made it known that the club did not want to sell Yorke to Manchester United unless they were prepared to exchange striker Andy Cole. Yorke played for Villa on the opening day of the season at Everton on 15 August 1998, however it appeared he made little effort during the match as he was unhappy at not being allowed to leave the club. Villa were left with no option but to sell the player and he was transferred to Manchester United for £12.6 million on 20 August 1998.

Manchester United
In his first season Yorke was a key player in guiding his club to a unique treble of the Premier League title, FA Cup and UEFA Champions League, and forming a legendary partnership with Andy Cole. Yorke finished the season as the top league goalscorer with 18 goals and contributed goals against Bayern Munich, Barcelona, Inter Milan, and Juventus in the Champions League, and he won the Premier League Player of the Season. Yorke was also a regular member of United's 1999–2000 title winning team, contributing 23 goals in all competitions.

Despite a less successful third season, Yorke scored his 100th Premier League goal in a 3-0 victory over Derby County on 24 November 2000 and also netted a hat-trick in the top of the table clash with Arsenal. In January 2002 a move to Middlesbrough fell through. He played his last game for United that month, and was not issued a squad number for the 2002–03 season. Altogether he scored 65 goals for Manchester United in 152 appearances.

Blackburn Rovers
In July 2002, Yorke moved to Blackburn Rovers for an initial £2 million, potentially rising to £2.6 million; United had wanted a fee of £6 million. He was signed to cover the long absence of Matt Jansen from a traffic accident, and was reunited with his former United strike partner Andy Cole.

Yorke scored 13 goals in all competitions in his first season at Ewood Park, including the winner on 26 October 2002 as Rovers won 2–1 at reigning champions Arsenal. The following 4 January on his return to Villa Park, he scored twice in a 4–1 win in the FA Cup third round. On 11 May, in the last game of the season, he opened a 4–0 win at Tottenham Hotspur as Blackburn beat Everton to sixth place and UEFA Cup qualification.

Birmingham City
On 31 August 2004, transfer deadline day, Yorke moved to Birmingham City on a one-year deal with the option of a second. Instead of a loan to Celtic, he chose to join Birmingham for a "substantial but undisclosed fee". It was later reported as £250,000.

Yorke scored on his home debut for Birmingham in a 1–1 draw against Charlton Athletic, with the equaliser seven minutes after replacing Clinton Morrison. He scored again against Graeme Souness's Newcastle on 3 October. However, Yorke fell out of favour at St Andrew's and was released by mutual consent in April 2005.

Sydney FC

Yorke immediately signed for Sydney FC, with a salary of $1 million a season. He scored the first goal for Sydney FC in its first A-League regular season match, a diving header against the Melbourne Victory. Yorke came to Sydney FC with the biggest pedigree of all players in the A-League, having won the treble with Manchester United. Yorke scored 7 goals in the A-League, with three of them being from penalty kicks. Sydney FC coach Pierre Littbarski moved Yorke into a midfield role and gave him the team captaincy.

He played a major role in leading Sydney FC to victory in the inaugural A-League Grand Final on 5 March against regional rivals Central Coast Mariners. He set up the only goal, scored by Steve Corica, in front of a sell out crowd of over 41,000 at the Sydney Football Stadium, and was awarded the Joe Marston Medal as best player in the grand final. Yorke was the marquee player for Sydney FC – meaning that his salary fell outside the salary cap. He was also a star name for the A-League as a whole. Aside from his footballing talents, the drawing power and credibility he brought both locally and internationally proved to be beneficial for the competition in its inaugural season, leading the Football Federation Australia to use his image and name for the promotion of the A-League's second season.

Due to the schedule of football in Australia, Yorke returned to Manchester United for training from March to June 2006, to retain fitness for the World Cup.

Yorke returned to Sydney FC to take part in a friendly against Everton in 2010. The game was considered his 'farewell game' as he never had the chance to say a proper farewell to the fans at Sydney FC. Everton won the match 1–0, and Yorke was substituted midway through the second half.

Sunderland

On 31 August 2006, Yorke's transfer to Sunderland was announced. The transfer for a fee of £200,000 (A$ $500,000) re-united Yorke with ex-teammate Roy Keane, manager of Sunderland. Yorke made his debut in the home match against Leicester City and received a rapturous standing ovation from home fans when he came on as a substitute in the first half. Yorke was used as a defensive midfielder rather than his usual striker role. He scored his first goal for Sunderland in the 2–1 loss against Stoke.

On 2 January 2008, during Sunderland's 1–0 defeat to Blackburn, Yorke was given a red card by referee Rob Styles. Yorke stated several times he would like to return to the A-League, preferably Sydney FC. However, following Sydney FC's signings at the time it seemed unlikely that Sydney would have been able to fit him under the salary cap. It was reported that Yorke play for rivals Central Coast Mariners, the team bankrolled by the man who brought him to Sydney, Peter Turnbull.

On 11 March 2008, it was announced that the Mariners were in "advanced negotiations" with Yorke to become the marquee for two years. However, on 1 July he signed a new one-year contract to stay with Sunderland for the 2008–09 season. He was named man of the match for his performance against Arsenal on 4 October 2008, with Sunderland drawing 1–1 at home. Following Keane's departure in December 2008, Yorke and Neil Bailey were named as assistants to Ricky Sbragia. Yorke was released at the end of the 2008–09 season.

Post-retirement
Yorke has completed his Level B coaching badge, and in 2010 was quoted as being interested in pursuing a career in coaching, ideally with Aston Villa. On 17 April 2011 he completed the London Marathon in a time of 3 hours and 32 minutes. On 14 August 2011, Yorke signed a two-year deal to work for Sky Sports as a pundit.

International career
Yorke was capped 72 times for the Trinidad and Tobago national team, scoring 19 goals. Along with his friend Russell Latapy, Yorke was a member of the 1989 'Strike Squad', the national team which narrowly failed to qualify for the 1990 FIFA World Cup. He retired from international football in 2001 after a disagreement with coach René Simões, who cut Yorke and Russell Latapy from the squad prior to a decisive game of the 2002 World Cup qualification, as both missed practice following a night partying. However he returned to the team for the 2006 World Cup qualification campaign, in which the team qualified for the World Cup finals for the first time in their history after a 2–1 aggregate qualifying victory over Bahrain.

Yorke was captain for all of Trinidad and Tobago's games at the 2006 World Cup and was man of the match in the 0–0 draw against Sweden, pipping his close friend Shaka Hislop to the honour despite the then West Ham goalkeeper making several world-class saves. He was one of six players in the Trinidad squad (the others being Brent Sancho, Dennis Lawrence, Chris Birchall, Carlos Edwards and Stern John) to have played every minute of the campaign. Yorke was rated the best defensive midfielder in the opening stages of the World Cup.

Yorke announced his retirement from international football in March 2007, choosing to focus on his club career at Sunderland. He captained the side in Germany, and up until his retirement. However, he made a guest return appearance for a friendly against England in June 2008 after being invited by FIFA vice-president Jack Warner. On 10 July 2008, the TTFF announced Yorke's return to the national team for the 2010 World Cup qualification campaign.

On 15 October 2008, he scored his first international goal after returning from retirement against the United States in a 2010 World Cup qualification match. The game ended 2–1 for Trinidad and Tobago. His goal was a crucial tie-breaker scored in the 79th minute, which put Trinidad and Tobago in a great situation to advance to the next qualifying stage, needing only a tie against Cuba in their final game. On 11 February 2009, Yorke scored a 26th-minute penalty for his country, but was sent off in the dying seconds of Trinidad and Tobago's opening match of 2010 World Cup qualification against El Salvador (2–2) after exchanging heated remarks with Mexican referee Marco Antonio Rodríguez (the Trini star had voiced his disapproval of the disruptions caused by the home crowd) and was consequently banned for four games due to his use of abusive language. The suspension was later reduced to two matches.

After being released from Sunderland and being unable to find a club before the end of the current transfer window, Yorke retired from football altogether in September 2009, and took up the post of assistant manager with the Trinidad and Tobago national team.

Early career
On 21 April 2019, Yorke was interviewed for the vacant role at National League side Sutton United. However, Sutton appointed Matt Gray Instead.

On 12 November 2021, Aston Villa appointed Steven Gerrard as their new manager. Yorke said he was disappointed not to be hired instead.

On 21 April 2022 it was reported that Yorke was being considered for the vacant manager's position at Perth Glory in the Australian A-League Men.

On 25 May 2022, Yorke managed the A-Leagues All Stars in their 3–2 loss against FC Barcelona.

Macarthur FC
On 1 July 2022, Yorke became the new manager of A-League Men side Macarthur FC, replacing Ante Milicic to become the club’s second manager. Three months later, he led the club towards its first trophy after winning the 2022 Australia Cup Final.

Yorke left the Bulls in January 2023, the day after a 1–0 loss to Adelaide United.

Personal life
Yorke grew up as a Tottenham Hotspur fan and his first jersey was a white Tottenham Hotspur shirt.

Yorke had a brief relationship with former model turned writer Katie Price that produced son Harvey, who was born in May 2002. He is autistic and partially blind, and has the genetic disorder Prader–Willi syndrome. In a 2009 interview, Yorke conceded being unfaithful to Price during their relationship, and subsequently playing no role in the upbringing of their son. He has not claimed paternity, despite a paternity test proving he is Harvey's father. He has paid no financial amount regarding Harvey's care and treatment nor visited or reached out to his son.

The Dwight Yorke Stadium in Bacolet, Tobago, constructed for the 2001 FIFA U-17 World Championship, was named in Yorke's honour. Yorke is a cricket fan. One of Yorke's closest friends is Brian Lara. During the 1999 Cricket World Cup, Yorke made regular appearances bringing on drinks for the West Indies cricket team. Yorke's older brother, Clint Yorke, is a former first-class cricketer who has represented the Trinidad and Tobago national cricket team as an opening batsman.

Yorke featured extensively in an episode of Australia's The Biggest Loser, which aired on 28 February 2006. The episode involved Yorke coaching the "red team" of contestants while they competed against the "blue team" in a game of football. Mark Rudan, Yorke's Sydney FC teammate, was the manager of the "blue team".

As a member of the squad that competed at the 2006 World Cup, Yorke was awarded the Chaconia Medal (Gold Class), the second highest state decoration of Trinidad and Tobago. He was also made a Sports Ambassador for the country.

Yorke released his autobiography, Born to Score, in 2009.

In December 2018, Yorke avoided bankruptcy by paying a £1.5 million debt to HM Revenue and Customs.

International

 * Scores and results list Trinidad and Tobago's goal tally first, score column indicates score after each Yorke goal.

Player
Aston Villa
 * Football League Cup: 1995–96

Manchester United
 * Premier League: 1998–99, 1999–2000, 2000–01
 * FA Cup: 1998–99
 * UEFA Champions League: 1998–99
 * Intercontinental Cup: 1999

Sydney FC
 * A-League: 2005–06

Sunderland
 * Football League Championship: 2006–07

Trinidad and Tobago
 * Caribbean Cup: 1989

Individual
 * Premier League Player of the Month: February 1996, January 1999, March 2000
 * PFA Team of the Year: 1998–99 Premier League
 * Premier League Player of the Season: 1998–99
 * Premier League Golden Boot: 1998–99
 * UEFA Champions League: Top goal scorer 1998–99
 * Joe Marston Medal: 2005–06
 * Sydney FC Hall of Fame: 2015
 * Hummingbird Medal Silver: 1992
 * Chaconia Medal Gold: 1999

Manager
Macarthur FC
 * Australia Cup: 2022

title: Dwight Yorke


text:
User:Muhamedmesic

On a Wikisabbatical. Find me on Facebook if needed. M. :)

title: User:Muhamedmesic


text:
User talk:Raymo~enwiki

Hello, welcome to Wikipedia.

You might find these links helpful: How to edit a page, How to write a great article, Naming conventions, Manual of Style. You should read our policies at some point too.

If you have any questions, see the help pages, add a question to the village pump, or ask me on my talk page. I hope you enjoy editing here and being a Wikipedian!
 * You can introduce yourself on the new users page.
 * You can find lots more information, including open tasks and daily tips, at the community portal.
 * You can sign your name using three tildes, like this: . If you use four, you can add a datestamp as well.
 * Before saving a page, it's a good idea to use the Show preview button to review your edits. Also, consider writing a summary for each edit.

Again, welcome! Chris Roy 15:34, 14 Mar 2004 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Raymo. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Raymo~enwiki that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name. If you think you might own all of the accounts with this name and this message is in error, please visit Special:MergeAccount to check and attach all of your accounts to prevent them from being renamed.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 02:19, 20 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 17:59, 22 April 2015 (UTC)

title: User talk:Raymo~enwiki


text:
User talk:Roaf~enwiki

Hello, welcome to Wikipedia.

You might find these links helpful: How to edit a page, How to write a great article, Naming conventions, Manual of Style. You should read our policies at some point too.

If you have any questions, see the help pages, add a question to the village pump, or ask me on my talk page. I hope you enjoy editing here and being a Wikipedian!
 * You can introduce yourself on the new users page.
 * You can find lots more information, including open tasks and daily tips, at the community portal.
 * You can sign your name using three tildes, like this: . If you use four, you can add a datestamp as well.
 * Before saving a page, it's a good idea to use the Show preview button to review your edits. Also, consider writing a summary for each edit.

Again, welcome! Chris Roy 15:34, 14 Mar 2004 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Roaf. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Roaf~enwiki that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name. If you think you might own all of the accounts with this name and this message is in error, please visit Special:MergeAccount to check and attach all of your accounts to prevent them from being renamed.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 02:42, 20 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 18:10, 22 April 2015 (UTC)

title: User talk:Roaf~enwiki


text:
User talk:Brazuca

Hello, welcome to Wikipedia.

You might find these links helpful: How to edit a page, How to write a great article, Naming conventions, Manual of Style. You should read our policies at some point too.

If you have any questions, see the help pages, add a question to the village pump, or ask me on my talk page. I hope you enjoy editing here and being a Wikipedian!
 * You can introduce yourself on the new users page.
 * You can find lots more information, including open tasks and daily tips, at the community portal.
 * You can sign your name using three tildes, like this: . If you use four, you can add a datestamp as well.
 * Before saving a page, it's a good idea to use the Show preview button to review your edits. Also, consider writing a summary for each edit.

Again, welcome! Chris Roy 15:35, 14 Mar 2004 (UTC)

title: User talk:Brazuca


text:
Bosnia and Herzegovina convertible mark

The convertible mark (Bosnian: konvertibilna marka, Cyrillic: конвертибилна марка; sign: KM; code: BAM) is the currency of Bosnia and Herzegovina. It is divided into 100 Pfenig or Fening (Пфениг/Фенинг) and locally abbreviated KM. While the currency and its subunits are uniform for both constituent polities of Bosnia and Herzegovina, namely the Federation of Bosnia and Herzegovina (FBiH) and Republika Srpska (RS), the designs of the KM 10, KM 20, KM 50, and KM 100 banknotes are differentiated for each polity.

History
The convertible mark was established by the 1995 Dayton Agreement. It replaced the Bosnia and Herzegovina dinar, Croatian kuna and Yugoslav novi dinar as the single currency of Bosnia and Herzegovina in 1998. Mark refers to the Deutsche Mark, the currency to which it was pegged at par.

Etymology
The names derive from German. The three official languages of Bosnia and Herzegovina, Bosnian, Serbian and Croatian, have adopted the German nouns Mark and Pfennig as loanwords marka and pfenig. The Official Gazette of BiH ( Bosnian: Službeni glasnik BiH), Official newspaper of FBiH ( Bosnian: Službene novine FBiH) and other official documents recognised pfenig or пфениг (depending on the script; Serbian uses both Latin and Cyrillic equally, while Bosnian and Croatian uses only Latin) as the name of the subdivision. Most, however, consider the "pf" cluster in "pfenig" to be nigh unpronounceable, so the pronunciation was practically immediately reduced to "fenig", which eventually gave rise to the "fening" misspelling. Banknotes of 50 fenings circulated from 1998 to 2003. They were denoted "50 KONVERTIBILNIH PFENIGA" / "50 КОНВЕРТИБИЛНИХ ПФЕНИГА"; technically, the word convertible should not qualify the word pfenig because only the mark is convertible. (See Errors for all of the errors on banknotes and coins.) Coins of 10, 20, and 50 pfenigs have circulated since 1998 (the 5-pfenigs coin was released in 2006). All of them are inscribed "~ feninga" / "~ фенинга" on the obverse. The misspelling fening/фенинг has never been corrected, and it took such a hold that it was officially adopted and not recognised as incorrect. Due to the overall confusion surrounding the foreign name of the currency, most people call the convertible mark simply "marka" ("mark") while pfennigs are referred to as "kovanice" ("nickels").

Plurals and cases
Serbo-Croatian is subject to a case system. For the purposes of pluralizing currency terms, three situations are relevant:

 * In combination with numbers 1, 21, 31, 41, 51, 61, 71, 81, 101, 1001, et cetera (i. e. all numbers ending in "1" except 11), nouns use the nominative case singular (the base form):
 * màrka ( màr : a – short vowel, rising tone) and pfénig/féning ( (p)fé : e – short vowel, rising tone)

 * In combination with numbers whose final digit is 2, 3, or 4 (except 12, 13, and 14), nouns use the genitive case singular (the "paucal form"):
 * màrke ( màr : a – short vowel, rising tone) and pféniga/féninga ( (p)fé : e – short vowel, rising tone)

 * In combination with numbers 0, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 100, 1000, 10000, et cetera (i. e. all numbers ending in 5, 6, 7, 8, 9, 0, 11, 12, 13, or 14), nouns use the genitive case plural:
 * mȁrākā ( mȁr : a – short vowel, falling tone; vowels ā are not accented but have genitive length) and pfénīgā/fénīngā ( (p)fé : e – short vowel, rising tone; vowels ī and ā are not accented but have genitive length)
 * (For further information on accents in BSC, see Serbo-Croatian phonology and Shtokavian dialect.)

For the pfenig, the plural is pfeniga/feninga with a short unaccented a, whereas the genitive plural is the same pfeniga/feninga but with a long unaccented i and a. A syllable after an accented syllable whose vowel is pronounced long and with a continuous tone, i. e. neither rising or falling, is said to have a genitive length (although the word does not necessarily have to be in the genitive case in order to have genitive length on its syllable; it can be in the locative also).

These matters should be noted when the local names are used in English. For example, the English plural "ten pfenigas" / "ten feningas" is incorrect because the final a in the BSC plural pfeniga/feninga already indicates the plural. Therefore "ten pfenigs" / "ten fenings" should be used. The Central Bank of Bosnia and Herzegovina (CBBH) uses "fenings" as the English plural. Likewise, "twenty-one markas", "two markes", and "twelve marakas" are incorrect; "twenty-one marks", "two marks", and "twelve marks", respectively, are correct.

Coins
In December 1998, coins were introduced in denominations of 10, 20 and 50 fenings. Coins of 5 fenings, KM 1, KM 2 and KM 5 were introduced later. The coins were designed by Bosnian designer Kenan Zekić and minted at the Royal Mint in Llantrisant (Wales, UK).

Banknotes
In 1998, notes were introduced in denominations of 50 fenings, KM 1, KM 5, KM 10, KM 20, KM 50, and KM 100. KM 200 notes were added in 2002, while the 50-fening and KM 1 and KM 5 notes were later withdrawn from circulation. All current notes are valid throughout the nation.

The Central Bank of Bosnia Herzegovina issues the banknotes, with distinct designs for the constituent polities of the Federation of Bosnia and Herzegovina and the Republika Srpska,1 except for the largest denomination, i. e. the KM 200 note. The banknotes are legal tender throughout the country. On the notes for the Republika Srpska, inscriptions are printed first in Cyrillic and then Latin script, and vice versa. Banknotes, with the exception of the KM 200 note, are printed by the French company Oberthur.

Nationwide issues
The portraits of Ivan Franjo Jukić and Meša Selimović, which are both writers, were featured by consensus between both entities on all KM 1 and KM 5 notes used between 1998 and 2010.

On 15 May 2002, a KM 200 banknote, designed by Robert Kalina, was introduced during a promotion that was held in the Central Bank of BH. The reverse design which depicts a bridge is meant to resemble the euro banknotes, which were also designed by Robert Kalina. After an international tender, the Austrian company Oesterreichische Banknoten und Sicherheitsdruck GmbH (OeBS) in Vienna was chosen to print the notes. Initially, six million were ordered.

Exchange rates
Initially the mark was pegged to the Deutsche Mark at par. Since the replacement of the German mark by the euro in 2002, the Bosnian convertible mark uses the same fixed exchange rate to euro that the German mark had (that is, 1 = 1.95583  ).

Errors
Banknotes and coins of Bosnia and Herzegovina have many mistakes and inconsistencies.

Officially, only one banknote has not been released in circulation because of a mistake, even though other banknotes with mistakes had been issued.

Banknote examples
These are the most important mistakes that have been noticed to date:
 * Both designs of the 50 fening banknote imprinted the adjective "convertible" next to the noun "pfenig", although only the mark has the "convertible" prefix ("50 KONVERTIBILNIH PFENIGA" / "50 КОНВЕРТИБИЛНИХ ПФЕНИГА").
 * The KM 1 banknote for Republika Srpska was imprinted "ИВО АНДРИЂ / IVO ANDRIĐ" instead of "ИВО АНДРИЋ / IVO ANDRIĆ". This banknote was immediately removed from circulation.
 * Both designs of the KM 5 banknote had the Cyrillic word "five" incorrectly printed in Latin script on its reverse ("PET КОНВЕРТИБИЛНИХ МАРАКА", instead of "ПЕТ ..."). Also, Meša Selimović's name is written in Cyrillic as "Меща Селимовић" instead of "Meша Селимовић" (the letter щ is not even used in any of the official languages of Bosnia and Herzegovina).
 * The KM 10 banknote for Republika Srpska, first series, 1998, had Aleksa Šantić's name printed in Latin script although it should have been printed in Cyrillic script as it is on all other examples of the 1998 series.
 * Both designs of the KM 100 banknote were incorrectly printed with the Cyrillic abbreviation of the Central Bank of Bosnia and Herzegovina with "Џ / Dž" instead of "Ц / C" (i. e. "ЏББХ / DžBBH" instead of "ЦББХ / CBBH") in the safety bar.
 * In 2017, Edin Bujak of the Department of Archaeology of the Faculty of Philosophy in Sarajevo noticed a mistake on the KM 10 banknote for the Federation of B&H. The picture of the stećak on the reverse is actually a picture of a stećak from Križevići, Olovo and not from the Radimlja necropolis as stated on the banknote. The Central Bank of Bosnia and Herzegovina confirmed this mistake, and it will be corrected in future printing of the banknote.

Coin examples

 * The name of the subdivision of the convertible mark has been incorrectly engraved on coins: the word "pfenig" has been engraved as "fening". This mistake has taken such a hold, especially because there were and are no 50 pfenig/fening banknotes in circulation, that "fening" was officially adopted as the name of the hundredth unit of the KM and is not recognized as incorrect.

title: Bosnia and Herzegovina convertible mark


text:
Wikipedia:Quickpolls

Quickpolls were a trial of a system for making fast decisions about problematic users. They consisted of polls among Wikipedia regulars on issues that needed to be quickly resolved. It operated from March to June of 2004, although some action continued into July.

After mixed reactions in the 30-day review process this page fell into disuse. As seen on the talk page, there was much dissatisfaction with the process, and no agreement on what changes were needed to fix it.

Potential alternatives to the quickpoll system include the "three strikes rule" and other ways of dealing with trolls and dealing with disruptive or antisocial editors.

At the time, Quickpolls policy contained the policy for this procedure. Concluded polls have been moved to Quickpolls/Archive (which also includes an example poll).

A proposal to revive quickpolls was active in March, 2005. See Bring back quickpolls.

title: Wikipedia:Quickpolls


text:
Wikipedia talk:Requests for arbitration/Plautus satire vs Raul654/Decision

Should someone strip out the "all proposed" stuff since this appears to be completed now? fabiform | talk 15:43, 14 Mar 2004 (UTC)

 * Better now? It was proposed at the time. Some of it (eg, findings of fact, perma-ban) is still proposed, some of it is active. Requests for arbitration/Plautus satire vs Raul654 has the final decision. Martin


text:
Wikipedia talk:Quickpolls/Archive 1

People who support the current quickpolls proposal

 * 1) —Eloquence 15:44, Mar 14, 2004 (UTC)
 * Anthony DiPierro 15:55, 14 Mar 2004 (UTC) Support, with one tweak: "If the vote subsequently drops below 70%, the remedy should be reversed."
 * 1) Angela - agree with Anthony.
 * 2) Ruhrjung 16:00, 14 Mar 2004 (UTC) - although I seriously would like to see longer lasting bans
 * 3) Seth Ilys 22:21, 14 Mar 2004 (UTC) - although there should be time-limits on how long quickpolls stay open -- say, 2 or 3 days?
 * 4) Secretlondon yes - but I would like there to be a minimum time - especially for political issues which may have a regional bias.
 * 5) *Better to handle with "...drops below X%, the remedy should be reversed."--Ruhrjung 22:34, 14 Mar 2004 (UTC)
 * 6) *The normal rules of sleep do not apply to Wikipedians ;-).—Eloquence 22:40, Mar 14, 2004 (UTC)
 * 7) * They do for those of us with office jobs :( Secretlondon 23:11, 14 Mar 2004 (UTC)
 * 8) Cyan 22:39, 14 Mar 2004 (UTC)
 * 9) Pete/Pcb21 (talk) 22:50, 14 Mar 2004 (UTC) (Although see tqo suggestions below)
 * 10) Dori | Talk 22:53, Mar 14, 2004 (UTC)
 * 11) BCorr ¤ Брайен 22:55, Mar 14, 2004 (UTC)
 * 12) Davodd 23:05, Mar 14, 2004 (UTC)
 * 13) fabiform | talk 23:07, 14 Mar 2004 (UTC) and I think there shouldn't be restrictions on the number of polls someone can call unless it turns out that the system isn't self-correcting
 * 14) Perl (Mabye 75 percent?)
 * 15) Taku 17:09, Mar 15, 2004 (UTC)
 * 16) Hephaestos|§ 17:12, 15 Mar 2004 (UTC)
 * 17) Fred Bauder 17:17, Mar 15, 2004 (UTC)
 * 18) William M. Connolley 18:49, 2004 Mar 16 (UTC)
 * 19) Tannin 02:31, 19 Mar 2004 (UTC) Most of my reservations have been dealt with now. Let's do it.
 * 20) Martin 02:16, 21 Mar 2004 (UTC) I have reservations: I think four weeks is slightly too long for desysopping, and I think the three month requirement is a mistake, and I'd prefer a more incremental introduction, but I can live with this as v1.0.
 * 21) Ryan_Cable 11:53, 25 Mar 2004 (UTC)
 * 22) ChrisO 01:36, 27 Mar 2004 (UTC) Not a bad system...
 * 23) I think its a lousy system, but its way better than near anarchy. Sam Spade 05:19, 29 Mar 2004 (UTC)
 * 24) Arvindn 13:43, 29 Mar 2004 (UTC)
 * 25) →Raul654 06:17, Apr 1, 2004 (UTC)
 * 26) Adam Conover 06:51, Apr 1, 2004 (UTC)

People opposed to specific proposal, but with ideas for improvements that may change their vote, if accepted
(Please list any changes you would like to make next to your vote.)

 * 1) Oppose. All quick results need to be for short, limited times, not indefinite. The idea is to modify behavior, not be a court without due process. Normal discusion of a problem can handle things after no more than a few repeated offences and quick actions. Things like referring to aribtration are not suitable for a quick poll. Jamesday 23:14, 14 Mar 2004 (UTC)
 * 2) Oppose.  Changes I (+sj+) would like to see before voting for this :
 * 3) * A more gradual introduction of this idea. This is a *major* and abusable change.  I don't like the idea of quickpolls doing anything 'permanently'.  Regular one-week bans/desysopping until a case can go to arbitration seems much less offensive to the victim, and quite sustainable.
 * 4) ** Quickpolls don't do anything permanent unless approved by arbitration. This was temporarily removed by Martin but I think it's a necessary protection.—Eloquence
 * 5) * Additionally, I think "2d and 3d offenses" should both indicate only a 24-hr ban, while "4th & further offenses" should allow up to a week ban. This would be a more moderate first step; after a couple months of trial use, I would be open to broadening or hardening the policy.
 * 6) ** This is already a very lenient policy. I'm not willing to soften it further in the initial phase. But I'd be open to softening in case it turns out to be a problem.—Eloquence
 * 7) *** Better now. But I do think some min number of edits -- 10? that's what we use when calculating Stats:#-of-users -- should be required, to get a sense of the voter.
 * 8) ** Here's a detailed 'worst-case scenario'.
 * 9) ***That's more of a story than a scenario, and not a very realistic one at that, largely because any quickpoll requires prior warnings about the policy in question
 * 10) **** Ah! This was unclear. "repeat offenders" could apply to 'someone who has violated any policy in the past' (indeed, I only just now realized the other way to parse it).  The new wording is great.
 * 11) ***...and also because it has an unrealistic "one against everyone" view of Wikipedia editing.
 * 12) **** Right. story it was; 'scenario' in quotes.  I agree its unrealistic.
 * 13) *** Now, the only point from that scenario which I can agree on is problematic is that of a one-week-desysopping being hard to undo once it has become final. A quick-resysopping clause on WP:RfA might sense; on the other hand, if people change their opinions so quickly, then maybe it's a good thing that they get some time to think about them first.—Eloquence
 * 14) **** See new comment below on min. length of time.
 * 15) * A less strident voting policy, coupled with a more strident listing policy. (I don't like the idea of every user with 3mo+100 edits being encouraged to edit Recentchanges whenever they are in a really foul mood!)  Perhaps 4mo+400 edits, or adminship, to list a quickpoll; only 1mo+100 edits to vote in one.  (that should be enough to avoid endless sockpuppets; as with any poll, the vote of someone demonstrated to be a sockpuppet can be ignored.) Adminship should suffice to 'qualify' a user.  +sj+ 12:20, 2004 Mar 20 (UTC)
 * 16) ** The voting policy is already less strident - there is no 100 edit policy any longer. Please read the current version of the proposal.—Eloquence 00:15, Mar 21, 2004 (UTC)
 * 17) *** Now the barrier to ranting on RC is really too low. Most of the time when I visit RC, I absolutely don't want to see emotional comments about who's abusing whom.  99% of edits to WP are not about that.  How about limiting the allowable RC change to a single link, on a new Quickpolls: line created for this purpose, consisting only of UserA:UserB, where UserA is listing a poll regarding UserB?
 * 18) *A minimum length of time a poll must be left up before acting on it, perhaps an hour? Again, make slow changes... this can be strengthened if it isn't abused.
 * 19) anthony 22:10, 24 Mar 2004 (UTC) I'm not sure how it could be fixed, though.

People opposed to the idea

 * 1) Oppose strongly. --Wik 23:57, Mar 14, 2004 (UTC)
 * 2) Eclecticology 05:04, 2004 Mar 15 (UTC) It's just more bureaucracy.
 * 3) Weakly sceptical; having seen it in action. May switch later. -- Cimon avaro 07:52, Mar 25, 2004 (UTC)
 * 4) I think quickpolls will become the place where people like Lord Kenneth and Reddi will rule the day. Wikipedia is (and should remain) a place where people seek consensus. I'm just worried the current system of friendly consensus will turn into a bunch of hard popularity votes. I'm worried that this vote itself might prove me right, if votes are simply tallied, and this comment goes unnoticed :-( Kim Bruning 18:17, 31 Mar 2004 (UTC)
 * 5) Polls for edit warriors? for admin oversights? for vandals? That makes no sense. These polls will further bog people down, waste time, and create witch-hunts. Previously banned people will not vote with their conscience, but with revenge in mind. People are going to start feeding off the drama of these polls. Some people will make a mockery of the system. Quickpolls should be used for questions like: should image3 be justified to the right or to the left? Leave discipline issues up to the 175 admins, the Mediation and Arbitration committees. If Arbitration refuses to hear it, that's the end. Get over it. Don't start these vigilante groups. Kingturtle 07:14, 15 Mar 2004 (UTC)

General Comments about the proposed policy
While I support this enthusiastically, I think its use should be extremely rare. While full blocks are the only way to deal with pure vandals, it would be nice for there to be allowance for people blocked this way, who might not be vandals but simply get carried away in a dispute, to at least be able to participate on talk pages. Per-page protection is another possibility (I assume per-page protection would not apply to talk pages as well). Unfortunately, these protections are not currently technically possible, but I hope this political "solution" does not stop the desire to have the technical techniques added. Anthony DiPierro 23:16, 14 Mar 2004 (UTC)

 * As long as we speak of 24-hours ban, it can hardly be any concern that the banned user is blocked also from talk-pages. This scheme can be realized without any software changes. Per-page protection and other alternatives seem to be a much later possibility.--Ruhrjung 23:34, 14 Mar 2004 (UTC)

 * This scheme can be realized without any software changes, and that's why I support it. But I see it as a less than optimal solution.  I'm not sure why you say it can hardly be a concern to block non-vandals from talk pages.  It is a concern, at least to me, and I would think others share that concern.  Again, we're not talking about someone intentionally destroying Wikipedia (although that is one of the three posibilities).  Anthony DiPierro 23:21, 16 Mar 2004 (UTC)

 * Of course it would be a serious concern and a severe condition if the ban laster longer than 24 hours.--Ruhrjung 17:53, 18 Mar 2004 (UTC)

Problems already resolved
Moved to Wikipedia_talk:Quickpolls/Initial proposal resolved issues

"Persecution" issue
I'm worried about political abuse - but we'll see how it goes. If it is clear that people with minority politics are being targeted then I think we will need to review and make amends if necessary. Secretlondon 23:12, 14 Mar 2004 (UTC)

The problem is that I don't think it will be - I expect that 172 will be listed here and maybe even myself. However I don't expect RickK or VeryVerily to end up being listed. Can you see the problem? Everything we have so far has been used for partisan ends, why should this be any different? I'm sorry if this is too blunt - but there seems to be a fair amount of minority baiting atmSecretlondon 23:21, 14 Mar 2004 (UTC)

 * It's almost certain that RickK will be listed here promptly for not following deletion policy. I've considered listing him for desysopping for that reason at least once a month for many months now. Jamesday 23:23, 14 Mar 2004 (UTC)

 * You just won't go to sleep will you Secretlondon? What do you mean by minorities? Trolls are in the minority, so are crackpot theorists, should they be left free to roam? As long as people abide by the policies, it doesn't matter whether they are in the minority does it? Dori | Talk 23:26, Mar 14, 2004 (UTC)

 * Minorities are for instance Poles who feel that Allied (including Soviet) views have been purported wrongly for 60 years. And people with a less rosy view of USA and UK, remember this is an Anglophone forum.--Ruhrjung 23:30, 14 Mar 2004 (UTC)

 * That doesn't solve the issue of verifiability. There are plenty of people that feel the US committed the 9/11 attacks, should they be allowed to express that in articles? Dori | Talk 23:33, Mar 14, 2004 (UTC)

 * However, more fair schemes would require software changes, and that would certainly take some time to accomplish.--Ruhrjung 23:32, 14 Mar 2004 (UTC)

 * I don't know, I think at least 20% of the regulars here are fair minded and can look past partisan disputes. And for those whose edits are rejected by an overwhelming majority of people, they're not going to win in the end anyway.  Personally I will vote against a 24-hour ban for anyone participating on the talk page unless they are obviously trolling or there has been a strong consensus reached against them and yet they continue to force their viewpoint. Anthony DiPierro 23:43, 14 Mar 2004 (UTC)

permananent de-sysopping issue

 * if the user in question is a sysop, a temporary desysopping (until the case is heard by arbitration, which may reinstate sysop privileges)

What if the arbitration committee refuse the case? Does the desysopping become permanent as it seems to have done in the case of 168...? Angela. 15:56, Mar 14, 2004 (UTC)
 * If they refuse to hear it, that means the decision is obvious and does not need review. So the answer to your question is yes, until sysop status is granted again on

Requests for adminship.—Eloquence 15:59, Mar 14, 2004 (UTC)
 * If they refuse to hear it it could just mean that the AC is overwhelmed with work. Eclecticology 05:04, 2004 Mar 15 (UTC)
 * At first glance I was that this could be a problem, but it is largely up to me to make sure I don't do something worthy of being desysopped. The only issue is that it could take a week to restore someone's status, but if there are still more than 70% of the quickpoll votes in support of the desysopping, that shouldn't be a problem. -- BCorr ¤ Брайен 22:55, Mar 14, 2004 (UTC)
 * If they refuse to hear it, it's obvious that they don't think there is a case to be heard and the action should be immediately undone. Jamesday 23:17, 14 Mar 2004 (UTC)

de-sysoping based on quickpoll should be limited to 24 hours at a time, rather than until heard by arbcom. Martin

 * All that would accomplish is added overhead: Say the arbitration commission takes the case after a week, and people feel that a sysop has egregiously violated policy - now they have to confirm that every day, with proper announcement of the poll etc. But this additional bureaucracy accomplishes nothing. We already have the "falling support" requirement - as soon as people stop supporting the desysoping, the sysop can be reinstated. And we have WP:RFA, where people can try to build consensus on a reinstatement. Please construct what you think would be a worst case scenario to determine whether this 24 hour limit is actually needed, or whether it just makes things more complicated..—Eloquence

All quick results need to be for short, limited times, not indefinite. The idea is to modify behavior, not be a court without due process. Normal discusion of a problem can handle things after no more than a few repeated offences and quick actions. Things like referring to aribtration are not suitable for a quick poll. Jamesday 23:14, 14 Mar 2004 (UTC)

 * The arbitration commission can always refuse to hear a case. The only difference here is that there's more support to hear it.—Eloquence 23:17, Mar 14, 2004 (UTC)

 * So this is a way of bypassing the arbitration committee? Secretlondon 23:18, 14 Mar 2004 (UTC)

 * I'll happily support anything with 24 hour time limits, but not something unlimited. We can hold non-quick polls and consensus building if repeated quick actions aren't doing the job. Jamesday 23:21, 14 Mar 2004 (UTC)

 * It's up to them to decide if they want to make a decision. In any case, we are talking about temporary blocks or actions which can be easily undone if there is community support to do so.—Eloquence 23:24, Mar 14, 2004 (UTC)

Worst case scenarios, as requested by Erik:

 * 1) Alice is a sysop. She edits a protected page to insert her POV. It's a repeat offence. She's been warned before.
 * 2) Bob doesn't like this, and starts a quickpoll. In about an hour, there are ten votes in favour: after all, it was an open and shut case.
 * 3) Dave the Developer de-sysops Alice for 24 hours, and asks the arbitration committee to hear the case.
 * 4) Meanwhile, Alice, realising the breadth of opposition to her actions, decides to change her ways. So, were she re-sysopped, she'd be a good and useful sysop.
 * 5) The arbitration committee is busy, and doesn't hear the case for a couple of weeks. It's got a backlog, perhaps (more than likely). Half the committee is on holiday. Whatever. When it does here it, it takes three weeks to make a decision (entirely plausible, on past form).
 * 6) Alice gets more and more frustrated by the impasse, and quits Wikipedia in anger. We make an enemy of a former friend.

Second scenario:

 * 1) Geri is a sysop. She edits a protected page to insert her POV. It's a repeat offence. She's been warned before.
 * 2) Hugh doesn't like this, and starts a quickpoll. In about an hour, there are ten votes in favour: after all, it was an open and shut case.
 * 3) Dave the Developer de-sysops Geri for 24 hours, and asks the arbitration committee to hear the case.
 * 4) Meanwhile, Geri, realising the breadth of opposition to her actions, decides to change her ways. So, were she re-sysopped, she'd be a good and useful sysop.
 * 5) The arbitration committee accepts the case. It then spends a week investigating the issue, taking statements, discussing the matter, and so forth. All of this is completely wasted time.

third scenario:

 * 1) Jeremy is a sysop. He edits a protected page to insert his POV. It's a repeat offence. he's been warned before.
 * 2) Karen doesn't like this, and starts a quickpoll. Nobody votes for it, because they've seen what happened to 168... and Alice, and Geri, and Jeremy's basically a good guy.
 * 3) Jeremy, emboldened by this, carries on. Other sysops follow Jeremy's example. We get vigilante justice, block wars, protection wars, non-sysops become second class citizens. Wikipedia fails.

The third scenario is hyperbolic, but representative of the sorts of problems that concern me. It's important that people feel free to vote for de-sysoping as a temporary measure that is aiming at fixing an emergency situation, rather than an act of punishment that will last indefinately.

Instead, I would suggest using repeated 24hr de-sysoppings. Aside from anything else, they would graphically demonstrate to the arbcom that this issue needs investigation. Given that sysops do other things than abuse their sysop powers, and most of them are moderately sensible, you'd probably only need two or three at top. Martin 00:11, 19 Mar 2004 (UTC)

 * In all of the cases, the sysop could simply re-apply for adminship on Requests for adminship, pledging not to violate policy in the future. If there is consensus to forgive the sysop, arbitration obviously needs not hear the case (I have just inserted a clause to make that clearer). Does that address your problem? I am quite opposed to requiring repeated 24 hour desysoppings because I fear that would bog down the quickpoll system needlessly. Let's use the wiki way for cases like this - try to build consensus.—Eloquence 00:33, Mar 19, 2004 (UTC)

 * The sysop could reapply on Requests..., but in the scenarios I've sketched out, they probably wouldn't get the level of support required, I suspect.

 * I agree with building consensus, but I'd prefer to build it from the status quo, rather than from the desysopped position.

 * My feeling is that quickpolls are actually very low overhead, really, so I can't see them getting that bogged down, and repeated 24hr de-sysoppings make it very easy for the community to come to a consensus (or the arbcom to come to a decision) that the sysop in question needs to be a normal user again.

 * Your clause is better, but still not quite good enough. Perhaps we could compromise on a maximum de-sysoping time (on the basis of a quickpoll) of one week? Martin 00:48, 19 Mar 2004 (UTC)

Alright, what do you think about my kinder, gentler guidelines?—Eloquence 01:02, Mar 19, 2004 (UTC)

 * That's definately more like it. I'll tweak a little (for wording really). Martin 18:33, 19 Mar 2004 (UTC)

What is a reverted edit issue

 * 100 "non-reverted edits". What is a "non-reverted edit". A user can make a really bad edit and it gets whittled away by three or four subsequent edits. One assumes that this isn't a "reverted edit". I'm not sure that this is a significant problem, but it is problematic.
 * In my understanding, it would be a reverted edit. Do you think this can be clarified somehow?—Eloquence
 * I can't think of a way to clarify this at present. At least, not a practical way. It is a difficulty though, and suggestions are welcome. Ideas anyone? Tannin
 * Also, I feel that this would become a less significant matter if we rise the entry bar a little higher - e.g., 200 edits, or admin user to start the poll. Either or both of these would reduce the salience of this matter. Tannin
 * It seems to me that Quickpolls started by trolls would never even reach 8 yes votes, and could be safely ignored. Anthony DiPierro 23:47, 14 Mar 2004 (UTC)
 * sock-puppets? --Ruhrjung 23:56, 14 Mar 2004 (UTC)
 * I don't see how sockpuppets will ever be able to reach 80% with over 10 votes without it being obvious. And obvious sockpuppets will of course not be counted. Anthony DiPierro 23:59, 14 Mar 2004 (UTC)

Barrier to entry issue

 * Only 3 months and 100 edits. This is too few. Seems to me the threshold should be quite a bit higher. Something in the order of 500 to 1000 edits. We want genuine Wikipedians participating in these polls, not trolls or blow-ins. I think this is particularly a problem as regards starting a Quickpoll. Imagine letting (Username omitted) loose with this! As presently formulated, the idea makes my troll-alarm go off.
 * Well, I do not agree. If we are being trolled we have other ways to deal with that. I think setting up a clique system here is not a good idea -- above all we want be open and friendly towards newbies. My suggestion would be to use a modest requirement at first and make it more strict if that should become necessary.

 * Two possible fixes for this problem. (a) increase the minimum time/edit requirement. (b) Allow any qualified user to vote but require an admin to start the Quickpoll. Before people howl about that being undemocratic, remember that a non-admin user needs only to persuade one admin user to start a Quickpoll. If you can't find one single admin to share your view out of ~150 admins, then the view obviously won't have enough support to pass anyway.  Also, this might help cut down on the "poll abuse" problem.
 * I'm afraid that some people will object to any system that requires admin participation on principle.—Eloquence

Implementational issues
I've just realised that I read this incorrectly to start with. I've voted for quickpolls, but wouldn't be able to vote in one myself (I thought the 3 months/100 edits only applied to those people starting polls, which I could live with happily enough). I don't know what I think of this rule. I'm still a month too young to vote in a quickpoll, but I'm about to be made a sysop. Hmmm. I'm not sure if I should propose a change just for me (I mean, I can wait a month, it's not going to kill me), in case it weakens the safeguards. fabiform | talk 23:13, 15 Mar 2004 (UTC)

 * I think we can fine-tune this limit as we go along. Right now it seems to me that 3 months is a good time to familiarize oneself with our policies.—Eloquence

Since this is all about percentages, and seeing all the detailed talk above, would it be a good idea to have a TOC tally? These would need to show the total number of votes, votes for and against (otherwise we wouldn't know if they were up to date or not), as well as the percentage. Eg, for the current poll (6: 2/4: 33%). Good idea, or very bad idea? fabiform | talk 23:29, 15 Mar 2004 (UTC)

 * Yes, a toctally would make sense (Optim's legacy lives on ..).—Eloquence

16th March review
After a 24 hour hiatus in new input I thought it would be ok to have a review of the discussion. As I see it the votes are
 * 1) 17 in favour
 * 2) 3 potentially favour but with stated reservations, for two users these reservations may have been satisfactorily addressed. Probably not satisfactorily addressed for Jamesday?
 * 3) 3 firmly against. Ec's opposition to bureaucracy is probably unresolvable. This will add a little more bureaucracy, but maybe there is appetite for it in this case. Kingturtle's opposition is, I think, based on the wish to trust admins more. Is this suggestion better than the status quo though for you Kingturtle. Wik is also opposed, but hasn't given reasons yet.

There are also several other issues raised that it wouldn't be fair to mark resolved. However the responses seem to indicate it would be worth giving this a go at least on a trial basis - no other suggestion in this area has come anywhere near this close to a consensus. Thus I propose the following route to take this forward:

 * 1) Ask Jimbo his opinion. This is an important issue and I think it requires his blessing.
 * 2) If and when the proposal receives his blessing, set off a one-month trial period. At the end of the month, take stock how successful quickpolls have been and then make a decision on their permanence.

I hope my review is a fair reflection of the actual debate; I tried to make it so. As a precaution, I'll hold off and let someone else do the actual contacting of Jimbo so that it doesn't look I am trying to ramrod this proposal through into policy.

Pete/Pcb21 (talk) 23:02, 16 Mar 2004 (UTC)

 * I think a one-month trial period is a good idea, in any event. I do have concerns about whether or not this can be fairly applied.  But the fact that it is open to most Wikipedians (not just sysops) and requires 80% leads me to believe it would. Anthony DiPierro 23:17, 16 Mar 2004 (UTC)
 * Just to clarify - unless I misunderstand, it's open to *everyone* who has been here longer than 3 months, and that requirement is merely insurance against sock puppet accounts. →Raul654 23:19, Mar 16, 2004 (UTC)
 * Well, 3 months with at least 100 (non-reverted) edits. And according to Eloquence that requirement is more than just insurance against sock-puppet accounts.  But still, 3 months isn't all that long. Anthony DiPierro 23:26, 16 Mar 2004 (UTC)

abstain...
Fennec brings up a good point. There should not be any votes to abstain. Yeas and Nays only. Kingturtle 05:03, 18 Mar 2004 (UTC)

sock puppet detection
Erik: I take your point about sock puppets expressing opinions upon whether other sock puppets are sock puppets, but I think that particular circumstance is best solved via the medium of common sense and good judgement. I've edited it to be "community consensus" - it should be clear to all that random sock puppets are an annoyance, not part of our community. Martin 00:30, 19 Mar 2004 (UTC)

 * Well, I fear that is a recipe for endless meta discussion and edit wars about what is or isn't a sock puppet, especially if we allow anyone to "flag" them as such. I would really prefer it if we would at least leave this particular decision to the maligned admin class, who are by definition known and trusted members of the community and exactly the kind of persons who should make such decisions.—Eloquence 00:38, Mar 19, 2004 (UTC)

 * Well, we've not had those problems on VfD (in that we haven't had any mis-deleted or mis-kept articles due to sock puppets, AFAICT), so I think we should take that risk. If it does become a problem, then we can change the policy quickly enough, right? Martin 00:50, 19 Mar 2004 (UTC)

 * Hm-hm. As the final decision rests with a sysop or developer I guess I can live with it for now. I hope it doesn't turn out to be a problem.—Eloquence 00:55, Mar 19, 2004 (UTC)

voting rule tweakage
The problem situations under previous quorum rules:

 * 1) 9 people are in favour of a temp-ban, the tenth is against. Under old rules, tenth should abstain, because voting against would paradoxically cause the ban to go ahead.
 * 2) 10 people are in favour of a temp-ban. Then, all ten change their mind. Under the old rules, the temp-ban stays in effect, because 15 people are required to reverse a decision.

So I fixed it. Very rules-lawyer of me, I know. Martin 00:36, 19 Mar 2004 (UTC)

Kingturtle's conversation moved down here
(out of the poll itself)
 * 1) Eloquence has convinced me. I am changing my vote. Kingturtle 04:41, 18 Mar 2004 (UTC)

previous (obsolete) discussion
 * Polls for edit warriors? for admin oversights? for vandals? That makes no sense. These polls will further bog people down, waste time, and create witch-hunts. Previously banned people will not vote with their conscience, but with revenge in mind. People are going to start feeding off the drama of these polls. Some people will make a mockery of the system. Quickpolls should be used for questions like: should image3 be justified to the right or to the left? Leave discipline issues up to the 175 admins, the Mediation and Arbitration committees. If Arbitration refuses to hear it, that's the end. Get over it. Don't start these vigilante groups. Kingturtle 07:14, 15 Mar 2004 (UTC)
 * 1) *If this system will not be implemented, I can guarantee you that vigilantism will continue on Wikipedia. People will not go to arbitration, because they know that arbitration takes forever. Instead they will ask a developer or sysop to make a quick decision, in some cases the developer or sysop will comply, and they will keep it as quiet as possible to avoid public outcry. And as you can see on WP:RFA, there is often wide support for maintaining the outcome of such actions. This is not a vigilante group, this is a way to avoid vigilantism, by requiring general community support for any immediate action. As a proponent of due process, you should support this process, as it is quite clear that it fills a vacuum. "That's the end, get over it" is not an argument many people are likely to accept.—Eloquence 10:45, Mar 15, 2004 (UTC)
 * 2) **I support due process - and the system I endorse is the Arbitration Committee. I realize the Arbitration Committee is yet to get its rear in gear, but that is the system I support - NOT the quickpoll system. The process needs to be centralized and consistant. Kingturtle 23:08, 15 Mar 2004 (UTC)
 * 3) ***This system complements the AC, it does not replace it. A certain degree of decentralization is a good thing - it speeds things up and leads to shared responsibility (and blame).—Eloquence
 * 4) ****I trust the judgment of admins. Why create this bureaucracy for something an admin can already do? An admin should be able to act immediately to stop the improper action of a user. The admin should not have to wait 24 hours to give someone a 24 hour ban. That gives the improper user 24 hours extra time to muck around in wikipedia. It is extremely rare for an admin to make a gaff in judgment. Trust the judgment of the admins. Kingturtle 23:57, 15 Mar 2004 (UTC)
 * 5) *****I don't reckon a quickpoll will take 24 hours to come to quorom, more like one hour is my guess. Also we have tried allowing to act unilaterally - in the sense that the backing for their action has not been formally verified, only informally, but it hasn't been sustainable in these very sensitive cases. Pete/Pcb21 (talk) 22:36, 16 Mar 2004 (UTC)

More questions
Since the one who is the subject of the poll cannot vote, to make it fair should the vote of the person proposing the poll count? Dori | Talk 04:06, Mar 19, 2004 (UTC)

 * Probably not.—Eloquence 04:10, Mar 19, 2004 (UTC)
 * Agreed. +sj+ 09:06, 2004 Mar 20 (UTC)

 * OK...so is this going to be reflected in the proposal? what do others think? Dori | Talk 04:32, Mar 20, 2004 (UTC)

Another question, are quickpolls perpetually open? Dori | Talk 04:32, Mar 20, 2004 (UTC)

Reading through the page above, one wonders how much the process intended to create concensus in reality changes the idea which most contributors voted for, and if they who cast their votes many days ago actually would do the same with the latest tweaks. ...Speaking for only myself, I must say that I would have been more than happy if the objective of de-sysopping was quite simply removed when it turned out this to have produced the most serious objections.--Ruhrjung 21:05, 20 Mar 2004 (UTC)

 * Everyone is of course free to change their vote, even after the proposal goes live. As for the desysopping, that was one of my motivations for creating the proposal in the first place.—Eloquence 23:55, Mar 20, 2004 (UTC)

placement
above the "Announcing a quickpoll" section needs to be a "Placement of a quickpoll" section. Where should these be placed? At the bottom of the Talk Page in question? Are there instances in which the Talk Page isn't appropriate? Should these ever take place on the Talk Pages of users? Should there be a single metapage devoted to the taking of quickpolls? Kingturtle 20:14, 20 Mar 2004 (UTC)

 * I was thinking that all quickpolls should be put on Quickpolls itself.—Eloquence

Going live
With 20 votes in support, and 4 (more or less) against, this is as close to consensus as it gets. I'm taking this live for a 30 days trial.—Eloquence 02:26, Mar 21, 2004 (UTC)

 * Maybe then the How to revert a page to an earlier version is to be updated accordingly?
 * I tried to. Can of course always be reversed. ;-)))
 * --Ruhrjung 13:49, 21 Mar 2004 (UTC)

"3 revert guideline?" 3 reverts should get a protected page, right? -24.4.83.91 04:05, 21 Mar 2004 (UTC)

 * That won't work if the same user keeps violating it on multiple pages.—Eloquence 04:11, Mar 21, 2004 (UTC)

 * IE, now the community has alternatives. Protection, protection on specific version, reverts by multiple users, or quickpoll temp-banning. Or some combinatino thereof. Which is nice. Martin 12:56, 21 Mar 2004 (UTC)

 * Only the latter two are community alternatives. The first two are sysop alternatives. anthony 08:14, 23 Mar 2004 (UTC)

3 months/90 days
"Any individual registered user who has been active on Wikipedia for longer than 3 months may start a quickpoll and vote in one."

 * Kingturtle wanted to change this to 90 days, but 3 months is much easier to calculate. anthony 08:13, 23 Mar 2004 (UTC)

90 days vs. 3 months
The problem with 3 months is that its length can vary from 90 to 92 days. Making the waiting period 90 days makes it fair to all users, no matter when they begin. 90 days is consistent. Kingturtle 08:16, 23 Mar 2004 (UTC)

 * You are fussing over nothing, three months is much easier to calculate by eye and people will virtually never be on the boundary. With the rules already fairly complex for these polls, this is an extra layer that we don't need. Pete/Pcb21 (talk) 09:53, 23 Mar 2004 (UTC)

 * Ok, I shoulda read the page first. Pete/Pcb21 (talk) 10:41, 23 Mar 2004 (UTC)

 * It is not fussing over nothing. Strangely and remarkably enough, during the very first QP, a voter's time-of-service was questioned. User:Hcheney's first post was 14:58, 23 Dec 2003 and his vote on QP took place 05:26, 23 Mar 2004...91 days. I feel counting the days is more fair. If it is difficult for others to count the days, I'll be happy to. It is a very quick calculation. Kingturtle 06:12, 24 Mar 2004 (UTC)

 * Why not count hours. After all, it's unfair for people who don't become a user in the 90 days before the clocks get moved ahead.

 * I don't think there is a difference in fairness, and judging from the fact that many sysops don't even know how to count 5 days (as I discovered by watching votes for deletion/undeletion) I think counting 90 is going to be too much for them to handle. anthony 22:26, 24 Mar 2004 (UTC)

 * There's nothing unfair about three months. It may vary in the number of days, but that variance is spread randomly among all users, and therefore is perfectly fair. Really, I think you're trying to fix a problem that doesn't actually exist.  anthony 11:02, 23 Mar 2004 (UTC)

 * Three months can vary in time. As we've seen, in the very first QP, a user was on the cusp. In a 90-day-three-months, he would get to vote, while in a 92-day-three-months, he would not get to vote. That isn't right. A flat 90 days would be more fair.

 * The list of 50 recently active wikipedians is based on 30 days, not one month (for example). Kingturtle 01:43, 26 Mar 2004 (UTC)

 * As I said, 90 days can vary in time too. There being a variance in time does not make it any less fair.  It's stupid to unnecessarily complicate things like this. anthony 02:11, 26 Mar 2004 (UTC)

 * Calculating 90 days takes 15 seconds. I can do it on my hands. It is not complicated at all. Kingturtle 02:49, 26 Mar 2004 (UTC)

 * You're smarter than many other wikipedians. anthony (this comment is a work in progress and may change without prior notice) 21:23, 31 Mar 2004 (UTC)

 * Here's another way, besides using fingers. Atop each date-article, that date's number is listed. March 11 is the 71st day in a Leap Year; August 3 is the 216th. 216 minus 71 equals 145. Kingturtle 23:02, 31 Mar 2004 (UTC)

 * Thanks for the lesson. That still doesn't change the argument. By the way, try explaining modulo arithmetic to people when the date overlaps years.  I've already tried it on VfD.  Of course the same mistake could be made with 3 months, but people seem to grasp that concept a bit better. anthony (this comment is a work in progress and may change without prior notice) 23:07, 31 Mar 2004 (UTC)

Exception for Sysops
A thought. I may be made a sysop soon, but have not yet been here three months. I won't be able to vote in any quickpolls. While I don't really care too much myself- a few weeks' delay won't bother me, at least not much :) this seems rather incongrous with the responsibilities granted to sysops. I therefore propose an exception to this 3-month rule for anyone who is a sysop already before that time. (And I promise not to vote in any quickpolls before then, even if this exception is approved... just for good measure.) It's a small matter, but still... why not? - Fennec 03:15, 28 Mar 2004 (UTC)

When to remove notice?
Is it really fair to remove the notice from Wikipedia:Recentchanges before the poll has ended? Dori | Talk 19:10, Mar 23, 2004 (UTC)

The notice needs to be kept - I had no idea quickpolls were in progress. Secretlondon 23:14, 23 Mar 2004 (UTC)

Can notice be placed on watchlist?
In addition to adding notice on Wikipedia:Recentchanges (the text shown atop the "Recent changes" page), can it be added to Watchlist? - Texture 23:14, 23 Mar 2004 (UTC)

 * The quickpolls page, or W:RC? You can watch either. Dysprosia 23:16, 23 Mar 2004 (UTC)
 * I just stared watching Quickpolls. Didn't have it on my radar or I would have participated. - Texture 23:25, 23 Mar 2004 (UTC)

Strange removal rules
The rules for removing a vote tally are weird. Or at least their effects are:

Suppose we have a vote going on with 19 for, 11 against. That's more than 60% for, so we keep the vote going. Now 10 more people vote for. Then the vote is 29 for, 11 against. That's less than 80%, so we remove the vote. By voting for the banning, those people have made removal of the vote possible. Sounds like an unintended consequence. - Andre Engels 22:31, 24 Mar 2004 (UTC)

No, I think that's exactly what the intended consequence is. The goal of a quickpoll is to reach a quick consensus. If an 80% consensus hasn't been reached by 40 votes, then we declare there not to be a community consensus and move on. Otherwise unsuccessful polls could stay up forever. - Seth Ilys 03:28, 25 Mar 2004 (UTC)

 * Ok, but explore Andre's point a little deeper. If it is 19-11 in favour, then the 80% barrier can NOT be broken before 40 votes. Thus there is literally no point have the poll any more. However the poll can not be removed, because with 30 votes the cut-off is lower. I.e. the system is a little bit broken. Pete/Pcb21 (talk) 09:55, 25 Mar 2004 (UTC)

So it really is the intended consequence that 19 votes for and 11 against we wait whether there might be a consensus, but that with 44 votes for and 11 against we give up? I don't see the logic there. In the first case it's "26 more votes and we're going to ban." In the second 25 of those 26 votes are in, one more and we are going to ban. Still, the first is apparently "still a consensus possible" while the second is "no, no consensus". Am I the only one who thinks that that is weird?

Here's a table.

In fact, the situation is even worse - when the vote is 32-8, 36-9, 40-10, etcetera, both banning and removing are allowed (here given as ban).

Looking from the other side, with 35 votes for, 9 votes against are enough to end the poll, but if there are 23 votes for, 16 votes against are needed. - Andre Engels 10:52, 25 Mar 2004 (UTC)

I also don't like the one-vote difference between ending the vote and banning. I would like to propose the following:
 * 10-25 votes: <= 50% in favor
 * 25-39 votes: >=12 votes against
 * 40 or more votes: <= 70% in favor

Compared to the current system, it keeps more when there are more than 40 votes (to get some sort of 'buffer area' between banning and removing of vote), it removes more when there are 25-40 votes (to remove my paradox) and it removes more with 10-20 votes (for simplicity). - Andre Engels 10:59, 25 Mar 2004 (UTC)

One penalty per poll?
Since quickpolls can stay on the voting page for up for 48 hours after an initial remedy is imposed, people can change their vote even after a user's 24-hour ban is lifted. Thus a user could have an initial vote meeting the 80%/8 support threshold, have that ban lifted if the vote slips below 70%/5 oppose... but the vote could *still* slip back above 80%. I don't think that it's fair or reasonable for a user to be banned, unbanned, and rebanned (potentially) multiple times as opinion shifts. The further on from the initial offense, the less weight that the original offense carries for voters -- whereas they should more ideally be launching a separate quickpoll for separate offenses.

I think that this was a major oversight in the quickpoll rules. The final paragraph of the "Removal" section should read more like: "Quickpolls should be removed from this page upon the completion of a 24-hour ban, or upon its reversal (by support falling below 70%) prior to the end of the 24-hour ban period." That way there's clearly only one penalty per poll. Comments? -- Seth Ilys 02:36, 25 Mar 2004 (UTC)

Is this some kind of joke? Wik has 50% support and i have 100 percent support. I am just trying to go about my business and upload pictures like I usually do. Now I see the potential for this being abused. Perl 02:38, 25 Mar 2004 (UTC)

 * Ahh, yes, good point. Seth. It's good to have a rules lawyer in the house sometimes. I'll fix. Martin 00:02, 30 Mar 2004 (UTC)

Archive protocol question
Perhaps I've missed something in the various explanations of how things work with this page, but why is the "Wik & Perl" poll on the archive page, but not the "GrazingshipIV & Anthony DiPierro" poll? BCorr | Брайен 13:58, Mar 25, 2004 (UTC)
 * GrazingshipIV deleted the discussion link without archiving it. - Texture 16:48, 25 Mar 2004 (UTC)

Texture look into archives for poll-I did archive it as the record will show. GrazingshipIV 17:03, Mar 25, 2004 (UTC)

 * My apologies. You did attempt to archive the discussion.  However, you did not use the link from Quickpolls which was Quickpolls/Archive.  Instead you created a new one off the Quickpolls/Anthony-Graz called Quickpolls/archives.  I have redirected Quickpolls/archives to the correct one specified on Quickpolls. - Texture 17:08, 25 Mar 2004 (UTC)

Question about Quorum
How were the numbers "8" (to censure) & "5" (to clear) selected? These numbers seem uncomfortably small to my taste, & I'd prefer a quorum based on the total number of Contributors to Wikipedia in Good Standing. Back when I belonged to a union, ISTR the quorum was set at 3% of the total membership (because we were lucky to get that many to a meeting) -- which might be achievable on Wikipedia.

ISTR (again) some 50,000 people are registered contributors to Wikipedia; assume that 90% of those would be acceptable under some usable definition of "Contributors to Wikipedia in Good Standing", then 3% would be 150. A majority of how 150 people vote would be far more convincing than the opinions of any 13 random Wikipedians. -- llywrch 02:36, 27 Mar 2004 (UTC)

 * However, this would also render the quickpoll process fairly useless. I agree that 150 people would be better, but when have you ever seen 150 people vote on anything on Wikipedia? I can't recall that happening, and I can't see the odds of it happening on a regular basis anytime soon. Ambivalenthysteria 03:57, 27 Mar 2004 (UTC)

 * You have to keep in mind that only a small number of registered users participate actively. According to only about 2000 wikipedians are active, and that it is unlikely to see even 60 of them vote (to make up the 3%). I also forgot to mention that many wikipedians may not be familiar with the case, or even if they are familiar, they may not make up their mind one way or the other. Dori | Talk 05:21, Mar 27, 2004 (UTC)

I still would like to see some explanation of how the numbers for this quorum were determined. We'll be having this argument, only far more heatedly, in one year when there are twice as many active wikipedians, & a number of them are appalled at how easily it is for a quickpoll to ban someone. (Not that I'm against banning troublemakers, but such a ban ought to be done with a clear process -- otherwise, it will become more trouble than it is worth.) -- llywrch 03:14, 28 Mar 2004 (UTC)

 * To answer the question directly, I selected 8 because it was 80% of 10, and I selected 5 because it was 30% of 15. The former numbers where chosen by Eloquence, I think. Martin 00:00, 30 Mar 2004 (UTC)

I think we should require a minimum of 20 votes / 80% approval to ban to avoid overly hasty decisions where not enough airtime has been given to counter-arguments. 10 votes is clearly not enough.—Eloquence 03:20, Mar 28, 2004 (UTC)

 * If you want to get that many votes, I think the solution is to change the guidelines for advertising quickpolls. Right now we remove the listing from Recent changes when 15 votes are cast. That page probably draws the most voters, so we shouldn't remove a quickpoll listed there until we're safely over whatever quorum we choose to require. --Michael Snow 17:47, 29 Mar 2004 (UTC)

While we're at it I think there should be a 24 hour limit on unimplemented polls. It seems that a poll which is close to but not quite at 80% could theoretically last forever. anthony (this comment is a work in progress and may change without prior notice) 03:32, 28 Mar 2004 (UTC)

 * How about if we say all quickpolls are open for 48 hours, then they get closed and archived. Even if a poll closes at 79.9% in favor. The only exception should be keeping a poll open that might reverse an already implemented ban by dropping support below 70% (i.e. if the ban was implemented after the first 24 hours, keep the poll open until the ban ends). Right now we're not clear because the page seems to say two different things. And this would allow us to get rid of the confusing table of fewer than 20 votes, less than 40% support, etc. --Michael Snow 16:42, 29 Mar 2004 (UTC)

 * I'd go for a 48 hour window to accept votes, as long as there's a minimum numbers of votes for a poll to be considered "approved", say 1% of the active Wikipedians. That would mean right now 20 votes, & would be adjusted upwards (hopefully ;) in the future. -- llywrch 20:33, 29 Mar 2004 (UTC)

 * Acting on my own suggestion, I've archived Anthony's second quickpoll, since it has passed the 48-hour mark. I figure that as the proponent of the poll, I can do that with some claim of legitimacy. If anybody objects, let me know, but I don't think we can have a quickpoll hanging over somebody's head indefinitely. --Michael Snow 03:13, 30 Mar 2004 (UTC)

Regarding quorum, I believe that emergency action should require only a small proportion of total Wikipedians - in the tens, not the hundreds. However, there might also be a possibility of some kind of General Resolution system, for settling non-emergency issues. To some extent, the elections for the Wikimedia board will have an element of that, I suspect. Martin 00:00, 30 Mar 2004 (UTC)

Change username
I asked a question at Wikipedia talk:username about whether internet addresses should be acceptible, but I realized that we need a way of enforcing name changes in general. What does everyone think of adding a "change username" to the list of why quickpolls are held (and to remedies)? It bothers me that quickpolls would get more power, but it bothers me more that right now admins and developpers have to make such decisions. Dori | Talk 20:14, Mar 28, 2004 (UTC)

 * I agree with what she says - it's a vaild point. Moncrief 21:18, Mar 28, 2004 (UTC)

 * Maximus Rex just altered something in my comment above - I really don't appreciate you changing my post. That is not acceptable Wikipedia behavior.  Moncrief 21:20, Mar 28, 2004 (UTC)
 * Ok, but Dori is really tired of people thinking that he is a female. Maximus Rex 21:23, 28 Mar 2004 (UTC)
 * I think that's an acceptable edit to make. Angela. 03:38, Mar 29, 2004 (UTC)
 * I agree with Dori - what he says is quite correct. →Raul654 21:27, Mar 28, 2004 (UTC)
 * This should definitely be added to quickpolls. The current RfC method is not attracting enough votes. Angela. 03:38, Mar 29, 2004 (UTC)

 * (Comment by Anthony removed by Anthony)

 * I take it this refers to holding a quickpoll over banning someone with an unacceptable username (against policy) who refuses to change it? In that case I oppose it, as these usernames should simply be blocked in my opinion. — Jor (Talk) 11:04, 29 Mar 2004 (UTC)

 * quickpolls seem good for "emergency" action, generally (hence "quick") - I'm not sure how well they would stretch to name-changes, which seem to me like a non-emergency issue. Then again, maybe if the community could deal speedily with inappropriate usernames, it'd act as some form of deterrent. After all, we can deal speedily with offensive talk page comments, just deleting them, so why shouldn't we be able to act equally quickly with regards to usernames?
 * Umm, put me down as "don't know", I guess... :) Martin 23:44, 29 Mar 2004 (UTC)

Strongly oppose. There can be polls for this, but not quickpolls. anthony (this comment is a work in progress and may change without prior notice) 01:06, 31 Mar 2004 (UTC)

format of listing
The current format of the listing on Recent Changes is intrusive and tedious. Every time you refresh recent changes it catches your eye, particularly so as it is in the same general screen area as the (much more important) "You have new messages" notice. The bolding has to go. Tannin 18:21, 30 Mar 2004 (UTC)

 * Yes, I think so, at least the way the system is being used now. Martin 21:56, 30 Mar 2004 (UTC)

both or neither
In two instances now, I've wished to vote for "both or neither", but it isn't easy to do this in the current system, which seems a shame. Martin 21:56, 30 Mar 2004 (UTC)

 * I think it's most honest if you actually decide how you wish to vote (i.e. if the requirement for banning are fulfilled or not) for both, and then cast your votes accordingly. ;-) --Ruhrjung 22:27, 30 Mar 2004 (UTC)

I am being honest (which is admittedly rare for me). I honestly wish to vote for "both or neither". I honestly believe that those two are the correct outcomes, given the nebulous state of the requirements for banning. I honestly find this hard to do in the current system. It's honestly occurred in two instances now. I honestly find this a shame.

To summarise:

 * Martin: I wish to vote for "both or neither".
 * Ruhrjung: You should decide how you wish to vote.
 * Martin: I wish to vote for "both or neither".

Ho hum. Martin 23:01, 30 Mar 2004 (UTC)

 * (William M. Connolley 18:20, 2004 Mar 31 (UTC)) I agree with Martin

Toctallies
Has there been a vote or decision to remove Toctallies? - Texture 01:02, 31 Mar 2004 (UTC)

There doesn't need to be a vote to remove incorrect toctallies. Has there been a vote to add toctallies? anthony (this comment is a work in progress and may change without prior notice) 01:03, 31 Mar 2004 (UTC)

 * Anthony, if you would say that the tallies are incorrect in your summary or anywhere we could update them faster than if you just revert the previous person and just say "rv" in your summary. - Texture 01:11, 31 Mar 2004 (UTC)

 * I don't want you to update them faster. In fact, I don't want you to update them at all. There is no consensus for toctallies. anthony (this comment is a work in progress and may change without prior notice) 01:14, 31 Mar 2004 (UTC)

 * Then consider it my comment and leave it be. And why did you remove Wik's vote and leave Jor's vote?  Neither appear to be over but why would you archive one and leave the other?  Especially if you are going to leave older votes.  Your actions don't make sense.  Is there something you are trying to accomplish? - Texture 01:23, 31 Mar 2004 (UTC)

 * Thank you for explaining. - Texture 02:38, 31 Mar 2004 (UTC)
 * Wik had 10 votes, Jor didn't. If you'd like to remove Jor anyway, I wouldn't object. anthony (this comment is a work in progress and may change without prior notice) 02:06, 31 Mar 2004 (UTC)

 * Ah, so that is why Wik's was removed. I take it you will now remove mine as well as there have been 10 votes? (Where is this 'remove after 10 votes' thing discussed by the way?) — Jor (Talk) 18:45, 31 Mar 2004 (UTC)

 * I've removed it. The guidelines for removal are on the Quickpolls page, under Removal of quickpoll listing. --Michael Snow 19:35, 31 Mar 2004 (UTC)

 * Toctallies are silly. If a user is interested in a section they can click on it and view the numbered lists for themselves.  If a sysop wants to know if it's time to block, they can use a computer to do the math.  I think it's safe to assume most wikipedians have computers.  Also, toctallies make it impossible to link to a section on the page, since the anchor name keeps changing. silsor 07:37, Mar 31, 2004 (UTC)
 * I access wikipedia through my typewriter. How am I supposed to do this number crunching you propose? →Raul654 07:40, Mar 31, 2004 (UTC)

It's probably not a good idea to make voting too difficult - having everyone who votes have to break out calc.exe doesn't seem helpful to me. I'll just switch things to "??" every time I vote - if someone cares, they can update. Martin 23:29, 1 Apr 2004 (UTC)

Encyclopedic content cannot be determined by vote
Obvious really. This is what happened on the article on scientific skepticism: One of the parties put the other party on the quickpolls page, clearly intending to get the other person off for 24 hours while editing the page to his POV. I've also seen a quickpoll stlye vote on talk:facism now, where votes really shouldn't happen. Quickpoll gives the mistaken impression that simple majority opinion is good enough for wikipedia. I'm saddened to see that happen. Whatever happened to the consensus rule?

Kim Bruning 13:11, 1 Apr 2004 (UTC)

Not at all a simple majority. ;-> --Ruhrjung 13:44, 1 Apr 2004 (UTC)

 * Agreed. the main advantage to quickpolls is that they allow response to someone who has done much more than violate the mere letter of existing policy -- but protests innocence or conspiracy or mis-representation and so shouldn't be blocked automatically.  If the '3-rv' guideline has become policy, then it should take 6 or 7 rvs, with multiple parties on one side and one on the other, before someone tries to settle such an issue via QP. +sj+ 20:18, 2004 Apr 2 (UTC)

I think for the record it should be stated that Reddi was CLEARLY in the wrong in injecting pseudo-science into the page despite repeated warnings from users other than Lordkenneth. The problem occured because Lordkenneth lost his cool and started making rash decisions-I think if taken to an arbitration committee it would be ruled that Reddi was vandalizing the page mostly because he does not beleive in science or the power of reason from a philosophical perspective, which is fine, it is just that those beleifs do not jive with the goals of a Encyclopedia. GrazingshipIV

 * I object to the entirety of graz's comment above, and want it to be noted that I for one find it entirely non-factual. Sam Spade 23:01, 1 Apr 2004 (UTC)
 * Yes but you and Lordkenneth have a personal history which he articulated quite nastily.It also seems that you hold some of Reddi's views, particularly the one about Lordkenneth. It would be good to state reasons for a critque makes it more beleivable. ;) GrazingshipIV 23:31, Apr 1, 2004 (UTC)

Re: Talk:Fascism, a couple of points. 1) The vote is not a "quickpoll-style vote". A quickpoll vote is to block a user for 24 hours.  This vote is not about that, but about article content.  2) The vote was in order to resolve a content dispute which was not proving amenable to discussion. Several of us tried to make some effort to explain to TDC why the Soviet Union should not be considered a fascist state, and he ignored us. 3) The vote, as it stands, is nowhere near a "simple majority". TDC has received no support for his position.  Hopefully, that will lead him to agree not to keep inserting this poisition, so we can unprotect the article and start working on it again.  While perhaps the vote is not per standard usage, I felt it was the best way to come to some sort of at least temporary agreement so as to unprotect the page. john 23:30, 1 Apr 2004 (UTC)

 * The objectives were different and assuredly quite noble.

 * I found it interesting to see that the poll you used was styled along the line of quickpolls, and you probably hadn't read Polling guidelines at all before you went and did it anyway. Polls can be quite destructive, perhaps we should allow quickpolls against people who fail to follow polling guidelines? ;-).

 * The main problem I see is that quickpolls misleads people into thinking that polls are ok, or worse, that *voting* here is ok. It's a kind of politics and psychology problem. It's harmless enough on its own, but people start following the example.

 * It's mentioned elsewhere, but just in short: polling and voting are not the only consensus building tools we have at our disposal. They are just the heaviest and clumsiest tools at our disposal. It's like using a  front loader to plant violets in your garden, where a small hand tool would have been more appropriate. You're just as likely to crush the violets and knock down the house. The front loader has its place, certainly, I won't disagree with that. Just this isn't it.

 * Kim Bruning 08:58, 2 Apr 2004 (UTC)

 * 2nd example in 2 days : VerilyVerily vs 172. :-( Kim Bruning 09:50, 2 Apr 2004 (UTC)

title: Wikipedia talk:Quickpolls/Archive 1