From 29607f138f5507a4aaf2f41f289c2718c5cefcc1 Mon Sep 17 00:00:00 2001 From: 315haoge <1452766901@qq.com> Date: Thu, 3 Dec 2020 15:38:01 +0900 Subject: [PATCH] Update mini-report.md --- mini-report.md | 61 +++++--------------------------------------------- 1 file changed, 5 insertions(+), 56 deletions(-) diff --git a/mini-report.md b/mini-report.md index 4de4d96..9979b91 100644 --- a/mini-report.md +++ b/mini-report.md @@ -1,58 +1,7 @@ ------------ -# 2011411 -## repo link: https://github.com/mailtoy/AbstractBuilder-2011411 -## Experience to maintain repo -Maintaining a repository is a good thing so that the developer's repository are further modified and developed. But it quite messy when the changes have to be checked and there are also many developers involved. -## Experience to review PRs -I found that if I had a late check for pull requests it would cause other people who came to fix it at the same point to reconfigure and I need to fix the conflicts. Exercises for the class is small enough to be easily modified, but if it's a large-scale, it might take a lot of time. -## Lessons learnt -Learn how to fork to help edit or update other developers' work. Made me realize that maintain a repository is important in social interaction. +# Student Id: 2011302 +## repo link: https://github.com/315haoge/chizihao/pulls +## Experience to maintain repo: The second lecture is very important for experience. It is useful to every developer to use Git and make programming easier. +## Experience to review PRs: To know everyone's sentiment correctly. The proficiency is important for developers. +## Lessons learnt: Next time, I will continue to use Git and hope to help more classmates to learn how to use it. It is convenient for us to our research. Programming is an interesting thing for me. My current research is related to SLAM, programming abaility is essential for me and I will continue to make better code for it. And thanks for your lecture. ------------- -# Student Id -## repo link: -https://github.com/aommoaGitHub/AbstractBuilder_Aom -## Experience to maintain repo: -It is hard to maintain the repository with a lot of people and a lot of contributors. A lot of contributors come with a lot of pull requests that means the repository's owner needs to check a lot of changes file and might have to discuss with these contributors before merge to the main branch. -## Experience to review PRs: -From the example in the class, each pull request doesn't change much so I don't feel much hard for reviewing the pull request. On the other hand for the big repositories, there will be a lot of changes in each pull request that why many repositories have rules for pull requests. - -## Lessons learnt: -This is my first time doing the pull request so It was opened my world about how and steps to become a contributor. And the class let me practice so that It makes me more clearly and also discuss the pro or con of managing/maintaining systems (as that pull request need to be reviewed first and also the doing steps on Github) - -------------- -======= -2011317 -## repo link: -https://github.com/bloodb4th/AbstractBuilder-2011317 -## Experience to maintain repo -The task is very time consuming if the one who try to submit PR doean't follow some convention. Tools such as GitKraken can greatly help to maintain many branches that can't be seen at GitHub. -## Experience to review PRs -In my case, I try to make sure that my PR is not conflicting with any other collaborators. If you have a conflict in your PR, the maintainer usually don't have enough time or patience to take a look at your PR. -## Lessons learnt -Tools and Convention can help collaborator and maintainer to achieve better Quality of Life. Using Edit Tools in GitHub usually can introducce an unseen problem. -======= - -# Student Id 2011017 -## repo link: https://github.com/AyanoIkegami/AbstractBuilder-2011017 -## Experience to maintain repo -It is hard to manage repository for me because there are many pull requests and sometimes it occurs confliction. -Therefore there are not good pull requests like the negative sentence while I want to get positive sentence. -## Experience to review PRs -I feel review is important because some pull requests are not good for me. -If I had merged everything, it would have been messed up. -## Lessons learnt -It is difficult to manage the repository which can send pull request from many people. -I want to check some issue and whether there are same pull requests already. -I think it is more complex in OSS repository case. -I wonder why they can managed OSS repositories. - -# Student Id 2011409 -## repo link: https://github.com/NoppadolAssava/AbstractBuilder_2011409 -## Experience to maintain repo -It is quite interesting to keep merging while managing the conflict. Most of the time I have to fix the conflict in merging by myself (some people edit the same part of the abstract). - -## Experience to review PRs -Many people keep making pull request with a negative sentiment although my goal is to get the positive sentiment in abstract. From this, I know that the direction of the project should be clearly define in the repo. - -## Lessons learnt -Although this class is just the mock-up, I feel that it is quite difficult to find people to make the pull request for my project. I think when I make my own real project I should keep to contribution.MD simple and easy to read so it can attract more people to contribute in.