NEAR - 9. Developer Activity

    Developer Activity

    With Electric Capital’s release of its annual report on developer activity, the topic of “developers” is a hot topic across crypto.

    Produce a rich analysis of NEAR developer activity, using metrics and definitions of your choice to answer the questions:

    • How many developers are active on NEAR?
    • How active are they?
    • How this has changed over time? \n

    Feel free to reference (and cite) the Electric Capital report to provide background, but the vast majority of your dashboard should be original work that provides a supplemental view to that report.

    Introduction

    Electric Capital is a crypto asset management company that recently released its annual report on developer activity in the cryptocurrency industry. The report provides insights into the number of developers working on various blockchain projects and their activity levels. It also highlights trends in developer activity, such as which projects are seeing an increase or decrease in developer involvement. The report has generated a lot of discussion and interest in the crypto community as it provides valuable insights into the development and growth of various blockchain projects.

    • Repository is a place where software code is stored and managed. It is a location where developers can access, share, and work on the code collaboratively.
    • Pull request is a feature provided by some version control systems, such as Git, to allow developers to request that changes they have made to a repository be pulled (or merged) into the main branch of the repository by the repository's maintainers.
    • Developer is a person who writes and tests computer code. They can be involved in the development of software, web applications, mobile apps, and other types of technology.
    • Contract is a legally binding agreement between two or more parties. In the context of blockchain, smart contract refers to self-executing contracts with the terms of the agreement written directly into code. This enables the automation of contract execution, and eliminates the need for intermediaries.
    • GitHub is a web-based platform for software development that provides a community for developers to collaborate, share and learn from each other. It is built on top of Git and offers features such as pull requests, issue tracking, and code review for open-source and collaborative software development. It also allows developers to store and manage their code in a central location, known as a repository.

    Method

    In the current dashboard I tried to track the NEAR ecosystem developing metrics.

    For all developer-level action, I monitor near.beta.github_activity table which includes:

    > * The total number of new issues opened for review. > * Count of resolved pull requests in total and over time. > * Fresh Code Entering the Ecosystem by count of Repository in total and over time. > * Continually-present coders by count the authors in total and over time. > * Leaders in the number of repositories or pull requests in total and over time.


    Additionally, this investigation seeks out recently deployed contracts by searching the near.core.fact_actions_events table for action name = "DeployContract."

    From a Development standpoint, this indicator shows us whether or not new DApps are being created for the protocol.


    This dashboard is set to a monthly frequency, but you can change it to your preferred timeframe after logging in to FS. 

    Analysis

    ✍🏻 Conclusion

    In conclusion, the data provided in the NEAR Developer Activity Dashboard suggests that the NEAR ecosystem is active and growing, with a large number of developers contributing to the development of the ecosystem. The high number of pull requests and closed pull requests indicate a high level of developer activity within the ecosystem. Additionally, the data highlights the activity of individual developers, such as "bowenwang1996", who has the most number of open pull requests. The spikes in new contract deployments in December 2021, April 2022, and July 2022 also suggest a high level of development activity during those months. The consistent increase in the number of developers joining the ecosystem starting in August 2021 also suggests strong growth in the NEAR community. Overall, the NEAR Developer Activity Dashboard provides a valuable tool for understanding the state and health of the NEAR ecosystem and making data-driven decisions.

    Hey there 👋!

    Firstly, I appreciate you sticking with it until the conclusion.

    I'm Hamed, a civil engineering Ph.D.

    student interested in data analysis.

    I've made many similar dashboards and visualizations since I started at Flipside in January.

    Please take a look at my various contact details and let me know what you think.

    About:

    Loading...
    Loading...
    Loading...
    Loading...
    Loading...

    :mag_right: Findings:

    The above graphics provided an overview of NEAR developing metrics such as:

    Total active developers: 2480

    Total count of repositories: 829

    Total contracts: 58.56K

    Also, it shows that December was the most volatile month for new repositories; that was the peak of an upward trend that began in 2020.


    :detective: Author Association Overview

    Author association in developing refers to the relationship between the developers who are making contributions to a project. In the context of a Github repository, it can refer to the association of developers with the repository, for example, if they are the owners or collaborators of the repository. The term "author association" can also refer to how developers are associated with the code they are contributing, such as if they are making changes to their own code or code written by other developers. Overall, author association is a way to track and understand the different roles and relationships that developers have within a project, and how they are interacting with the codebase.

    :mag_right: Findings:

    Charts and graphs in this section illustrate the rising popularity of author-related indicators throughout time.

    The contributors are the most engaged on the NEAR ecosystem, as evidenced by the number of pull requests, repos, and active developers they have contributed to.

    The owners were the least active demographic.

    Together, 2480 active developers had submitted 52.4K pull requests across 829 repositories.

    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...

    :mag_right: Findings:

    Over 4K repository have been merged and closed by over 20K pull request.

    The following charts represent the active developer, pull request and repositories based on base reference name over time.

    Loading...
    Loading...

    :gear:State Overview

    In the context of a Github repository, the state of a merge or closed repository refers to the status of pull requests (PRs) that have been submitted to the repository. A pull request is a request made by a developer to merge their code changes into the main codebase of a repository. When a pull request is opened, it is in a "pending" state and is open for review by other developers.

    When the pull request is accepted by the repository owner or maintainer, it is considered to be "merged" into the main codebase. At this point, the pull request is closed and the changes are incorporated into the repository. A closed repository is one that is no longer open for new contributions.

    On the other hand, if the pull request is not accepted, it will be closed without merging the changes. The repository maintainer or the author of the request can give a reason for why the request was closed. In this case, the repository will remain open for new contributions.

    Overall, the state of merge or closed repository gives an idea about the activity, the acceptance rate and the efficiency of the development process.

    Activity breakdown

    The two most active NEAR Github developers are contributors and members, which is one of the important observations from the dashboard. This shows how crucial these two communities are for the expansion and improvement of the NEAR ecology. In addition, the data shows that over half of the NEAR Github's active users have just been there for a month and have taken part in two or fewer actions. There appears to be a big number of infrequent contributors, but only a few of people who are continuously involved in the codebase. This data can be utilized to zero down on the most active developers and provide them with exclusive resources and attention.

    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...

    :1st_place_medal: Top 10 “Creator & Closer” Active Developers Over Time

    :hourglass_flowing_sand: Still Open Repositories

    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...

    :1st_place_medal: Top 10 “Created & Closed” Repositories

    :mag_right: Findings:

    • nearcore is the first closed repository based on pull request and active developer count over time that followed by creat-near-app and near wallet with 21, 11, 28 & 11.4%, respectively.
    • \

    :mag_right: Findings:

    The graphs in this section show the distribution of repositories by pull request and active developers.

    as can be seen the most of repos have had less than 5 active developers and pull requests.

    Overall, the count of developers, pull requests and repositories on still open repositories have increased over time.

    :mag_right: Findings:

    As can be seen the count of pull request of active developers increased over time by top 10 developers. and peaked at over 500 in December and February for repository count.

    The repository count decreased after peaking in February.

    This pattern was repeated for creator active developers, too.

    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    db_img