i have gone through fork and try to learn this module. really great work
i have gone through https://github.com/facebook/react-native/pulse project and really glad to find below data
I selected rShetty/awesome-podcasts as I have been meaning to start using more podcasts as a source of information. This project appears to be in somewhat of a maintenance mode with high activity in April and smaller volume of changes during the following months, but there are open pull requests, 94 listed contributors, 5,706 stars and 296 forks on the project which would indicate it is an active project.
I choose F# compiler, I language that I love.
An example of how the use of the open source paradigm can also benefit big corporation like Microsoft and how it was right to open to this approach (if you told me in the 90s…)
a lot of contribution both from ms emploieed than from free lancher
even if this had been a group of students … I would have said that, everyone has participated but, they have exploited a lot of the work of a few !
- 31 active pull requests between Jan 28, 2019 - Feb 4, 2019
- 7 authors have pushed 55 commits to master and 61 commits to all branches
- Commit at least once a day
4 There are 49 Forks and 40 Stars
Thank you for your slide and exercise.
- Find an active open source project.
- Point to 2 pieces of evidence that the project is active.
In the past month there are 8 new issues and 6 closed. Not many, but alive.
We can see there was many commits in master on 2013, which declined over the
years, but never stopped.
4? Reflect on how you might use these insights to assess collaboration in group work.
Alive and group work are not the same…
We can see that there are opened 500 issues (oldest from 2012) and opened 71
pull requests (oldest from 2013). This suggests that while the project might be
alive, they don’t have anyone to organize the community properly, e.g. close
old tickets (accept or reject).
I chose Scala Native with 3 pull requests merged in the last 24 hours and 767 pull requests closed overall (as of 2/6) it seems to be a very active project.
Under insights we can see the vast amount of work is being contributed by two people though many people have made contributions.
The pulse of the project shows recent (I’ve extended out to 1 month) non-pull request commits and who committed them.
When reflecting on how to use this to assess group work, the quantity of commits, the timing of commits and the number of lines of code added and deleted can all help provide an overview of how the group was working on the project.
Find an active open source project.
I looked at this project: https://github.com/home-assistant/home-assistant
Point to 2 pieces of evidence that the project is active.
The project releases a couple of times per week (last release was yesterday)
These pieces of evidence can be:
- How quickly pull requests are reviewed
They have over 12k pull request closed, oldest pull request is from oct 2018, but on the first page all pull request are new and handled quite fast
- Data in Insights
There you see that the close quite a lot tickets per week and also that the merge pull request regularly.
- Number of forks or stars
Currently over 21k stars and 6k forks
- Some other metric
The contribution stats are quite interested. There you see that the project is still growing.
The active open source project I found is ecl-ml a machine learning library for big data processing. From the insights tab, the visualization shows an active contribution to master. The commits insights tab shows that the project is still being worked on though not actively. The project has 849 commits and 24 contributors. The contributors insights tab show who is actively contributing to a group work and the commits insights shows how consistent the project is being worked on.
As a vim user, I looked at Neovim project (https://github.com/neovim/neovim). Neovim project is very active (some updates a day ago) with more than 12k commits.
Reflection: I can use these metrics to evaluate the assignments. For example, knowing the time the students started to do the assignment and how dedicated they were (a commit by two or three days) is important to measure if they really have had difficulties and have tried to solve a problem before asking for help.
Let’s take a look at Kubernetes repo https://github.com/kubernetes/kubernetes:
from the looks of it, this is a pretty popular repo. it has over 70000 commits and 2000 contributors.
Now let’s look at the insights page:
We have over 100 pull requests merged and proposed in one week (That’s huge!).
Now the commits page:
This is a project that was started years ago (at least 6-7 yrs) and it has commits which were made minutes ago. Granted most of those are made by a bot, but still counts.
Now, using the same strategy in Classroom scenario, we can assess group collaboration with Commit history/activity, Contributors section in insights page and Pull request activity (some students act as scrum masters where their role is to keep the project workflow smooth).
I selected Blynk-Server for easy to build IoT mobile-hardware connected applications.
First Metric : Commits and Contributors
As shown in the below image, more than 4k commits has been issued showing the massive activity of the project. Also contributors are over 10 persons.
Second Metric : Resolved issues
Dates of closed issues are close meaning project is still active and improving.
Third Metric : Latest release date
Latest release was 5 days ago meaning it is still active.
On courses, the more updates, contributors willing to improve it and solving issues is tackled, the more success of the course.
- 21 pull requests closed in last 18 days
- 3/4 contributors committed to repo in the last week
You can easily tell from the insights how active and involved students are in the development process
- plenty of stars and forks
- recent commits and PRs merged
For me: a lot of issues but also a lot of PRs created/merged. As stats: 41 PRs merged by 25 people in the last week - perfect example of team work
For students: really helpful examples of commit message, PR discussions and flow to develop as team
This open sources project is still active due to the following facts
- The total number of fork and star is highly impressive
- Within a period of 1 week, there is over 100 pull request merged and over 100 is pull request are awaiting review before been merged.