| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| advantages [2025/06/11 18:47] – admin | advantages [2025/06/11 19:56] (current) – admin |
|---|
| * //Git Winch// is a //loosely-coupled// minimalist user and data management system, mainly focused on small and medium size offices. That means it does not enforce rigid ways of working. Each office has enough wiggle room to develop their own working system based on top of //Git Winch.// | * //Git Winch// is a //loosely-coupled// minimalist user and data management system, mainly focused on small and medium size offices. That means it does not enforce rigid ways of working. Each office has enough wiggle room to develop their own working system based on top of //Git Winch.// |
| |
| * //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. | * //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]]. |
| |
| * 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 do other nefarious activities. We do not do anything of that sorts so you are very sure your files can never be read by us. | * 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// 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. |
| * 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. |
| | |
| * 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. | * 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. |
| |
| * 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 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. |