Hyperledger Bevel Q3 report #286
Conversation
suvajit-sarkar
requested review from
tkuhrt,
VRamakrishna,
arsulegai,
denyeart,
jimthematrix,
mbrandenburger,
non-fungible-nelson,
petermetz,
swcurran and
yacovm
as code owners
| # Maintainer Diversity | ||
|
|
||
| - There is change in the maintainers for Bevel. You can find our current maintainer list here: | ||
| <a href="https://github.com/hyperledger/bevel/blob/main/MAINTAINERS.md" class="external-link" rel="nofollow">https://github.com/hyperledger/bevel/blob/main/MAINTAINERS.md</a>. |
There was a problem hiding this comment.
The maintainers file contents does not match the list in this report.
|
|
||
|
|
||
| 1. Getting code contributions for Hyperledger Bevel still remains a challenge. | ||
| 2. The Bevel project has received no external contributions; nearly all contributions for the last couple of releases have come from the Accenture team. Accenture will not be able to maintain the project without other organization or individual contributor help in maintaining. |
There was a problem hiding this comment.
Would you need additional assistance on this topic?
There was a problem hiding this comment.
Yes, please. Can connect to discuss
There was a problem hiding this comment.
does this summary on external contributions take into account the bevel-fabric-operator component? Isn't that contributed by a different organization? or is that not considered under the Bevel umbrella, which if so would be a mistake.
There was a problem hiding this comment.
the bevel and bevel-fabric-operator have separate code base/repo which runs independently, the comment here is for bevel
There was a problem hiding this comment.
Would having an umbrella of projects help in reaching the goal? For instance, Cello is another project with kubernetes operators.
suvajit-sarkar
force-pushed
the
gh-pages
branch
from
e198a78
to
a4e2211
Compare
Signed-off-by: suvajit-sarkar <suvajit.sarkar@accenture.com>
suvajit-sarkar
force-pushed
the
gh-pages
branch
from
a4e2211
to
1e81957
Compare
|
|
||
|
|
||
| 1. Getting code contributions for Hyperledger Bevel still remains a challenge. | ||
| 2. The Bevel project has received no external contributions; nearly all contributions for the last couple of releases have come from the Accenture team. Accenture will not be able to maintain the project without other organization or individual contributor help in maintaining. |
There was a problem hiding this comment.
does this summary on external contributions take into account the bevel-fabric-operator component? Isn't that contributed by a different organization? or is that not considered under the Bevel umbrella, which if so would be a mistake.
Co-authored-by: Tracy Kuhrt <tracy.a.kuhrt@accenture.com> Signed-off-by: Suvajit Sarkar <55580532+suvajit-sarkar@users.noreply.github.com>
Co-authored-by: Tracy Kuhrt <tracy.a.kuhrt@accenture.com> Signed-off-by: Suvajit Sarkar <55580532+suvajit-sarkar@users.noreply.github.com>
Co-authored-by: Tracy Kuhrt <tracy.a.kuhrt@accenture.com> Signed-off-by: Suvajit Sarkar <55580532+suvajit-sarkar@users.noreply.github.com>
Co-authored-by: Tracy Kuhrt <tracy.a.kuhrt@accenture.com> Signed-off-by: Suvajit Sarkar <55580532+suvajit-sarkar@users.noreply.github.com>
Signed-off-by: adityajoshi12 <adityaprakashjoshi1@gmail.com>
added report for bevel-operator-fabric
No description provided.