Skip to content

Latest commit

 

History

History
234 lines (131 loc) · 7.17 KB

astropy_evaluation_03.md

File metadata and controls

234 lines (131 loc) · 7.17 KB
Raw

Project Name: Astropy

Evaluating Person or Team: Ben Kaplan benrkaplan (github)

Project Data

  1. Project description:

    The Astropy Project is a community effort to develop a common core package for Astronomy in Python and foster an ecosystem of interoperable astronomy packages.

  1. Project website/homepage: https://www.astropy.org/index.html

  2. Project repository: https://github.com/astropy/astropy

License

  1. What is the project's license?

    Astropy is licensed under a 3-clause BSD style license. (BSD-3-Clause)

Code Base

  1. What is the primary programming language in the project?

    The project is 95.6% Python, 4.4% C and then a handful of other stuff thats irrelevant.

  2. What is the development environment?

    All that is needed is Python but having conda installed is recommended.

  3. Are there instructions for how to download, build, and install? How easy is it to find them? Do they seem easy (relatively speaking) to follow?

    There is an instructions page, it's super easy if you already have Anaconda installed and takes a whole 30 seconds after copying and pasting one command. If not, it takes about 5 minutes to get Anaconda installed.

  4. Does the project depend on external additional software modules such as database, graphics, web development, or other libraries? If so, are there clear instructions on how to install those?

    They require the following or a newer version: Python 3.6, numpy 1.16.0, and pytest 3.1.

  5. Is the code easy to understand? Browse some source code files and make a judgment based on your random sample.

    Everything I've looked at seems pretty organized and readable, its just python and they appear to follow standardized formatting.

  6. Is this a big project? If you can, find out about how many lines of code are in it, perhaps on OpenHub.

    It's huge theres 151000 lines of code according to OpenHub.

  7. Does the repository have tests? If so, are the code contributors expected to write tests for newly added code?

    Contributors are not required to write their own tests but there is a repo in the github repo for testing.

Code and Design Documentation

  1. Is there clear documentation in the code itself?

    Yes the documentation is pretty solid.

  2. Is there documentation about the design?

    There website has a whole documentation page about the design of the project.

Activity Level

  1. How many commits have been made in the past week?

    There have been 29 commits on all branches between March 1-8.

  2. When was the most recent commit?

    3 hours ago (11:44pm currently).

  3. How many issues are currently open?

    952 are open as of right now.

  4. How long do issues stay open?

    Issues appear to stay open for an average of 1-2 days.

  5. Read the conversations from some open and some closed issues. Is there active discussion on the issues?

    There is very active discussion on all the issues I've looked at.

  6. Are issues tagged as easy, hard, for beginners, etc.?

    They are not tagged on difficulty.

  7. How many issues were closed in the past six months?

    318 issues have been closed in the past six months.

  8. Is there information about how many people are maintaining the project?

    There are 324 contributors according to Github.

  9. How many contributors has the project had in the past six months?

    In the past 6 months there have been 41 contributors.

  10. How many open pull requests are there?

    There are 58 open pull requests.

  11. Do pull requests remain un-answered for a long time?

    No, they appear to be open for on average 12-36 hours.

  12. Read the conversations from some open and some closed pull requests. Is there active discussion on the pull requests?

    There is active discussion on pull requests as well.

  13. How many pull requests were opened within the past six months?

    454 pull requests have been opened in the past six months.

  14. When was the last pull request merged?

    7 hours ago.

Welcomeness and Community

  1. Is there a CONTRIBUTING document? If so, how easy to read and understand is it? Look through it and see if it is clear and thorough.

    There is a very detailed contributing document for all types of contributions that can be made and how to make them.

  2. Is there a CODE OF CONDUCT document? Does it have consequences for acts that violate it?

    Yes, however there are no consequences that I could see.

  3. Do the maintainers respond helpfully to questions in issues? Are responses generally constructive? Read the issue conversations.

    They appear to respond very constructively and respectfully.

  4. Are people friendly in the issues, discussion forum, and chat?

    Yes everyone is friendly.

  5. Do maintainers thank people for their contributions?

    Yes, they appear to the majority of the time.

Development Environment Installation

Install the development environment for the project on your system. Describe the process that you needed to follow:

  1. how involved was the process?

    Borderline zero involvement, super easy.

  2. how long it take you?

    I already had Anaconda installed so it took about thirty seconds start to finish.

  3. did you need to install additional packages or libraries?

    No

  4. were you able to build the code following the instructions?

    Yes

  5. did you need to look for additional help in installing the environment?

    No

  6. any other comments?

    No other comments honestly.

Summary

  1. Do you think this is a project to which it would be possible to contribute in the course of a few weeks before the end of this semester?

    Yes I think that would be possible.

  2. Would you be interested in contributing to this particular project?

    I'm not super stoked on the idea behind the project it turns out. I think I would still be interested in contributing to it just not super stoked on it.