Suggest an Edit on DCS

Overview

You may suggest an edit to someone else’s work on the Door43 Content Service using the following procedure.  Keep in mind that most users will gladly receive suggestions using this process.

The process described below is called the “fork and pull request” model.  A “fork” is simply a copy of someone else’s project.  A “pull request” is a way of asking whoever you copied the project from to add your changes into their project.

Step by Step

The following procedure assumes that you have a Door43 account, if you don’t, create one by going to https://git.door43.org/user/sign_up.

Before continuing, make sure that you are signed in to DCS by going to https://git.door43.org/user/login.

Fork the Project

The first step is to find the project that you want to help.  You can search for projects by name on the Explore page, https://git.door43.org/explore/repos.  For this guide, we’ll use the English Open Bible Stories project as our example.

  1. Go to the project page, for English Open Bible Stories, go to https://git.door43.org/Door43/en_obs
  2. Click on the “Fork” button in the upper right of the page.
  3. On the “New Repository Fork” page, click on the green Fork Repository button.
  4. You are now brought to a page that is your own copy of the project.  You can tell that it is a copy because there is a “fork” icon that is next to your username and the project name in the header, like below:

Make Your Changes

Now you are ready to make your suggested changes.  For example, to suggest a change to the first story in English Open Bible Stories, follow this procedure.

  1. Verify you are on your fork on the project by looking at the username and project name in the header.
  2. Navigate to the first story by clicking on “content” and then “01.md”.
  3. Click the pencil icon that is part way down the screen, on the right.
  4. You are now in edit mode and you can make your suggested edit.
  5. When you are finished editing, scroll to the bottom of the page and find the text boxes below the “Commit Changes” header.
  6. Put a title and description of your changes into the text boxes so that the original project maintainer knows why you made the change you are suggesting.
  7. Leave the radio box selected that says “Commit directly to the master branch.” 
  8. Click on the green Commit Changes button.
  9. You may repeat steps 2-7 as many times as you need to make all of your suggested changes.

Create a Pull Request

Once your changes have been made you can now ask the original project maintainer to accept them by issuing a pull request.  Follow these steps.

  1. Verify you are on your fork on the project by looking at the username and project name in the header.
  2. Under the name of you project, click the “Pull Requests” button that has a number next to it.
  3. Now click the green “New Pull Request” button in the upper right.
  4. Scroll down on the page to verify the changes that you are suggesting.
  5. Scroll back up to the top and give your pull request a title in the title box.
  6. Fill out the description box under “Write” to provide the original maintainer a description of the changes you are suggesting.
  7. Click the green “Create Pull Request” button.

Follow Up

Once you’ve created the pull request using the above process, the original maintainer will be notified of your suggested change.  They may want to ask you some questions, which they will do by commenting on the pull request that you created.  You will receive an email with their comments.  You can go to the pull request page that you created at any time to see the comments and to see whether or not your suggestions have been incorporated.

Removing Your Fork

After your changes have been accepted by the original maintainer, you may want to delete your fork of the project to prevent confusion in the future.  Follow these steps:

  1. Verify you are on your fork on the project by looking at the username and project name in the header.
  2. Click on the “Settings” button in upper right. 
  3. Scroll to the very bottom and click the “Delete This Repository” button.
  4. In the verification pop-up:
    1. Verify the name of the repository is the project you want to delete.
    2. Type in the name of the repository as directed.
    3. Click the “Confirm Deletion” button.

MAST technician job description and what to expect.

A MAST technician will encounter a wide range of issues on a MAST. The nature of the issues will be both technical and social. Having impeccable technical skills will only get you part of the way there. You should also be aware that you will need the so-called “soft...

Post MAST-TSP Workshop

Hello all, As we are developing the materials and support that we all need. Would you please add a post here of those things that you would like to have or need to know where it is? For instance - here are the websites that will be good to remember:...

Installing MAST Apps on a tablet

Here is a video on how I install apps...not just any apps....but MAST specific apps on atablet.  I know....sounds exciting!  Well, actually it is.  The work that translators do on these tablets is life changing.  Along with the video, I have added tablet specs and an...

How to Get Help

John explains the different tools used for technical support for Bible Translation.  Email is probably the best type of support.  Just send a helpdesk ticket to [email protected]       https://www.youtube.com/watch?v=mphZwBbiuuU   Some...

Changing Server Settings

Here is documentation on how to set the WACS server up in tStudio Android. I’m thinking that this will become a popular question. Server Settings Keep the settings for the server as determined by the program. There is no need to edit any of the settings unless...

Android Install

The following apps are recommended to install and place on the front pane of an Android tablet for written and oral translation projects.  The tech only items should not appear on pane display.  

Installing SyncThing on a Windows 10 computer

Follow these simple instructions on installing SyncThing on a Windows 10 machine for MAST data collection. Notes: Install SyncTrazor

How to migrate or clone a repo on door43 to WACS

How to migrate or clone a repo on Door43 to WACS. Compare mirror and non-mirror options.

How to format Translation Notes for publishing (V-MAST)

In V-MAST, translators are given free rein to reformat the content. However, they should not reformat content destined to be published as source text. This article specifies the expected content format. Note that BTT Writer does its own formatting when translating tN,...

How to Prepare tS Translation Notes Projects for Publishing

Note: This article is one in a series of articles describing how to get a GL project ready to publish so that others can benefit from it. This article deals with Translation Notes (tN) projects created in translationStudio. A complete Bible tN project consists of...