Project Name: BigBlueButton
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](insert link here)
What is the purpose of the project:
How easy was it to find information about contributing on the website?
Contributing instructions: [Here](insert link here)
URL for the code repository: [Code repository](insert link here)
Bug/Issue tracker link: [Bug/Issue tracker](insert link here)
Mailing list: [Mailing list](insert link here)
Chat channel: [Chat channel](insert link here)
Other communication channels:
License: [License](insert link here)
Is it OSI approved license:
Programming Language(s):
URL for contributing instructions: [Contributing instructions](insert link here)
Are the contributing instructions clear?
URL for code of conduct / community norms / community guildelines: [Community Guidelines](insert link here)
URL for instructions for users to download and install the package: [here](insert link here).
Are these instructions clear? Do you think they would be easy to follow?
URL for instructions for how to install development environment: [here](insert link here)
Are these instruction clear? Do you think they would be easy to follow?
Number of contributors: xxx contributors
Usernames of three contributors with largest number of commits; for each of them list the link to their latest commit:
- [Name] (xxx commits) - [Their Latest Commit](insert link here)
- [Name] (xxx commits) - [Their Latest Commit](insert link here)
- [Name] (xxx commits) - [Their Latest Commit](insert link here)
Number of commits: xxxx commits
Latest commit
-
link to the commit: [Latest commit](insert link here)
-
who made that commit:
-
what type of work was commited? (was it a fix to a bug, implementation of a new feature, ...)
Issues
-
how many open issues are there: [xxx Open Issues](insert link here)
-
url for the last issue created: [Last issue created](insert link here)
-
how many users discuss the issue: xx person
-
when was the issue reported:
-
-
how many closed issues are there: [xxx closed issues](insert link here)
- url for the last issue closed: [Last issue closed](insert link here)
- how many users discussed the issue: xx people
- when was the issue reported:
- when was the issue closed:
-
how active is the discussion on the issues:
-
example of a lot of good discussion: [Good discussion](insert link here)
-
example of an issue that does not have much discussion: [Not much discussion](insert link here)
-
-
are there issues marked "good for newbies", "beginner" or some other indicators that imply that they are good for beginner contributors:
-
how many of such issues are there? xxx issues
-
look at a few of them, do they look beginner friendly?
-
-
are there issues marked "documentation" or some other indicators that imply that they are documentation (user or developer specific):
-
how many of such issues are there?
-
look at a few of them, do you think you could submit a fix?
-
Pull requests
-
how many open pull requests are there: xx pull requests
-
url for the last pull request created: Last Pull Request created
-
when was the last pull request made: Last Pull Request created
-
url for the oldest pull request created: Oldest Pull Request created
-
when was the oldest pull request made:
-
-
how many closed pull requests are there:
-
url for the last pull request closed: Last Pull Request closed
-
how many users discussed the pull request: xx users
-
when was the pull request made:
-
when was the pull request closed:
-
-
do maintainers respond quickly to pull requests when they are opened?
Each member of your group should attempt to configure the development environemnt for this project. Complete the following for each member:
Name:
Operating system:
Was the installation successful? (if not, explain what went wrong and what you did to try to remedy it)
How long did the whole process take?
How friendly is this project for beginner contributors?
Do the maintainers respond helpfully to questions in issues?
Are people friendly in the issues, discussion forum, and chat (for example, IRC or Slack)?
Do pull requests get reviewed?
Do maintainers thank people for their contributions?
Are there special skills required to contribute to the project? If so, what are they?
Are there any special hardware/software requirements to be able to contribute to the project? If so, what are they?