Skip to content

Latest commit

 

History

History
128 lines (84 loc) · 4.86 KB

vscode_evaluation.md

File metadata and controls

128 lines (84 loc) · 4.86 KB
Raw

Vscode:

Umar Khan, Mohammed Tarek, Keisuke Suzuki:

License

  1. What is the project's license? The main license of the repository is MIT license.

Code Base

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

  2. What is the development environment? For example, is it Gnu C++ on Linux? Are there instructions for how to download, build, and install? The development environment for is Linux. There are isntructions on how to isntall it on Windows, Linux as well as Mac.

  3. Does the project depend on external additional software modules such as database, graphics, web development, or other libraries? There is a Extensions file that contains all the libraries that are borrowed from outside sources to work on in this project.

  4. Is the code easy to understand? Browse some source code files and make a judgment based on your random sample. It is indented well and commented well

  5. Is this a big project? If you can, find out about how many lines of code are in it, perhaps on OpenHub. It is a huge project. According to openhub, the project has 639,878 lines.

  6. Does the repository have tests? The reopsitory does have tests.

Code and Design Documentation

  1. Is there clear documentation in the code itself? Some files are clearly indented but some are not.

  2. Is there documentation about the design? Nothing has been found about the design of project structure.

Activity Level

  1. How many commits have been made in the past week? There are a total of 373 commits in the past week.

  2. When was the most recent commit? The last commit was done 4 hours ago by user weinand.

  3. How many issues are currently open? There are 4,541 issues that are currently open.

  4. How long do issues stay open? An issue depends on the long big the issue is, if it is a big issue, it usually takes like 10 hours. However, if it is a small issue it takes an hour or so.

Compute the number of days that each was open and take the average. Typically the average time for an issue to stay open is around 1 hour, but if it is a large issue, it will take around 10 hours for the issue to be closed.

  1. Is there active discussion on the issues? If it is a small issue, usually it is just question and answer with no discussion. However, if the issue is complex enough, there is usually discussions on how to tackle the issue by various people before coming to a complete conclusion and closing the issue.

  2. Are issues tagged as easy, hard, for beginners, etc.? There are tags in issues such as 'debug', 'needs more info', 'testplan-item', 'integrated-terminal' etc.

  3. How many issues were closed in the past six months? There were a total of 190 issues that were closed in the past 6 months.

  4. Is there information about how many people are maintaining the project? There is no information on the number of maintainers

  5. How many contributors has the project had in the past six months? It had a total of 385 contributors in the last 6 months

  6. How many open pull requests are there? There are a total of 149 pull requests that the project has currently.

  7. Do pull requests remain un-answered for a long time? Look at the closed pull requests to see how long they stayed open. Take the five most recently closed ones and look at when each was first reported. Compute the number of days that each was open and take the average. Pull requests do not remain unanswered for a long time. Maintainers respond within 6 hours.

  8. Is there active discussion on the pull requests? There is active discussion on the pull requests.

  9. How many pull requests were opened within the past six months? There were a total of 517 pull requests in the past 6 months.

  10. When was the last pull request merged? Last commit was 4 hours ago.

Welcomeness and Community

  1. Is there a CONTRIBUTING document? If so, how easy to read and understand is it? There is a contributiing document that is fairly easy to understand. It shows the user various ways to be able to contribute, such as asking questions, giving feedback and even reporting issues.

  2. Is there a CODE OF CONDUCT document? Does it have consequences for acts that violate it? Yes, It deos have conde of conduct and it does have consequences for those who violate them..

  3. Do the maintainers respond helpfully to questions in issues? Are responses generally constructiion? Maintainers respond mostly on major issues and those responses are helpful.

  4. Are people friendly in the issues, discussion forum, and chat? People are friendly in all the sections.

  5. Do maintainers thank people for their contributions? Maintainers do thank people for their contributions

Summary

Do you think this is a project to which it would be possible to contribute in the course of a semester? This is a porject where it would be possible to contribute for those who have knowledge of Typescript.