... | ... | @@ -2,7 +2,7 @@ |
|
|
|
|
|
## TASK MANAGEMENT IN THE CONTENT AND TRANSLATIONS SUBAREA
|
|
|
|
|
|
Meetings: Fridays 11:00 am (every two weeks or when needed; they may be proposed by anyone, at least a couple of days in advance).
|
|
|
Meetings: Fridays 11:00 am.
|
|
|
|
|
|
In this sub-area it has been decided, as the in rest of the areas of the OCW, to use mainly GitLab to manage the evolution of tasks and OCP to validate and register them so they can be paid.
|
|
|
|
... | ... | @@ -87,16 +87,3 @@ IN OCP: |
|
|
|
|
|
1. One of them will take the task in GitLab. The collaboration of the other people will be mentioned in the section for comments on the corresponding task.
|
|
|
2. All of them will explain their work and the time spent in OCP trough the button "I did some work on this" |
|
|
|
|
|
|
|
|
## ANOTHER OPTION
|
|
|
|
|
|
Even if the sub-area has stated to use OCP to validate the tasks, still there is freedom for anyone to choose another option, such as VALIDATION IN GITLAB. For those who prefer to do it this way, these are the instructions:
|
|
|
|
|
|
To validate a task in GitLab instead of doing it in OCP, the doer should:
|
|
|
1. Not touch OCP at all
|
|
|
2. Indicate the time spent by writing in comments the command /spend xh, making sure that the amount appears in the right column under "Time Tracking"
|
|
|
3. Place the task in the column COMPLETED
|
|
|
4. Look for two validations from people in the communication area. The validators should write in the comments box the command: #validated
|
|
|
5. Once this is done, the task must be placed in the column OCW VALIDATED and leave it there till the task has been paid
|
|
|
6. Once paid, the doer should move the task to the column CLOSED |
|
|
\ No newline at end of file |