Skip to content

Latest commit

 

History

History
206 lines (96 loc) · 7.55 KB

tidepool_evalutation.md

File metadata and controls

206 lines (96 loc) · 7.55 KB

Project Evaluation Activity

Project Name: Tidepool (Blip)


Finding info about contributing on the website.

In the following section you should only enter the information that you found on the project website. Some of the answers will be impossible to find, others may be very hard to find. Do not google for answers.

Project website: Website

What is the purpose of the project:

It is an interoperable automated insulin dosing app to make diabetes data more accessible, actionable, and meaningful for people with diabetes, their care teams, and researchers. Blip is the internal name for Tidepool for Web, a tool for seeing diabetes data in one place.

How easy was it to find information about contributing on the website?

It was easying finding how to setup the development environment but not so much what could be contributed.

Contributing instructions: Here

URL for the code repository: Code repository

Bug/Issue tracker link: Bug/Issue tracker

Mailing list: No mailing list

Chat channel: No chat channel outside of issues.

Other communication channels:


Finding info at the project repository and bug/issue tracker.

License: License

Is it OSI approved license: Yes

Programming Language(s): JavaScript, Less, Dockerfile, Shell, CSS, EJS

URL for contributing instructions: No contributing instructions but there is a development instruction

Are the contributing instructions clear? Somewhat. There are many steps.

URL for code of conduct / community norms / community guildelines: No community guidelines.

URL for instructions for users to download and install the package: here.

Are these instructions clear? Do you think they would be easy to follow? At a glance, yes but isn't very detailed for each step in the event something goes wrong.

URL for instructions for how to install development environment: here

Are these instruction clear? Do you think they would be easy to follow? Somewhat, there are many steps.

Number of contributors: 38 contributors

Usernames of three contributors with largest number of commits; for each of them list the link to their latest commit:

  1. [clintonium-119] (3421 commits) - Their Latest Commit
  2. [jebeck] (792 commits) - Their Latest Commit
  3. [krystophv] (666 commits) - Their Latest Commit

Number of commits: 9115 commits

Latest commit

  • link to the commit: Latest commit

  • who made that commit: clintonium-119

  • what type of work was commited? (was it a fix to a bug, implementation of a new feature, ...) Pull request merge

Issues

  • how many open issues are there: 12 Open Issues

    • url for the last issue created: Last issue created

    • how many users discuss the issue: 1 person

    • when was the issue reported: May 31, 2022

  • how many closed issues are there: 32 closed issues

    • url for the last issue closed: Last issue closed
    • how many users discussed the issue: 1 people
    • when was the issue reported: Mar 31, 2020
    • when was the issue closed: Mar 31, 2020
  • how active is the discussion on the issues: Not active

  • are there issues marked "good for newbies", "beginner" or some other indicators that imply that they are good for beginner contributors: No

    • how many of such issues are there? There were no such labels or issues.

    • look at a few of them, do they look beginner friendly? There were no such labels or issues.

  • are there issues marked "documentation" or some other indicators that imply that they are documentation (user or developer specific): No

    • how many of such issues are there? There were no such labels or issues.

    • look at a few of them, do you think you could submit a fix? There were no such labels or issues.

Pull requests

  • how many open pull requests are there: 10 pull requests

  • how many closed pull requests are there: 1285

    • url for the last pull request closed: Last Pull Request closed

    • how many users discussed the pull request: 2 users

    • when was the pull request made: Last week as of 3/3/2024

    • when was the pull request closed: 4 days ago as of 3/3/2024

  • do maintainers respond quickly to pull requests when they are opened? No, rarely.

Development Environment

Each member of your group should attempt to configure the development environemnt for this project. Complete the following for each member:

Name: Brandon Chen

Operating system: Windows 11

Was the installation successful? (if not, explain what went wrong and what you did to try to remedy it) Installation was successful but running locally is another problem. There are many steps for running it locally which requires docker, redux dev tools, getting past email verification, etc.

How long did the whole process take? About 15-30 mins for installation. Did not try running it locally but would take much longer.


Summary assesment

How friendly is this project for beginner contributors?

No friendly for beginner contributors with not much discussion and activeness.

Do the maintainers respond helpfully to questions in issues?

Maintainers are not as active as other ones I have seen in other projects.

Are people friendly in the issues, discussion forum, and chat (for example, IRC or Slack)?

Yes

Do pull requests get reviewed?

Yes? It seems to be mostly just the maintainer opening and closing pull requests.

Do maintainers thank people for their contributions?

Yes

Are there special skills required to contribute to the project? If so, what are they?

No

Are there any special hardware/software requirements to be able to contribute to the project? If so, what are they?

Requires docker, redux dev tools, and Kitematic to run locally.