## 3 Proposed Methodology  
### Overview of Proposed System  
This paper designs an open-source coordination management system (OSCMS) using a novel triple-blockchain architecture for decentralized OS governance. To address the current and future issues of OS project management and OS ecosystem governance, the OSCMS provides a comprehensive range of solutions for the decentralized transformation of an OS ecosystem and is also a fair and transparent community platform. The triple-blockchain architecture is located at the upper layer of the underlying blockchain modules, directly adopting mature underlying technologies such as state databases, virtual machine engines and communication protocols. The form of consortium blockchain is selected to avoid unlimited low-cost account creation, organize major OS communities and introduce necessary control. In the triple-blockchain architecture, OIChain (open-source information chain) is used to record OI (open-source information) of various versions, CFChain (citation-feedback chain) is used for citations, feedback and ratings, RSChain (reward-sponsorship chain) is used for transactions involving funds such as sponsorships and rewards. These decentralized OS businesses are controlled by smart contracts, which are tamper-proof, traceable and more automated. The above three blockchains jointly maintain the system. They are not only related to each other but also need to conduct necessary interoperability with the external environment, that is, different OS communities and their related tools. On the one hand, different blockchains bind and cooperate with each other only through specified queries. This process is referred to as pre-verification and will be detailed using the specific case in Section 3.3.2. The pre-verification proposed in this paper is a blockchain interoperability scheme based on the specific multi-blockchain architecture, which no longer requires complex or expensive cross-chain technologies. On the other hand, the OS community is the external environment with which OSCMS interacts through an oracle. They have large code warehouses and provide some functions that OSCMS also needs, such as authentication and continuous integration. Oracle servers are not strictly part of OSCMS. There are already some mature and reliable oracle services collaborating with major blockchain platforms and providing services, such as Oraclize and Chainlink. Regardless of the specific service provider, they are collectively referred to as oracle in this paper. The oracle server is connected to the three blockchains in the OSCMS through pre-deployed oracle smart contracts. When a blockchain needs to perform external queries, this contract will be called. When the oracle server receives the oracle contract calls, it performs the specified queries and returns the results. The interoperability between triple-blockchain architecture and the external environment includes calling community APIs to query information about the community account and code warehouse and calling the API provided by the automated test tool in the code warehouse to query the test report. For the latter, some continuous integration tools support the automatic testing of the code in the warehouse, such as Travis CI, Jenkins, CodeShip, etc. Continuous integration is one of the software development practices. Before the code is integrated into the backbone and a new software version is created, it must pass automated testing [54]. Different OS code hosting platforms may use different tools to support continuous integration. For instance, Travis CI is a common system for CI and deployment. Of the continuous integration projects in GitHub, more than half use Travis CI to automatically build and run tests. In the OSCMS, the code reward service needs to query the automatic test report to the API provided by the continuous integration tool in the code warehouse through an oracle. Continuous integration tools are not strictly part of the OSCMS. The specific tool used depends on the community platform.