text:
List of pieces that use the whole-tone scale

This is a list of notable musical works which use the whole tone scale.

 * Béla Bartók
 * Cantata Profana, b. 186–187
 * Concerto for Orchestra, fifth movement, b. 484
 * String Quartet No. 1, end of movement 3
 * String Quartet No. 4, first movement, b. 157–160
 * String Quartet No. 5 "The sequence of tonalities of the single sections [of the sonata form] produce the whole-tone scale". "In the first movement of the Fifth String Quartet...the tonalities of the individual sections form a complete whole-tone scale (B♭–C–D–E–F♯–G♯–B♭)."
 * Mikrokosmos, Volume V, No.136 "Whole-Tone Scales"
 * Alban Berg
 * Violin Concerto
 * "Nacht" from Seven Early Songs
 * Hector Berlioz
 * Francs-Juges Overture
 * Ferruccio Busoni
 * An die Jugend for piano, the right hand part of the "Preludietto, Fughetta ed Esercizio" is based on the whole tone scale.
 * Frédéric Chopin
 * Prelude No. 19, mm. 43–44, in the bass, "while the melody moves down chromatically"
 * Alexander Dargomyzhsky
 * The Stone Guest, passage from act 3
 * Peter Maxwell Davies
 * Symphony No. 3, first movement, horns, between rehearsals P and Q

 * Claude Debussy
 * Chansons de Bilitis
 * Children's Corner
 * Images for piano, No. 1
 * Jeux
 * La mer
 * Pelléas et Mélisande, act 4 scene 2
 * Prélude à l'après-midi d'un faune, b. 32–33, 35–36
 * Voiles from Préludes, Book 1
 * Edward Elgar
 * The Dream of Gerontius
 * Blair Fairchild
 * A Baghdad Lover, nine songs for bass and piano, Op. 25 (1911)
 * Mikhail Glinka
 * Ruslan and Lyudmila, near the end of the overture, in the finale to act 1, and in the act 4 chorus "Pogibnet! Pogibnet!"
 * The Human Abstract
 * "Holographic Sight"
 * Leoš Janáček
 * Sinfonietta (1926)
 * Sigfrid Karg-Elert
 * "Allegro burlesco" from the Sonatina exotique for piano
 * King Crimson
 * "Fracture"
 * One More Red Nightmare
 * Kraftwerk
 * "Spacelab" (from The Man-Machine)
 * Franz Liszt
 * Fantasy and Fugue on the chorale "Ad nos, ad salutarem undam", for organ
 * Réminiscences de Don Juan
 * Gustav Mahler
 * Symphony No. 5, end of fifth movement, b. 784-787
 * Das Lied von der Erde, sixth movement, b. 454-459
 * Olivier Messiaen
 * Quartet for the End of Time (movement 6, "Danse of Fury, for the seven trumpets", cello part)
 * Lee Morgan
 * "Our Man Higgins"
 * Wolfgang Amadeus Mozart
 * A Musical Joke
 * Giacomo Puccini
 * Madama Butterfly
 * Maurice Ravel
 * Jeux d'Eau, page 1
 * Vladimir Rebikov
 * Une fête, No. 6
 * Les rêves
 * Nikolai Rimsky-Korsakov
 * Piano Concerto, 1882, Allegro
 * Arnold Schoenberg
 * "Am Wegrand", Op. 6, no. 6
 * Chamber Symphony No. 1
 * "Jesus bettelt", Op. 2, no. 2
 * Pelleas und Melisande
 * String Quartet No. 1
 * Franz Schubert
 * "Sanctus" from the Mass No. 6 in E♭ major, D. 950
 * Sparks
 * "In the Future" from the album Indiscreet
 * Karlheinz Stockhausen
 * Montag aus Licht, act 1, scene 6, "Das große Geweine", b. 879–881
 * Igor Stravinsky
 * L'Histoire du soldat
 * Heitor Villa-Lobos
 * Chôros No. 2
 * String Quartet No. 3, second movement (Molto Vivo)
 * Stevie Wonder
 * "You Are the Sunshine of My Life" (introduction)
 * Joe Hisaishi
 * "Les Aventuriers" from Piano Stories II – The Wind of Life, 1996


text:
Mesa (computer graphics)

Mesa, also called Mesa3D and The Mesa 3D Graphics Library, is an open source implementation of OpenGL, Vulkan, and other graphics API specifications. Mesa translates these specifications to vendor-specific graphics hardware drivers.

Its most important users are two graphics drivers mostly developed and funded by Intel and AMD for their respective hardware (AMD promotes their Mesa drivers Radeon and RadeonSI over the deprecated AMD Catalyst, and Intel has only supported the Mesa driver). Proprietary graphics drivers (e.g., Nvidia GeForce driver and Catalyst) replace all of Mesa, providing their own implementation of a graphics API. An open-source effort to write a Mesa Nvidia driver called Nouveau is developed mostly by the community.

Besides 3D applications such as games, modern display servers (X.org's Glamor or Wayland's Weston) use OpenGL/EGL; therefore all graphics typically go through Mesa.

Mesa is hosted by freedesktop.org and was initiated in August 1993 by Brian Paul, who is still active in the project. Mesa was subsequently widely adopted and now contains numerous contributions from various individuals and corporations worldwide, including from the graphics hardware manufacturers of the Khronos Group that administer the OpenGL specification. For Linux, development has also been partially driven by crowdfunding.

Implementations of rendering APIs

Mesa is known as housing implementations of graphic APIs. Historically the main API that Mesa has implemented is OpenGL, along with other Khronos Group related specifications (like OpenVG, OpenGL ES or recently EGL). But Mesa can implement other APIs and indeed it did with Glide (deprecated) and Direct3D 9 since July 2013. Mesa is also not specific to Unix-like operating systems: on Windows for example, Mesa provides an OpenGL API over DirectX.

Mesa implements a translation layer between a graphics API such as OpenGL and the graphics hardware drivers in the operating system kernel. The supported version of the different graphic APIs depends on the driver, because each hardware driver has its own implementation (and therefore status). This is especially true for the "classic" drivers, while the Gallium3D drivers share common code that tend to homogenize the supported extensions and versions.

Mesa maintains a support matrix with the status of the current OpenGL conformance visualized at https://mesamatrix.net/. Mesa 10 complies with OpenGL 3.3 for Intel, AMD/ATI, and Nvidia GPU hardware. Mesa 11 was announced with some drivers being OpenGL 4.1 compliant.

Mesa 12 contains OpenGL 4.2 and 4.3 and Intel Vulkan 1.0 support.

Mesa 13 brought Intel support for OpenGL 4.4 and 4.5 (all Features supported for Intel Gen 8+, Radeon GCN, Nvidia (Fermi, Kepler), but no Khronos-Test for 4.5-Label) and experimental AMD Vulkan 1.0 support through the community driver RADV. OpenGL ES 3.2 is possible with Intel Skylake (Gen9).

1st stable version of 2017 is 17.0 (new year Counting). Ready features are certified OpenGL 4.5, OpenGL 4.5 for Intel Haswell, OpenGL 4.3 for Nvidia Maxwell and Pascal (GM107+). Huge performance gain was measured with Maxwell 1 (GeForce GTX 750 Ti and more with GM1xx). Maxwell-2-Cards (GeForce GTX 980 and more with GM2xx) are underclocked without Nvidia information.

The Khronos CTS test suite for OpenGL 4.4, 4.5 and OpenGL ES 3.0+ is in now (2017-01-24) Open Source and all tests for Mesa 13 and 17 are now possible without costs.

2nd stable version of 2017, 17.1.0, came out on 10 May 2017 with some interesting improvements. OpenGL 4.2+ for Intel Ivy Bridge and OpenGL 3.3+ for Intel Open SWR Rasterizer are 2 of the highlights.

Due to the modularized nature of OpenGL, Mesa can support extensions from newer versions of OpenGL without claiming full support for such versions. For example, in July 2016, Mesa supported OpenGL ES 3.1 but also all OpenGL ES 3.2 extensions except for five, as well as a number of extensions not part of any OpenGL or OpenGL ES version.

3rd Version 17.2 is available since September 2017 with some new OpenGL 4.6 features and velocity improvements in 3D for Intel and AMD. Only 1.4% of Tests fail for OpenGL 4.5 in Nouveau for Kepler.

4th Version 17.3 is ready since December 2017. Many improvements in many drivers are available. OpenGL 4.6 is nearly fully available (Spir-V is not ready). AMD Vulkan Driver RADV is now fully conformant in Khronos-Test.

1st version of 2018 is 18.0 and available since March 2018 by same scheme in 2017. Full OpenGL 4.6 support is not ready, but many features and improvements were successfully tested in RC3. 10-bit support for Intel i965 in Colors is also a Highlight. New is support for Intel Cannon Lake and AMD Vega with actual Linux Version. AMD Evergreen Chips (RV800 or R900) are near OpenGL 4.5 support. Old AMD R600 or RV700 Chips can only support OpenGL 3.3 with some features of OpenGL 4.x. Freedreno is the Driver for Adreno Hardware and near OpenGL 3.3 support.

2nd version of 2018 is 18.1 and available since May. Target is Vulkan 1.1.72 in Intel ANV and AMD RADV driver. OpenGL 4.6 with spir-V is also main target. Permanent work is possible completion of Features and Optimization of drivers for older hardware like AMD R600/Evergreen, Nvidia Tesla and before, Fermi, Kepler or Intel Sandybridge, Ivybridge, Haswell or Broadwell. ARM Architecture made also great improvements in Adreno 3xx/4xx/5xx and Broadwell VC4/VC5 for Raspi with main target OpenGL ES.

3rd version of 2018 is 18.2 and available in calendar stable in September. OpenGL 4.6 with spir-V and Vulkan 1.1.80 are in WIP. The soft Driver for virtual machines VIRGL is ready for OpenGL 4.3 and OpenGL ES 3.2. RadeonSI is also ready for OpenGL ES 3.2. ASTC Texture Compression Support and Compatibility Modus Support for OpenGL 4.4 (3.1 in 18.1) are other highlights in RadeonSI for AMD GCN Cards. New Vulkan 1.1 and more features for Intel and AMD are available. See more Details for Vulkan in Mesamatrix.

4th version of 2018 is 18.3 and released as stable Version 18.3.1 in December 2018. Many features in Detail and support of newer hardware are main parts. Full support of OpenGL 4.6 is not ready.

1st Version of 2019 is 19.0 and was now released at March. Full support of OpenGL 4.6 is not ready, but many improvements on this way are in all drivers.

2nd Version of 2019 is 19.1. Transition of TGSI to NIR is here one main Feature on way to OpenGL 4.6 with Spir-V and more OpenCL. RadeonSI runs well in dev-Version with NIR.

3rd Version of 2019 is 19.2. OpenGL 4.6 is Beta ready for new Intel Iris Driver.

4th Version of 2019 is 19.3. OpenGL 4.6 is ready for Intel i965 and optional for new Iris Driver.

First Version of 2020 is 20.0. Vulkan 1.2 is ready for AMD RADV and Intel ANV. Intel Iris is default for Intel Broadwell Gen 8+. RadeonSI driver switched to using NIR by default, instead of TGSI.

2nd Version of 2020 is 20.1. Many improvements are ready in many drivers. Zink is a new virtual driver for OpenGL over Vulkan.

3rd Version of 2020 is 20.2. OpenGL 3.0 for Zink is one new feature. LLVMpipe will support OpenGL 4.3+ (4.5+ in 20.3). ARM Panfrost is mostly improved with many modules. Shared virtual memory is possible for OpenCL in Nouveau with Pascal and higher.

4th Version of 2020 is 20.3. v3d and v3dv are new drivers for OpenGL and Vulkan 1.0 with Broadcom hardware like Raspberry Pi 4. OpenCL 1.2 is full supported in clover module. Zink support OpenGL 3.3+. LLVMpipe virtual driver support now OpenGL 4.5+ with 4.6 in view. Lavapipe (originally called Vallium ) as Vulkan Tree of LLVMpipe is merged.

In Mesa 21.0 d3d12 will be merged with OpenGL 3.0 to 3.3. Microsoft and Collabora develops new emulation d3d12 in WSL2 to Windows 10 with Direct 3D 12. OpenCL 1.2 is also target in d3d12. An acceleration of factor 2 to 5 is done in Benchmark SPECviewperf with improved OpenGL Code. Many Mesa 21.0 features improves performance. New Release 21.0.0 is public since 11 March 2021.

Mesa 21.1 is second release of year 2021. OpenGL 4.6+ and OpenGL ES 3.1+ is available for Zink. AMD Driver 600g can change to NIR with more possibilities for old Radeon HD 5000 and 6000 cards. Qualcomm Turnip reaches Vulkan 1.1+ and software emulation Lavapipe Vulkan 1.1+. Google VirtIO GPU Driver Venus with Vulkan 1.2+ is merged in experimental state with low performance in mesa main tree.

Mesa 21.2 is third release of year 2021. Google Virtual Vulkan IO Driver Venus will be official introduced with full Vulkan 1.2+ support (more mesamatrix). ARM Panfrost: OpenGL ES 3.1+ Support is available and panVK is the new Vulkan Driver. Initial support started for ARM Apple M1 with new driver Asahi. 21.2 is available since 4 August 2021.

An old plan is to split old drivers in a classic tree with many advantages in programming, support, bug fixing for the modern gallium 3D part. One problem here is Intel i965 with support of Popular old hardware to Intel Haswell and before also with Windows 10 support. A new Gallium3D driver Crocus for Intel Gen 4 Graphics to Haswell is here in development to complete here the gallium3D area with possible split in the next time of year 2021. Crocus is optional available in 21.2. Amber branch is for old drivers without Gallium 3D Functions like Radeon R200, intel i915 and 965 with actual version 21.3.9.

In Version 22.0 Classic drivers are retired. Vulkan 1.3 is available for Intel Anvil and AMD RADV.

Microsoft introduces new driver „Dozen“ for WSL 2 in early development stage as Vulkan over d3d12 in Mesa 22.1.

RustiCL is available at 22.3 with official OpenCL 3.0 Conformance for Intel XE Graphics. Performance is equal and better to AMD ROCm with AMD 6700 XT Card.

A main development target of Mesa 23.0 was ray tracing for Vulkan.

Microsoft develops the Dozen driver for Vulkan in WSL. Vulkan 1.0+ with 80% 1.1 and 1.2 will be available in Mesa 23.2 after delay to 23.1 (See mesamatrix). RustiCL for AMD hardware is available in 23.1.

VirGL for virtual machines jumps in Mesa 23.2 to OpenGL 4.6. Apple Asahi for Apple Arm Machines jumps from OpenGL 2.1 to 3.1 with 90% features of OpenGL 3.2 and 3.3 and OpenGL ES 2.0 to 3.0.

Microsoft Supports in WSL OpenGL 4.6+ in Mesa 24.0 (in Mesa 23.3: 4.3+) with direct 12 translation driver dozen.

Vulkan
The Khronos Group officially announced Vulkan API in March 2015, and officially released Vulkan 1.0 on 16 February 2016. Vulkan breaks compatibility with OpenGL and completely abandons its monolithic state machine concept. The developers of Gallium3D called Vulkan to be something along the lines of Gallium3D 2.0 – Gallium3D separates the code that implements the OpenGL state machine from the code that is specific to the hardware.

Version 1.3 is immediately available with Mesa 22.0. Hardware with support of OpenGL ES 3.1 should run at Vulkan Level 1.3 and before.

As Gallium3D ingests TGSI, Vulkan ingests SPIR-V (Standard Portable Intermediate Representation version "V" as in "Vulkan").

Intel released their implementation of a Vulkan driver for their hardware the day the specification was officially released, but it was only mainlined in April and so became part of Mesa 12.0, released in July 2016. While already the i965 driver wasn't written according to the Gallium3D specifications, for the Vulkan driver it makes even less sense to flange it on top of Gallium3D. Similarly there is no technical reason to flange it with NIR, but yet Intel's employees implemented their Vulkan driver that way.

It is to be expected that AMD's own proprietary Vulkan driver, which was released in March, and was announced to be released as free and open-source software in the future and be mainlined into Mesa, also abandons Gallium3D.

RADV is a free project for AMD and is available since version 13. Conformance with Khronos-Test came in version 17.3. Actual is Full support of Vulkan 1.0 and 1.1 since Mesa 18.1.

Nvidia released their proprietary GeForce driver with Vulkan support at launch day and Imagination Technologies (PowerVR), Qualcomm (Adreno) and ARM (Mali) have done the same or at least announced proprietary Vulkan drivers for Android and other operating systems. But when and whether additional free and open-source Vulkan implementations for these GPUs will show up, remains to be seen.

Mesa Software Driver VIRGL starts Vulkan Development in 2018 with GSOC projects for support of Virtual machines.

Lavapipe is a CPU-based Software Vulkan driver and the brother of LLVMpipe. Mesa Version 21.1 supports Vulkan 1.1+.

Google introduces Venus Vulkan Driver for virtual machines in Mesa 21.1 with full support for Vulkan 1.2+.

Qualcomm Turnip and Broadcom v3dv are new drivers for Qualcomm Adreno and Broadcom Raspberry 4 Hardware. Turnip is the Vulkan brother of freedreno for OpenGL. V3dv supports Vulkan 1.0+ since Mesa 20.3. In Version 21.1 Turnip supports Vulkan 1.1+.

Panfrost PanVK for ARM Mali is at way to Vulkan 1.1, but only 1.0 is stable available with Mesa 22.0.

Project Dozen is connecting direct 3D 12 (d3d12) with Vulkan for Linux Emulation WSL2 in Windows 10 and 11. In Mesa 23.2 Vulkan 1.0 is full conformant supported and 80% of 1.1 and 1.2 (mesamatrix).

Explicit fencing
A kind of memory barrier that separates one buffer from the rest of the memory is called a fence. Fences are there to ensure that a buffer is not being overwritten before rendering and display operations have completed on it. Implicit fencing is used for synchronization between graphics drivers and the GPU hardware. The fence signals when a buffer is no longer being used by one component so it can be operated on or reused by another. In the past the Linux kernel had an implicit fencing mechanism, where a fence is directly attached to a buffer (cf. GEM handles and FDs), but userspace is unaware of this. Explicit fencing exposes fences to userspace, where userspace gets fences from both the Direct Rendering Manager (DRM) subsystem and from the GPU. Explicit fencing is required by Vulkan and offers advantages for tracing and debugging.

Linux kernel 4.9 added Android's synchronization framework to mainline.

Generic Buffer Management
Generic Buffer Management (GBM) is an API that provides a mechanism for allocating buffers for graphics rendering tied to Mesa. GBM is intended to be used as a native platform for EGL on DRM or openwfd. The handle it creates can be used to initialize EGL and to create render target buffers.

Mesa GBM is an abstraction of the graphics driver specific buffer management APIs (for instance the various libdrm_* libraries), implemented internally by calling into the Mesa GPU drivers.

For example, the Wayland compositor Weston does its rendering using OpenGL ES 2, which it initializes by calling EGL. Since the server runs on the "bare KMS driver", it uses the EGL DRM platform, which could really be called the GBM platform, since it relies on the Mesa GBM interface.

At XDC2014, Nvidia employee Andy Ritger proposed to enhance EGL in order to replace GBM. This was not taken positively by the community, and Nvidia eventually changed their mind, and took another approach.

Implementations of video acceleration APIs
There are three possible ways to do the calculations necessary for the encoding and decoding of video streams:

 * 1) use a software implementation of a video compression or decompression algorithm (commonly called a CODEC) and execute this software on the CPU
 * 2) use a software implementation of a video compression or decompression algorithm (commonly called a CODEC) and execute this software on the GPU (the 3D rendering engine)
 * 3) use a complete (or partial) hardware implementation of a video compression or decompression algorithm; it has become very common to integrate such ASICs into the chip of the GPU/CPU/SoC and therefore abundantly available; for marketing reasons companies have established brands for their ASICs, such as PureVideo (Nvidia), Unified Video Decoder (AMD), Video Coding Engine (AMD), Quick Sync Video (Intel), DaVinci (Texas Instruments), CedarX (Allwinner), Crystal HD (Broadcom); some ASICs are available for licensing as semiconductor intellectual property core; usually different versions implement different video compression and/or video decompression algorithms; support for such ASICs usually belong into the kernel driver, to initialize the hardware and do low-level stuff. Mesa, which runs in user-space, houses the implementations of several APIs for software, e.g. VLC media player, GStreamer, HandBrake, etc., to conveniently access such ASICs:

 * Video Acceleration API (VAAPI) – the most common API for Linux, used by AMD and Intel
 * Video Decode and Presentation API for Unix (VDPAU) – used by Nvidia
 * DirectX Video Acceleration (DXVA) – Microsoft Windows-only
 * OpenMAX IL – designed by Khronos Group for video compression
 * Distributed Codec Engine (DCE) – designed by Texas Instruments
 * X-Video Bitstream Acceleration (XvBA) – extension to Xv - succeeded by VAAPI
 * X-Video Motion Compensation (XvMC) – extension to Xv - succeeded by VAAPI

For example, Nouveau, which has been developed as part of Mesa, but also includes a Linux kernel component, which is being developed as part of the Linux kernel, supports the PureVideo-branded ASICs and provides access to them through VDPAU and partly through XvMC.

The free radeon driver supports Unified Video Decoder and Video Coding Engine through VDPAU and OpenMAX.

V4L2 is a kernel-to-user-space interface for video bit streams delivered by webcams or TV tuners.

Due to patent concerns regrading the H.264, H.265 and VC-1 video codecs, Fedora Linux disabled support for VAAPI acceleration for those in its build of Mesa in September 2022.

Device drivers
The available free and open-source device drivers for graphic chipsets are "stewarded" by Mesa (because the existing free and open-source implementation of APIs are developed inside of Mesa). Currently there are two frameworks to write graphics drivers: "classic" and Gallium3D. An overview over some (but not all) of the drivers available in Mesa is given at https://mesamatrix.net/.

There are device drivers for AMD/ATI R100 to R800, Intel, and Nvidia cards with 3D acceleration. Previously drivers existed for the IBM/Toshiba/Sony Cell processor of the PlayStation 3, S3 Virge & Savage chipsets, VIA chipsets, Matrox G200 & G400, and more.

The free and open-source drivers compete with proprietary closed-source drivers. Depending on the availability of hardware documentation and man-power, the free and open-source driver lag behind more or less in supporting 3D acceleration of new hardware. Also, 3D rendering performance was usually significantly slower with some notable exceptions. Today this is still true for Nouveau for most NVIDIA GPUs while on AMDs Radeon GPUs the open driver now mostly matches or exceeds the proprietary driver's performance.

Direct Rendering Infrastructure (DRI)
At the time 3D graphics cards became more mainstream for PCs, individuals partly supported by some companies began working on adding more support for hardware-accelerated 3D rendering to Mesa. The Direct Rendering Infrastructure (DRI) was one of these approaches to interface Mesa, OpenGL and other 3D rendering API libraries with the device drivers and hardware. After reaching a basic level of usability, DRI support was officially added to Mesa. This significantly broadened the available range of hardware support achievable when using the Mesa library.

With adapting to DRI, the Mesa library finally took over the role of the front end component of a full scale OpenGL framework with varying backend components that could offer different degrees of 3D hardware support while not dropping the full software rendering capability. The total system used many different software components.

While the design requires all these components to interact carefully, the interfaces between them are relatively fixed. Nonetheless, as most components interacting with the Mesa stack are open source, experimental work is often done through altering several components at once as well as the interfaces between them. If such experiments prove successful, they can be incorporated into the next major or minor release. That applies e.g. to the update of the DRI specification developed in the 2007-2008 timeframe. The result of this experimentation, DRI2, operates without locks and with improved back buffer support. For this, a special git branch of Mesa was created.

DRI3 is supported by the Intel driver since 2013 and is default in some Linux distributions since 2016 to enable Vulkan support and more. It is also default on AMD hardware since late 2016 (X.Org Server 1.18.3 and newer).

Software renderer
Mesa also contains an implementation of software rendering called swrast that allows shaders to run on the CPU as a fallback when no graphics hardware accelerators are present. The Gallium software rasterizer is known as softpipe or when built with support for LLVM llvmpipe, which generates CPU code at runtime. Since Mesa 10.x OpenGL 3.3+ is supported for Softpipe (10.3) and LLVMpipe (10.2). Actually about 80% of Features from OpenGL 4.x are implemented in Mesa 17.3 (See Mesamatrix).

In Mesa 12.0 a new Intel Rasterizer OpenSWR is available with high advantages in clusters for large data sets. It's more focused on engineering visualisation than in game or art imagery and can only work on x86 processors. On the other hand, OpenGL 3.1+ is now supported. Acceleration values from 29 to 51 related to LLVMPIPE were measured in some examples. OpenGL 3.3+ is supported for OpenSWR since Mesa 17.1.

VirGL is a Rasterizer for Virtual machines implemented in Mesa 11.1 since 2015 with OpenGL 3.3 support and showed in Mesamatrix since Mesa 18. In actual new Mesa 18.2 it supports more than the others with OpenGL 4.3 and OpenGL ES 3.2. About 80% of OpenGL 4.4 and 4.5 features are also now ready. Vulkan Development starts with GSOC 2018 projects.

Actual virGL state in Mesamatrix is full support of OpenGL 4.6+ and OpenGL ES 3.2+ with some necessary Linux software.

D3d12 is a project of Microsoft for WSL2 emulation of OpenGL 3.3+ and OpenCL 1.2+ with Direct3D 12. D3D12 is merged in 21.0. Actual state in Mesa 23.1 is OpenGL 4.2+ with nearly 4.4+ and OpenGL ES 3.1+.

Venus is a new Vulkan VirtIO GPU Driver for GPU in virtual machines by Google. Venus is merged in 21.1 and for public in 21.2 introduced. Venus supports Vulkan 1.3+ in Mesa 23.1. Hardware minimum is Vulkan 1.1 with some extensions.

Mega drivers
The idea of bundling multiple drivers into a single "mega" driver was proposed by Emma Anholt. It allows for a single copy of the shared Mesa code to be used among multiple drivers (instead of it existing in each driver separately) and offering better performance than a separate shared library due to the removal of the internal library interface. The state trackers for VDPAU and XvMC have become separate libraries.

shader-db
shader-db is a collection of about 20,000 shaders gathered from various computer games and benchmarks as well as some scripts to compile these and collect some statistics. Shader-db is intended to help validate an optimization.

It was noticed that an unexpected number of shaders are not hand-written but generated. This means these shaders were originally written in HLSL and then translated into GLSL by some translator program, such as e.g. HLSL2GLSL. The problem is, that the generated code is often far from being optimal. Matt Turner said it was much easier to fix this in the translator program than having to make Mesa's compiler carry the burden of dealing with such bloated shaders.

shader-db cannot be considered free and open-source software. To use it legally, one must have a license for all the computer games that the shaders are part of.

Software architecture
The so-called "user-mode graphics device drivers" (UMD) in Mesa have very few commonalities with what is generally called a device driver. There are a couple of differences:
 * they are meant to work on top of additionally existent kernel mode graphics device drivers, that are e.g. available as part of the Linux kernel found in the source code under  Each UMD communicates with its kernel mode counterpart with the help of a specific library, name libdrm_specific and a generic one, named libdrm. This section shall look solely on the user-mode part above libdrm
 * there is some implementation of the finite-state machine as specified by e.g. OpenGL; this implementation of the OpenGL state machine may be shared among multiple UMDs or not
 * they consist to a great part of some sort of compiler, that ingests e.g. GLSL and eventually outputs machine code. Parsers may be shared among multiple UMD or be specific

Mesa's Intermediate Representations
One goal of Mesa is the optimization of code that is to be executed by the respective GPU. Another is the sharing of code. Instead of documenting the pieces of software, this article shall instead look at the Intermediate Representations used in the process of compiling and optimizing. See Abstract syntax tree (AST) and Static single assignment form (SSA form).

SPIR-V
SPIR-V is a certain version of the Standard Portable Intermediate Representation. The idea is, that graphics applications output SPIR-V instead of GLSL. In contrast to the latter, SPIR-V is binary to avoid implementation differences between GLSL compiler frontends of different driver implementations, as this has been a major source of application incompatibilities and bugs. Also SPIR-V binary usually also passed through some general optimizations. SPIR-V's binary representation also offers some degree of obfuscation, which might appeal to some software vendors as a form of intellectual property protection; however, SPIR-V contains ample information for reflection and tools exist that translate SPIR-V back into high quality, human readable high level code. A UMD needs only apply optimizations, that are specific to the supported hardware.

 * SPIR-V Specification (Provisional)

GLSL IR

 * cgit.freedesktop.org/mesa/mesa/tree/src/compiler/glsl/README
 * XDC2014, Matt Turner:, Matt Turner - GLSL compiler: Where we've been and where we're going
 * XDC2015, Matt Turner:, http://www.x.org/wiki/Events/XDC2015/Program/turner_glsl_compiler.pdf

NIR
NIR (New Internal Representation) was introduced to overcome TGSI limitations. NIR was extended in last and actual releases as base of Spir-V support and is since 2016 main development area. LLVMpipe, i965, RadeonSI, Nouveau, freedreno, vc4 are changed to NIR from TGSI. RADV, Zink and other new drivers starts with NIR. All drivers with full OpenGL 4.6 support are related to NIR by SPIR-V support. Also AMD r600 has a fork with NIR for better support of HD5000 and HD6000 series. This option for r600 is default since Mesa 21.0.
 * Connor Abbott - NIR, or moving beyond GLSL IR in Mesa XDC2014
 * (Mesa-dev) 2014-12-15 Reintroducing NIR, a new IR for mesa
 * cgit.freedesktop.org/mesa/mesa/tree/src/compiler/nir/README
 * fosdem.org/2016/schedule/event/i965_nir/attachments/slides/1113/export/events/attachments/i965_nir/slides/1113/nir_vec4_i965_fosdem_2016_rc1.pdf
 * NIR in RadeonSI
 * Nouveau update 2018
 * Nouveau with NIR in Mesa 19.3

TGSI
The Tungsten Graphics Shader Infrastructure (TGSI) was introduced in 2008 by Tungsten Graphics. All Gallium3D-style UMDs ingest TGSI. NIR is now Main development area, so TGSI is only for older driver like r300g default infrastructure and will be deprecated in some years.

GLSL-To-TGSI code will be deleted in Mesa 22.2. Default is newer NIR-to-TGSI with GLSL-to-NIR for all native NIR drivers. Some older TGSI drivers are supported with this NIR Code path. Later NIR-To-TGSI will be deprecated for native NIR drivers only.

LLVM IR
The UMDs  and   do not output machine code, but instead LLVM IR. From here on, LLVM does optimizations and the compilation to machine code. This does mean, that a certain minimum version of LLVM has to be installed as well.

RADV ACO IR
RADV ACO uses own IR that is close to NIR, for optimizing and generating end binary code for Vulkan SPIR-V shaders on top of Radeon GPUs (GCN 1+, aka GFX6+) GPUs. As of version 20.1.0 the ACO is only used in RADV (Vulkan driver) and not in RadeonSI yet.

Mesa's GLSL compiler
Mesa's GLSL compiler generates its own IR. Because each driver has very different requirements from a LIR, it differentiates between HIR (high-level IR) and LIR (low-level IR).

Gallium3D
Gallium3D is a set of interfaces and a collection of supporting libraries intended to ease the programming of device drivers for 3D graphics chipsets for multiple operating systems, rendering or video acceleration APIs. It is free and open-source graphics device driver software.

A feature matrix is being provided at https://mesamatrix.net/.

The development of Gallium3D started in 2008 at Tungsten Graphics, and the implementation is available as free and open-source software as part of Mesa 3D hosted by freedesktop.org. The primary goal of making driver development easier, bundling otherwise duplicated code of several different drivers at a single point, and to support modern hardware architectures. This is done by providing a better division of labor, for example, leaving memory management to the kernel DRI driver.

Gallium3D has been a part of Mesa since 2009 and is currently used by the free and open-source graphics driver for Nvidia (nouveau project), for AMD's R300–R900,  Intel's 'Iris' driver for generation 8+ iGPUs and for other free and open-source GPU device drivers.

Software architecture
Gallium3D eases programming of device drivers by splitting the graphics device driver into three parts. This is accomplished by the introduction of two interfaces: Gallium3D State Tracker Interface and the Gallium3D WinSys Interface. The three components are called:

 * Gallium3D State Tracker
 * Each graphical API by which a device driver is being addressed has its own State Tracker, e.g. there is a Gallium3D State Tracker for OpenGL and a different one for Direct3D or GLX. Each State Tracker contains an implementation of the Gallium3D State Tracker Interface, and is unique, this means is shared by all existent Gallium3D device drivers.

 * Gallium3D hardware device driver
 * This is the actual code, that is specific to the underlying 3D graphic accelerator, but only as far as the Gallium3D WinSys Interface allows. There is a unique Gallium3D hardware device driver for each available graphics chip and each implements the Gallium3D State Tracker Interface as well as the Gallium3D WinSys Interface. The Gallium3D hardware device driver understands only TGSI (Tungsten Graphics Shader Infrastructure), an intermediate language for describing shaders. This code translated shaders translated from GLSL into TGSI further into instruction set implemented by the GPU.

 * Gallium3D WinSys
 * This is specific to the underlying kernel of the operating system and each one implements the Gallium3D WinSys Interface to interface with all available Gallium3D hardware device drivers.

Differences from classic graphics drivers
Gallium3D provides a unified API exposing standard hardware functions, such as shader units found on modern hardware. Thus, 3D APIs such as OpenGL 1.x/2.x, OpenGL 3.x, OpenVG, GPGPU infrastructure or even Direct3D (as found in the Wine compatibility layer) will need only a single back-end, called a state tracker, targeting the Gallium3D API. By contrast, classic-style DRI device drivers require a different back-end for each hardware platform and several other APIs need translation to OpenGL at the expense of code duplication. All vendor device drivers, due to their proprietary and closed-source nature, are written that way meaning that, e.g. the AMD Catalyst implements both OpenGL and Direct3D, and the vendor drivers for the GeForce have their implementations.

Under Gallium3D, Direct Rendering Manager (DRM) kernel drivers will manage the memory and Direct Rendering Interface (DRI2) drivers will be more GPU processing oriented. During the transition period from userspace modesetting to kernelspace modesetting some of the Mesa 3D drivers, such as the radeon driver or Intel's drivers, ended up supporting both DRI1 and DRI2 and used DRI2 if available on the system. Gallium3D additionally requires a level of shader support that is not available on older cards like e.g. ATi r100-r200 so users for those cards need to keep using Mesa 3D with DRI2 for their 3D usage.

Tungsten Graphics Shader Infrastructure
Tungsten Graphics Shader Infrastructure (TGSI) is an Intermediate representation like LLVM Intermediate Representation or the new Standard Portable Intermediate Representation (SPIR) to be used by the Vulkan API and OpenCL 2.1. Shaders written in OpenGL Shading Language are to be translated/compiled into TGSI, then optimizations are made, and then the TGSI shaders are being compiled into shaders for the instruction set of the used GPU.

NIR is the new Layer representation in Mesa with full SPIR-V support and since 2019 main development area of all newer drivers with OpenGL 4.6 support.

LLVM usage
In addition, using the modular structure of Gallium3D, there is an effort underway to use the LLVM compiler suite and create a module to optimize shader code on the fly.

The library represents each shader program using an extensible binary intermediate representation called Tungsten Graphics Shader Infrastructure (TGSI), which LLVM then translates into GLSL shaders optimized for target hardware.

Adoption
Several free and open-source graphics device drivers, which have been, or are being written based on information gained through clean-room reverse engineering, adopted the driver model provided by Gallium3D, e.g. nouveau and others (see Free and open-source graphics device driver for a complete list). The main reason may be that the Gallium3D driver model lessens the amount of code required to be written. Of course, being licensed under a free software license, this code can at any time by anybody be rewritten to implement the DRI-, or some other, driver model.

History
Original authors of Gallium3D were Keith Whitwell and Brian Paul at Tungsten Graphics (acquired by VMware in 2008).

Milestones
As of fall 2011, there were at least 10 known, mature and working Gallium3D drivers. Open-source drivers for Nvidia graphics cards by the name of Nouveau team develops its drivers using the Gallium3D framework.

2008-07-13: Nouveau development is done exclusively for the Gallium framework. The old DRI driver was removed from the master branch of the Mesa repository on Freedesktop.org.

2009-02-11: The gallium-0.2 branch was merged into mainline Master branch of Mesa. Development is done in Mesa mainline.

2009-02-25: Gallium3D can run on Linux as well as FreeBSD kernels.

2009-05-01: Zack Rusin from Tungsten Graphics added the OpenVG state tracker to Mesa 3D, which enables Scalable Vector Graphics to be hardware-accelerated by any Gallium3D-based driver.

2009-07-17: Mesa3D 7.5 is released, the first version to include Gallium3D.

2010-09-10: Initial support for the Evergreen GPUs was added to the r600g driver.

2010-09-21: There are two Gallium3D drivers for ATI hardware known as r300g and r600g for R300-R500 and R600-Evergreen GPUs respectively.

2010-09-21: Major commits were made to the code to support Direct3D 10 and 11. In time, this might offer the ability to use recent Direct3D implementations on Linux systems.

2011-11-30: Intel 965g and Cell Gallium drivers were removed from the master branch of Mesa as unmaintained and broken.

2013-11-30: Mesa 10 with OpenGL 3.2, 3.3 and OpenCL 1.0+

2014-11-18: Major commits were made to the code to support Direct3D 9.

2015-09-15: Mesa 11 with OpenGL 4.0, 4.1 and OpenCL 1.2 (incomplete)

2015-12-15: Mesa 11.1 Driver VIRGL for virtual machines with OpenGL 3.3

2016-07-08: Mesa 12 with OpenGL 4.2, 4.3 and Vulkan 1.0 (Intel ANV and AMD RADV)

2016-11-01: Mesa 13 with OpenGL 4.4 and OpenGL ES 3.2

2017-02-13: Mesa 17.0 with OpenGL 4.5 and freedreno driver with OpenGL 3.0 and 3.1

2017-05-10: Mesa 17.1 OpenGL 4.2+ for Intel Ivy Bridge (more than Intel driver for Windows, OpenGL 3.3+ for Intel Open SWR Rasterizer (important for cluster Computer for huge simulations)

2017-12-08: Mesa 17.3 AMD Vulkan Driver RADV full compliant in Khronos Test of Vulkan 1.0

2018-05-18: Mesa 18.1 with Vulkan 1.1 (Intel ANV and AMD RADV)

2018-09-07: Mesa 18.2 with OpenGL 4.3 for Soft Driver VIRGL (important for virtual machines in cloud Cluster Computer), OpenGL ES 3.1 for Freedreno with Adreno A5xx

2019-06-11: Mesa 19.1 released with Intel's next generation 'iris' graphics driver for generation 8+ iGPUs

2019-12-11: Mesa 19.3 released OpenGL 4.6 with Intel i965 with gen 7+ and optional Iris Gen 8+

2020-03-18: Mesa 20.0 released OpenGL 4.6 with AMD GCN and Vulkan 1.2 for Intel

2020-05-27: Mesa 20.1 released NIR vectorisation support and shared virtual memory support for OpenCL in Clover

2020-11-30: Mesa 20.3 full support of OpenCL 1.2 in Clover

2021-03-11: Mesa 21.0 initial support of "D3D12“: Direct 3D 12 for WSL2 in Windows 10 with OpenGL 3.3+, ARM Freedreno: OpenGL 3.3+

2021-05-05: Mesa 21.1 initial support of Google VirtIO GPU Driver "Venus“ with Vulkan 1.2+; Zink: OpenGL 4.6+, OpenGL ES 3.1+; Qualcomm Turnip, Lavapipe: Vulkan 1.1+

2021-08-04: Mesa 21.2 initial support of new Intel Crocus OpenGL 4.6 driver based on gallium3D to Intel Sandy Bridge to Haswell for old i965, Vulkan Driver panVK for ARM Panfrost

2022-03-09: Mesa 22.0 full support of Vulkan 1.3 by Intel Anvil and AMD RADV

2023-05-10: Mesa 23.1 OpenCL with Rust: RustiCL for AMD GCN Hardware available (more hardware wip)

2023-09-30: Mesa 23.2 with Apple Asahi OpenGL 3.1 and OpenGL ES 3.0, RADV supports Ray Tracing in AMD RDNA 2 and 3, Intel Anvil Vulkan H.265 decoding support

Performance

 * Performance comparison of free and open-source graphics device drivers

History
Project initiator Brian Paul was a graphics hobbyist. He thought it would be fun to implement a simple 3D graphics library using the OpenGL API, which he might then use instead of VOGL (very ordinary GL Like Library). Beginning in 1993, he spent eighteen months of part-time development before he released the software on the Internet in February 1995. The software was well received, and people began contributing to its development. Mesa started off by rendering all 3D computer graphics on the CPU. Despite this, the internal architecture of Mesa was designed to be open for attaching to graphics processor-accelerated 3D rendering. In this first phase, rendering was done indirectly in the display server, leaving some overhead and noticeable speed lagging behind the theoretical maximum. The Diamond Monster 3D, using the Voodoo Graphics chipset, was one of the first 3D hardware devices supported by Mesa.

The first true graphics hardware support was added to Mesa in 1997, based upon the Glide API for the then new 3dfx Voodoo I/II graphics cards and their successors. A major problem of using Glide as the acceleration layer was the habit of Glide to run full screen, which was only suitable for computer games. Further, Glide took the lock of the screen memory, and thus the display server was blocked from doing any other GUI tasks.

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

title: Mesa (computer graphics)


text:
User talk:Sam Spade/ - archive/Februar 2005

Ta
Thanks Sam.

Lapsed Pacifist 18:04, 23 Jan 2005 (UTC)

 * Your very welcome, glad to have you, 18:04, 23 Jan 2005 (UTC)

Meeting reminder
Sam, just to let you know I've logged on to #AMA and Wally is also there. Hopefully you will show up before the top of the hour when the meeting is supposed to begin. — ©  Alex756  18:24, 23 Jan 2005 (UTC)

Logs of first AMA Membership meeting
You may view the log of the first meeting on the following two pages: AMA IRC Meeting log (1-23-05) (first hour) and AMA IRC Meeting log (1-23-05) Pt II (remainder of meeting). If you are interested in commenting on the agenda of the meeting please do so here:AMA Meeting (suggested topics).

OFFICIAL SECOND MEETING NOTICE AND REQUEST FOR INFORMATION

 * "The second AMA Membership meeting will be held on Sunday January 30 2005 at 19:00 UTC on freenode IRC channel #AMA. That is 2 PM Eastern NA Time, 11 AM Pacific NA Time, and 8 PM Central European (Amsterdam/Stokholm/Warsaw/Venice) Time. All members are invited to attend."

The coordinator is requesting that members submit the following information for the upcoming coordinatorÕs report:
 * How many individuals did you help as an advocate
 * What is the maximum amount of time you put into a case
 * Do you feel your work as an advocate was successful?
 * How can the advocacy program of the AMA be improved?

Thank you. Please submit your responses here: AMA Coordinator/January 2005 Survey

 * — ©  Alex756  23:30, 23 Jan 2005 (UTC) (The Coordinator)

Need comment
I have been added huge content onto Classical definition of republic and I would like your criticism and/or suggestions. I don't know, without some oversight, what looks good or not, and I would enjoy some constructive criticism, suggestions, ideas. I am still working on it and I need some feedback. Strange, that nobody has gone in and changed anything. Can I get some help please.WHEELER 14:55, 24 Jan 2005 (UTC)

 * OK, will do. Cheers, 15:12, 24 Jan 2005 (UTC)

Arbitration
Arbitration is being sought against you. See WP:RfAr. Adraeus 00:02, 25 Jan 2005 (UTC)

Thanks and need one more favor
Thanks for your edits on the Classical republic article. I have added to the post Romanitas in conjuction with a new article titled Culture defines politics. Can you comment on it for me or do you have any information for pertinent to the new article.WHEELER 01:04, 25 Jan 2005 (UTC)

Arbitration Committee case opening
You have been named as a disputant in the recently opened Charles Darwin/Lincoln dispute case brought before the Arbitration Committee. You may wish to add evidence to Requests for arbitration/Charles Darwin/Lincoln dispute/Evidence to support your case. -- Grun t 🇪🇺 03:34, 2005 Jan 25 (UTC)

Hello, and help?
Thanks for your welcome message on my talk page. Very, very helpful. So, I've begun trying to edit boldly, and almost right off the bat I am embroiled in heated discussion. Could you take a look at the talk page for Talk: Nineteen Eighty-Four and let me know if I am out of line? I think I am right, but then, I've often been wrong before. :) It's more a private question so I can have a third party take a look at my actions and response and let me know how I could improve my approach in the future. Thank you in advance. Alavery7 17:14, 25 Jan 2005 (UTC)

Hi Sam
Sam, there WAS an ongoing discussion concerning whether to remove all stuff that was not about the book. You took one look and made a reference which indicated that you thought that one person was the author of the stuff you removed. That was not the case at all. However, since you decided to remove stuff I did contribute with other stuff that I did not, you seemed to be in agreement with the discussion to clean up the article. Now you appear to have jumped to another conclusion. Sam, I am the type who does not care. I don't delete the work of others, I do discuss, I am polite and I don't revert and I walk away from heated discussions when they are no longer enjoyable. This seems to be such a time. MPLX/MH 20:17, 25 Jan 2005 (UTC)

 * I don't understand why you think I thought that. I didn't. I got the note above from User:Alavery7. I reviewed the article in question, and skimmed its talk page. I made the edit I thought necessary, with no emphasis or excess of thought upon who had wrote it. I then took the passage into the talk page in question and explained why I had removed it. You responded in a way I did not like, making assumptions about my having tried to single someone out, and by removing maybe 1/3rd of the article to the talk page. I understood (perhaps wrongly) your reasoning in that as having been to prove a point of consistency. Regardless of your motivation, I very much disagree w your having removed such a large portion of the article. I have no desire to be less than delightful to be around, and intend to discuss things as needed. I'm sorry we got off on a bad foot, and I promise spend the time necessary to improve the talk page communications. Please try to see things from my eyes, and how moving such a large portion of the article to the talk could seem disturbing to another. Cheers, 22:42, 25 Jan 2005 (UTC)

Psychobilly article
Hello Sam Spade, I'm a newbie to Wikipedia. I created a psychobilly article, but now the vast majority of it has been randomly deleted by an anonymous user. I need your help getting it back. Thank you very much. Inanechild 23:41, 27 Jan 2005 (UTC)

 * Everything looks fine to me, as far as I can tell all your edits have been restored. I'm a big Hank III fan, and you? 10:13, 28 Jan 2005 (UTC)

Kevin B. MacDonald
Do you mind having a look at the KM article again? Most of it was moved to Jewish ethnocentrism on spurious grounds and I've reverted both but expect more hassle. If you agree with the move too (I hope not), I think I'll give up, as I've wanted to do for a long time. Jacquerie27 08:56, 28 Jan 2005 (UTC)

 * OK. 15:51, 28 Jan 2005 (UTC)

Kevin MacDonald
I've left a note on your talk page about KM. Jacquerie27 08:58, 28 Jan 2005 (UTC)

 * This is my talk page ;) 15:51, 28 Jan 2005 (UTC)

 * Whoops! Sorry, I have had a sound laugh when reading this. You two have reminded my Marx Brothers' dialogues. (Unsigned reader)

Need Check for me.
I have edited Family/State paradigm. Somehow, those edits are not showing up on the page. Look at the history and then look at the page. Something is screwy and somebody has messed with the computer codes. Please look into this please. Thanks.WHEELER 15:39, 28 Jan 2005 (UTC)

 * Don't worry, your edits will turn up, the wiki is simply running slow at the moment. 15:47, 28 Jan 2005 (UTC)

Please disregard last. Thanks.WHEELER 15:47, 28 Jan 2005 (UTC)

 * No worries, all is well. Cheers, 15:51, 28 Jan 2005 (UTC)

Thanks for the message
Thanks for the message but that article on "Kultur" has no relation to what I originally wrote. This is sad. I will have to redo the whole thing all over again. WHEELER 19:22, 30 Jan 2005 (UTC)

 * See Talk:Kultur and . Cheers, 19:37, 30 Jan 2005 (UTC)

 * Can you restore the original page history? When the guy changed the title he started the page history all over. Can those be reconnected back. Thanks for your work and vote. WHEELER 21:40, 30 Jan 2005 (UTC)

 * Unfortunately I can't, I'm not an admin. Try getting an admin to do it, you may have to ask a few of them, but eventually one of them ought to be willing. Good luck, 07:07, 31 Jan 2005 (UTC)

OFFICIAL THIRD MEETING NOTICE AND REQUEST FOR INFORMATION
The second AMA IRC Membership meetingwas held on Sunday January 30, 2005 at 19:00 UTC on freenode.net IRC channel #AMA. Attending were Wally, Metasquares, Anthere, Sam Spade, and alex756 (coordinator). The log of the second meeting can be found here: AMA IRC Meeting log (1-30-05).

"The third AMA Membership meeting will be held on Saturday February 12, 2005 at 17:00 UTC on freenode IRC channel #AMA. That is 12:00 Noon Eastern NA Time, 9 AM Pacific NA Time, and 6 PM Central European (Amsterdam/Stokholm/Warsaw/Venice) Time. All members are invited to attend.

Suggested Topics and Specific Proposals

 * MEMBERS PLEASE REVIEW

 * Suggestions for topics/proposals and agenda to be discussed at the next meeting are to be found at: AMA Meeting (suggested topics). All members are requested to make proposals there and respond to proposals on the talk page there before the beginning of the next meeting so discussion can be held forthwith concerning such proposals. Thank you, your Coordinator.

The coordinator is requesting that members who have not done so already submit the following information for the upcoming coordinatorÕs report:
 * How many individuals did you help as an advocate
 * What is the maximum amount of time you put into a case
 * Do you feel your work as an advocate was successful?
 * How can the advocacy program of the AMA be improved?

Thank you. Please submit your responses here. — ©  Alex756  23:21, 30 Jan 2005 (UTC)

Thanks for the Info
Th name signing thing's been bugging me for a while so thanks for that especially :) User:The IP (sig added by 07:07, 31 Jan 2005 (UTC))

 * No problem, glad to have you! Cheers, 07:07, 31 Jan 2005 (UTC)

Changed title
I changed the title of "Culture defines politics" to Cultural imprint on politics. I think this is a winner of a title for the subject material. I hope you agree. Let me know what you think? Thanks for your consideration and time. WHEELER 19:17, 31 Jan 2005 (UTC)

WikiProject Jehovah's Witnesses
I invite you to sign in as a participant to the new WikiProject Jehovah's Witnesses project and add that page to your watchlist. Tom Haws 21:04, Feb 1, 2005 (UTC)

Adding the AMA to your welcome message
Sam, I think we might have touched on this, but since you do give welcome messages and have your own, perhaps you could add the AMA to the list of links to new members, that might get some new people interested. I noticed that one of your recent new members just joined the AMA. — ©  Alex756  21:27, 1 Feb 2005 (UTC)

 * I think thats an important plan long term, but I think we need to create a more solid framework for the AMA before searching for an influx of clients and members. We'd probably get about as many members as clients, in my estimation. So far, has the AMA had more members or clients? Something to keep in mind. 21:42, 1 Feb 2005 (UTC)

 * I think that there are really only a few people involved in the AMA, even though 30 members are listed (now 31) quite a few of them have not made contributions in a long time, so I think our active membership is really low, probably between 8-10 which is reflected in the number of people who responded to my poll for more information (I know you have a problem with it, but no one else has brought up the same issue as you about it taking too much time to respond with a few lines of general summary). When we started there was not any reason anyone couldn't join, so I don't see any reason not to let people join now. Maybe if they see we are promoting it and thinking up all kinds of activites, that will get more people interested and more cases that we can use to further develop our expertise and learn more about the dispute resolution process. I am not convinced by your thinking above. — ©  Alex756  02:40, 2 Feb 2005 (UTC)

Primitivism
The only things I know about primitivism is what I gleaned from a friend of mine who briefly became one (she started eating pigeons and roadkill) and from a presentation I saw by some primitivists on tour. I found them earnest but unconvincing and a bit odd.

Anyway, as you can gather from my friend (she's since become a Catholic), one thing primativists try to do is get away from the mediated food chain and domestication of animals etc by killing and eating their own food. As far as I can gather they even reject subsistence farming as too technological and want to go back to the hunter-gatherer model of living.

Basically, they're utopians but even the pre-Marxist "utopian socialists" of the 19th century (Owen etc) who set up rural communes are seen as too industralist and modern for primativists. AndyL 22:13, 1 Feb 2005 (UTC)

 * Well thats disturbing... All I know is what I hear from Ted Kazynski, Socialists, and of course what I know from watching non-stop archaeological films w my 12yr old. He has a thing for "ape men", early men, bigfoot, etc and I like to encourage educational hobbies (like editing an encyclopedia, for example ;) 22:22, 1 Feb 2005 (UTC)

Thanks
Thanks for the word of encouragement. I just hate the hypocrisy and the lying. I moved the whole thing to Wikinfo. And I won't be fighting the deletion process. I will continue to work on Wikipedia.WHEELER 14:20, 2 Feb 2005 (UTC)

 * Glad to hear that, we need more citations and less hypocracy around here, thats for sure!

 * Cheers, 16:15, 2 Feb 2005 (UTC)

Charles Darwin case closed
Sam, I really appreciate what you have done in the CD/AL case in favor of Vincent. Unfortunately, he has got the ban, but Adraeus got it too. You have made a great job. --Neigel von Teighen 22:56, 4 Feb 2005 (UTC)

 * I feel that the verdict was much too harsh on Vincent, who was new to the project and seemed confused about the proper method of handling conflict here. I think he generally tried to follow the rules, and was treated unfairly by both his opponents and the commitee. Yes alot of time and energy was wasted, but I think that was less to do w Vincent than our vague process of determining article content. I also think the ruling in regards to Andreus was to leniant, of course I am biased due to the long history of ugliness I have experienced from him, but if your review the evidence I compiled, most of it doesn't relate to him insulting me alone, he has always been very carefree when it comes to incivility. I lodged a bit of a complaint here, but I doubt it will be taken very seriously. Thank you for your thoughtful note, 09:51, 5 Feb 2005 (UTC)

mmx and xmm
sorry about the mmx and xmm mix up i thought it was a spelling mistake didnt read the source :-S sorry User:Roguecomgeek

 * Hmm.. no comprende 09:51, 5 Feb 2005 (UTC)

Thanks for the welcome
The Subject/headline says it all really. Mel Etitis ( Μελ Ετητης ) 14:50, 23 Jan 2005 (UTC)

 * Righteous! Cheers, 15:31, 23 Jan 2005 (UTC)

From me too - of course mine is way belated Tršdel 14:31, 24 Jan 2005 (UTC)

Thanks for your welcome! I found the links very useful. Zikari 03:01, 25 Jan 2005 (UTC)

And from me. Always nice to be greeted in a foreign land. abomination 05:13, 25 Jan 2005 (UTC)

Thank you for the welcome, and the useful links :) Potatojunkie 12:30, 6 Feb 2005 (UTC)

Oh hey, I just noticed you all up there! Glad to see I've helped a bit, let me know if there is anything more I can do! 12:42, 6 Feb 2005 (UTC)

survey in Talk:anarchism
Since you've been one of the regular editors of the anarchism article, I'd like to see your answers to the survey posted in the talk pages. Cheers, --albamuth 21:03, 6 Feb 2005 (UTC)

 * ok. 21:34, 6 Feb 2005 (UTC)

IP Address
Have I just done something stupid by signing an old talk post of mine that I posted with my IP address (accidentally) with my username, thus connecting the two to unsavvory characters?Theaterfreak64 00:34, Feb 7, 2005 (UTC)

 * Probably not. Not only was what you did more in the spirit of the wiki community (letting us know who were talking to), it also made you slightly more anonymous and less vulnerable. Having ones IP address on display, while unlikely to result in any unpleasantness, does provide an easier opportunity for tracking you down or hacking you. See . Cheers, 08:01, 7 Feb 2005 (UTC)

Missing Wikipedians
I would like to know why you removed gK from that list. -- AllyUnion (talk) 12:39, 7 Feb 2005 (UTC)

 * . 12:51, 7 Feb 2005 (UTC)

Tutorial/Introduction
You appear to have submerged the (very) nice Tutorial which Isomorphic wrote, and I've contributed to, behind a redirect to the Introduction. Seeing no discussion of this on the talk page for the Tutorial, I'm curious why you did this, and where it might have been discussed. In lieu of any such discussion, might I suggest you retract the redirect until such discussion has taken place somewhere? --Baylink 14:35, 7 Feb 2005 (UTC)

 * I don't know anythiung about that, I responded to the note at the top of this page. I am copying this conversation to Wikipedia talk:Introduction. Cheers, 14:43, 7 Feb 2005 (UTC)

Atheism
What prompted you to make the edits today? No doubt you were aware of the need for discussion before changing this article. Please consider joining the discussion. BM seems to be trying get it going by adressing some of your edits. Mgm|(talk) 18:38, Feb 7, 2005 (UTC)

your signature (again)
I've mentioned this a while ago, but you haven't taken action. It is not acceptable to use a standard template for your signature, like what you are using Template:vip. Change it immediately, because we've been discussing either redirecting, modifying or removing that template. When that happens, all your signatures on every page you've signed are going to break. -- Netoholic @ 19:00, 2005 Feb 7 (UTC)

 * It would appear you could use a course in public speaking, since you seem to have trouble expressing yourself intelligibly. Are you talking about this "conversation"? I don't know what your on about, but I'll be looking into it. 21:43, 7 Feb 2005 (UTC)

 * This conversation. There really is no reason to delay. Go into your user preferences and change your signature so it doesn't use any template. -- Netoholic @ 21:58, 2005 Feb 7 (UTC)

 * I think not. 22:12, 7 Feb 2005 (UTC)

Plagerism
I know that at least one paragraph of the Louis Pasteur article is plagerized directly from World Book, that is, the last one in the germ theory section. However, 1) I know not enough about the subject to do more than paraphrase (not summerize) this paragraph (and that would take some work even still), 2) if I list it on the copyright violations page, I think I will be suggesting that the whole article be deleted, as you know, and 3) no one has responded to the post on the talk page yet, which has been up since Nov. 29, 2004.

What would you suggest?

--Theaterfreak64 00:16, Feb 8, 2005 (UTC)

 * I rewrote it a bit, what do you think? (Sam Spade | talk | contributions) 12:07, 8 Feb 2005 (UTC)

Thanks.--Theaterfreak64 08:05, Feb 12, 2005 (UTC)

Febuary 25th.
You planning on joining in? Good. Then everybody else on Wikipedia can see you for what you really are. Rick K 23:41, Feb 8, 2005 (UTC)

 * Of course not, your the only troll on this page. (Sam Spade | talk | contributions) 10:02, 9 Feb 2005 (UTC)

Current discussion you might be interested in
http://en.wikipedia.org/wiki/Wikipedia:Votes_for_deletion/Conscious_evolution

thanks for the welcome
Hey Sam, thanks for the welcome! It's a pleasure to be a part of this project. I'm just sorry that I didn't know about the wiki world much earlier. I'll probably have lots of questions, even after reading the many tutorials.

--Whysperseed 14:38, Feb 9, 2005 (UTC)

 * Of course, and feel free to ask.Keep in mind you don't need to read all the tutorials, they were mainly intended to be used as reference :) (Sam Spade | talk | contributions) 15:59, 9 Feb 2005 (UTC)

Sig
It took me a while to figure out what Neotholic meant, but I think I get it. Using a template like this the server needs to do a transclusion every time it reads your signature. For talk pages you frequently visit that could really drain resources and slow down the rate at which it is loaded.

Why are you using a template anyway? Using the option to code it in your user preferences makes it nearly impossible to vandalise your sig, while now, simply vandalising the template would do. Mgm|(talk) 10:26, Feb 8, 2005 (UTC)

 * Vandalism isn't a big concern for me, I've had precious little of it in my time here. But server needs are quite important, and I am more than willing to compromise when someone polite is making an inteligible request. How is this? (Sam Spade | talk | contributions) 11:52, 8 Feb 2005 (UTC)

 * Hi Sam; Regarding your signature, your Talk page is not being linked. I think that the problem may be the lower case "u" and the underscore; "user-talk" should be "User talk" (I think) Cheers to you, hydnjo talk 22:11, 9 Feb 2005 (UTC)

 * Oops - I forgot about self-referencing links. Your sig is most probably fine as is. Sorry about my confusion on this issue. hydnjo talk 23:36, 9 Feb 2005 (UTC)

 * Haha... Where did you come from? ;) (Sam Spade | talk | contributions) 14:20, 10 Feb 2005 (UTC)

 * hydnjo .... backs away ..... bowing ....and wondering wtf, where did I come from ;) hydnjo talk 22:59, 10 Feb 2005 (UTC)

 * Quite alright, nice to meet you. Let me know if you think of anything I can help you with, eh? Cheers, (Sam Spade | talk | contributions) 12:31, 11 Feb 2005 (UTC)

The content is not the same as the community
Note that the content of the Wikipedia (as opposed to the community) is also organized in a fashion that is not overtly hierarchival. For the most part, the relationship between the individual articles does not form any sort of structure.

 * Your joking, right? How about Jimbo, the wikimedia board, the developers, beaurocrats, the arbitration commitee, the mediation commitee, admins, users, new users, anons, known sockpuppets and trolls, and hard banned users.... doesn't that sound like a clear hierarchy to you? Also this ignores completely the general guideline to avoid self references when possible, on top of the POV and factual inaccuracy. 08:24, 24 Jan 2005 (UTC)

 * Sorry -- I think you didn't read well. The developers, bureaucrats, admins, etc., are the community, not the content. Michael Hardy 23:03, 10 Feb 2005 (UTC)

 * You are correct, I did misread, but I still would insist their is an overt hierarchy, from featured article status to totally disputed stubs on vfd, and everywhere in between. Also I would say their ought to be more such article hierarchy, not less. Cheers, (Sam Spade | talk | contributions) 12:16, 11 Feb 2005 (UTC)

Hello
Sorry I didn't know what to say when you came by my profile recently to welcome me, but thanks. Now, there's the matter of some dude calling me a Neo-Nazi and playing all these straw man fallacies. I sternly objected to his ignorant McCarthyism but he has now gone and contacted RickK on his talk page and I don't know what'll happen. Is this common, the "witchfinder general" blacklisting? Does this happen to everybody at some point, on Wikipedia? How do I avoid it? Borderer 02:20, 11 Feb 2005 (UTC)

 * Wikipedia has its own self-centric POV, like all communities. The one here strongly resembles that of an average american or european university, altho with a great deal more pro-Jewish and pro-Israeli bias. It is far left, agressively multi-cultural (pro-homosexual, etc...), anti-theist, and often willing to throw intellectual honesty and rigour out the window to enforce these POV's. RickK is a bit of a "grand inquisitor", altho he is actually rather unpopular w the in-crowd, which is on the Mailing list, in case your interested. Let me know if there is anything I can do to be of assistance, I'm a ]]Wikipedia:AMA|members advocate]], and unlike many others (likely most) here, I appreciate intellectual honesty and real diversity ;) (Sam Spade | talk | contributions) 12:24, 11 Feb 2005 (UTC)

LaurelBush and Laurel Bush
Thanks for the welcome. I am now using (mostly) Laurel Bush, and I believe Wikipedia should come with the warning "Can be nicely addictive". LaurelBush.
 * (Sam Spade | talk | contributions) 12:40, 12 Feb 2005 (UTC)

Dnagod
You can see the discussion for yourself at the Conscious Evolution VfD page. You'll see why he was blocked. SlimVirgin 14:25, Feb 12, 2005 (UTC)

 * That would appear to be a wrongful block. See Administrators' noticeboard/Incidents. (Sam Spade | talk | contributions) 14:32, 12 Feb 2005 (UTC)

 * If you mean &lquo;not in accordance with the letter of Wikipedia rules” then you might be right, but if you mean “morally wrong”, then you're definitely not. Mel Etitis ( Μελ Ετητης ) 14:41, 12 Feb 2005 (UTC)

 * I mean both. I am here on the wikipedia to promote the neutral dissemination of knowledge. Those who use power to enforce bias are contrary to the purpose of the project. (Sam Spade | talk | contributions) 14:46, 12 Feb 2005 (UTC)

 * It's not clear to me why you're so keen to defend someone who spewed racist insults in almost every posting to Wikipedia Talk pages, especially when it's those insults (not the character of his far-from-neutral additions to Wikipedia) which led to the ban. Do you really think that the precise application of the Wikipedia rules (though see my comment at Administrators' noticeboard/Incidents) is more important than common decency and morality? (I'm of course assuming that it's not because you agree with Dnagod's paranoid and hate-filled ravings.) Mel Etitis ( Μελ Ετητης ) 15:07, 12 Feb 2005 (UTC)

 * Firstly, I am a member of AMA, and have undertaken User:Dnagod as a (completely unofficial at this juncture) "client". I did this based on need, not POV. Secondly, your Personal attacks on User:Dnagod and insinuations regarding myself are unfortunate. If you are unable to separate the person from the argument (which would be unfortunate) you could always read User:Sam Spade/Theoretical Biases, where my personal opinions are expressed. You can read that even if you are able to separate the person from the argument, BTW ;) (Sam Spade | talk | contributions) 15:17, 12 Feb 2005 (UTC)

 * I am able to separate arguer from argument, but in Dnagod's case there was no such separation (unless you're implying that he's not a racist, it's only the way he talks). The final sentence of my previous message wasn't meant to be sarcastic, nor to insu=inuate anything other than what I said. (It's true, though, that I think that defending unworthy people against what are perceived as being unfair attacks can start off as being noble, but gradually become something else; it's also true that I've no firm opinion yet as to whether that applies to you, though I confess to being worried.) As to my supposed personal attacks on Dnagod, I merely responded to the way in which he himself spoke. When someone accuses me of being part of a Jewish conspiracy, and rants about the Jewish domination and corruption of Wikipedia, it's not exactly making a leap of logic to refer to them as racist. Indeed, Wikipedia policy seems to back me up on this. Mel Etitis ( Μελ Ετητης ) 15:40, 12 Feb 2005 (UTC)

 * I was refering to "paranoid and hate-filled ravings", not if he was a racist or not. I think were all fairly certain he is a racist. (Sam Spade | talk | contributions) 17:10, 12 Feb 2005 (UTC)

 * When someone takes all criticism as evidence of the critic's membership in a cabal, isn't that paranoid? And isn't racism, especially in the way that he express it, hate-filled? And aren't repetitive and ungrounded fulminations against such a hated cabal ravings? I refer again to Wikipedia policy. Besides, what I say to you about another user is surely not what the policy is about; it's concerned with what I say to that other user. Mel Etitis ( Μελ Ετητης ) 17:24, 12 Feb 2005 (UTC)

 * Just to be clear, I'm not trying to get you in trouble for making personal attacks, I am saying I don't like to hear them, that I find them unfortunate, detracting from the case at hand. Maybe I'm an idealist, but I envision a wikipedia where all verifiable, expert POVs are included, where admins who insist on violating policy are no longer admins, and where special interest group POV majoritocracy does not determine article content (or worse, if articles are deleted). (Sam Spade | talk | contributions) 18:11, 12 Feb 2005 (UTC)

All verifiable, expert POVs yes, but he didn't express any of those. You recently indicated that you don't believe Hitler wanted to destroy European Jewry. It's because of comments like that that some people draw certain conclusions, perhaps unfairly, about your support for Dnagod. SlimVirgin 18:27, Feb 12, 2005 (UTC)

I see you havn't read Reductio ad Hitlerum yet. Sad that. Please do, and then place any slander you can come up w @ User:Spleeman/Sam Spade. Thanks, (Sam Spade | talk | contributions) 19:02, 12 Feb 2005 (UTC)

 * I also remember, rather clearly, being accused (as part of a group) of intellectual dishonesty because I argued that there was a significant difference between a voter with no (or fewer than five) previous edits and one with twenty or thirty. Mel Etitis ( Μελ Ετητης ) 18:40, 12 Feb 2005 (UTC)

 * I never accused you of anything, but that VfD was a joke, as have been other, related VfD's. (Sam Spade | talk | contributions) 19:02, 12 Feb 2005 (UTC)


text:
User talk:Yegorm

Welcome to the Wikipedia
Here are some links I thought useful:

 * Tutorial
 * Help desk
 * Foundation issues
 * Policy Library
 * Utilities
 * Cite your sources
 * Verifiability
 * Wikiquette
 * Civility
 * Conflict resolution
 * Neutral point of view
 * Pages needing attention
 * Peer review
 * Bad jokes and other deleted nonsense
 * Brilliant prose
 * Featured pictures
 * Boilerplate text
 * Current polls
 * Mailing lists
 * IRC channel

Feel free to contact me personally with any questions you might have. About, Help desk, and Village pump are also a place to go for answers to general questions. You can sign your name by typing 4 tildes, like this: ~.

(Sam Spade | talk | contributions) 22:04, 12 Feb 2005 (UTC)

title: User talk:Yegorm


text:
Femtotechnology

Femtotechnology is a term used in reference to the hypothetical manipulation of matter on the scale of a femtometer, or 10−15 m. This is three orders of magnitude lower than picotechnology, at the scale of 10−12 m, and six orders of magnitude lower than nanotechnology, at the scale of 10−9 m.

Theory
Work in the femtometer range involves manipulation of excited energy states within atomic nuclei, specifically nuclear isomers, to produce metastable (or otherwise stabilized) states with unusual properties. In the extreme case, excited states of the individual nucleons that make up the atomic nucleus (protons and neutrons) are considered, ostensibly to tailor the behavioral properties of these particles.

The most advanced form of molecular nanotechnology is often imagined to involve self-replicating molecular machines, and there have been some speculations suggesting something similar might be possible with analogues of molecules composed of nucleons rather than atoms. For example, the astrophysicist Frank Drake once speculated about the possibility of self-replicating organisms composed of such nuclear molecules living on the surface of a neutron star, a suggestion taken up in the science fiction novel Dragon's Egg by the physicist Robert Forward. It is thought by physicists that nuclear molecules may be possible, but they would be very short-lived, and whether they could actually be made to perform complex tasks such as self-replication, or what type of technology could be used to manipulate them, is unknown.

Applications
Practical applications of femtotechnology are currently considered to be unlikely. The spacings between nuclear energy levels require equipment capable of efficiently generating and processing gamma rays, without equipment degradation. The nature of the strong interaction is such that excited nuclear states tend to be very unstable (unlike the excited electron states in Rydberg atoms), and there are a finite number of excited states below the nuclear binding energy, unlike the (in principle) infinite number of bound states available to an atom's electrons. Similarly, what is known about the excited states of individual nucleons seems to indicate that these do not produce behavior that in any way makes nucleons easier to use or manipulate, and indicates instead that these excited states are even less stable and fewer in number than the excited states of atomic nuclei.

In fiction
Femtotechnology plays a critical role in the 2005 science-fiction novel Pushing Ice. It also features in various stories by Greg Egan such as Riding the Crocodile, where he proposes the idea of a "strong bullet" which overcomes the instability of high atomic weight femto-structures by being accelerated to near light speed, letting it travel interstellar distances before impacting a target and constructing a stable nano-scale structure as it decays.

title: Femtotechnology


text: Template:Utah-geo-stub

title: Template:Utah-geo-stub


text:
Talk:Telecom Reform Act

Merged with Telecommunications Act of 1996 as per previous editor's instructions and template. MPLX/MH 22:08, 12 Feb 2005 (UTC)

title: Talk:Telecom Reform Act


text:
Rzeczpospolita (newspaper)

Rzeczpospolita is a Polish nationwide daily economic and legal newspaper, published by Gremi Media. Established in 1920, Rzeczpospolita was originally founded as a daily newspaper of the conservative Christian National Party during interwar Poland. The paper's title is a translation of the Latin phrase res publica (meaning "republic", or "commonwealth"), and is part of the traditional and official name of the Polish state, "Rzeczpospolita Polska."

The newspaper came under government control during the Polish People's Republic (1945–1989). Following the 1989 political revolutions across Europe, the new democratically-elected government relinquished its editorial oversight and ownership of Rzeczpospolita, contributing to the end of media censorship in communist Poland and ushering in a new era of independent press.

In 2016, Rzeczpospolita had a circulation of 274,000; 75% of its readers were reported to have higher education. Generally considered to be center-right of the political spectrum, the paper's editorial board represents conservative-liberal views. Rzeczpospolita is among the most frequently cited media sources in the country and is considered a newspaper of record for Poland.

History
The paper was founded by Ignacy Jan Paderewski and the first issue was published on 15 June 1920. Paderewski sold the paper in 1924 to Wojciech Korfanty, another prominent politician of that time. The editor-in-chief Stanisław Stroński sought to maintain the quality of the content by cooperating with a group of authors, including Adolf Nowaczyński, Kornel Makuszyński, and Władysław Witwicki. The last issue of Rzeczpospolita in the Second Polish Republic was published on the last day of 1931.

During World War II (1940–1943), an irregular paper associated with a Polish resistance group Polish People's Independence Action was issued under the same title.

On 23 July 1944, when the war had not yet ended, the first issue of Rzeczpospolita, a newspaper of the Polish Committee of National Liberation, was published in Chełm. The editor-in-chief was Jerzy Borejsza, a communist activist and journalist during the interwar years, who collaborated with Russians, and later presented opinions in line with the Kremlin. The newspaper began strenuous endeavours to form a positive image of the new government. The Home Army commanders and their decision to commence the Warsaw Uprising were criticised, while nationalisation and land reform were supported.

After the war, Rzeczpospolita was issued by a cooperative publishing house Czytelnik whose president was Borejsza himself. He delegated the editorial duties to Paweł Hoffman, who soon changed the title to ''Rzeczpospolita. Dziennik Gospodarczy (The Economic Daily), and later to Rzeczpospolita. Dziennik Polityczno-Gospodarczy (The Economic and Political Daily''). In 1949, with a new chief editor Henryk Korotyński, the paper joined the campaign against the Roman Catholic Church.

In December 1948, the state authorities had established another newspaper Trybuna Ludu (People's Tribune), an organ of a newly formed political party, the Polish United Workers' Party. Rzeczpospolita had been issued by another two years, until 1951 when it was discontinued because the coexistence of several party newspapers was considered unfavorable for a consolidated one-party state. A part of the team joined Głos Pracy, while others including Korotyński moved to Życie Warszawy.

In 1980, the state had faced a crisis, and consequently the party's overall image deteriorated significantly. This prompted the idea to relaunch a separate government newspaper. In the spring of 1981, thus during the rise of Solidarity, Edmund Osmańczyk, member of parliament of the Polish People's Republic, proposed to revive Rzeczpospolita as a "governmental medium presenting the position of the state on a daily basis". Józef Barecki, former editor of Trybuna Ludu, a member of the Central Committee of the Communist Party and of the parliament, as well as a government spokesman for a year, was appointed as the editor-in-chief. The first issue of the new Rzeczpospolita appeared during martial law, on 14 January 1982.

The state, as an entity, had become officially independent from the party (even though this independence was still largely fictitious within a communist state). Thus, from 1982 onwards, Rzeczpospolita and Trybuna Ludu resumed their parallel existence as the official bulletins of the government and the party apparatus respectively. This dualism corresponded to the situation in the Soviet Union, where the government newspaper Izvestia functioned alongside the party's Pravda, and where Izvestia has steered a course strikingly similar to Rzeczpospolita in the 1990s.

After, the partially free elections of 4 June 1989, and after Tadeusz Mazowiecki became Prime Minister, the management of the newspaper changed as well. Rzeczpospolita was no longer a government medium, and became an independent newspaper. Its new editor-in-chief was Dariusz Fikus (until 1996).

The new Polish government made Rzeczpospolita legitimately independent. In February 1991, Państwowe Przedsiębiorstwo Wydawnicze "Rzeczpospolita", a state publishing company, with Maciej Cegłowski as the new CEO, together with the French Robert Hersant press group, Presse Participations Europennes, established Presspublica company. Its first CEO was the then editor-in-chief of Rzeczpospolita, Dariusz Fikus. Initially, the Polish shareholder held 51% of company shares, while the French owned 49%. In 1993, Rzeczpospolita was named the Newspaper of the Year by the Pheidippides Committee.

In the mid-1990s, the Polish party sold the additional 2% of shares to the French. In 1996, the Norwegian Orkla Media corporation acquired shares held by the Robert Hersant group. During the next 10 years, 51% of shares were held by the subsidiary of Orkla Press Polska, Presspublica Holding Norway, while 49% belonged to Państwowe Przedsiębiorstwo Wydawnicze "Rzeczpospolita" (from 1 March 2000, to Przedsiębiorstwo Wydawnicze "Rzeczpospolita" SA). In October 2006, the shares of Orkla Press Polska were taken over by Mecom Poland Holdings SA forming part of the British Mecom Group.

In October 2011, Gremi Media, owned by the Polish entrepreneur Grzegorz Hajdarowicz, purchased the shares from Mecom Poland and the shares belonging to PW Rzeczpospolita (the State Treasury), becoming a 100% shareholder of Presspublica publishing house. The publishing house changed its name to Gremi Media, after which, in January 2017, it was transformed into a joint stock company operating under the business name of Gremi Media SA.

Contents
The basic edition of Rzeczpospolita is divided into four sections: the main one, dedicated to general news; the economic one (Ekonomia i rynek), the legal one (Prawo co dnia); and the regional one (Życie Regionów).

The general news section features, e.g., information on current political events, reports from Poland and abroad, commentaries and essays, expert opinions, as well as news relating to culture, science, lifestyle, or sports. Prawo co dnia ("Law Every Day") focuses on the changes in regulations and legislation and on legal analyses, including articles on labour law, analyses and expert opinions, or industry-related communications. Ekonomia i rynek ("Economy and Market") provides information about markets, enterprises, finance, current stock quotes, analyses of the economic situation and trends in Poland and abroad, as well as opinions of economists, experts and representatives of the business world.

The nationwide issue of the newspaper includes a series of regional monthly supplements entitled Życie Regionów ("Life of the Regions"). They are dedicated to important investments, business and education in the regions, as well as matters related to local politics, sports, and culture. Życie Regionów is the organiser of public debates that are crucial for local communities, as well as the media partner of major regional events.

On Saturdays, Plus Minus, the weekend edition of Rzeczpospolita, appears, containing articles related to civilisation, literature, lifestyle and metapolitics. It mainly includes essays, commentaries and feature articles, as well as reviews of books and cultural and sporting events. Interviews form a particularly important part of Plus Minus.

Supplements
Newspaper subscription includes such specialised supplements as Podatki (taxes), Administracja (administration), Rzecz o prawie (law), Ekspert Księgowego (accounting), Praca i ZUS (labour and social security matters), or Prawo w Biznesie (law in business).

Dobra Firma ("Good Company") is a daily supplement to the main issue. It is primarily addressed to entrepreneurs from the SME sector. In an easy-to-understand manner, it covers both the legal issues relevant to business owners (taxes, social security, contracts, employment), and business matters (marketing of new products, business ideas, available solutions relating to company vehicles).

Nieruchomości ("Real Estate") appears on Mondays and Fridays. On Mondays, topics relating to construction and housing are presented, while on Fridays, matters related to the commercial real estate market are covered.

Every Tuesday, Rzeczpospolita Cyfrowa ("Digital Republic") is issued with Rzeczpospolita, dedicated to new technologies, with particular focus on their application in running a business and in developing new business branches.

Moje Pieniądze ("My Money") is a Thursday supplement devoted to personal finance. It offers tips on saving and investing money, buying shares and choosing insurance.

The Friday supplement is Rzecz o Historii ("The thing about History"), offering informative articles and historical analysis.

Lists and rankings
Regular publications of Rzeczpospolita include lists and rankings of companies, brands and institutions operating on the Polish market. The best known are: the 500 List, the 2000 List, the Ranking of the Most Valuable Polish Brands, and the Ranking of Law Firms.

The 500 List
The list of the largest Polish companies by revenue, first published in 1999. Modelled on the Fortune list, it is now the only such ranking in Poland. The best developing companies on the list receive the prestigious Rzeczpospolita Eagles awards.

The 2000 List
The list of the best companies according to Rzeczpospolita, first published in 2002. It takes into account their revenues, employment, and results. The ranking of the largest exporters is published as a supplement. Outstanding enterprises from the list receive the Good Company, Exports Eagle and Exports Brand awards.

The Ranking of the Most Valuable Polish Brands
The Ranking of the Most Valuable Polish Brands provides a professional valuation of over 300 brands created specifically for the needs of the Polish market. Apart from value, the strength of brands in separate industry categories is also estimated. The ranking has been published since 2003.

The Ranking of Law Firms
The ranking includes law firms servicing enterprises and operating on the Polish market. Law firms are broken down, among others, in terms of the number of lawyers and legal counsels, the generated revenues and profits, the servicing of the leading market transactions, or the best lawyers in respective areas of law. The ranking has been published since 2003.

Until 2007, Rzeczpospolita was published in the classic broadsheet format. The format then changed to compact, a modern and more functional one.

Style
In 2005, the newspaper received the Grand Front award, and in 2006, during the 27th edition of the competition organised by the Society for News Design, Rzeczpospolita was named "The best designed newspaper in the world". Rzeczpospolita received the Grand Front award also in 2013, for the best cover (dedicated to the resignation of Pope Benedict XVI).

Website
rp.pl was one of the first online news services in the Polish media. The service has operated for 25 years as of 2022, having been launched in March 1997. From November 2014, it has been using RWD technology (full responsiveness). Its current version has been available since 2015.

The website has over 32 million hits and 3 million unique users per month (data as of January 2017 ).Rp.pl is one of the most frequently visited nationwide newspaper websites. In the "Business-Finance-Law" category, Gremi Group is ranked the 6th among all Polish groups of online services.

Mobile application
Rzeczpospolita application for mobile devices combines 5 types of content: printed issues in PDF format, printed newspaper edition in digital form (HTML), videos from Rzeczpospolita.tv (VOD), live streaming of Rzeczpospolita.tv programs, and the latest news from rp.pl service (Najnowsze z RP.pl newsfeed).

The application is available on Google Play and Apple App Store.

Online TV
Since 2009, a video service of Rzeczpospolita has been available at tv.rp.pl. In 2016, an online Rzeczpospolita TV was launched at the same address, currently broadcasting 24/7. Its core are the three daily live programs, "RZECZoPOLITYCE", "RZECZoBIZNESIE" and "RZECZoPRAWIE", as well as commercial programs and coverage of the events organised by Rzeczpospolita. The hosts are well-known Rzeczpospolita contributors, such as Bogusław Chrabota, Michał Szułdrzyński, Marcin Piasecki, Jacek Nizinkiewicz, Ewa Usowicz, Tomasz Pietryga, or Anna Wojda.

The channel is broadcast via Google Hangouts and can be watched daily through the home page of rp.pl. All programs are also available as VOD on tv.rp.pl.

Circulation and sales
A single average issue of Rzeczpospolita is about 65,000 copies. In 2016, approximately 54,000 copies were sold.

Paper version and digital subscription
Rzeczpospolita is distributed through paper version subscription, paper version sales and digital version. Subscription is divided into Basic subscription and Plus subscription dedicated to a more involved, specialised audience. Subscription of Rzeczpospolita offers features such as professional book publications, training, multimedia tools, or access to the archives.

The digital version of Rzeczpospolita is available around 21:00 CET. on the day preceding the day of paper edition.

Opinion leader
Rzeczpospolita has been often rated as the most frequently quoted medium in Poland, and it is considered a newspaper of record for Poland.

In 2014, it was considered the most opinion-making medium of the decade (2004–2013). Also in 2016, Rzeczpospolita won in the ranking of the most influential media in Poland, prepared on a regular basis by the Media Monitoring Institute.

Editorial staff
The editorial staff currently consists of 150 persons (including the secretariat and editors of online content). The headquarters are located in Warsaw at ul. Prosta 51.

Editors-in-chief

 * 1989–1996 – Dariusz Fikus
 * 1996–2000 – Piotr Aleksandrowicz
 * 2000–2004 – Maciej Łukasiewicz
 * 2004–2006 – Grzegorz Gauden
 * 2006–2011 – Paweł Lisicki
 * 2011–2012 – Tomasz Wróblewski
 * 2012 – Andrzej Talaga (acting editor-in-chief)
 * 2013–present – Bogusław Chrabota

title: Rzeczpospolita (newspaper)


text:
Galaxy Records

Galaxy Records was a record label founded in 1964 by Max and Sol Weiss in Berkeley, California. It was a division of Fantasy Records.

History
Galaxy Records was officially launched in 1964 in Berkeley, California. In 1967 Galaxy and Fantasy were sold. After ten years of inactivity, Galaxy released albums by Art Pepper, Chet Baker, Stanley Cowell, Nat Adderley, Tommy Flanagan, Red Garland, Johnny Griffin, Roy Haynes, Hank Jones, Philly Joe Jones, Shelly Manne, and Ira Sullivan. Galaxy Records was closed down for good around 1990's due to conflict problems.

Discography
Galaxy Records first album series, the G-200/8200 series consisted of nine, primarily R&B, albums released between 1963 and 1968. In 1977 Galaxy started the GXY-5100 series, which was a jazz series that ran to 1985.

title: Galaxy Records