bibledit-gtk-data 4.9-1 / usr / share / bibledit-gtk / site / gtk / tutorials / collaboration.html

This file is indexed.

/usr/share/bibledit-gtk/site/gtk/tutorials/collaboration.html is in bibledit-gtk-data 4.9-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below. 

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <link href="../../bibledit.css" rel="stylesheet" type="text/css" /><!-- 

Copyright (©) 2003-2011 Teus Benschop and Contributors to the Wiki.

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts.  A copy of the license is included in the section entitled "GNU
Free Documentation License" in the file FDL.

-->
    <title></title>
  </head>
  <body>
    <div id="menu">
      <ul>
        <li>
          <a href="../../home.html">1 Bibledit</a>
        </li>
        <li>
          <a href="../tutorials.html">Tutorials</a>
        </li>
        <li style="list-style: none; display: inline">
          <hr />
        </li>
        <li>
          <a href="bibledit-for-windows-tutorial.html">Bibledit for Windows Tutorial</a>
        </li>
        <li>
          <a href="checking.html">Checking</a>
        </li>
        <li>Collaboration
          <ul>
            <li>
              <a href="collaboration/1intro.html">1. Introduction</a>
            </li>
            <li>
              <a href="collaboration/2reposetup.html">2. Repository setup</a>
            </li>
            <li>
              <a href="collaboration/3reposinit.html">3. Repository initialization</a>
            </li>
            <li>
              <a href="collaboration/4conflictres.html">4. Conflict resolution</a>
            </li>
          </ul>
        </li>
        <li>
          <a href="3-editing.html">Editing</a>
        </li>
        <li>
          <a href="keyterms-tutorial.html">Keyterms</a>
        </li>
        <li>
          <a href="merge-tutorial.html">Merging</a>
        </li>
        <li>
          <a href="navigation.html">Navigation</a>
        </li>
        <li>
          <a href="notes.html">Notes</a>
        </li>
        <li>
          <a href="planning.html">Planning</a>
        </li>
        <li>
          <a href="printing.html">Printing</a>
        </li>
        <li>
          <a href="project.html">Project</a>
        </li>
        <li>
          <a href="questions.html">Questions</a>
        </li>
        <li>
          <a href="references.html">References</a>
        </li>
        <li>
          <a href="related-verses.html">Related verses</a>
        </li>
        <li>
          <a href="revert.html">Revert</a>
        </li>
        <li>
          <a href="searching.html">Searching</a>
        </li>
        <li>
          <a href="spelling.html">Spelling</a>
        </li>
        <li>
          <a href="styles.html">Styles</a>
        </li>
      </ul>
    </div>
    <div id="content">
      <h1>
        Collaboration
      </h1>
      <h3>
        <a name="TOC-Setup" href="" id="TOC-Setup"></a>Setup
      </h3>
      <p>
        It is recommended to read the <a href="https://sites.google.com/site/bibledit/gtk/tutorials/collaboration/1intro">brief introduction</a> to the system.
      </p>
      <p>
        The central part to collaboration is the repository. The system administrator will have <a href="https://sites.google.com/site/bibledit/gtk/tutorials/collaboration/2reposetup">set the repository up</a>, will have <a href="https://sites.google.com/site/bibledit/gtk/tutorials/collaboration/3reposinit">initialized it</a>, and issued its URL. If the repository is a secure one, <a href="https://sites.google.com/site/bibledit/gtk/tutorials/collaboration/2reposetup/secure-shell-keys-setup">set up the secure shell keys</a> to access it.
      </p>
      <p>
        The repository is now ready for use. It remains to add users who make use of this repository and share their data through it.
      </p>
      <p>
        In this tutorial it will be user Jim. In Bibledit, Jim opens the project he wishes to share with others, or he creates a new project. He goes to menu <a href="https://sites.google.com/site/bibledit/gtk/reference/menu/menu-preferences/dialog-remote-repository">Preferences / Remote repository</a>. and sets everything up. Jim can now work on Bibledit as before, and his data will be automatically updated in the repository.
      </p>
      <h3>
        <a name="collaborating" href="" id="collaborating"></a>Collaborating
      </h3>
      <p>
        Now we come to the purpose of everything, which is working together on one project.
      </p>
      <p>
        This collaboration is very simple: Just work on your data as you did before. At times when you´d like to share your work with others, or when you'd like to see work done by others, choose menu File / Project / Send-Receive.&nbsp;Bibledit cares for everything, and everything will be updated and shared automatically.
      </p>
      <h3>
        <a name="safety" href="" id="safety"></a>Safety
      </h3>
      <p>
        Suppose that two or more people collaborate on one project. One of them is a bad typist. He makes many errors. The bad typist has the potential the harm or destroy the project's data. If he makes serious mistakes in his own data, then the collaboration mechanism will propage his mistakes to the other members of the team. This is not a desirable situation.
      </p>
      <p>
        Bibledit has a solution for this situation. You can use two mechanisms of Bibledit simultaneously.
      </p>
      <p>
        1. Collaboration through the network or the USB stick.
      </p>
      <p>
        2. <a href="https://sites.google.com/site/bibledit/gtk/tutorials/merge-tutorial">Merging changes</a>.
      </p>
      <p>
        This is how to do it:
      </p>
      <p>
        1. The experienced person has project "master" that has the master copy of the Bible. Collaboration of the master project is switched off so that no changes can enter that project by mistake.
      </p>
      <p>
        2. The experienced person has project "messy" that initially is a copy of the master project. Collaboration is switched on.
      </p>
      <p>
        3. The unexperienced typist has project "messy" too, with collaboration switched on.
      </p>
      <p>
        4. The unexperienced typist makes changes in project "messy", and through collaboration these changes go into project "messy" of the experienced typist too. This all goes automatic.
      </p>
      <p>
        5. Once in a while the experienced person goes to the Merge tool. He opens project "master" and project "messy", reviews the changes as proposed in project "messy", makes any edits he likes, takes out any mistakes he does not like, and then finally merges the changes from "messy" into "master". This is done chapter by chapter. Once the merge is done, project "master" and "messy" are identical again in that particular chapter.
      </p>
      <p>
        6. Any changes entered or not entered propagate to the unexperienced typist again through the collaboration. If the unexperienced typist made a big mess in a certain chapter, through the collaboration this mess is cleared up again on his computer.
      </p>
      <h3>
        <a name="notes" href="" id="notes"></a>Notes
      </h3>
      <p>
        - The collaboration system can conveniently be used for automatic backup.
      </p>
      <p>
        - Collaboration of two projects on the same computer is possible if those projects have the same ancestor, that is, one is created by importing all the Biblebooks exported of the other one. This can be helpful for demo purposes and to test and learn to use this tool if only one computer is available.
      </p>
      <p>
        - Sending and receiving the data of your Bible will happen automatically at intervals. Bibledit will receive any changes from the repository, and then send its own changes to that repository. To manually send and receive your Bible, use menu File / Send / receive.
      </p>
      <p>
        - Using collaboration with merging data has advantages in the following situation: Think of the situation that a bad typist is out in the bush, and comes to town with his stick, and has little time for the master person to merge while he waits. So just plugging in he stick, a quick automatic merge, and away he goes again. Then if the master person has some time in the days or weeks following, he can then carefully go through the messy project, and merge it with the master project, taking his time for it, and doing an accurate job.
      </p>
      <p>
        - There is not much need to maintain the git repository since Bibledit does run maintenance on it at regular times. But if you really like to compress the repository well, you can run "git gc --aggressive" in the repository. Note that Bibledit already runs "git gc" at regular times.
      </p>
      <p>
        - If two or more users were to work on the same chapter at the same time, this would pose a problem for Bibledit. This type of collaboration is not supported. People should work on different chapters, or on the same chapters, but not simultaneously. Then the merging of the changes will work well.<br />
      </p>
    </div>
  </body>
</html>

APT Browse - Built by Thomas Orozco.