... | ... | @@ -9,10 +9,11 @@ General Idea |
|
|
|
|
|
Workflow for CE coordinators
|
|
|
----------------------------
|
|
|
**Note:** CE development does not require an internal account.
|
|
|
|
|
|
Forking the main repository
|
|
|
* (create an account)
|
|
|
* (contact SW coordinators to get CE maintainer status
|
|
|
* (contact SW coordinators to get CE maintainer status)
|
|
|
* Log in into your account
|
|
|
* Depending on whether the CE uses BMS or VTM as as basis go to
|
|
|
* the [jvet/VVCSoftware_VTM](https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM) repository page for VTM
|
... | ... | @@ -36,6 +37,11 @@ Adding users: |
|
|
Workflow for CE members (writing)
|
|
|
---------------------------------
|
|
|
|
|
|
If you don't have a GitLab account, register at https://vcgit.hhi.fraunhofer.de
|
|
|
For more details on registration see [VVC software development workflow](VVC-Software-Development-Workflow)
|
|
|
|
|
|
**Note:** CE development does not require an internal account.
|
|
|
|
|
|
If you did not use git before, set up your work environment using the **git config** tool using your name and email address.
|
|
|
|
|
|
```bash
|
... | ... | @@ -59,9 +65,11 @@ git clone <url> [target_path] |
|
|
|
|
|
with the ```<url>``` of the repository that can be found in the web page of your CE repository
|
|
|
|
|
|
The URL can be found on the project page of the CE:
|
|
|
|
|
|
![04-url](/uploads/6dd857de635b5123bec72e44fb96d4f1/04-url.png)
|
|
|
|
|
|
```target_path``` is optional. If you are working on multiple CEs, it may be helpful to clone them into different directories names after the CE, e.g. ```VVCSoftware_BMS_CE1```
|
|
|
```target_path``` is an optional parameter. If you are working on multiple CEs, it may be helpful to clone them into different directories names after the CE, e.g. *VVCSoftware_BMS_CE1*
|
|
|
|
|
|
**Note:** The CE repository should have something like "JVET-?-CE?" in it's URL. Make sure to clone the right CE.
|
|
|
|
... | ... | |