User talk:Mnemotronic

License tagging for Image:Toolbar.GIF
Thanks for uploading Image:Toolbar.GIF. Wikipedia gets thousands of images uploaded every day, and in order to verify that the images can be legally used on Wikipedia, the source and copyright status must be indicated. Images need to have an image tag applied to the image description page indicating the copyright status of the image. This uniform and easy-to-understand method of indicating the license status allows potential re-users of the images to know what they are allowed to do with the images.

For more information on using images, see the following pages:
 * Image use policy
 * Image copyright tags

This is an automated notice by OrphanBot. If you need help on selecting a tag to use, or in adding the tag to the image description, feel free to post a message at Media copyright questions. 19:12, 27 January 2007 (UTC)

Proposed changes to "Distributed revision control"
I am proposing the following changes to the Distributed revision control page:

Advantages * Allows users to work productively even when not connected to a network Not universally true:

Some non-distributed revision control systems that utilize "Version merging" do allow disconnected users to make changes to the controlled items. Generally, the user must manually enable file modifications (via permissions or mode settings) at the local file system level for the files to be changed. Later, when the user re-establishes communication with the repository, the system is notified of the user's "intention to modify" those items which have been changed. Merging, conflict resolution, and other repository operations may be initiated or published at that time.

Advantages * Makes most operations much faster since no network is involved

Depending on the system, this may or may not be a factor. For an isolated user, the activity of refreshing the local copy of the repository is that which generally requires the greatest amount of time. Some systems may perform operations take a significant time, but this is implementation-specific. Factors affecting the refresh time include network bandwidth and latency, repository performance, and the overall delta between the local copy and the repository -- the greater the number of changes, the longer the refresh takes. If that user's contributions are to be shared with others, then at some point a network will be involved, and merging may be required. At that time, significant effort may be required to integrate the changes made by the isolated user. For a proper comparison between RCS implementations, this effort will need to be compared to that expended by a user who works connected and merges regularly.

Disadvantages

Revision control systems which integrate work task/package assignment, tracking, and reporting may not indicate the correct status of the disconnected user's work in process.

Every user maintains a mirror of the entire repository on his or her local system. For larger projects, long-lived projects, or those with many branches, the consumption of local storage resources may be a factor.

Mnemotronic (talk) 01:04, 9 May 2009 (UTC)