VisionMobile: Open Control Index (10)-Open Source Control Index

Openness

Our goal is to determine whether open source projects are "open" or "closed ". This is rarely publicly discussed or covered with a license. We define and control open-source projects in a transparent and comprehensive way, such as defining Open-Source Licenses, classifying them as "copyleft", and "Tolerance.

Unlike open-source licenses, the control mode consists of obscure terms, conditions, and project access, impact, decision-making, and derivative control points. We have studied eight mobile open-source projects: Android, MeeGo, Linux, Qt, WebKit, Mozilla, Eclipse, and Symbian. We interviewed community leaders, project representatives, colleges and open-source scholars to learn how control plays a role in the project and how to measure and define good practices.

In the report, the open source project openness is measured by the open source control index. The index contains 13 indicators in four aspects:

1. Access: access to the latest source code, Developer support mechanisms, public roadmap, and transparent decision-making processes.

2. Development: the developer's influence on the project content and direction.

3. Derivatives: the developer's ability to create and publish derivatives from the source code.

4. Community: the Community architecture treats developers fairly.

Open Control Index
Android	23%
QT	58%
Symbian	58%
MeeGo	61%
Mozilla	65%
WebKit	68%
Linux	71%
Eclipse	84%

We ordered the open-source control index. The higher the score, the more open the score. Open source control indexes measure the openness of projects in terms of transparency, decision making, reusability, and Community architecture.

Open Control and open source are used together to ensure the free use, modification and build of developers and users. In many aspects, open-source control involves Open-Source Licenses that are not covered. We hope that research can change the public's understanding of open-source transparency.

Access:

1. Whether the open source code can be used by all developers inSame timeFree access?

Score: Android (1) Eclipse (4) Linux (4) MeeGo (4) Mozilla (4) Qt (4) Symbian (4) Webkit (4)
Score 4: Yes
Rating 3: No-there are differences in the following aspects: a: developer; B: Source Code; c: Time
Score 2: No-there are differences in the two aspects mentioned above.
Score 1: No-there are differences in all aspects mentioned above

2. Is the source code license loose (permissive) OSI license?

Score: Android (4) eclipse (3) Linux (2) meego (2) Mozilla (3) Qt (3) Symbian (3) WebKit (3)
Rating 4: yes-loose license (Apache, BSD, MIT)
Rating 3: Yes-weak Copyleft license (EPL, GNU lgpl v2/v3)
Score 2: yes-strong Copyleft license (gnu gpl v2/v3)
Rating 1: No-no license/private license available

3. Developer support mechanism: Can the project email list, forum, bug tracking database, source code library, developer documentation, and development tools be open to all developers?

Score: Android (2) eclipse (3) Linux (3) meego (3) Mozilla (3) Qt (3) Symbian (3) WebKit (3)
Rating 3: Yes-the Developer support mechanism is open to all developers
Rating 2: No-limited developer support mechanisms. For example, Android does not provide access to the bug tracking database.
Rating 1: No-difference Developer support mechanism

4. Is the project roadmap public?

Score: Android (1) eclipse (3) Linux (2) meego (1) Mozilla (3) Qt (4) Symbian (3) WebKit (2)
Score 4: yes-All roadmap can be obtained, with clear route contribution requirements
Rating 3: Yes-the roadmap information can be obtained, but there is no requirement for contribution or similar
Score 2: No-there is no formal roadmap, but buzilla has a requirement for the submitter and contributor
Score 1: No

5. transparent decision-making mechanism: the project meeting minutes/discussions are open to understand why and how to make decisions?

Score: Android (1) eclipse (4) Linux (3) meego (4) Mozilla (3) Qt (2) Symbian (4) WebKit (3)
Score 4: Yes
Rating 3: Yes-some information is available, but it is difficult to obtain and incomplete
Rating 2: No-but plans to provide more information and make the process more public
Score 1: No

Development:

6. Transparent contribution and acceptance process: Is the code contribution and acceptance process clear and the contribution progress updated (through Bugzilla or similar )?

Score: Android (1) eclipse (2) Linux (2) meego (2) Mozilla (2) Qt (1) Symbian (1) WebKit (2)
Score 4: yes-the contribution and acceptance process are clear and the progress status is displayed.
Score 3: Yes-the contribution and acceptance process are clear, but no progress is provided
Score 2: No-provides the contribution process and Process status.
Score 1: No-the contribution process is provided, but the process status is not provided.

7. Transparency of project contribution: Can I determine the source of source code contribution?

Score: Android (2) eclipse (4) Linux (4) meego (3) Mozilla (2) Qt (2) Symbian (2) WebKit (2)
Score 4: yes-there are good statistics and provide such information
Rating 3: Yes-manual search and collection of information from different sources
Score 2: No-you can view this information through the copyright statement of each file/contribution.
Score 1: No

8. Become a contributor: Are there any requirements and process documents for contribution? Is the process fair (is it possible for all developers to become contributors )?

Score: Android (1) Eclipse (3) Linux (3) MeeGo (2) Mozilla (3) Qt (1) Symbian (2) Webkit (3)
Rating 3: Yes-there is a document lock in the process, and all developers can become
Score 2: No-the process is fuzzy and you cannot determine whether it is applicable to all developers.
Score 1: No-the submission process is restricted to certain project-specific members.

9. Transparency of the submitter: Can you determine who is the submitter of the project? That is, developers who have the right to submit source code to baseline.

Score: Android (1) Eclipse (3) Linux (3) MeeGo (3) Mozilla (1) Qt (1) Symbian (2) Webkit (3)
Rating 3: Yes-provide relevant information with good project statistics
Score 2: No-manual query is required and the information is collected from different sources
Score 1: No-related information not provided

10. Do I need to sign or authorize the copyright to contribute the license?

Score: Android (3) Eclipse (3) Linux (2) MeeGo (2) Mozilla (3) Qt (3) Symbian (3) Webkit (2)
Score 4: Yes-copyright signature and patent authorization required
Rating 3: Yes-copyright and patent authorization required
Rating 2: Yes-requires a copyright license/"sign-off" process (requires contributors to indicate that the code is themselves and is legal free software)
Score 1: No-No contribution Permit

Derivatives

11. Do you use trademarks to control how to use the platform and where to use the platform? Do you need to pass mandatory compatibility tests before release?

Score: Android (1) Eclipse (2) Linux (2) MeeGo (1) Mozilla (2) Qt (2) Symbian (1) Webkit (2)
Score 2: No-you can contribute code freely and use project trademarks without complete formal compatibility requirements
Score 1: Yes-before release, the Code must pass the formal compatibility Process

12. Are the application derivatives pushed to the market restricted by project approval, release, and discovery?

Score: Android (2) Eclipse (4) Linux (4) MeeGo (4) Mozilla (4) Qt (4) Symbian (3) Webkit (4)
Score 4: No-
Rating 3: Yes-Restrictions on approval, release, or discovery
Score 2: Yes-there are two restrictions on approval, release, or discovery.
Score 1: Yes-Restrictions on approval, release, and Discovery

Community

13. Whether the Community structure is flat or hierarchical (that is, do you have the right to distinguish members based on their identities ?)

Score: Android (1) Eclipse (2) Linux (2) MeeGo (2) Mozilla (1) Qt (2) Symbian (1) Webkit (2)
Score 2: No-there is No formal member relationship, or there is No difference in development and acquisition between members and non-members
Score 1: Yes-You have different rights based on the position of the Member.

Related links:

• VisionMobile: Open Control Index (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
• My industry ecosystem chain and miscellaneous articles