User Tools

Site Tools


groups:tsc:project-updates:iroha-2018-jan

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
groups:tsc:project-updates:iroha-2018-jan [2018/01/21 11:04]
Nikolay Yushkevich
groups:tsc:project-updates:iroha-2018-jan [2018/01/22 06:13] (current)
Nikolay Yushkevich
Line 5: Line 5:
  
 ===== Project Health ===== ===== Project Health =====
-The main focus of Hyperledger Iroha project now is to freeze the number ​of features, bring more optimisations to the codebase, and focus primarily on three aspects of product'​s quality model:+The main focus of Hyperledger Iroha project now is to freeze the implementation ​of new features, bring optimisations to the codebase, and focus primarily on the three aspects of product'​s quality model:
   - Reliability (fault tolerance, recoverability)   - Reliability (fault tolerance, recoverability)
   - Performance Efficiency (in particular time-behavior and resource utilization)   - Performance Efficiency (in particular time-behavior and resource utilization)
Line 15: Line 15:
  
 ===== Issues ===== ===== Issues =====
-Since the last report, Sonarqube [[https://​sonar.soramitsu.co.jp]] metrics ​has not improved a lot. We know about the fact and since the files, having most of the technical debt are going to be completely removed from the project after we finish with the integration of new model classes — we plan to reach maintainability grade of A level.+Since the last report, Sonarqube [[https://​sonar.soramitsu.co.jp]] metrics ​have not improved a lot. We know about the fact and since the files, having most of the technical debt are going to be completely removed from the project after we finish with the integration of new model classes — we plan to reach maintainability grade of A level.
  
 Moreover, we expect the coverage to be improved a lot after changes in the total grade calculation [[https://​github.com/​codecov/​support/​issues/​470]] in Codecov service, and after we finish with an integration test framework, being in development currently. Right now, the grade is very low — 48,9% branch coverage in sonarqube [[https://​sonar.soramitsu.co.jp/​project/​activity?​custom_metrics=coverage&​graph=custom&​id=hyperledger:​iroha:​develop]] and 31% in Codecov service [[https://​codecov.io/​gh/​hyperledger/​iroha/​tree/​develop]]. After the integration test framework is completed, we will perform a further testing of our transaction and query pipelines using boundary value analysis and classification tree method.  ​ Moreover, we expect the coverage to be improved a lot after changes in the total grade calculation [[https://​github.com/​codecov/​support/​issues/​470]] in Codecov service, and after we finish with an integration test framework, being in development currently. Right now, the grade is very low — 48,9% branch coverage in sonarqube [[https://​sonar.soramitsu.co.jp/​project/​activity?​custom_metrics=coverage&​graph=custom&​id=hyperledger:​iroha:​develop]] and 31% in Codecov service [[https://​codecov.io/​gh/​hyperledger/​iroha/​tree/​develop]]. After the integration test framework is completed, we will perform a further testing of our transaction and query pipelines using boundary value analysis and classification tree method.  ​
  
-Sometimes, the documentation does not match the version and is related only to nightly builds. This is an issue we are researching solution for, and need help with, as our current tools cannot provide documentation for several versions, or the tools were poorly reviewed.+Sometimes, the documentation does not match the version and is related only to nightly builds. This is an issue we are researching ​solution for, and need help with, as our current tools cannot provide documentation for several versions, or the tools were poorly reviewed.
  
 ===== Releases ===== ===== Releases =====
Line 37: Line 37:
 There is a positive trend that the community members are actively helping with questions in Gitter and telegram chat. Unfortunately,​ the team of maintainers is not reacting actively to community questions in email lists, or other places, but is promoting to use GitHub issues to report about troubles and reacts to any posted question or defect found. There is a positive trend that the community members are actively helping with questions in Gitter and telegram chat. Unfortunately,​ the team of maintainers is not reacting actively to community questions in email lists, or other places, but is promoting to use GitHub issues to report about troubles and reacts to any posted question or defect found.
  
-Development is related mostly to bug fixes, technical debt elimination,​ and some features, which will help to improve the pipeline and optimize the performance of Iroha peer: push-based interaction between client and peer, interaction ​test framework, quality plan. Other work is related to usability and interoperability:​ expanded list of client libraries (right now it is Java and Python, with C# requiring further contribution),​ event logging and message codes with the classification of faulty states. ​+Development is related mostly to bug fixes, technical debt elimination,​ and some features, which will help to improve the pipeline and optimize the performance of Iroha peer: push-based interaction between client and peer, integration ​test framework, quality plan. Other work is related to usability and interoperability:​ expanded list of client libraries (right now it is Java and Python, with C# requiring further contribution),​ event logging and message codes with the classification of faulty states. ​
  
 ===== Current Plans ===== ===== Current Plans =====
Line 48: Line 48:
  
 ===== Contributor Diversity ===== ===== Contributor Diversity =====
-Since our last report, several individuals have contributed to the project with their expertise, use case suggestions,​ partnership proposals and expressed their intention to help in future. They referenced events, where the team of maintainers was involved (hackfest and summit), as well as the course, which was published last year on edX. Unfortunately,​ no exact statistics were made, and approximately the number of new contributors is around 5 people.+Since our last report, several individuals have contributed to the project with their expertise, use case suggestions,​ partnership proposalsand expressed their intention to help in future. They referenced events, where the team of maintainers was involved (hackfest and summit), as well as the course, which was published last year on edX. Unfortunately,​ no exact statistics were made, and approximately the number of new contributors is around 5 people.
groups/tsc/project-updates/iroha-2018-jan.1516532683.txt.gz · Last modified: 2018/01/21 11:04 (external edit)