We are continuing to deliver weekly releases of new features and bug fixes to the community. The community are regularly opening bugs in our GitHub repository, and they are being turned around quickly. We are also receiving and answering a significant number of questions on both Rocket.Chat and Stack Overflow. We are continuing to see an uptick in new contributors to the project, however contributions are mostly limited to documentation updates at this time.
There are no issues at this time.
We are delivering weekly releases of new features and bug fixes to the community. The information about each release is available in GitHub in the release notes: https://github.com/hyperledger/composer/releases
We see very little activity on the project mailing lists. We see significant amounts of activity on Rocket.Chat, Stack Overflow, and GitHub issues. In IBM, we have two team members dedicated to providing assistance to end users on Rocket.Chat and Stack Overflow (Paul O'Mahoney and Rob Thatcher) and they regularly and quickly answer all questions. We are continuing to see other people in the community regularly answer questions as well, which is a good step forwards. The current contributors are also good at responding to comments GitHub issues in a timely manner.
We have delivered a significant release in the last three months, Composer v0.19.0. This release is significant because it includes a completed set of features that we think mean Composer is ready for production. Those features are:
We also received a sizable external contribution from nicolapaoli to add API key support to the Composer REST server, allowing Composer users to secure their REST APIs in a easy fashion without having to use an external authentication system such as LDAP or OAuth2. This is the biggest contribution from someone outside the core contributor team we have seen to date!
As discussed on previous TSC calls, we would like to work towards a Composer v1.0 release. We think that v0.19.0 is a great base for a v1.0, and are currently focusing on outstanding bug fixes and test debt to harden the codebase whilst we let the community try it out. We are working through the outstanding legal concerns (around copyright/license headers etc) and are awaiting the external security audit which begins in May.
No new maintainers since the last project update. The current set of maintainers are:
Contributions have been received from the following organisations in the 3 months since the last update:
Optional Please provide any additional information that you feel would be useful for TSC to be aware.