This lesson shows you the way in which your Repository should be arranged.
|Expected duration||40 minutes|
|Objective||To give guidelines on how the GitLab repository should be arranged|
Your repo is a extension of you. So, treat it like it is something important. Keep it up to date and please follow the guidelines that we will give you.
Creating a Group
The first thing to do is to create a GitLab account, if you don't have one yet.
When you login in to gitlab you will be redirected to your projects page. Then, click on the group tab on the top space of the page to go to your groups page.
Here you will create a group for all of your teammates. You just have to do this one time per group. Please do not create a group for each of your teammates.
A group is like a filesystem folder, but for repositories. It is where you will create all the repos for this class.
The group path has to be ISIS3510_202020_TeamN (N been the number of your team). The group name should be the same. And, it has to include in the description, the name of all the members of the group, with their respective institutional codes and emails (name - code: email) and the problems you chose to solve. You can choose any visibility level, but we recommend to leave it in private for the moment.
Then, click on new project to create a repository. You have to create 3 projects. One for each code project (Android and iOS, Android and Kotlin) and one for your team wiki, in which your team will upload future documents and also keep and update the product backlog.
The repositories have to be named properly. Each one with the name of the project that would be stored inside. If your team is going to do iOS and Android, the repositories should be named as you see in the following image:
If you are going to do Android and Kotlin the repository for Kotlin has to be named Kotlin.
Adding Members to the Group
Go to the Members section in the left bar. In there, write in the search bar the username of your teammates, and add them to the group. Don't forget to add our user: se4ma.uniandes.
Go to the 'Wiki' project and create a 'Home' page which has to include, the group name, the name of all the members of the group, with their respective institutional codes and emails (name - code: email) and the problems you chose to solve. Also, upload the team contract to the wiki.
Finally, create a Table of Content in which you should organize all the deliverables by Sprint:
Each Sprint must have a subdirectory (SprintX where X is the number of the sprint) and inside of it, there should be a page for each micro sprint (MSY where Y is the number of the micro sprint) as follows:
Important: If the deliverable isn't correctly named nor inside the corresponding subdirectory, it won't be graded.
Defining Milestones and Issues
Now that your team have the repositories, it is important to define the functionalities that would be implemented in the apps. To do that, go to the WIKI repository. In there, select issues at the right bar and then select milestones.
Create one milestone for this Sprint, select the start and the due date.
Then, go to labels, clicking on the left bar. And create labels that would be assign to the functionalities that will be created next. For instance, you should create labels like Android, iOS, Backend, Web, Analytics, Test, Design. Each one of the labels should have a different color and a description.
After creating all the labels, go to List in the left bar. Here you can create issues. An issue is one functionality of your application, or something that yuo have to do as part of the development of the app, for instance the design of the assets of the app is an issue. Create all the issues and remember to assign a person in charge of the issue, a milestone, the labels related to the issue and a due date.
After you have create all the issues go to Board in the left bar. Once there, select "Add default lists" to add the "To Do" and "Doing" lists.
With this, you can use the lists to keep a visual state of your development. When you are going to start working in one issue, move it to the Doing list, and when you finish doing the issue move it to the closed list.
|1.0||Sergio Yodeb Velasquez Yepes||February 28, 2018|
|2.0||Laura Natalia Bello Jimenez||February 6, 2019|