Fork Machine

Posted on by admin



Smallte Fork Dispenser for Instant Bowl Noodle Packing Machine / Instant Noodle Packing MachineGet more information please email to 'jeyni.wang@smallte.cn';w.

Get reviews, hours, directions, coupons and more for Lake Fork Machine & Tool at 3694 Fm 515, Emory, TX 75440. Search for other Machine Shops in Emory on The Real Yellow Pages®. Smallte Fork Dispenser for Instant Bowl Noodle Packing Machine / Instant Noodle Packing MachineGet more information please email to 'jeyni.wang@smallte.cn';w.

A timeline chart of how Linux distributions have forked.

In software engineering, a project fork happens when developers take a copy of source code from one software package and start independent development on it, creating a distinct and separate piece of software. The term often implies not merely a development branch, but also a split in the developer community, a form of schism.[1]

Free and open-source software is that which, by definition, may be forked from the original development team without prior permission, without violating copyright law. However, licensed forks of proprietary software (e.g.Unix) also happen.

Etymology[edit]

The word 'fork' has been used to mean 'to divide in branches, go separate ways' as early as the 14th century.[2] In the software environment, the word evokes the fork system call, which causes a running process to split itself into two (almost) identical copies that (typically) diverge to perform different tasks.[3]

In the context of software development, 'fork' was used in the sense of creating a revision control 'branch' by Eric Allman as early as 1980, in the context of SCCS:[4]

Creating a branch 'forks off' a version of the program.

The term was in use on Usenet by 1983 for the process of creating a subgroup to move topics of discussion to.[5]

'Fork' is not known to have been used in the sense of a community schism during the origins of Lucid Emacs (now XEmacs) (1991) or the BSDs (1993–1994); Russ Nelson used the term 'shattering' for this sort of fork in 1993, attributing it to John Gilmore.[6] However, 'fork' was in use in the present sense by 1995 to describe the XEmacs split,[7] and was an understood usage in the GNU Project by 1996.[8]

Forking of free and open-source software[edit]

Free and open-source software may be legally forked without prior approval of those currently developing, managing, or distributing the software per both The Free Software Definition and The Open Source Definition:[9]

The freedom to distribute copies of your modified versions to others (freedom 3). By doing this, you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.

Receiving text messages on ipad. You can send a text message to one or more people.

— The Free Software Definition[10]

3. Derived Works: The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.

In free software, forks often result from a schism over different goals or personality clashes. In a fork, both parties assume nearly identical code bases, but typically only the larger group, or whoever controls the Web site, will retain the full original name and the associated user community. Thus, there is a reputation penalty associated with forking.[9] The relationship between the different teams can be cordial or very bitter. On the other hand, a friendly fork or a soft fork is a fork that does not intend to compete, but wants to eventually merge with the original.

Eric S. Raymond, in his essay Homesteading the Noosphere,[12] stated that 'The most important characteristic of a fork is that it spawns competing projects that cannot later exchange code, splitting the potential developer community'. He notes in the Jargon File:[13]

Forking is considered a Bad Thing—not merely because it implies a lot of wasted effort in the future, but because forks tend to be accompanied by a great deal of strife and acrimony between the successor groups over issues of legitimacy, succession, and design direction. There is serious social pressure against forking. As a result, major forks (such as the Gnu-Emacs/XEmacs split, the fissioning of the 386BSD group into three daughter projects, and the short-lived GCC/EGCS split) are rare enough that they are remembered individually in hacker folklore.

David A. Wheeler notes[9] four possible outcomes of a fork, with examples:

  1. The death of the fork. This is by far the most common case. It is easy to declare a fork, but considerable effort to continue independent development and support.
  2. A re-merging of the fork (e.g., egcs becoming 'blessed' as the new version of gcc.)
  3. The death of the original (e.g. the X.Org Server succeeding and XFree86 dying.)
  4. Successful branching, typically with differentiation (e.g., OpenBSD and NetBSD.)

Distributed revision control (DVCS) tools have popularised a less emotive use of the term 'fork', blurring the distinction with 'branch'.[14] With a DVCS such as Mercurial or Git, the normal way to contribute to a project, is to first create a personal branch of the repository, independent of the main repository, and later seek to have your changes integrated with it. Sites such as GitHub, Bitbucket and Launchpad provide free DVCS hosting expressly supporting independent branches, such that the technical, social and financial barriers to forking a source code repository are massively reduced, and GitHub uses 'fork' as its term for this method of contribution to a project.

Forks often restart version numbering from 0.1 or 1.0 even if the original software was at version 3.0, 4.0, or 5.0. An exception is when the forked software is designed to be a drop-in replacement for the original project, e.g.MariaDB for MySQL[15] or LibreOffice for OpenOffice.org.

Forking proprietary software[edit]

In proprietary software, the copyright is usually held by the employing entity, not by the individual software developers. Proprietary code is thus more commonly forked when the owner needs to develop two or more versions, such as a windowed version and a command line version, or versions for differing operating systems, such as a word processor for IBM PC compatible machines and Macintosh computers. Generally, such internal forks will concentrate on having the same look, feel, data format, and behavior between platforms so that a user familiar with one can also be productive or share documents generated on the other. This is almost always an economic decision to generate a greater market share and thus pay back the associated extra development costs created by the fork.

A notable proprietary fork not of this kind is the many varieties of proprietary Unix—almost all derived from AT&T Unix under license and all called 'Unix', but increasingly mutually incompatible.[16]SeeUNIX wars.

The BSD licenses permit forks to become proprietary software, and copyleft proponents say that commercial incentives thus make proprietisation almost inevitable. (Copyleft licenses can, however, be circumvented via dual-licensing with a proprietary grant in the form of a Contributor License Agreement.) Examples include macOS (based on the proprietary NeXTSTEP and the open source FreeBSD), Cedega and CrossOver (proprietary forks of Wine, though CrossOver tracks Wine and contributes considerably), EnterpriseDB (a fork of PostgreSQL, adding Oracle compatibility features[17]), Supported PostgreSQL with their proprietary ESM storage system,[18] and Netezza's[19] proprietary highly scalable derivative of PostgreSQL. Some of these vendors contribute back changes to the community project, while some keep their changes as their own competitive advantages.

See also[edit]

  • Modular programming
  • Team effectiveness

References[edit]

  1. ^'Schism', with its connotations, is a common usage, e.g.'the Lemacs/FSFmacs schism'Archived 12 December 2009 at WebCite (Jamie Zawinski, 2000), 'Behind the KOffice split'Archived 6 July 2013 at the Wayback Machine (Joe Brockmeier, Linux Weekly News, 2010-12-14), 'Copyright assignment - once bitten, twice shy'Archived 30 March 2012 at the Wayback Machine (Richard Hillesley, H-Online, 2010-08-06), 'Forking is a feature'Archived 29 February 2012 at the Wayback Machine (Anil Dash, 2010-09-10), 'The Great Software Schism'Archived 6 January 2012 at the Wayback Machine (Glyn Moody, Linux Journal, 2006-09-28), 'To Fork Or Not To Fork: Lessons From Ubuntu and Debian'Archived 26 February 2012 at the Wayback Machine (Benjamin Mako Hill, 2005).
  2. ^Entry 'fork' in Online Etymology DictionaryArchived 25 May 2012 at the Wayback Machine
  3. ^'The term fork is derived from the POSIX standard for operating systems: the system call used so that a process generates a copy of itself is called fork().' Robles, Gregorio; González-Barahona, Jesús M. (2012). A Comprehensive Study of Software Forks: Dates, Reasons and Outcomes(PDF). OSS 2012 The Eighth International Conference on Open Source Systems. doi:10.1007/978-3-642-33442-9_1. Archived(PDF) from the original on 2 December 2013. Retrieved 20 October 2012.
  4. ^Allman, Eric. 'An Introduction to the Source Code Control System.'Archived 6 November 2014 at the Wayback Machine Project Ingres, University of California at Berkeley, 1980.
  5. ^Can somebody fork off a 'net.philosophy'? (John Gilmore, net.misc, 18 January 1983)
  6. ^Shattering — good or bad? (Russell Nelson, gnu.misc.discuss, 1 October 1993)
  7. ^Re: Hey Franz: 32K Windows SUCK!!!!! (Bill Dubuque, cu.cs.macl.info, 21 September 1995)
  8. ^Lignux? (Marcus G. Daniels, gnu.misc.discuss, 7 June 1996)
  9. ^ abcWhy Open Source Software / Free Software (OSS/FS, FLOSS, or FOSS)? Look at the Numbers!: ForkingArchived 5 April 2006 at the Wayback Machine (David A. Wheeler)
  10. ^Stallman, Richard. 'The Free Software Definition'. Free Software Foundation. Archived from the original on 14 October 2013. Retrieved 15 October 2013.
  11. ^'The Open Source Definition'. The Open Source Initiative. Archived from the original on 15 October 2013. Retrieved 15 October 2013.
  12. ^Raymond, Eric S. (15 August 2002). 'Promiscuous Theory, Puritan Practice'. Archived from the original on 6 October 2006.
  13. ^ForkedArchived 8 November 2011 at the Wayback Machine (Jargon File), first added to v4.2.2Archived 14 January 2012 at the Wayback Machine, 20 Aug 2000)
  14. ^e.g.Willis, Nathan (15 January 2015). 'An 'open governance' fork of Node.js'. LWN.net. Archived from the original on 21 April 2015. Retrieved 15 January 2015. Forks are a natural part of the open development model—so much so that GitHub famously plasters a 'fork your own copy' button on almost every page. See also Nyman, Linus (2015). Understanding Code Forking in Open Source Software (Ph.D.). Hanken School of Economics. p. 57. hdl:10138/153135. Where practitioners have previously had rather narrow definitions of a fork, [..] the term now appears to be used much more broadly. Actions that would traditionally have been called a branch, a new distribution, code fragmentation, a pseudo-fork, etc. may all now be called forks by some developers. This appears to be in no insignificant part due to the broad definition and use of the term fork by GitHub.
  15. ^Forked a project, where do my version numbers start?Archived 26 August 2011 at the Wayback Machine
  16. ^Fear of forkingArchived 17 December 2012 at the Wayback Machine - An essay about forking in free software projects, by Rick Moen
  17. ^EnterpriseDBArchived 13 November 2006 at the Wayback Machine
  18. ^Fujitsu Supported PostgreSQLArchived 20 August 2006 at the Wayback Machine
  19. ^NetezzaArchived 13 November 2006 at the Wayback Machine

External links[edit]

  • Right to Fork at Meatball Wiki
  • A PhD examining forking: (Nyman, 2015) 'Understanding Code Forking in Open Source Software - An examination of code forking, its effect on open source software, and how it is viewed and practiced by developers'
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Fork_(software_development)&oldid=997044581'
-->

This article describes the steps to set up a Git repository on your local machine, with the intent to contribute to Microsoft documentation. Server for nfs user manager. Contributors may use a locally cloned repository to add new articles, do major edits on existing articles, or change artwork.

You run these one-time setup activities to start contributing:

  • Determine the appropriate repository
  • Fork the repository to your GitHub account
  • Choose a local folder for the cloned files
  • Clone the repository to your local machine
  • Configure the upstream remote value
Forklift

Important

If you're making only minor changes to an article, you do not need to complete the steps in this article. You can continue directly to the quick changes workflow.

Fork Machine

Overview

To contribute to Microsoft's documentation site, you can make and edit Markdown files locally by cloning the corresponding documentation repository. Microsoft requires you to fork the appropriate repository into your own GitHub account so that you have read/write permissions there to store your proposed changes. Then you use pull requests to merge changes into the read-only central shared repository.

If you're new to GitHub, watch the following video for a conceptual overview of the forking and cloning process:

Determine the repository

Documentation hosted at docs.microsoft.com resides in several different repositories at github.com.

  1. If you are unsure of which repository to use, then visit the article on docs.microsoft.com using your web browser. Select the Edit link (pencil icon) on the upper right of the article.

  2. That link takes you to github.com location for the corresponding Markdown file in the appropriate repository. Note the URL to view the repository name.

    For example, these popular repositories are available for public contributions:

    • Azure documentation https://github.com/MicrosoftDocs/azure-docs
    • SQL Server documentation https://github.com/MicrosoftDocs/sql-docs
    • Visual Studio documentation https://github.com/MicrosoftDocs/visualstudio-docs
    • .NET Documentation https://github.com/dotnet/docs
    • Azure .Net SDK documentation https://github.com/azure/azure-docs-sdk-dotnet
    • ConfigMgr documentation https://github.com/MicrosoftDocs/SCCMdocs

Fork the repository

Using the appropriate repository, create a fork of the repository into your own GitHub account by using the GitHub website.

A personal fork is required since all main documentation repositories provide read-only access. To make changes, you must submit a pull request from your fork into the main repository. To facilitate this process, you first need your own copy of the repository, in which you have write access. A GitHub fork serves that purpose.

  1. Go to the main repository's GitHub page and click the Fork button on the upper right.

  2. If you are prompted, select your GitHub account tile as the destination where the fork should be created. This prompt creates a copy of the repository within your GitHub account, known as a fork.

South Fork Machine Lebanon Oregon Phone Number

Choose a local folder

Make a local folder to hold a copy of the repository locally. Some of the repositories can be large; up to 5 GB for azure-docs for example. Choose a location with available disk space.

  1. Choose a folder name should be easy for you to remember and type. For example, consider a root folder C:docs or make a folder in your user profile directory ~/Documents/docs/

    Important

    Avoid choosing a local folder path that is nested inside of another git repository folder location. While it is acceptable to store the git cloned folders adjacent to each other, nesting git folders inside one another causes errors for the file tracking.

  2. Launch Git Bash

    The default location that Git Bash starts in is typically the home directory (~) or /c/users/<Windows-user-account>/ on Windows OS.

    To determine the current directory, type pwd at the $ prompt.

  3. Change directory (cd) into the folder that you created for hosting the repository locally. Note that Git Bash uses the Linux convention of forward-slashes instead of back-slashes for folder paths.

    For example, cd /c/docs/ or cd ~/Documents/docs/

Create a local clone

Using Git Bash, prepare to run the clone command to pull a copy of a repository (your fork) down to your device on the current directory.

Authenticate by using Git Credential Manager

If you installed the latest version of Git for Windows and accepted the default installation, Git Credential Manager is enabled by default. Git Credential Manager makes authentication much easier because you don't need to recall your personal access token when re-establishing authenticated connections and remotes with GitHub.

  1. Run the clone command, by providing the repository name. Cloning downloads (clone) the forked repository on your local computer. Gears of war ultimate edition steam.

    Tip

    You can get your fork's GitHub URL for the clone command from the Clone or download button in the GitHub UI:

    Be sure to specify the path to your fork during the cloning process, not the main repository from which you created the fork. Otherwise, you cannot contribute changes. Your fork is referenced through your personal GitHub user account, such as github.com/<github-username>/<repo>.

    Your clone command should look similar to this example:

  2. When you're prompted, enter your GitHub credentials.

  3. When you're prompted, enter your two-factor authentication code.

    Note

    Your credentials will be saved and used to authenticate future GitHub requests. You only need to do this authentication once per computer.

  4. The clone command runs and downloads a copy of the repository files from your fork into a new folder on the local disk. A new folder is made within the current folder. It may take a few minutes, depending on the repository size. You can explore the folder to see the structure once it is finished.

Configure remote upstream

After cloning the repository, set up a read-only remote connection to the main repository named upstream. You use the upstream URL to keep your local repository in sync with the latest changes made by others. The git remote command is used to set the configuration value. You use the fetch command to refresh the branch info from the upstream repository.

  1. If you're using Git Credential Manager, use the following commands. Replace the <repo> and <organization> placeholders.

  2. View the configured values and confirm the URLs are correct. Ensure the origin URLs point to your personal fork. Ensure the upstream URLs point to the main repository, such as MicrosoftDocs or Azure.

    Example remote output is shown. A fictitious git account named MyGitAccount is configured with a personal access token to access the repo azure-docs:

  3. If you made a mistake, you can remove the remote value. To remove the upstream value, run the command git remote remove upstream.

Next steps

  • To learn more about adding and updating content, continue to the GitHub contribution workflow.