text:
HMNB Portsmouth

His Majesty's Naval Base, Portsmouth (HMNB Portsmouth) is one of three operating bases in the United Kingdom for the Royal Navy (the others being HMNB Clyde and HMNB Devonport). Portsmouth Naval Base is part of the city of Portsmouth; it is located on the eastern shore of Portsmouth Harbour, north of the Solent and the Isle of Wight. For centuries it was officially known as HM Dockyard, Portsmouth: as a Royal Dockyard, Portsmouth functioned primarily as a state-owned facility for building, repairing and maintaining warships; for a time it was the largest industrial site in the world.

From the 1970s, the term 'Naval Base' began to be used for Portsmouth (and other Royal Dockyards), acknowledging a greater focus on personnel and support elements alongside the traditional industrial emphases. In 1984 Portsmouth's Royal Dockyard function was significantly downsized and downgraded, and was formally renamed the 'Fleet Maintenance and Repair Organisation' (FMRO). The FMRO was privatised in 1998; in 2002, shipbuilding (which had not taken place on site since the late 1960s) resumed in the form of block construction, but this again ceased in 2014.

Today, Portsmouth is the home base for two-thirds of the Royal Navy surface fleet, including the two aircraft carriers, HMS Queen Elizabeth (R08) and HMS Prince of Wales (R09). Naval logistics, accommodation and messing are provided on site, with personnel support functions (e.g. medical and dental; education; pastoral and welfare) provided by Defence Equipment and Support. Other functions and departments, e.g. Navy Command Headquarters support staff, are also accommodated within the Naval Base. The base is additionally home to a number of commercial shore activities, including the ship repair and maintenance facility operated by BAE Systems Maritime Services.

The base is the oldest in the Royal Navy, and it has been an important part of the Senior Service's history and the defence of the British Isles for centuries. It is home to one of the oldest surviving drydocks in the world. The former Block Mills are of international significance, having been the first factory in the world to employ steam-powered machine tools for mass production. The Royal Naval Museum has been on the site since 1911. In 1985 a partnership between the Ministry of Defence and Portsmouth City Council created the Portsmouth Naval Base Property Trust to manage part of the historic south-west corner of the Naval Base, under a 99-year lease, as an heritage area, the Portsmouth Historic Dockyard. It allows members of the public to visit important maritime attractions such as Mary Rose, HMS Victory, HMS Warrior (1860) and the National Museum of the Royal Navy.

Functioning base
Portsmouth naval base is home to two-thirds of the Royal Navy's surface ships, and employs up to 17,200 people.

Senior personnel
The Naval Base Commander (NBC) since June 2022 is Commodore John Voyce. The harbour is under the control of the King's Harbour Master (KHM), who is the regulatory authority of the Dockyard Port of Portsmouth, an area of approximately 50 sqmi that encompasses Portsmouth Harbour and the Eastern Solent. KHM Harbour Control is based in the Semaphore Tower building. Shipping movements are handled by a team of admiralty pilots headed by the Chief Admiralty Pilot.

In 1836 the Commander-in-Chief, Portsmouth was given accommodation within the Dockyard (in Admiralty House) and in 1889 he was given HMS Victory to be his ceremonial flagship. These privileges were inherited by the Commander-in-Chief Naval Home Command (whose post was combined with that of Second Sea Lord in 1994), who continued to fly his flag from HMS Victory until 2012. That year the post of Commander-in-Chief reverted to the First Sea Lord, and with it the use of Victory as flagship. The Second Sea Lord is now based at the Henry Leach Building on Whale Island, which is also the headquarters of the Fleet Commander.

List of based ships
Some of the following ships (e.g. the patrol vessels) are not based in Portsmouth, but form part of the Portsmouth Flotilla.

First-rate ship of the line

 * HMS Victory

Queen Elizabeth-class aircraft carriers

 * HMS Queen Elizabeth (R08)
 * HMS Prince of Wales (R09)

Type 45 destroyers

 * HMS Daring (D32) – completing refit, scheduled to return to the fleet in 2024
 * HMS Dauntless (D33)
 * HMS Diamond (D34)
 * HMS Dragon (D35) – in refit, scheduled to return to the fleet by end 2024
 * HMS Defender (D36) – entered refit in 2023, scheduled for major upgrade work until 2026
 * HMS Duncan (D37)

Type 23 frigates

 * HMS Lancaster (F229) (Currently forward deployed to Bahrain for 3 years from 2022)
 * HMS Iron Duke (F234) (completed LIFEX refit in 2023)

In changes to base porting arrangements announced in November 2017, HM Ships Westminster, Richmond, Kent and St Albans were to move to the HMNB Devonport by 2023; HM Ship HMS Argyll (F231) moved in the opposite direction. HMS Monmouth (F235) and HMS Montrose (F236) were also to move to Portsmouth. However, Monmouth retired in 2021, Montrose decommissioned in 2023 and Argyll and Westminster followed in 2024. Richmond became a Devonport ship on completion of her refit. St Albans moved to Devonport in July 2019 in preparation for her major refit.

Hunt-class mine countermeasures vessels

 * HMS Ledbury (M30)
 * HMS Cattistock (M31)
 * HMS Brocklesby (M33)
 * HMS Middleton (M34) – assigned to 9 Mine Countermeasures Squadron operating from HMS Jufair in Bahrain
 * HMS Chiddingfold (M37) – assigned to 9 Mine Countermeasures Squadron operating from HMS Jufair
 * HMS Hurworth (M39)

River-class patrol vessels

 * HMS Tyne (P281) – Fishery protection vessel
 * HMS Severn (P282) – Fishery protection vessel
 * HMS Mersey (P283) – Fishery protection vessel
 * HMS Forth (P222) – forward deployed to the Falklands as guard ship since 2019
 * HMS Medway (P223) – forward deployed to the Caribbean since 2020
 * HMS Trent (P224) – forward deployed from Gibraltar since 2021
 * HMS Tamar (P233) – forward deployed to the Indo-Pacific region since 2021, with primary logistics hub at the British Defence Singapore Support Unit in Singapore
 * HMS Spey (P234) – forward deployed to the Indo-Pacific region since 2021, with primary logistics hub at the British Defence Singapore Support Unit in Singapore

Cutlass-class patrol vessels

 * HMS Cutlass (P295) – Gibraltar Squadron
 * HMS Dagger (P296) – Gibraltar Squadron

Archer-class patrol vessels

 * HMS Blazer (P279) – Southampton Universities Royal Naval Unit
 * HMS Exploit (P167) – Birmingham Universities Royal Naval Unit
 * HMS Puncher (P291) – London Universities Royal Naval Unit
 * HMS Ranger (P293) – Sussex Universities Royal Naval Unit
 * HMS Smiter (P272) – Oxford Universities Royal Naval Unit

Experimental vessel

 * XV Patrick Blackett (since 2022) – experimental vessel in RN service

Defence Dive School/Fleet Diving Unit Portsmouth

 * 3× Sea-class 15 m diving support boats

Portsmouth Historic Dockyard

Portsmouth Historic Dockyard is the name given to the portion of the base which is open to the public; it plays host to:
 * The raised wreck of the Tudor carrack Mary Rose viewable in a new (2013) Mary Rose Museum building.
 * HMS Victory, Nelson's flagship at Trafalgar, which (whilst still being in commission) is also open to the public
 * HMS Warrior (1860), the first ocean-going Ironclad (built at Blackwall on the River Thames in 1860 and now moored in the dockyard).
 * HMS M33, a World War I monitor (opened to the public in 2015)
 * The National Museum of the Royal Navy, Portsmouth, one of the world's leading maritime museums. Exhibits include the Trafalgar Sail (the foretop sail of Victory used at the Battle of Trafalgar, 1805)
 * Action Stations, a centre containing interactive exhibits demonstrating various aspects of naval science as well as a number of simulators
 * The Dockyard Apprentice exhibition, telling the story of the Dockyard itself and working life within it.
 * Portsmouth Harbour Tours
 * Boathouse 4 (opened 2015), which tells the 'forgotten story' of the small boats of the Navy and is an active boat building and restoration site.

The Portsmouth Naval Base Property Trust has long sought to extend the area of the Historic Dockyard to cover Dry Docks 4 and 5 and the historic Block Mills building among others. In 2015 an architectural design competition for the project was won by Latz+Partner; however, the Ministry of Defence subsequently indicated that property to the north of the Mary Rose will not be ceded for several years at least, due to the site's proximity to the berth of the new Queen Elizabeth-class aircraft carriers.

History
Along with Woolwich, Deptford, Chatham and Plymouth, Portsmouth has been one of the main Royal Navy Dockyards or Bases throughout its history.

Medieval period
Richard I ordered construction of the first dock on the site in 1194, while his successor John added walls around the area in 1212. The docks were used by various kings when embarking on invasions of France through the 13th and 14th centuries, including the Saintonge War in 1242. Edward II ordered all ports on the south coast to assemble their largest vessels at Portsmouth to carry soldiers and horses to the Duchy of Aquitaine in 1324 to strengthen defences.

Tudors
The first recorded dry dock in the world was built in Portsmouth by Henry VII in 1495. The first warship built here was the Sweepstake of 1497; of more significance were the carracks Mary Rose of 1509 and Peter Pomegranate of 1510—both were rebuilt here in 1536. The wreck of the Mary Rose (which capsized in 1545, but was raised in 1982) is on display in a purpose-built museum. A fourth Tudor warship was the galleass Jennett, built in 1539 and enlarged as a galleon in 1558.

The appointment of one Thomas Jermyn as Keeper of the Dock at Portsmouth is recorded in 1526, with a Clerk of the Stores being appointed from 1542. Contemporary records suggest that the dry dock was enlarged and rebuilt in 1523 in order to accommodate the Henry Grace à Dieu (the largest ship of the fleet at that time); but a hundred years later it is described as being filled with rubble.

Following the establishment of Chatham Dockyard in the mid-1500s, no new naval vessels were built here until 1648, but ships from Portsmouth were a key part of the fleet that drove off the Spanish Armada in 1588. There are no on-site remains of the Tudor dock and yard.

Seventeenth century
Naval shipbuilding at Portsmouth recommenced under the English Commonwealth, the first ship being the eponymous fourth-rate frigate Portsmouth launched in 1650. (Portsmouth had been a parliamentarian town during the civil war.) A resident Commissioner was first appointed in 1649; fifteen years later the Commissioner was provided with a house, and extensive gardens, at the centre of the yard. A new double dry dock (i.e. double the standard length so as to accommodate two ships at once) was built by the Commonwealth government in 1656, on what was then the tip of land at the north-west corner of the yard. It was joined by a single dry dock, just to the south; the yard's one shipbuilding slip (completed in 1651) stood between the two docks. These would all have been built of timber, rather than stone.

By 1660 the dockyard had, in addition to these large-scale facilities for shipbuilding and repairs, a new rope house (1,095 ft in length) and a variety of small storehouses, workshops and dwellings arranged around the site, which was now enclosed by a wooden palisade. After the Restoration, there was continued investment in the site with the excavation of a new mast pond, begun in 1664, alongside which a mast house was built in 1669. Between 1665 and 1668 Bernard de Gomme fortified the dockyard with an earthen rampart (complete with one bastion and two demi-bastions), as part of his wider fortification of Portsmouth and Gosport.

Dummer's pioneering engineering works
As France began to pose more of a military threat to England, the strategic importance of Portsmouth grew. In 1689, Parliament ordered a new dry dock to be built there, large enough to accommodate the latest first-rate and second-rate ships of the line (which were too big for the existing docks). Work began in 1691; as with all subsequent extensions to the dockyard, the new works were built on reclaimed land (on what had been mud flats, to north of the old double dock) and the civil engineering involved was on an unprecedented scale.

The work was entrusted to Edmund Dummer, naval engineer and surveyor to the Navy Board. His new dry dock (the "Great Stone Dock" as it was called) was built to a pioneering new design, using brick and stone rather than wood and with an increased number of 'altars' or steps (the stepped sides allowed shorter timbers to be used for shoring and made it much easier for shipwrights to reach the underside of vessels needing repair). Extensively rebuilt in 1769, the Great Stone Dock is now known as No.5 dock.

Along with the new dock, Dummer proposed that two wet docks (non-tidal basins) be built: the first ("Lower") Wet Dock was entered directly from the harbour and provided access to the Great Stone Dock; since much expanded, it remains in place (now known as "No. 1 Basin"). The second ("Upper") Wet Dock was entered by way of a channel. To empty the dry dock, Dummer designed a unique system which used water from the Upper Wet Dock to drive a water-wheel on the ebb tide, which in turn powered a set of pumps. (At high tide, an auxiliary set of pumps was used, powered by a horse gin.)

In 1699 Dummer adapted the channel leading to the Upper Wet Dock, enabling it to be closed off at each end by a set of gates, thus forming a second dry dock (called the "North Stone Dock" after it was rebuilt with stone altars in 1737, and known today as No 6 dock). Severed from the harbour, the Upper Wet Dock became a reservoir into which water from various nearby dry docks could be drained; it was vaulted and covered over at the end of the eighteenth century, but still exists today underground. By 1700 a shipbuilding slip had been constructed off the (Lower) Wet Dock, parallel with the dry dock (roughly where No 4 dry dock is today).

Eighteenth century
Between 1704 and 1712 a brick wall was built around the Dockyard, following the line of the town's 17th-century fortifications; together with a contemporary (though altered) gate and lodge, much of the wall still stands, serving its original purpose. A terrace of houses for the senior officers of the yard was built at around this time (Long Row, 1715–19); later in the century it was joined by a further terrace (Short Row, 1787). In 1733 a Royal Naval Academy for officer cadets was established within the Dockyard, the Navy's first shore-based training facility and a forerunner of Britannia Royal Naval College in Dartmouth.

The 'Great Rebuilding'
The second half of the eighteenth century was a key period in the development of Portsmouth (and indeed of the other Royal Dockyards). A substantial planned programme of expansion and modernisation was undertaken from 1761 onwards, driven (as would be future periods of expansion) by increases both in the size of individual ships and in the overall size of the fleet. In the 1760s the Lower Wet Dock (by then known as the Great Basin) was deepened, the Great Stone Dock was rebuilt and a new dry dock (known today as No 4 dock) was built alongside it over a five-year period from 1767. During 1771–76 the former Upper Wet Dock was reconfigured to serve as a reservoir into which water from the dry docks could be drained by way of culverts (enabling ships to be dry docked much more speedily). From 1789 work was begun on replacing the old wooden South Dock with a modern stone dry dock (known today as No 1 dock, it currently accommodates the museum ship HMS M33).

North of the reservoir a channel was dug leading to a new boat basin, beyond which several shipbuilding slips were constructed on reclaimed land at what became known as the North Corner of the dockyard. The rest of the reclaimed land was given over to storage space for timber with saw pits and seasoning sheds alongside, as shown in the dockyard model of 1774. The open ground between the Basin and the officers' terrace was likewise used to store timber.

Several of Portsmouth Dockyard's most notable historic buildings date from this period, with several older wooden structures being replaced in brick on a larger scale. The three great storehouses (Nos 9, 10 & 11)  were built between 1764 and 1785 on a wharf, alongside a deep canal (or camber) which allowed transport and merchant vessels to moor and load or unload goods; the camber was rebuilt in Portland stone between 1773 and 1785. On the other side of the camber, on newly reclaimed land, two more sizeable brick storehouses were built to serve as a sail loft and a rigging store; the reclaimed land was later named Watering Island after a fresh water supply was provided for ships mooring alongside.

The Great Ropehouse, a double ropery over 1,000 ft in length, dates from the same period. It is, however, the sixth ropehouse (since 1665) to have stood on the site. Both its immediate predecessors were destroyed by fire (in 1760 and 1770) and the current building was itself gutted by fire in 1776 as the result of an arson attack. It was called a 'double' ropery because the spinning and laying stages took place in the same building (on different floors) rather than on two separate sites. Other buildings associated with ropemaking (including hemp houses, a hatchelling house, tarring house and storehouses) were laid out alongside and parallel to the ropehouse; they largely date from the same period. (Ropemaking was discontinued at Portsmouth in 1868, since when the ropery has functioned as a storehouse).

Later, in 1784, a large new house was built for the Dockyard Commissioner. Unusually for the time it was designed by a civilian architect (Samuel Wyatt, with Thomas Telford as clerk-of-works); most other dockyard buildings were designed in-house. The dockyard chapel, built eighty years earlier, was demolished to make way for the new Commissioner's house and a new chapel (St Ann's Church) was built nearby. At the same time a set of offices for the senior officers of the yard was built (in place of an earlier office block), overlooking the docks and basin; it continues to provide office space to this day.

After the old Commissioner's House had been demolished, four identical quadrangular buildings were built, flanking the timber ground east of the Basin; as well as providing storage space, they accommodated workshops for a variety of trades, including joiners, wheelwrights, wood-carvers, capstan-makers and various other craftsmen. A new smithery was also built nearby, immediately to the north (the latest in a succession of smiths' shops to have been built on the site); dating from 1791, it was mainly occupied with anchor making. Ten years later this process was vividly described: "The immense masses of the anchors, the ponderous hammers, the vast size of the bellows, the roaring of the flaming furnaces, the reverberations of the falling cumbrous hammers, and the fiery pieces of metal flying in all directions, are truly awful, grand and picturesque".

Samuel Bentham and industrial revolution
In 1796 Samuel Bentham was appointed Inspector General of Naval Works by the Admiralty with the brief of modernising the Royal Dockyards. As such, he took on responsibility for overseeing the continued rebuilding at Portsmouth and initiated further key engineering works. A prolific inventor and precision engineer, Bentham's initiatives at Portsmouth ranged from instituting new management principles in the manufacturing departments to developing the first successful steam-powered bucket dredger, which began work in the harbour in 1802. His other projects included the following:

The 1761 rebuilding plan had envisaged the old wooden double dock being refurbished, but Bentham instead proposed expanding the Basin (building over the double dock in the process) and adding a further pair of single docks built entirely of stone (unlike previous 'stone docks' which had had timber floors). The proposal was accepted; the new docks (now known as Nos 2 and 3 docks) were completed in 1802-3 and are still in place today (accommodating HMS Victory and the Mary Rose respectively). While constructing a new entrance to the Basin, Bentham introduced the innovation of an inverted masonry arch to tie together the walls on either side. He went on to use the same principle in constructing the new dry docks attached to the basin; it soon became standard for dock construction around the world. In constructing the docks and basin he made pioneering use of Smeaton's waterproof cement. He also designed a "ship caisson" to close off the entrance to the basin (another innovation which soon became a standard design).

To deal with the increasing number of docks, Bentham in 1797 proposed replacing one of the horse pumps above the reservoir with a steam engine. His plan was that the engine should be used not only to drain the reservoir (by night) but also to drive a sawmill and woodworking machinery (during the day); he also envisaged linking it to a freshwater well, to enable water to be pumped through a network of pipes to various parts of the dockyard. A table engine, designed by Bentham's staff chemist James Sadler, was installed in 1799; it represented the first use of steam power in a Royal Naval Yard. By 1800 a second steam engine (a Boulton & Watt beam engine) was being installed alongside the first. Meanwhile, Bentham designed and built a series of subterranean vaulted chambers over the reservoir, upon which he erected a pair of parallel three-storey workshops to contain reciprocating and circular saws, planning machines and morticing machines, built to his own designs, to be driven by the two engines (which were accommodated together with their boilers in the south workshop). Tanks installed on the upper floor provided a head of water for Bentham's aforementioned dockyard-wide pipe network, providing both salt water for firefighting and fresh water for various uses (including, for the first time, provision of drinking water to ships on the wharves) sourced from a newly sunk 274 ft well.

Between the two Wood Mills buildings a single-storey workshop was built in 1802 to accommodate what soon came to be recognised as the world's first steam-powered factory for mass production: Portsmouth Block Mills. Marc Brunel, father of Isambard Kingdom Brunel, famously designed the machines, which manufactured ships' pulley blocks through a total of fifteen separate stages of production. Having been presented with Brunel's designs, which would be built by Henry Maudslay, Bentham incorporated them into his woodworking complex and linked them to the engines by way of line shafts.

At the same time as building his Wood Mills, Bentham, with his deputy Simon Goodrich, was constructing a Metal Mills complex a little to the north-east. Alongside a smithery were a copper-smelting furnace and refinery, and a steam engine which drove a rolling mill and tilt hammers. Begun in 1801, these facilities were for recycling the copper sheathing of ships' hulls. In 1804 the works were extended to accommodate machinery for the rolling of iron to make bars and bolts. A millwrights' shop was also established nearby. The Wood Mills, Block Mills, Metal Mills and Millwrights' department were all placed under Goodrich's supervision as Mechanist to the Royal Navy.

Nineteenth century
In 1800, the Royal Navy had 684 ships and the Dockyard was the largest industrial complex in the world. In 1805 Horatio Nelson toured the newly opened block mills before embarking from Portsmouth on HMS Victory, leaving Britain for the last time before his death at the Battle of Trafalgar.

From 1814 wooden covers were built over some of the slips and docks, to designs by Robert Seppings.

From 1815 the system of Dockyard apprenticeship was supplemented by the establishment of a School of Naval Architecture in Portsmouth (for training potential Master Shipwrights), initially housed in the building which faces Admiralty House on South Terrace. Taking on students from the age of 14, this was the forerunner of Portsmouth Dockyard School (later Technical College) which continued to provide specialist training until 1970.

Victorian dockyard expansion
The adoption of steam propulsion for warships led to large-scale changes in the Royal Dockyards, which had been built in the age of sail. The Navy's first 'steam factory' was built at Woolwich in 1839; but it soon became clear that the site was far too small to cope with this revolutionary change in ship building and maintenance.

Therefore, in 1843, work began in Portsmouth on further reclamation of land to the north of the then Dockyard to create a new 7-acre basin (known today as No 2 Basin) with a sizeable factory alongside for manufacturing marine steam engines. The Steam Factory, on the western edge of the basin, housed a series of workshops: for construction and repair of boilers, for punching and shearing and for heavy turning; there was also an erecting shop for assembling the finished engines. The upper floor housed pattern shops, fitting shops and other light engineering workshops. Line shafts throughout were powered by an 80hp steam engine accommodated to the rear. A new Brass and Iron Foundry was also built soon afterwards, on the southern edge of the basin, and in 1852 the Great Steam Smithery was opened alongside the Steam Factory (where Bentham's Metal Mills had formerly stood), containing a pair of steam hammers designed by James Nasmyth. The infrastructure and buildings were designed by a group of Royal Engineer officers, overseen by Captains Sir William Denison and Henry James. (The new steam basin was built over what had been the boat pond and boat houses; so in 1845 a new facility (No 6 Boathouse) was built alongside the mast pond, to the south, which was converted into a boat pond.)

Three new dry docks were constructed over the next 20 years, opening off the new basin, and another was built on reclaimed land west of the basin, immediately north of the shipbuilding slips. The slips were now five in number, with Nos. 3–5 being covered by interlinking metal roofs (believed to have comprised the widest iron span in Britain when built in 1845). Meanwhile, facilities for building wooden hulls continued to be updated with a large sawmill having been built behind the slips in 1843.

Developments in shipbuilding technology, however, led to several of the new amenities having to be rebuilt and expanded (almost as soon as they were finished). A much larger Iron Foundry was opened in 1861, immediately to the east of its predecessor; it was further expanded in the following decade. In 1867 a very large Armour Plate Workshop was opened, filling the space between the new North and South dry docks on the eastern side of the basin.

In 1860 policing of the dockyard was also transferred to the new No. 2 Division of the Metropolitan Police, a role it fulfilled until 1933.

The 'Great Extension'
Technological change affected not only ships' means of propulsion, but the materials from which they were built. By 1860 wooden warships, vulnerable as they were to modern armaments, had been rendered largely obsolescent. The changeover to metal hulls not only required new building techniques, but also heralded a dramatic and ongoing increase in the potential size of new vessels. The Dockyards found themselves having to expand in kind. At Portsmouth, plans were drawn up in the late 1850s for further land reclamation north and east of the new Steam Basin, and from 1867 work was begun on a complex of three new interconnected basins, each of 14–22 acres. Each basin served a different purpose: ships would proceed from the repairing basin, to the rigging basin, to the fitting-out basin, and exit from there into a new tidal basin, ready to take on fuel alongside the sizeable coaling wharf there.

Three dry docks were also constructed as part of the plan, as well as parallel pair of sizeable locks for entry into the basin complex; the contemporary pumping station which stands nearby not only served to drain these docks and locks, but also delivered compressed air to power equipment around the edges of the basins: five cranes, seven caissons and forty capstans were run on compressed air from the pump house.

The "Great Extension" of Portsmouth Dockyard was largely completed by 1881. Alongside the new Basins new buildings were erected, on a huge scale, to accommodate new manufacturing and construction processes. These included a gun-mounting workshop (built alongside the pumping station in 1881) which produced gun turrets, and a torpedo workshop (built to the east of No 12 dock in 1886).

Before the end of the century, it was recognised that there would have to be still further expansion across all the Royal Dockyards in order to keep pace with the increasing likely size of future naval vessels. At Portsmouth two more dry docks, Nos 14 & 15, were built alongside the Repairing Basin in 1896; (within ten years these, together with the adjacent docks 12 & 13, had to be extended, and by the start of World War I Dock No 14 was over 720 ft in length).

The dockyard railway
In 1843 construction began on a railway system within the dockyard. In 1846 this was connected to Portsmouth Town railway station via what became known as the Admiralty Line. By 1952 there was over 27 miles of track within the dockyard. Its use declined in the 1970s: the link to the mainline was closed in 1977 and locomotives ceased operating within the yard the following year.

In 1876 a railway station was built on what became known as South Railway Jetty on Watering Island (west of the Semaphore Tower). It was served by a separate branch line which crossed the South Camber by way of a swing bridge and continued on a viaduct over the foreshore, joining the main line just east of Portsmouth Harbour railway station.

A small railway station and ornamental cast-iron shelter served in particular the needs of Queen Victoria and her family, who would often transfer from yacht to train at this location; this line soon became the main arrival/departure route for personnel. The swing bridge and viaduct were damaged in the wartime blitz and subsequently dismantled in 1946. The Royal Naval Railway Shelter has recently been moved to the other side of the island and restored.

Twentieth century
By the end of the 19th century No 5 Slip had been uncovered and extended (to a length of 666 ft) to become the yard's principal shipbuilding slip. At the same time the adjacent dry dock (No 9) was filled in to provide space for stacking steel plates, alongside which a further smithery (No 3 Engine Smithery) was erected in 1903. Meanwhile, slips 1–4 were repurposed (being no longer large enough for warship construction). Before long Nos 4 and 3 had been filled in, and the space beneath their cast iron covers converted into a shipbuilding workshop (No 3 Ship Shop); the neighbouring No 2 Slip was used for hauling up torpedo boat destroyers for a time, while No 1 was used as a boat slip.

In 1900 the Third class cruiser HMS Pandora was launched, followed by the armoured cruisers Kent in 1901 and Suffolk in 1903. Two battleships of the pre-Dreadnought King Edward VII Class were launched in 1904—Britannia and New Zealand.

Dreadnoughts
The first modern battleship, Dreadnought, was built in 1905–06, taking one day more than a year. Further dreadnoughts followed—Bellerophon in 1907, St. Vincent in 1908, Orion in 1910, King George V in 1911, Iron Duke in 1912 and Queen Elizabeth in 1913.

Electrification came to the Yard with the opening of a 9,800 kW power station in 1906. At this time the 1846 Steam Factory still served as the dockyard's main heavy engineering complex, but the following year a very large New Steam Factory (to the east of No 12 dock) was opened. Equipped for the repair and maintenance of steam turbine propulsion units, it was soon put to the task of fitting out dreadnoughts. Nearby a new boiler shop had recently been built (south of No 13 dock), together with a new sawmill. Dry-docking provision was further increased in 1912 through the addition of an Admiralty Floating Dock, large enough to accommodate a dreadnought, which was moored just off Fountain Lake Jetty. Also in 1912 No 5 Slip was further extended.

The largest Naval ships were now too large for the interlocking basins, so to guarantee access to the new dry docks the intervening walls between the basins were removed to create a single large non-tidal body of water (No 3 Basin), with a pair of 850 ft entrance locks being built at the same time. These (C & D locks) were operational from 1914, and they, together with the enlarged basin and docks, have remained in use, largely unaltered, ever since. On 8 April 1913, Portsmouth Dockyard opened the first of two new large 850 ft long drydock locks directly connecting Portsmouth Harbour to No.3 Basin, the first named 'C' Lock. A year later, 'D' Lock was opened in April 1914.

First World War
The largest vessel launched at Portsmouth during World War I was the 27,500-ton battleship Royal Sovereign in 1915. The only other launchings during the war were the submarines J1 and J2 in 1915, and K1, K2 and K5 in 1916. Some 1,200 vessels, however, underwent a refit at Portsmouth during the course of the War, and over the same period 1,658 ships were either hauled up the slipways or placed in dry-dock for repairs.

For the duration of the war significant numbers of women were employed in the yard, including in the erstwhile male domains of the Engineering Department, the Electrical Department and the Constructive Department. By the end of the war a total of 2,122 women were employed; 280 worked as clerks, the rest were manual workers.

Inter-war years
The period after the war was inevitably a time of contraction at the Dockyard, and there were many redundancies. In accordance with the Government's Ten Year Rule the Dockyard worked over the next decade and a half with a presumption of enduring peace rather than future conflict.

The majority of warships launched at Portsmouth following the end of the War were cruisers—Effingham in 1921, Suffolk in 1926, London in 1927, Dorsetshire in 1929, Neptune in 1933, and Amphion and Aurora in 1934. There were also four destroyers—Comet and her sister Crusader in 1931, and the flotilla leaders Duncan in 1932 and Exmouth in 1934. The only other vessels launched between the wars were the mining tenders Nightingale in 1931 and Skylark in 1932.

In 1922 HMS Victory was brought into No 2 Dry Dock (where she remains to this day). She was opened to the public on 17 July 1928, and ten years later a museum building (the Victory Gallery) was opened nearby to house works of art and other items related to the ship (including W L Wyllie's Panorama of the Battle of Trafalgar).

New Dockyard facilities in this period included a Steel Foundry, built in 1926, and the Central Metallurgical Laboratory, established ten years later. The "Semaphore Tower" was opened in 1930, a facsimile of its namesake (dating from 1810–24) which had been destroyed in a fire in 1913. The arch beneath incorporates the Lion Gate, once part of the 18th-century fortifications. The original Semaphore Tower had been erected between a sizeable pair of buildings: the Rigging Store and Sail Loft (both of 1784), which perished in the same fire; in the end only one of the pair was rebuilt, as a five-storey office block. In 1937 work began on a new boathouse (No 4 Boathouse), which replaced the last working masthouse of the yard (in place there since c.1700). Construction was halted by the start of the Second World War, and the southern half of the new building was never completed; during the war it was fully occupied with building landing craft, small boats and midget submarines.

Second World War
The destroyer flotillas (the capital ships having been evacuated to Scapa Flow), were essential to the defence of the English Channel, particularly during Operation Dynamo (the Dunkirk evacuation) and against any potential German Invasion. The base itself served a major refit and repair role. The Germans realised this importance and the city and base in particular was heavily bombed.

Portsmouth and the Naval Base itself were the headquarters and main departure point for the military and naval units destined for Sword Beach on the Normandy coast as a part of Operation Overlord and the D-Day landings on 6 June 1944. Troops destined for each of the landing beaches left from Portsmouth aboard vessels such as the armed merchant cruisers HMCS Prince Henry and HMCS Prince David, escorted by the Canadian destroyers HMCS Algonquin and Sioux. The majority of the naval support for the operation left from Portsmouth, including the Mulberry Harbours. Boathouse 4 (built around the start of hostilities) contributed to the construction of landing craft and support vessels as well as more specialised craft such as midget submarines.

Post Second World War
There was much rebuilding, demolition and consolidation of bomb-damaged buildings in the aftermath of the Second World War. At the same time, a number of returning ships were refitted in the yard (while others were de-equipped, ready for scrapping). The Dockyard was kept busy with refitting and modernisation works through the 1950s and 60s. Private yards were used to a greater extent for shipbuilding, but five new frigates were launched at Portsmouth in this time. Numbers employed in the dockyard remained steadily above 16,000 through the 1950s and early '60s; but a Defence Review published in 1969 (after the withdrawal of British forces from east of Suez) signalled a significant reduction in the size of the fleet and a parallel downsizing of workforces in the Royal Dockyards.

In the decade that followed No 5 shipbuilding slip was taken out of commission; it was infilled (along with the other remaining slips at the north corner) and the adjacent buildings were demolished. Nevertheless, elsewhere in the yard a number of new workshops and other facilities were built in the 1970s, especially around Nos 12–15 docks (including a large Heavy Plate Shop, now the Steel Production Hall, built on the site of the Edwardian Boiler Shop).

In June 1981, however, the government announced that shipbuilding would cease at Portsmouth, that the workforce would be reduced from just under 7,000 to 1,225 and that the erstwhile Royal Dockyard would become a Fleet Maintenance & Repair Organisation (FMRO) with a minor support and repair role (Devonport and Rosyth would take over major refits and ship modernisation work). The run-down of the Dockyard was put on hold, however, at the start of the Falklands Conflict, with all available hands being put to the task of preparing the Falklands Task Force.

Falklands Task Force
In 1982 Argentina invaded the Falkland Islands. In response a task force of British military and merchant ships was dispatched from Portsmouth Naval Base to the islands in the South Atlantic to reclaim them for the United Kingdom.

The task force consisted of the following ships:
 * Two aircraft carriers
 * Two landing ship docks
 * Eight destroyers
 * Fifteen frigates
 * Three patrol ships
 * Five submarines
 * Three survey vessels
 * Five minesweepers
 * Ten fleet tankers
 * Six logistic landing ships
 * Five supply ships
 * One helicopter supply ship
 * Eighteen merchant ships including troop/cruise ships such as Queen Elizabeth 2 and SS Canberra

Following some losses, the majority of these ships returned to Portsmouth later that year.

Rundown of the Dockyard
Thereafter, some of the cuts that had been proposed in the 1981 Defence White Paper were reversed. The retention of a larger fleet meant that a larger workforce was retained at Portsmouth than had been envisaged (around 2,800); however the run-down of the old Dockyard went ahead, with dry docks 1–7 being closed, just under half the dockside cranes demolished and ten out of the nineteen major workshops on the site taken out of service. The dockyard's 'Edwardian piece de résistance', the Great Factory of 1905, ceased manufacturing in 1986 and was converted to serve as a warehouse (at the end of the century it was linked by monorail to other nearby buildings to create a large Central Storage and Distribution Facility).

In the older parts of the dockyard several buildings, ranging from storehouses to foundries, were converted for office use; this trend continued in later years. Similarly, the Great Steam Smithery (1852) adjoining the Steam Factory (aka No 2 Ship Shop) underwent conversion in 1993 to provide squash courts, offices, messrooms and a self-service laundry. In the same year, Victory Building, a new neo-Georgian office block, was opened on a prominent site facing the historic No 1 basin (just one of several new office blocks built across the dockyard site in each decade of the second half of the century); it accommodated staff of the Second Sea Lord, relocated there from London.

In 1998 the work of the FMRO was contracted out to the private sector in the shape of Fleet Support Limited.

Twenty-first century
In the summer of 2005 Portsmouth Naval Base and the Solent played host to two special events organised as part of the Trafalgar 200 commemorations recognising the 200th Anniversary of the Battle of Trafalgar. These were the International Fleet Review and the International Festival of the Sea.

In 2007 it was reckoned that the Royal Navy/MOD directly employed 9,774 people at Portsmouth, of whom 5,680 were ships' crew and the rest either service personnel or civilian employees working in the naval base. In addition, there were 3,834 private-sector employees on the base, including defence contractors, sub-contractors and heritage-related workers.

Shipbuilding, maintenance and repair
Shipbuilding recommenced on the site in 2003 following the construction of a facility by VT Group on the site of No. 13 dry dock (having relocated there from the old Thornycroft Yard in Woolston, Southampton). Modular construction of warships took place in an interlinked complex of large buildings: the Steelwork Production Hall, the Unit Construction Hall and the Ship Assembly Hall. Construction of modules for the Type 45 destroyers and Queen Elizabeth-class aircraft carriers took place here, latterly under BAE Systems Maritime – Naval Ships. The project was intended to secure the base's future for the next forty years and revitalise shipbuilding in the city; but in 2013 it was announced that, due to budget cuts, the shipbuilding facility in Portsmouth would close in favour of BAE keeping its yards in Glasgow open. (There was speculation at the time that this was to help retain Scotland in the union during the 2014 Scottish independence referendum.)

BAE Systems, having subsumed Fleet Support Ltd, continues to manage ship repair and maintenance facilities around No. 3 Basin at Portsmouth. As of 2016 the former shipbuilding complex was being used for repairing minehunters and other small craft.

New aircraft carriers
In 2013 a £100 million upgrade of the naval base facilities and harbour was begun, in preparation for the arrival of the two Queen Elizabeth-class aircraft carriers (Portsmouth having been chosen to serve as their home base). These ships required the harbour to be dredged to allow safe entry and exit. Victory Jetty and the Middle Slip Jetty were strengthened and upgraded (the latter being renamed Princess Royal Jetty on completion of the works), so as to enable both carriers to lay alongside at the same time. HMS Queen Elizabeth arrived in Portsmouth in 2017, and HMS Prince of Wales followed two years later.

Civil and military administration of the Dockyard
From 1546 until 1832 prime responsibility for administering H.M. Royal Navy Dockyards lay with the Navy Board, and resident commissioners who were naval officers though civilian employees of the Navy Board, not sea officers in charge of the day-to-day operational running of the dockyard and superintendence of its staff, following the abolition of that board its functions were merged within the Admiralty and a new post styled Admiral-superintendent was established the admiral-superintendent usually held the rank of rear-admiral though sometimes vice-admiral. His immediate subordinate was an officer known as the captain of the dockyard (or captain of the port from 1969). This followed the appointment of a (civilian) Chief Executive of the Royal Dockyards in September 1969 and the creation of a centralised Royal Dockyards Management Board. Admiral-superintendents ceased to be appointed in the royal navy after 15 September 1971, and existing post-holders were renamed port admirals. In May 1971 the post was renamed Flag Officer, Portsmouth and Admiral Superintendent until July 1971 when it was renamed Flag Officer, Spithead and Port Admiral until August 1975, the post name was changed again to Flag Officer, Portsmouth and Port Admiral until October 1996 when it ceased to exist as a separate command that was then absorbed into the First Flotilla Command later renamed Portsmouth Flotilla.

The Naval Barracks (HMS Nelson)
In 1847 a barracks was built within the Duke of York bastion of the 18th-century Portsea fortifications, east of the dockyard, to house troops manning the town's defences. It was named Anglesey (or Anglesea) Barracks. The bastion was demolished in 1870–76.

In 1899 the Admiralty purchased these barracks from the War Office and constructed a Naval Barracks on the site, designed by Colonel Sir Henry Pilkington RE. (Prior to this, Royal Navy personnel in Portsmouth had been accommodated either on commissioned vessels or in hulks). Opened in 1903, the barracks were commissioned as HMS Victory (but renamed HMS Nelson in 1974 to avoid confusion with the flagship). A Wardroom (with accommodation for officers) was built across the street on the site of the old garrison hospital. In 1906 the nearby Holy Trinity Parish Church was purchased and brought inside the perimeter wall; for a time it functioned as the RN Barracks chapel, but it was destroyed by bombs in the Second World War. Just to the north-west, Anchor Gate House was built in 1898 to house the Commodore of the Barracks.

Several barrack blocks were demolished and rebuilt in the latter half of the 20th century, but a number of original buildings remain including the canteen (Eastney block), the drill hall and gymnasium, Jervis block (formerly Seamen's Quarters), Barham block (formerly Depot Offices) and the Wardroom. In addition, one barrack block remains, along with its adjacent canteen building, from the earlier Army barracks (Anglesey Barracks) which formerly stood on the site. Nearby, the associated garrison prison (which later served as the Naval Detention Centre) is now home to the Royal Marines School of Music.

In November 2016 the Ministry of Defence published A Better Defence Estate, which indicated that the HMS Nelson Wardroom would be disposed of by 2021; three years later, however, the disposal date was deferred.

Associated establishments in the Portsmouth area
The presence of the Dockyard and Fleet led to the establishment of a variety of other naval and military installations in and around Portsmouth over the years, some of which are listed below.

Naval

 * HMS King Alfred (1994 shore establishment): a Royal Naval Reserve unit located in the renovated "Semaphore Tower".
 * HMS Excellent (shore establishment): Whale Island, Portsmouth (includes Navy Command Headquarters together with a front-line Naval Training establishment operated by Babcock International (with all catering, front of house, cleaning and hotel services sub-contracted to Compass Group plc)). The name was formerly attached to the barracks and other facilities of the RN Gunnery Establishment (based on the island from 1891 to 1985); these now form part of the training base.
 * HMS Temeraire: Burnaby Road, Portsmouth. Training of Naval Physical Training Instructors and sports grounds and facilities for Portsmouth-based personnel. RN School of Physical Training has been known as Temeraire since 1971, and moved to its current site in 1988.
 * HMS Collingwood (shore establishment): Fareham. Naval training provided mainly under contract to Babcock International (catering and cleaning services are sub-contracted to Sodexo). Commissioned in 1940 as a training establishment for 'new entry' seamen, it later housed the RN School of Electrical Engineering, but serves today as headquarters of the Maritime Warfare School.
 * HMS Sultan (shore establishment): Gosport. Naval (and tri-service) training, home of the centre of excellence for mechanical and electrical engineering. Naval training provided mainly under contract to Babcock International (catering and cleaning services are sub-contracted to Sodexo); opened on this site in 1956.
 * Institute of Naval Medicine, Gosport.
 * Marchwood Military Port, Southampton Water. Royal Fleet Auxiliary base-port.

Decommissioned

 * HMS Dryad (shore establishment): Now MOD Southwick Park—Tri-Service Defence School of Policing and Guarding
 * HMS Dolphin (shore establishment) diesel electric submarine base—Now MOD Fort Blockhouse
 * HM Gun Wharf, later HMS Vernon (shore establishment) torpedo and mines establishment – Now in civilian use as Gunwharf Quays
 * HMS Daedalus Fleet Air Arm base
 * Royal Naval Hospital, Haslar
 * Eastney Barracks (Royal Marine Artillery barracks 1867–1923, Royal Marines barracks 1923–1995) — converted into housing.
 * Forton Barracks (Royal Marine Light Infantry barracks 1848–1923, then HMS St Vincent (Gosport shore establishment) boys' training establishment until 1968) — Now in civilian use as St Vincent College
 * Royal Clarence Victualling Yard, Gosport
 * RNAD Gosport: a composite site which included:
 * RNAD Priddy's Hard (1776) gunpowder storage and shell-filling facility. Closed 1988 – now Explosion! Museum of Naval Firepower
 * RNAD Bedenham (1908) gunpowder stores were moved here from Priddy's Hard (judged to be dangerously close to the Dockyard).
 * RNAD Elson (now part of DM Gosport)
 * RNAD Frater (now part of DM Gosport)
 * RNAD Marchwood (1811) closed 1961 – Converted for housing and use by Marchwood Yacht Club
 * Haslar Gunboat Yard (opened 1859, closed 1973)
 * HMS Mercury (shore establishment): RN Signals School 1941–1993, Leydene House, East Meon, near Portsmouth
 * HMS Phoenix: Fire fighting training establishment 1946–1993, now part of HMS Excellent

Military
The Fortifications of Portsmouth were developed over several centuries to protect the fleet and dockyard from attacks either by land or by sea. From 1665 Bernard de Gomme oversaw construction of defensive Lines around both Portsmouth (the Dockyard and the old town) and Gosport (on the opposite side of Portsmouth Harbour). These defences were extended in the 18th century, before being superseded in the 19th by the Palmerston forts which encircle Portsmouth on and off-shore.

These fortifications required substantial numbers of personnel to man them and, from the mid-18th century onwards, they (together with other troops who were either stationed in the garrison or preparing to embark overseas) were accommodated in a variety of barracks in and around the city. By 1900 these included:

According to the census over 6,000 men were living in barracks in the Portsmouth area in 1911.
 * Cambridge Barracks, High Street (Infantry) – established in 1825 in a set of late-18th century warehouses; the officers' quarters have been occupied by Portsmouth Grammar School since 1926.
 * Clarence Barracks (Royal Garrison Artillery) – established in 1760 as Fourhouse Barracks on land between St Nicholas Street and the fortifications (alongside an earlier Royal Marine Barracks); renamed in 1827; rebuilt around 1881, expanding across the old defensive lines into the field beyond; demolished c.1967.
 * Colewort Barracks, St George's Road (Army Service Corps) – built as a garrison hospital, converted to barracks 1694, demolished to make way for expansion of nearby power station in the 1920s.
 * Hilsea Barracks (Royal Field Artillery) – built 1854, Royal Army Ordnance Corps from 1921; closed 1962, site redeveloped for housing (the surviving 18th-century Gatcombe House served as the Officers' Mess).
 * Milldam Barracks (Royal Engineers) – built late 18th century onwards, housed the Engineers responsible for upkeep of the fortifications; sold in 1969 and now occupied by the University of Portsmouth and Portsmouth Register Office.
 * Point Barracks (Artillery) – built alongside the medieval Round Tower in 1846–50; sold to Portsmouth City Council in the early 1960s following disbandment of the UK's Coastal Artillery network. Part of the brick structure was demolished, but is marked by stones in the ground alongside the surviving casemates.
 * St George Barracks, Gosport (Infantry) – built 1856–59 as a transit barracks for troops, continuing in military use until 1991; several buildings remain, since converted to new uses.
 * Victoria Barracks (Infantry) – built in 1888 alongside New Clarence Barracks; demolished 1967.

Naval Base Commander (Portsmouth)

The head of HMNB Portsmouth is titled Naval Base Commander (Portsmouth).

 * 2011–2012: Commodore Tony Radakin
 * 2012–2018: Commodore Jeremy Rigby
 * 2018–2019: Commodore Jim Higham
 * 2019–2022: Commodore Jeremy Bailey
 * 2022–present: Commodore John Voyce OBE

(decorations and ranks detailed at the time of being in Command, and do not reflect subsequent promotions, or honours and awards)

title: HMNB Portsmouth


text:
San Mateo Daily Journal

The San Mateo Daily Journal is a daily newspaper published six days a week, Monday through Friday plus a combo weekend edition. The newspaper is distributed throughout San Mateo County, California.

Operations
The Daily Journal's publisher is Jerry Lee and its editor is Jon Mays. A 2007 poll on its website indicated its readers consider it to be politically moderate. It is one of the few independently owned and operated newspapers in the San Francisco Bay Area.

In 2008, there was an incident of racks of the papers being cleaned out by a man working for a competing newspaper, Palo Alto Daily Post.

The Washington Post stated that the paper is one of the few publications that report on East Palo Alto within San Mateo County.

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

title: San Mateo Daily Journal


text:
Jahangir Khoja

Jahanghir Khoja, Jāhangīr Khwāja or Jihangir Khoja (, جهانگير خوجة; ; 1788 – 1828), was a member of the influential Afaqi khoja clan, who managed to wrest Kashgaria from the Qing Empire's power for a few years in the 1820s but was eventually defeated and executed.

Career
Burhan ad-Din, a Khoja of the White Mountain faction, was the grandfather of Jahangir. Before rebellion broke out in May 1826 and during a fortuitously timed earthquake that destroyed most towns in the Ferghana Valley, Jahangir Khoja managed to flee to Kashgar from Kokand, where he had been held in prison in accordance with a secret agreement concluded between the Khanate of Kokand and Qing dynasty China concerning descendants of Appak Khoja. Among Jahangir's troops were Kyrghyz, Tajiks and White Mountain fighters. After appearing in Kashgar with only several hundred of his followers, he quickly increased his force with volunteers and within several months had collected about 200,000 troops under his banner. Jahangir Khoja overthrew Qing power in Kashgar, Yarkand, Khotan, Kargalik, Yangi Hissar and Maralbashi, having annihilated the Qing garrisons in these 6 cities of West Kashgaria. Hui Muslims were targeted in slave raids by Muslims of the Kokand Khanate. Enslavement didn't depend on religious status but political allegiance, since Turkic Muslim Ishaqi and Turfanis who served the Qing against fellow Turkic Muslim Afaqi and Khokandis were also enslaved by their fellow Turkic Muslims led by Jahangir. Kashgari Muslims purchased Ghalcha Mountain Tajiks as slaves. His forces captured several hundred Chinese Muslims (Dungan or Hui), who were taken to Kokand. Tajiks bought two Chinese slaves from Shaanxi whom they enslaved for a year before Tajik Beg Ku-bu-te returned them to China. All Chinese captured—including merchants and 300 soldiers Janhangir captured in Kashgar—had their queues cut off when brought to Kokand and Central Asia as prisoners. It was reported that many of the Chinese Muslim merchant captives became slaves themselves, with accounts of Chinese Muslim slavery in Central Asia increasing. The queues were removed from Chinese Muslim prisoners and then sold or given to various owners; one of them, Nian, ended up as a slave to Prince Batur Khan of Bukhara. Omar Khan ended up owning Liu Qifeng and Wu Erqi. The others—Zhu, Tian Li and Ma Tianxi—ended up with various owners but plotted an escape. The Russians record an incident in which they rescued the Chinese Muslim merchants who had escaped after they were sold by Jahangir's army in Central Asia and sent them back to China.

Nevertheless, the Qing Daoguang Emperor managed to mobilize "all forces of the Empire, that were put into motion" and by September1827 had assembled an army of 70,000 in Aksu under the command of General of Ili Chang Ling. In January 1828 this Army moved against Jahangir Khoja. Other sources say that the Chinese governor led 80,000 Chinese Muslim troops against Jahangir. Jahingir's forces were defeated within one month at a decisive battle on the banks of the Tuman River north of Kashgar. Although his forces during the battle outnumbered those of the Qing, the latter were much better organized, being a regular state army. Jahangir had not created a regular army and had disbanded his voluntary army after gaining control of Western Kashgaria and taking the Gulbagh Qing Fortress in Kashgar at the beginning of 1827, when he had slaughtered all its defenders (about 12,000 Manchu and Chinese troops and members of their families). After receiving word that a Qing army was on its way to Kashgar, Jahangir again mustered voluntary troops. This army had no artillery units, despite having captured the six large cannons of the Gulbagh fortress, which were not brought and used in the battle. By contrast, Qing troops applied well-organized intense cannon fire across the Tuman River on Jahangir's positions, sending his troops reeling into confusion. Mercenaries from Badakhshan, Kokand and Kunduz fled first, then the Kashgarians lost ground. Qing troops rushed to Kashgar and, upon entering the city, embarked on the wholesale massacre of the local population of about 20,000 civilians. On January29, 1828, Jahangir managed to escape and hide himself in the mountainous Alay Valley among the Kyrgyz people. Daoguang Emperor was dissatisfied with this turn of events and wrote to Chang Ling:  I sent an army to eliminate the evil itself, you were at the lair of the beast, but let him to escape, now all previous victories have no any value, because he is still alive, the germ of the future rebellions. Jahangir's capture resulted from the treachery of the former Kyrgyz Hakim of Kashgar, Ishak Khoja, who sent a misleading letter to Jahangir telling him that the main body of Qing troops had departed and inviting him to Kashgar to regain power. When Jahangir heard the news he hurried back to Kashgar but was ambushed by Qing troops under the General of Ili, captured and delivered to Beijing. There he was exposed to the attention of China's capital's population, being carried for several weeks in a mobile iron cage through the main streets of Beijing. Finally he was brought to the Daoguang Emperor for interrogation but, having gone mad due to bad treatment, he was unable to answer any questions. Immediately after the interrogation was completed he was executed by slicing (Lingchi). Jahangir Khoja's body was cut into numerous pieces and his bones thrown to the local dogs. His portrait was buried in the hill near Beijing. He was 40 years old at the time of his death.

Aftermath
With Jahangir dead, the Chinese decided to punish the Khokandians for their sympathy with the Khojas and imposed restrictions on their exports to Kashgar. In retaliation, at the behest of Muhammad Ali Khan, the Khan of Kokand, Yusuf Khoja became ruler of what was at that time known in the west as Chinese Turkestan. Jahangir's invasion led to a change in policy and Han settlement was allowed in the Tarim Basin after his invasion whereas before the invasion, Han were not allowed to permanently settle in the Tarim Basin.

title: Jahangir Khoja


text:
Talk:St. Mary's Hospital

I moved this page to "St._Marys_Hospital", because it's official spelling dsoes not include a apostrophe. Peb1991 23:17, 7 Apr 2005 (UTC)

title: Talk:St. Mary's Hospital


text:
One-pot synthesis

In chemistry a one-pot synthesis is a strategy to improve the efficiency of a chemical reaction in which a reactant is subjected to successive chemical reactions in just one reactor. This is much desired by chemists because avoiding a lengthy separation process and purification of the intermediate chemical compounds can save time and resources while increasing chemical yield.

An example of a one-pot synthesis is the total synthesis of tropinone or the Gassman indole synthesis. Sequential one-pot syntheses can be used to generate even complex targets with multiple stereocentres, such as oseltamivir, which may significantly shorten the number of steps required overall and have important commercial implications.

A sequential one-pot synthesis with reagents added to a reactor one at a time and without work-up is also called a telescoping synthesis.

In one such procedure the reaction of 3-N-tosylaminophenol I with acrolein II affords a hydroxyl substituted quinoline III through 4 sequential steps without workup of the intermediate products (see image). The addition of acrolein (blue) is a Michael reaction catalyzed by N,N-diisopropylamine, the presence of ethanol converts the aldehyde group to an acetal but this process is reversed when hydrochloric acid is introduced (red). The enolate reacts as an electrophile in a Friedel-Crafts reaction with ring-closure. The alcohol group is eliminated in presence of potassium hydroxide (green) and when in the final step the reaction medium is neutralized to pH 7 (magenta) the tosyl group is eliminated as well.

title: One-pot synthesis


text:
Wikipedia talk:Bots/Archive 6

VFD Hourly Discussions
I know that Anthony_DiPierro was running a bot to update his own personal subpage to keep a track of the hourly discussions... but since the format on VFD has changed, he has not fixed his hourly discussions. I would like to use a bot for the purpose of updating a subpage on my user page, keeping a track of all the new discussions being added by the hour. -- AllyUnion (talk) 04:26, 2 Feb 2005 (UTC)
 * You mean just links to the newly created vote-pages or also links to changes in vote pages? What exactly do you hope to achieve, I think if we're going to run a bot on VfD we might as well make it one that organises VfD in such a way you don't need to run a personal bot to check for new VfDs. --fvw *  04:32, 2005 Feb 2 (UTC)
 * Each hour, it would post links to any new VFD discussions, keeping 7 days of VFD on the list. Here's a sample of what I mean: User:AllyUnion/VFD_List -- AllyUnion (talk) 07:53, 2 Feb 2005 (UTC)

 * Ah, right. I don't find it very elegant (and I think doing it hourly instead of on-demand maybe wasting server resources unless a lot of people use it), but as long as VfD isn't reorganised into something that can provide something similar, support. --fvw *  08:20, 2005 Feb 2 (UTC)

 * Well, there is no elegance in utility, unless you make it that way. I'm going for functionality over pretty. -- AllyUnion (talk) 11:23, 2 Feb 2005 (UTC)

 * Support. The server resources used by running a script once an hour are negligible. anthony 警告 20:33, 4 Feb 2005 (UTC)

 * The bot is using pywikipediabot framework, and is currently running to do this task. -- AllyUnion (talk) 02:24, 7 Feb 2005 (UTC)

 * The bot works! And if there is no objection soon, I would like to request a bot flag for the bot. -- AllyUnion (talk) 10:47, 8 Feb 2005 (UTC)

 * I don't think you should set a bot flag on an account that is not used exclusively as a bot. Allyunion used to be your real account. I would rather this were renamed to a non-used account, and one that isn't so similar to your current user name, in order to avoid confusion. Angela. 10:46, Feb 19, 2005 (UTC)

 * Okay. I'll create a new account for the bot.  See User:VFD Bot. -- AllyUnion (talk) 04:50, 24 Feb 2005 (UTC)

Additional uses to bot (User:Allyunion)
Well, due to the security update, I will not be able to implement this bot yet, but I would like the approval to have my bot additionally do the following tasks at roughly exactly around every 00:00 UTC:
 * 1) Add each VFD subpage day.  Example:
 * Reason for this is because the VFD system has changed such that each day has a subpage for VFD based on the UTC clock. The transincludes must be included every day in order to properly present the VFD. -- AllyUnion (talk) 17:07, 5 Feb 2005 (UTC)
 * 1) Edit each new subpage day to include: == MONTHNAME DATE == (Like == February 5 == )
 * Again, VFD system changed, and each day will require to display its day section, allowing a person direct access to the VFD day. -- AllyUnion (talk) 17:07, 5 Feb 2005 (UTC)
 * 1) Take the last recently moved subpage day (transinclude) to Votes for deletion/Old, edit all VFD subpages to include the content from Template:Vfd top and Template:Vfd bottom.  (This bot will not count any of the votes, just merely include content from the templates, making it easier on the maintainers)
 * Each VFD subpage includes the content from both of these templates. I believe they are not applied due to the technical limitations of the number of templates that can be used on each page. -- AllyUnion (talk) 17:07, 5 Feb 2005 (UTC)
 * I have decided not to do this feature, until the bot really can do something useful. -- AllyUnion (talk) 00:59, 6 Feb 2005 (UTC)
 * Actually, rethinking to add the content from Template:Vfd top and Template:Vfd bottom but as HTML comments, on all VFD subpages after moved to WP:VFD/Old -- AllyUnion (talk) 07:13, 6 Feb 2005 (UTC)

-- AllyUnion (talk) 17:07, 5 Feb 2005 (UTC)

 * Having a bot to update VfD would be wonderful. One suggestion: as step 3), have it create the subpage for tomorrow.  There's no reason not to create it ahead of time, so it's ready when it's needed.

 * About adding and  : I don't know if this is such a good idea.  When I'm scanning /Old, I ignore the sections with colored backgrounds, because they've already been closed.  Adding the templates ahead of time would make it harder to see which pages have been processed.

 * Also, if it's feasible, change "roughly around" to "exactly". This thing'll be run as a cron job anyway, so there's no reason not to run it at the right time. dbenbenn | talk 21:00, 5 Feb 2005 (UTC)

 * You're forgetting about the time it takes for it to get a Wikipedia page. That is why I say roughly.  Because the load time to get the page is not always exact, the time when the bot posts something to the Wikipedia will not always fall exactly 00:00 UTC. -- AllyUnion (talk) 00:54, 6 Feb 2005 (UTC)
 * How do you think I manage to do it by hand every day at midnight (except when I flake out)? You load the page ten minutes early, get the changes ready, then hit "save page" at the right time.  Edit conflicts aren't an issue, because the page is only edited once or twice a day.  Of course, doing the same thing with a bot would complicate the code slightly.  It's no big deal either way.  dbenbenn | talk 05:10, 6 Feb 2005 (UTC)
 * The code won't be complicated any further than it already is. If the bot runs exactly 10 minutes before the UTC date rolls over to the next day, all it has to do is search for the current date, then replace    for  \n .  Or in computing terms:    for  \n . -- AllyUnion (talk) 07:08, 6 Feb 2005 (UTC)
 * Additionally, if it is running 10 minutes before the next UTC day, then yes, it would create the VFD page for tomorrow. I would actual want the bot to do that one hour before hand. just to be on the safe side.  Of course, all changes presume that the Wikipedia is working, and is not down at the time of the updates. -- AllyUnion (talk) 07:31, 6 Feb 2005 (UTC)

Well, the additional complication would be having it wait until midnight before submitting the change. Also, there are actually 5 lines to edit on VfD. See this diff for a representative example. dbenbenn | talk 08:31, 6 Feb 2005 (UTC)
 * As I said, it would only be adding, not removing the discussions. Removing the discussion would still be a human job, since the bot will not know when a discussion is closed.  It would be changing at line 13 and line 50, but it will not be making any changes at line 19 and line 45. -- AllyUnion (talk) 09:57, 6 Feb 2005 (UTC)
 * I think there's a slight misconception here about how the edits to VfD work. Every day at midnight, the new day is added, and the oldest day (now 6 days old) is removed, and added to /Old.  The discussions on that old day aren't closed yet—anyone can still vote.  It's just that the day doesn't appear on the main VfD page anymore.  The votes get closed one by one as someone gets around to closing and tallying them.  There's no reason for the bot not to do the complete extension (all 5 lines of the diff above), and it would be tremendously helpful.  dbenbenn | talk 21:17, 6 Feb 2005 (UTC)
 * Oh, if that is the case, then it can be done. -- AllyUnion (talk) 22:52, 6 Feb 2005 (UTC)
 * And the submission should be right at midnight or slightly thereafter. -- AllyUnion (talk) 22:54, 6 Feb 2005 (UTC)
 * And of course, it would move the page appropriately to the Old page as well. -- AllyUnion (talk) 22:55, 6 Feb 2005 (UTC)
 * Technical detail: Search for " Current votes:  " and find and replace that.  Search for "  Old votes:  " and find and replace that. -- AllyUnion (talk) 22:57, 6 Feb 2005 (UTC)

Changed to exactly. I still question whether it can post two pages at once at exactly 00:00 UTC. -- AllyUnion (talk) 23:56, 6 Feb 2005 (UTC)
 * Please let me know when you're going to start running your bot. Also, I'm curious to see the source code, if you're willing to share it.  Thanks, dbenbenn | talk 02:26, 7 Feb 2005 (UTC)
 * I don't see any problem with two edits at once a day, the rate limiting is just there to avoid overloading the server and allow for verification of bot actions. --fvw *  02:30, 2005 Feb 7 (UTC)

 * Another minor technicality: have it submit the changes for VfD first, and the change to /Old second (like, a couple seconds later). That way, you never have votes on /Old and VfD at the same time, which would contradict the Deletion process.  (Of course, it's only a matter of a few seconds anyway, but I'm a mathematician. :)  dbenbenn | talk 02:55, 7 Feb 2005 (UTC)

 * If that's how you want it, then it will submit the new VFD page first, then the Old page after that in the same script. -- AllyUnion (talk) 06:18, 7 Feb 2005 (UTC)

 * Oh, and yes, I will let you look at the code. -- AllyUnion (talk) 07:08, 7 Feb 2005 (UTC)

Okay. I'm all done with tasks 1 and 2. Task 3 will be another script. If anyone cares to view the scripts made based on the pywikipediabot framework, please leave a comment at my talk page. -- AllyUnion (talk) 10:54, 7 Feb 2005 (UTC)

Further additional tasks
(clarification of task 1)
 * 1) Post a new edited WP:VFD page
 * 2) Add the new UTC day section link on WP:VFD (in the Jump to specific days box)
 * 3) Remove the six days ago section link on WP:VFD (in the Jump to specific days box)
 * 4) Add a new six days ago /Old section link on WP:VFD (in the Jump to specific days box)
 * 5) Add the new UTC day transinclude on WP:VFD
 * 6) Remove the six days ago transinclude on WP:VFD
 * 7) Add the six days ago transinclude on WP:VFD/Old

Summary of tasks
A summary of its tasks can be found on its user page and whether or not it is working at this time: Allyunion -- AllyUnion (talk) 05:36, 8 Feb 2005 (UTC)

Interlanguage specialities at eo:

 * Halló! At eo:Vikipedio:Sciindaĵoj you find a note / an abstract about valid interlanguage links from eo: to other languages which differ from the original titles. Regards eo:Vikipediisto:Gangleri - Gangleri | [ Th] | T 00:30, 2005 Feb 9 (UTC)
 * Additions added there: Links to eo: will "lead to the target" throught a redirect. Gangleri | [ Th] | T 08:36, 2005 Feb 9 (UTC)

Upload script request
I'm in need of a script. I recently found a large dump of classical music, all CC-by-SA. I used wget recursively to fetch all of it (650 files; 5.29 gigs). I need to upload them now. I'd like to do it with a unix command line program. I figure the syntax should be something like:
 * >wikiupload Raul654bot:mypassword ./song.ogg --rate=100 --location=commons "This is a public domain song I uploaded "

 * The 1st arguement is the username and password (necessary for uploading files)
 * The 2nd arguement is the file to upload. So in the case of uploading a large number of files, I can just use the *
 * The 3rd arguement specifices the upload rate. I believe this is necessary because bots are supposed to be able to run at low speeds initially.
 * The 4th arguement specifies where it should go: en, de, commons, wikibooks, etc.
 * The 5th arguement is the upload text - IE, the text to be put on the image page.

→Raul654 07:36, Feb 9, 2005 (UTC)

cURL might already do what you're after. It's what I use for putting automated content into the Wikipedia - (I'm only adding article text, and I'm doing it using PHP's cURL library, so I don't think my code is likely to be of much use to you, otherwise I'd just give you the code). Nevertheless I think it should be able to do what you're after from the command line.

The following args look most applicable:
 * --cookie (you'll need a cookie for your uploading data under your username / password)
 * --limit-rate (so as to not upload too fast)
 * --form (With various args as per the Upload forms, which will include the description, and the path to the file)
 * The destination URL (which will be different depending on where you want it to go, but will presumably be the commons most of the time).

If you're lucky then maybe someone has already done this using cURL on the command line, and will let us know the command they used.

Docs and source code available at: http://curl.haxx.se/

Note that you'll probably have to call it multiple times (e.g. using "xargs"), if you want wildcard / multi-file-upload functionality.

All the best, Nickj (t) 08:08, 9 Feb 2005 (UTC)

I talked it over with Kate ,and here's what we got:

 * curl -F wpName=Bob -F wpPassword=asdf --cookie-jar ./mycookies "http://commons.wikimedia.org/w/wiki.phtml?Special:Userlogin&action=submit" > output1.html

 * curl -F wpUpload=@./Bob_test_file.txt -F wpUploadDescription=This_is_a_test -F wpUploadAffirm=1 --limit-rate 100k --cookie-jar ./mycookies "http://commons.wikimedia.org/w/wiki.phtml?Special:Upload&action=submit" > output2.html

The first one logs in Bob (whose password is asdf) and creates a cookie jar containing the log in cookie, and the second one actually does the upload (of file Bob_test_file.txt with description This_is_a_test). I tested, and the first one works *I think* but the 2nd one does not. I could appreciate someone helping debug it. →Raul654 09:38, Feb 9, 2005 (UTC)

 * You can try the pywikipediabot framework. They have a script called upload.py that you could use, if you made the script runable.  Then you can create a perl script or a bash script based on upload.py to loop through the contents of the directory.  I am uncertain if they have the pywikipedia framework ready for the commons. -- AllyUnion (talk) 10:13, 9 Feb 2005 (UTC)

 * Not only is pywikipediabot extremely difficult to get working, but it's nonfunctional at the moment. →Raul654 15:28, Feb 9, 2005 (UTC)

 * The newest version is working. -- AllyUnion (talk) 11:03, 10 Feb 2005 (UTC)

Debugging - Raul, you did good, and you were 95% of the way there:

With the first command: With the second command:
 * I added wpLoginattempt="Log in" (which is the same as clicking the "log in" button) - (may or may not be needed, but it won't hurt).
 * Added wpRemember=1 (may or may not be needed, but it won't hurt).
 * The URL could be wrong - I used http://commons.wikimedia.org/wiki/Special:Upload instead.
 * Need the file's path in "wpUploadFile", rather than "wpUpload".
 * Add 'wpUpload="Upload file"', which is the same as clicking the button (may or may not be needed, but it won't hurt).
 * With uploading, I think you want "--cookie", rather than "--cookie-jar", since "--cookie" is read-only, whereas --cookie-jar is for storing stuff (i.e. use store to log in, then read to upload).
 * Note that you'll also want to put in a license tag in the description, otherwise the tagging folks will hunt down and nail you to a tree ;-)

Putting all that together into two commands, we get: curl -F wpName=Nickj -F wpPassword=NotMyRealPassword -F wpLoginattempt="Log in" -F wpRemember=1 --cookie-jar ./mycookies "http://commons.wikimedia.org/w/index.php?title=Special:Userlogin&action=submit" > output1.html curl -F wpUpload="Upload file" -F wpUploadFile=@./Part of Great Barrier Reef from Helicopter.jpg -F wpUploadDescription="Photo I took in Jan 2005 over part of the Great Barrier Reef in a helicopter " -F wpUploadAffirm=1 --cookie ./mycookies "http://commons.wikimedia.org/wiki/Special:Upload" > output2.html
 * First command :
 * Second command (note that I have omitted the rate limiting bit, as my installed curl is so ancient that it doesn't have that option, but you probably want to add it back):

And to the right is the result, as a thumbnail:

All the best, Nickj (t) 23:23, 9 Feb 2005 (UTC)
 * Ok, I did a lot of work on this. The problem is, the method above fails for files above 4.7 megs (5000000 bytes) because mediawiki gives you an "Are you sure you want to upload this big file?" prompt. I tried a workaround but it doesn't work yet. You can see my script here. Run it by by doing: ./wikiupload username pass file →Raul654 08:39, Feb 10, 2005 (UTC)

For the record i fixed Rauls bot so that it no longer has this limit. . —Ævar Arnfjörð Bjarmason 11:37, 2005 Feb 10 (UTC)

VFD Old Bot work
On all pages moved to VFD/Old: On their talk pages, include a link to the VFD discussion, with a signed name. On all VFD subpages, include on the top and, with no finalization of the count. -- AllyUnion (talk) 10:25, 9 Feb 2005 (UTC)
 * No, this is bad. The usual way to finalise the votes is to go to /Old, pick an article that hasn't been boked, and resolve it. If they're all pre-boxed, it will make the process more difficult and less likely to be completed. —Ben Brockert (42) UE News  06:13, Feb 10, 2005 (UTC)
 * Just to clarify:  Anything between those two brackets will not show up on the page. -- AllyUnion (talk) 21:59, 10 Feb 2005 (UTC)
 * Ah, I completely ignored that they were in comment tags. In that case, please do that, it would help a lot. —Ben Brockert (42) UE News  04:02, Feb 11, 2005 (UTC)
 * I've decided against creating this feature as there are two shortcuts now. -- AllyUnion (talk) 23:39, 3 Mar 2005 (UTC)

User:Allyunion - Changing template to subst
A few users forget to use as. This bot is to correc that as well as: to. -- AllyUnion (talk) 02:45, 10 Feb 2005 (UTC)
 * Can't really hurt. It would be good to check that the action was completed at the same time. —Ben Brockert (42) UE News  06:14, Feb 10, 2005 (UTC)

Bot for maintaining Municipalities and Counties of Norway
Will be using pywikipediabot, especially replace.py and of course under supervision adhering to bot best practices and speed limits. The purpose is to maintain the various Municipalities_of_Norway: Many of the articles need a cleanup. A uniform use of the new infoboxes will help. Based on the standard numbering of municipalities, some statistical information can be added automagically. -- Egil 11:32, 11 Feb 2005 (UTC)

Request for flag made on meta:Requests for permissions -- Egil 19:59, 21 Feb 2005 (UTC)

1512

 * Bugzilla:1512 describes specialities about interlanguage links to and from eo:. All the titles I could identify have been fixed manualy both at eo: and at Wikipedias in other languages. The list of "affected" titles can be found here. At some languages changes to valid interlanguage links / to the valid titles have been reverted now manualy or by bots, probably because users where not aware of this problem. Please do not hesitate to contact me if you have any questions. Regards Gangleri | [ Th] | T 12:53, 2005 Feb 17 (UTC)
 * See also: post at projects/pywikipediabot 04:16, 2005 Feb 18 (UTC)

bot request
Can someone make a bot to go through the 366 days of the year and put links into the BBC's on this day page? They come in the format http://news.bbc.co.uk/onthisday/hi/dates/stories/month/date/ replacing month with the month, and date with a numerical date, not including a leading zero, 9 not 09. Dunc|☺ 22:39, 19 Feb 2005 (UTC)
 * I don't think you need a bot for that... really... See my comment on your talk page. -- AllyUnion (talk) 11:10, 20 Feb 2005 (UTC)

Sorry if I didn't make myself clear. The link ought to go into an external links section in the pages in the style of "February 20" rather than the little ones that appear on the front page. It should be possible to go to March 18 (say) on any date of the year and the link should link to http://news.bbc.co.uk/onthisday/hi/dates/stories/march/18. If it is coded into the article text with –  then that will always take the user to today's article, rather than the date in the article title. Dunc|☺ 12:45, 20 Feb 2005 (UTC)

 * This has or is being handled under User:Kakashi Bot maintained and run by me. Since this is a one time 'run', I don't think a bot flag is necessary. -- AllyUnion (talk) 19:09, 25 Feb 2005 (UTC)

Responding to Sandbot request
I am responding to a request given at Bot requests for a bot that cleans out the sandbox. The request is that the bot should clean the sandbox every 6 hours.

The following sandboxes will be cleaned every 6 hours:
 * Sandbox
 * Tutorial (Editing)/sandbox
 * Tutorial (Formatting)/sandbox
 * Tutorial (Wikipedia links)/sandbox
 * Tutorial (Related site links)/sandbox
 * Tutorial (External links)/sandbox
 * Wikipedia talk:Tutorial (Talk pages)

This bot will be running under User:Sandbot, and using either Template:Please leave this line alone (sandbox heading) or a similar template. -- AllyUnion (talk) 10:27, 25 Feb 2005 (UTC)
 * This also includes all talk pages, except for Wikipedia talk:Tutorial (Talk pages). Each sandbox will be cleaned separately 15 minutes apart from each other. -- AllyUnion (talk) 10:56, 25 Feb 2005 (UTC)

There has been a change, due to a request. All tutorial related sandboxes will be cleaned out every week. -- AllyUnion (talk) 18:39, 25 Feb 2005 (UTC)

VfD newpage bot
Recently there have been some 'general' articles on VfD pages to establish consensus on inclusion (or exclusion) of certain groups of articles. It would be useful to have the link (or {include}) to those articles placed on the top of each day's VfD page. I've been doing this manually but would prefer the VfD bot to handle this; would that be ok? Radiant! 11:40, Mar 4, 2005 (UTC)

 * Should there be no objection in 7 days from Radiant's request, I will add the feature to the bot. -- AllyUnion (talk) 06:17, 5 Mar 2005 (UTC)

Zbot
Ok, this is my first attempt at a bot, so if I seem to be missing anything, let me know. The main reason I created this bot is that I wanted to have a bot that changes flag images. What I mean by that is replacing one flag image from here, with another, which can be either on here or at the Commons. An example would be (which will be a test run if approved), is switching from Image:Belarus flag large.png to Image:Flag of Belarus.png. Not only this will free up the many images we use here at Wikipedia EN, this will also do the work that I have done by hand for months. And, if we ever go to svg conversion, this bot can be used to help in the conversion. While I am not sure how long it will take before it can be approved, but I am an idiot in dealing with programming and could use some help on trying to make the bot work. Zach (Sound Off) 06:52, 12 September 2005 (UTC)

 * Are you re-uploading the images to rename them, or are you just changing which image is shown in articles? —Cryptic (talk) 07:12, 12 September 2005 (UTC)
 * Changing what is shown in the articles. If there is any images to upload, I will do it myself manually. But, as I post on User:Zbot, I crashed Python and I am an idiot when coming to programing. In order for this bot to work, I probably might have to ask for someone to code it for me. Zach (Sound Off) 07:27, 12 September 2005 (UTC)
 * And since we can use SVG files, the bot can also be created (by someone else, since I gave up at coding) to help do the image conversion. Zach (Sound Off) 21:10, 12 September 2005 (UTC)
 * The discussion has moved to Bot requests. -- Beland 04:16, 13 September 2005 (UTC)

Bot for maintaining Municipalities and Counties of Norway
Will be using pywikipediabot, especially replace.py and of course under supervision adhering to bot best practices and speed limits. The purpose is to maintain the various Municipalities_of_Norway: Many of the articles need a cleanup. A uniform use of the new infoboxes will help. Based on the standard numbering of municipalities, some statistical information can be added automagically. -- Egil 11:32, 11 Feb 2005 (UTC)

Request for flag made on meta:Requests for permissions -- Egil 19:59, 21 Feb 2005 (UTC)

1512

 * Bugzilla:1512 describes specialities about interlanguage links to and from eo:. All the titles I could identify have been fixed manualy both at eo: and at Wikipedias in other languages. The list of "affected" titles can be found here. At some languages changes to valid interlanguage links / to the valid titles have been reverted now manualy or by bots, probably because users where not aware of this problem. Please do not hesitate to contact me if you have any questions. Regards Gangleri | [ Th] | T 12:53, 2005 Feb 17 (UTC)
 * See also: post at projects/pywikipediabot 04:16, 2005 Feb 18 (UTC)

Simple Matt Crypto bot?
User:Matt Crypto (bot) is doing a simple, valid change every midnight. I don't think the bot flag should be set (since the cryptography wikireader always needs more attention ;)) but it ought to be put on the list of bots. Not putting it in myself because I'm not sure the bot is allowed. :) r3m0t 11:59, Feb 21, 2005 (UTC)

 * The bot flag in my opinion is meant to avoid a situation where the bot clutters up the recent changes. If a bot makes just a single change or a few changes every day, a bot flag seems unnecessary. - Andre Engels 08:52, 24 Feb 2005 (UTC)

 * Yes, I think a bot flag is unnecessary (unless there's some other reason apart from filtering RC). I requested permission to run this script last December at Wikipedia_talk:Bots/Archive_4. — Matt Crypto 11:31, 4 Mar 2005 (UTC)

Responding to Sandbot request
I am responding to a request given at Bot requests for a bot that cleans out the sandbox. The request is that the bot should clean the sandbox every 6 hours.

The following sandboxes will be cleaned every 6 hours:
 * Sandbox
 * Tutorial (Editing)/sandbox
 * Tutorial (Formatting)/sandbox
 * Tutorial (Wikipedia links)/sandbox
 * Tutorial (Related site links)/sandbox
 * Tutorial (External links)/sandbox
 * Wikipedia talk:Tutorial (Talk pages)

This bot will be running under User:Sandbot, and using either Template:Please leave this line alone (sandbox heading) or a similar template. -- AllyUnion (talk) 10:27, 25 Feb 2005 (UTC)
 * This also includes all talk pages, except for Wikipedia talk:Tutorial (Talk pages). Each sandbox will be cleaned separately 15 minutes apart from each other. -- AllyUnion (talk) 10:56, 25 Feb 2005 (UTC)

There has been a change, due to a request. All tutorial related sandboxes will be cleaned out every week. -- AllyUnion (talk) 18:39, 25 Feb 2005 (UTC)

VfD newpage bot
Recently there have been some 'general' articles on VfD pages to establish consensus on inclusion (or exclusion) of certain groups of articles. It would be useful to have the link (or {include}) to those articles placed on the top of each day's VfD page. I've been doing this manually but would prefer the VfD bot to handle this; would that be ok? Radiant! 11:40, Mar 4, 2005 (UTC)

 * Should there be no objection in 7 days from Radiant's request, I will add the feature to the bot. -- AllyUnion (talk) 06:17, 5 Mar 2005 (UTC)

VFD into a list of day links
As per discussion on Wikipedia talk:Votes for deletion, I'll be making WP:VFD into a list of day links probably during the day (UTC) on Sunday 13 March 2005. Votes for deletion (full list) (or WP:VFDF) will be the full list with all day pages transcluded for a multi-megabyte monster page. I've left notes on Wikipedia talk:Bots and User talk:AllyUnion about the change - David Gerard 09:41, 11 Mar 2005 (UTC)

 * No consensus has been developed over this decision. I object until I understand what is being trying to solve / accomplished. -- AllyUnion (talk) 19:32, 12 Mar 2005 (UTC)

VFD Bot extension
 (copied from my and AllyUnion's talk pages —Korath (Talk) 01:36, Mar 14, 2005 (UTC))

Also, as long as I'm here, could I trouble you to tweak Vfdbot to add a or something similar to the previous day's page when updating the list of days currently transcluded into WP:VFD? I catch two or three vfds a week being added to the first day listed on vfd instead of the current day, and sometimes two or three a day where they're added to yesterday's page just after midnight UTC. The latter aren't a problem if they're missed (and I don't bother to correct them even when I see them), but the former certainly are. —Korath (Talk) 00:28, Mar 14, 2005 (UTC)

 * I'll tweak VFD Bot later. I'm kind of suppose to be studying for my finals.  ^^;;;  Do me a favor and post in the talk page for WP:BOTS to make sure it gets approval. --AllyUnion (talk) 00:55, 14 Mar 2005 (UTC)

 (end copy —Korath (Talk) 01:36, Mar 14, 2005 (UTC))

Request done. -- AllyUnion (talk) 00:27, 25 Mar 2005 (UTC)

Categories for deletion / category population / category depopulation bot assistant
Moved to: User:AllyUnion/NekoDaemon. Another request will be placed once the bot is completed. -- AllyUnion (talk) 08:29, 14 May 2005 (UTC)

Minor Sandbot change
I am modifying Sandbot to reinforce the existence of the header every 30 minutes (all sandboxes). The main sandbox will be cleaned every 12 hours instead of every 6 hours. -- AllyUnion (talk) 22:36, 24 Mar 2005 (UTC)

DYK Bot?
Manually archiving DYK items to Recent additions is still managable, but can anyone with more knowledge about bots tell me if it's possible to automate the archiving process (also outlining the pics correctly).

It should:
 * Archive all but the latest 2 updates from the section on DYK talk to Recent additions.
 * Archive the oldest 50 items including pics to a free numbered subpage in Recent additions.
 * Warn users about their articles being featured.

I'd also love for template updates to be automated during weekends and holidays, when no else seems to do them, but that may not be possible because that would require the bot having admin access. - Mgm|(talk) 10:11, Mar 28, 2005 (UTC)

 * The pywikipediabot framework doesn't have anything for page moves at the moment as far as I am aware... -- AllyUnion (talk) 14:37, 28 Mar 2005 (UTC)

The text that needs archiving would be only a section of the page. Complete page moves wouldn't be necessary. It's just text that needs to be copied, then deleted at the old location. Mgm|(talk) 14:45, Mar 28, 2005 (UTC)

 * Section? I'm not quite certain you're driving at.  It would help me if you detail the exact archiving process and what text your moving around. -- AllyUnion (talk) 03:23, 29 Mar 2005 (UTC)

Update: The code is still being written, however I have a good idea what this bot does. Some definitions for the purpose of anyone who wishs to know:
 * dyk = Did you know
 * dykline = A line of information containing the dyk info plus a possible associated picture. It is assumed that all associated pictures proceed "...that"
 * block = A blank newline in the wikicode that separates several dyklines. A block will refer to several dyklines between two blank newline or one of the key search features, such as a hidden HTML comment or section.

 * 1) On the page Template talk:Did you know...  User:Kurando-san will move all blocks under the ===ARCHIVE USED SUGGESTIONS HERE=== section except for 3 blocks to Recent additions.
 * 2) On the page Recent additions, if the number of dyklines exceed 50, move the oldest blocks (the bottom blocks) to an archive page, like Recent additions 25 until the number of dyklines on the archive page is equal or greater than 50 dyklines.  Once the number of dyklines exceed 50, create a new archive page and add to the next number in the archive.  In this case, Recent additions 26.  Repeat until Recent additions is less or equal to 50 dyklines.

-- AllyUnion (talk) 08:50, 6 Apr 2005 (UTC)

Update: I've been writing this code for several days now. It kind of works... but not really. I have posted up the code at User:AllyUnion/did_you_know.pl. If anyone manages to produce a correct output, I'll give them a Barnstar. -- AllyUnion (talk) 03:35, 9 Apr 2005 (UTC)

I'm still on a semi-Wiki-vacation. But I took some time, and I think I fixed the bot now. -- AllyUnion (talk) 13:13, 14 Apr 2005 (UTC)

Works. Running monthly under User:Kurando-san. -- AllyUnion (talk) 22:03, 14 Apr 2005 (UTC)

Wikipedia:Featured picture candidates archival bot
The purpose of this bot is to move nominations with a signed initial nomination to the 14 day holding period after 14 days have been passed. -- AllyUnion (talk) 09:31, 29 Mar 2005 (UTC)

 * Running under User:Kurando-san at the moment. -- AllyUnion (talk) 04:59, 5 Apr 2005 (UTC)

RKBot
I have written a small script to automate the MS Internet Control to do various substitutions on the German wikipedia and am requesting bot status for de:User:RKBot. --Reinhard 21:20, 10 Apr 2005 (UTC)

 * See de:Wikipedia:Bots. They have their own policy. r3m0t talk 22:11, Apr 10, 2005 (UTC)

Adding a task to VFD Bot
Update Votes for deletion/Log/Yesterday every day and put yesterday's transinclude on the page. -- AllyUnion (talk) 10:31, 15 Apr 2005 (UTC)

CFD Archival Bot
User:NekoDaemon has been assigned to automatically do the following things:

 * 1) Add new CFD Day Transinclude at the same time as the VFD Bot
 * 2) Create the new CFD Day Transinclude at the same time as the VFD Bot
 * 3) Close the CFD Day Transinclude page at the same time as the VFD Bot

-- AllyUnion (talk) 05:44, 18 Apr 2005 (UTC)

Using Pearle for cleanup tags
I have created Template:cleanup-date to replace Template:cleanup. It is intended to make it easier to use Category:Wikipedia cleanup in a first in, first out fashion. I would like to use Pearle to change cleanup tags to cleanup-date tags. The first data source would be the per-month subpages of Cleanup, which I will analyze offline and feed to the bot. For all remaining uses of the cleanup tag, I would have the bot look at previous versions at one-month intervals, to determine the month in which the tag was originally assigned. -- Beland 02:09, 9 May 2005 (UTC)

VFD Bot functionality change
Due to the change of how VFD is run, the VFD Bot will perform the updates on Votes for deletion (long form) as before, and perform the new styled updates on Votes for deletion. -- AllyUnion (talk) 04:58, 9 May 2005 (UTC)

PeriodBot
I've written a program that crawls the offline dump looking for paragraphs that end without punctuation. If I run this to help me find articles to (manually) edit, does that count as a bot? Do I have to limit my manual edits to some rate? Brighterorange 14:21, 12 May 2005 (UTC)

 * Seems to me that if it does neither automated access to the live Wikipedia articles nor automatic modification, it isn't a bot. --Carnildo 17:54, 12 May 2005 (UTC)
 * Hooray! Brighterorange 18:53, 12 May 2005 (UTC)

title: Wikipedia talk:Bots/Archive 6


text: User talk:70.48.100.185

title: User talk:70.48.100.185