Git Winch Guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
advantages [2025/06/11 18:53] – adminadvantages [2025/07/09 11:16] (current) – admin
Line 6: Line 6:
  
   * //Git Winch// is totally file-agnostic. What this means is that the office is free to use //any// file they choose. We do NOT lock you into any files. We do not put you into our "private walled-garden" ... Read about the "walled-garden" problem [[https://www.techtarget.com/searchsecurity/definition/walled-garden | here ]] and  [[https://en.wikipedia.org/wiki/Closed_platform|here]].   * //Git Winch// is totally file-agnostic. What this means is that the office is free to use //any// file they choose. We do NOT lock you into any files. We do not put you into our "private walled-garden" ... Read about the "walled-garden" problem [[https://www.techtarget.com/searchsecurity/definition/walled-garden | here ]] and  [[https://en.wikipedia.org/wiki/Closed_platform|here]].
 +  
 +  * You can create template files for //ALL// the files your office uses. This ensures that you can create a new file for //any// application you use, right from within //Git Winch.// For e.g. you can immediately work on a new letter with your office letterhead on it.
  
   * We do NOT make offices transmit files //through our server.// This is a huge deal, if you think deeply. In today's AI driven world; many large companies are using your data to train their AI -- and some often surreptitiously do other nefarious activities such as user-profiling, etc. //We do not do anything of that sorts so you are very sure your files can never be read by us. Your privacy is totally protected.//   * We do NOT make offices transmit files //through our server.// This is a huge deal, if you think deeply. In today's AI driven world; many large companies are using your data to train their AI -- and some often surreptitiously do other nefarious activities such as user-profiling, etc. //We do not do anything of that sorts so you are very sure your files can never be read by us. Your privacy is totally protected.//
      
-  * There are many office systems that allows you to //attach// files and then send those files to others. For e.g. Slack or Microsoft Teams. This is actually a serious headache, which needs a deeper explanation. Read about the [[vfour?do=export_xhtml|"V-Four" problem here]].+  * There are many office systems that allows you to //attach// files and then send those files to others. For e.g. Slack or Microsoft Teams. This is actually a serious headache, which needs a deeper explanation. Read about the [[vfour?do=export_xhtml|"V-Four" problem here]]. //Git Winch// completely avoids that headache.
  
   * //Git Winch// will keep other members working on the files in a repository informed about which files they are working. It prevents the same file being worked-upon, thus it is useful for working on binary files as there would be very little chance of merge errors.   * //Git Winch// will keep other members working on the files in a repository informed about which files they are working. It prevents the same file being worked-upon, thus it is useful for working on binary files as there would be very little chance of merge errors.
Line 15: Line 17:
   * Members can leave additional notes on each and every file, if they so want – such meta-information about files can be very useful to help others working on those files.   * Members can leave additional notes on each and every file, if they so want – such meta-information about files can be very useful to help others working on those files.
  
-  * The coordination server of //Git Winch// only stores the file-paths and that too only for those files your office is working on. Not the data itself. This is for coordinating the work and reducing chances of clashes.+  * The coordination server of //Git Winch// only stores the file-paths and that too only for those files your office is working on. Not the data itself. This is for coordinating the work and reducing chances of clashes. In short, we never intrude into your privacy.
    
   * The owner/manager creates his/her own repository at one of the compatible Git Hosts: Github or Gitlab or Gitea ... As both Gitlab and Gitea allows self-hosting too, this gives you the maximum flexibility on where the central repositories of the office are to be located. Gitlab and Github allow free Git hosting.* You can also choose to host Gitlab or Gitea on your own servers too, if you so want, for maximum privacy and independence.   * The owner/manager creates his/her own repository at one of the compatible Git Hosts: Github or Gitlab or Gitea ... As both Gitlab and Gitea allows self-hosting too, this gives you the maximum flexibility on where the central repositories of the office are to be located. Gitlab and Github allow free Git hosting.* You can also choose to host Gitlab or Gitea on your own servers too, if you so want, for maximum privacy and independence.
Line 21: Line 23:
   * Your files are not only backed up at the Git Host of your choice, but you and your office can //revert// back to previous version of the same files. This is especially a major advantage for creative offices such as graphic artists, marketing agencies, architects...    * Your files are not only backed up at the Git Host of your choice, but you and your office can //revert// back to previous version of the same files. This is especially a major advantage for creative offices such as graphic artists, marketing agencies, architects... 
  
-  * The office workers need not have any account at the Git Host. Only the owner takes such an account. In fact even the owner just sets up a special Personal Access Token, on the host and nothing much else there. The advantage of using Github/Gitea/Gitlab is available to you without the complexity. Regular office workers need not have any knowledge about the host. This also becomes very useful if you plan to delegate work to temporary workers too.+  * The office workers need not have any account at the Git Host. Only the owner takes such an account. In fact even the owner just sets up a special Personal Access Token (PAT), on the chosen Git host and nothing much else there. The advantage of using //Git Winch// to manage Github/Gitea/Gitlab is that, those services are available to you without the complexity. Regular office workers need not have any knowledge about the Git host system. This also becomes very useful if you plan to delegate work to temporary workers too. 
 + 
 +  * If the owner is too busy, all he/she has to do is to delegate the rest of the setting up work to a manager. The owner does NOT share the PAT but instead an encrypted version can be shared with the said manager to do the work on behalf of the owner. This ensures that the PAT never goes astray and yet, work can be delegated to the said manager. You can have any number of managers too.
  
   * The system allows owners/managers to distribute work to the office-workers on a //need-to-know// basis. So office workers need not become member of each and every repository of the office. All that membership is in the hands of the owners/managers.   * The system allows owners/managers to distribute work to the office-workers on a //need-to-know// basis. So office workers need not become member of each and every repository of the office. All that membership is in the hands of the owners/managers.
Line 27: Line 31:
   * The owner/manager creates deploy-keys and then passes on the private key to the appropriate member who is allowed to work on the files of a repository. But if a person wants to generate his/her own keys; that also can be done. In that case, after creating the keys, the said member has to pass on the public key to the owner/manager who will then use that key to enroll the person as a member of the said repository.   * The owner/manager creates deploy-keys and then passes on the private key to the appropriate member who is allowed to work on the files of a repository. But if a person wants to generate his/her own keys; that also can be done. In that case, after creating the keys, the said member has to pass on the public key to the owner/manager who will then use that key to enroll the person as a member of the said repository.
  
-  * The managers of such members are also happy as they can see the list of filenames that are being currently worked upon… and by whom. They also can do what we call a //hashtag analysis//... That's [[hashtagvalues?do=export_xhtml|explained here.]]+  * The managers of such members are also happy as they can see the list of filenames that are being currently worked upon… and by whom. 
 + 
 +  * Owners/managers also can do what we call a //hashtag analysis//... That's [[hashtagvalues?do=export_xhtml|explained here.]] This can be used to //quantize// the kind and amount of work that is being done in the office.
  
   * Owner/manager can download session logs and can see the IP address and geo-location of each members, their login and logout, and file-handling actions. This is very useful for taking attendance in the office, and getting to know the amount and kind of work each member is doing.   * Owner/manager can download session logs and can see the IP address and geo-location of each members, their login and logout, and file-handling actions. This is very useful for taking attendance in the office, and getting to know the amount and kind of work each member is doing.
Line 36: Line 42:
  
   * If by some chance you need to do some advanced Git commands, you can easily drop into a console window, and carry out the actions using command-line Git. You can also use the popular //TortoiseGit// if you so choose, provided the repository was cloned using the //Git Winch Client Application.//   * If by some chance you need to do some advanced Git commands, you can easily drop into a console window, and carry out the actions using command-line Git. You can also use the popular //TortoiseGit// if you so choose, provided the repository was cloned using the //Git Winch Client Application.//
 +
 +  * ALL commits pushed into your Git host are //signed.// That means there is NO chance that anyone can forge someone else's name into a commit and then push it. All signatures are verifiable by anyone who has access to that repository. Even if the original author is no longer part of the office, that person's signatures in the commits he/she made are still verifiable.
  
  
-* NOTE: Gitlab and Github are external services. We are not associated with them. Use their free services with your eyes open i.e. read all their terms of service and privacy policy.+*<sup>**NOTE:** Gitlab and Github are external services. We are not associated with them. Use their services (whether free or paid) with your eyes open i.e. read all their terms of service and privacy policy.</sup>
  
 ----- -----
 [[/concepts?do=export_xhtml | Learn the concepts]] | [[/topics?do=export_xhtml | Table of Contents]] [[/concepts?do=export_xhtml | Learn the concepts]] | [[/topics?do=export_xhtml | Table of Contents]]
advantages.1749660792.txt.gz · Last modified: by admin

Page Tools