This document provides details about what resources are available for Hyperledger projects and labs.  If there are any questions about anything on the document or if you'd like to leverage any of these resources for your project or lab, feel free to leave a comment below or reach out to community-architects at hyperledger dot org.

ServiceLabIncubation ProjectGraduated Project
Infrastructure


Github reposYesYesYes
Chat channelOptionalYesYes
Mailing list
YesYes
Paid toolingYes (with some restrictions at the discretion of Hyperledger staff)YesYes
Marketing


Access to Hyperledger's channels (social, newsletters, blogs, meetups, etc)Yes (with some restrictions at the discretion of the Marketing lead)YesYes
Page(s) on the wikiOptionalYesYes
Page on the Hyperledger site
YesYes
Creation of an official project name and logo
YesYes
Coordinate promotion of major project milestones and releases
YesYes
Option to create a Twitter account
YesYes
Priority placement on site and wiki

Yes
Swag (stickers, shirts and potentially other items with the project logo in the Hyperledger store)

Yes
Onboarding New Users and Contributors


Able to take part in Hyperledger's annual Mentorship programYesYesYes
Able to have project/lab featured in a contribution campaignYes (at the discretion of Hyperledger staff)YesYes
Workshops

Yes
Documentation and Translation supportTBDTBDTBD
Training/Certification


LF created training course
Yes (at the discretion of LF Training)Yes (at the discretion of LF Training)
LF created certification

Yes (at the discretion of LF Training)
Other


License scanning
YesYes
Security audits
Not usually (although this can be done at the discretion of staff)Yes (at the discretion of Hyperledger staff)
  • No labels

17 Comments

  1. Tracy Kuhrt

    David Boswell : For security audits, it seems that we have been doing them for some of our incubated projects (but not all of them). Is this a change that we are deliberately making? Or just an oversight in the table?

    1. David Boswell

      Tracy Kuhrt – Thanks for flagging this.  We had left this out since we don't typically do audits for incubation projects, although as you point out it has been done.  I added a note to say we don't usually do this for that level of project but we have the discretion to do it as needed.

  2. Sherwood Moore

    Great idea. Thanks for putting this together David Boswell . Adding links to help with navigation wherever possible would make this an even more useful tool.

    1. David Boswell

      Sherwood Moore – Good suggestion about adding links where possible for each specific resource.  I'll take a pass at doing that.

  3. Hart Montgomery

    This is a fantastic table.  Thank you for putting it together David Boswell.

    One thing it does highlight is the lack of extra benefits for graduating from incubation.  We probably need to have more incentives for graduating from incubation than we currently do.  Moreover, the project dependencies make this even murkier.  Given the fact that some projects function more as "families" rather than standalone efforts (e.g. Aries/Indy and Sawtooth/Grid/Transact), what happens if one project from the family is graduated but another project upon which the graduated project depends is only in incubation?  Suppose (just for the purposes of this argument) that we restrict security audits to graduated projects.  A security audit for the graduated project might necessitate a security audit for the project in incubation–what do we do in this case?

    The TSC has spent a huge amount of collective manpower over its existence discussing the project lifecycle, so maybe it's not worth revisiting that at this point.  But I think we should try to incentivize projects to graduate more than we are currently doing.

    1. Arun S M

      Interesting question. Here are my thoughts

      1. Should we have such high level of dependency across projects where security audits are mandated? Should TSC be careful in not allowing such high dependent project be proposed as a new project altogether?
      2. In case of these projects being dependency library. Do we currently consider auditing all the imported libraries?

    2. David Boswell

      Hart Montgomery Arun S M Kamlesh Nagware – Thanks for your feedback and I see that you've each mentioned that having more resources at the graduated level would be helpful.  Here are some ideas to consider, although it would also be really helpful to hear from people involved in projects about what additional help they'd be interested in.

      • I think there is probably something around documentation and translation support for graduated projects that would be worth doing.  If possible, perhaps we can make some budget available to bring in a technical writer, for example, to help with project docs?
      • We could also make the resources available to Incubation projects time bound – for instance, an Incubation project could have a year to grow and mature and at the end of that time the TSC decides to either move it to Graduated or move it to the Labs.
      • The project placement on the Hyperledger site does not currently provide a distinction between Graduated and Incubation projects since they're treated the same way now.  We're looking at updating the site this year to give more prominent positioning to Graduated projects, so the priority placement item will become more of an incentive.
      • The same is true of Workshops – this is a new concept so we have not yet seen the benefits to a project of running a workshop.  After we've done a few of these we can analyze the outcome and if we can see a bump in users and contributors to a project after a workshop then this will become an incentive for Graduation status too.

  4. Arun S M

    This table makes it easy to distinguish, thanks David Boswell. You have covered all the necessities, we need more benefits for graduated projects. adding more items would translate to increased workload on Hyperledger staff. But here are a few random thoughts

    1. In case of deciding the priorities, operational preference will be given to graduated projects.
    2. Community showcase & benefits from the marketing team. I don't see any called out, other than Hyperledger channels. Having access to channels is a benefit, sure. But pro-actively marketing a project is a huge plus to graduated projects. This could also include assistance in market research, adoption insights etc.
    3. Website with Hyperledger's domain as an option for incubated projects.
    4. Language and translation support.
    5. Assured demo booths at Hyperledger organized events (including the HGF, Hyperledger Member Summit etc) for graduated projects. Extend this to swag merchandises.

  5. Arnaud J Le Hors

    Thanks David for putting this in a table format. This is much more effective than the old text version.
    Why being shy about writing "no" where applicable? We only have yes or blank. I think we should be more blunt.

    1. David Boswell

      Arnaud J Le Hors – That's certainly fine with me to add 'no' instead of having items be blank.  My initial thought when I set this up was that adding something to each box would clutter up the page and make it harder to scan to see where there were 'yes'es.  But I'm fine adding 'no' in blank spaces if that seems better.

  6. Kamlesh Nagware

    David Boswell  Thanks David for putting this together. I think more benefits should be given graduated projects, current table don't have much difference in benefits between incubated & graduated projects. More Marketing support, hyperledger support to graduated projects.

  7. Peter Somogyvari

    One more idea for incentives for projects to get to 'active' status could be to get these paid** bonus services (unless these are already in the HL GH org and I'm just not aware).

    https://github.com/features/security/code

    https://resources.github.com/code-scanning/

    ** As long as the price is both reasonable and affordable of course.

    1. David Boswell

      Peter Somogyvari – Thanks for the feedback and that is a good suggestion.  We'll look into those.

  8. Dan Middleton

    Can you give examples of `paid tooling`?

    1. Peter Somogyvari

      Dan MiddletonOne that comes to mind would be a custom Jenkins instance for CI/release management etc.

  9. Yi Yuan

    David Boswell, I have a question, for some project before labs. at PoC level or just some sample code.

    are we able to have Access to Hyperledger's channels (social, newsletters, blogs, meetups, etc) support?


    For ex, we have many topics from different part related with NFT for now. and in fabric, we have ERC-721 fabric sample at Feb 2021

     https://wiki.hyperledger.org/display/fabric/Contributor+Meetings+2021


    do we have any related blogs in the past?

    are we able to have this kind of "tiny" project post with blogs in the future?

    To make those projects been published on both technological meeting and social media?

    1. David Boswell

      Yi Yuan – Yes, community members can make use of our different channels.  For instance, any community member can add items into our weekly developer newsletter.  In this case though, it sounds like you're referring to work that is happening within an existing project so that would be covered as part of the services for a project.  So if the people involved would like to talk about any of these services – such as writing a blog post and promoting on social media – let me know and we can help with that.