Skip to content

Instantly share code, notes, and snippets.

@dhmlau

dhmlau/loopback-application.md

Last active May 11, 2022 07:48
Show Gist options
  • Save dhmlau/a955bd7b3928df9d79ace0d6b28b5f4c to your computer and use it in GitHub Desktop.
Save dhmlau/a955bd7b3928df9d79ace0d6b28b5f4c to your computer and use it in GitHub Desktop.
Download ZIP
Project Application Form - Work in progress
Raw
loopback-application.md

Project Application Form

https://github.com/openjs-foundation/cross-project-council/blob/main/NEW_PROJECT_APPLICATION.md

Applicant

Diana Lau [email protected] GitHub: @dhmlau

Description

LoopBack is a popular Node.js framework for API creation and a platform to build large scale Node.js applications using proven patterns with TypeScript as a first class citizen. It also supports SOAP and enterprise databases.

Reason for Applying

Reason: We’re gaining more adoption and contributors in the community. We also have more alignment with other open source projects, such as Express and AJV. To continue the growth for LoopBack, we believe it makes sense to join the OpenJS Foundation for more open governance.

Expectation from the foundation:

  • Provide a vendor-neutral governing organization and the structure around project processes.
  • Help community contributors to self-organize into a well-functioning body by offering best practices and guidance, like establishing a Technical Steering Committee, etc.
  • Cover infrastructure costs. For example:
    • Own and pay for the domains like loopback.io
    • If we run out of the free minutes offered by GitHub Actions, then we would like OpenJS to fund additional build minutes for our CI process.
    • A video-conferencing tool (e.g. Zoom) we can use for community calls like our monthly Maintainers Call. At the moment, the calls are hosted on IBM-paid Webex.
  • For the longer term, it would be great if OpenJS can reimburse travel expenses for LoopBack maintainers speaking at conferences.
  • Nice to have: sponsor swag like printing stickers to give away at meetup & conferences.

Statement of alignment with OpenJS Foundation charter and mission

Note: Used https://gist.github.com/mcollina/beb83b8bc594ae506e11c83aef9c537d as reference

LoopBack is a community targeting the development of a Web framework for Node.js in a sustainable manner. It follows the OpenJS Foundation principles to operate transparently, openly, collaboratively, and ethically.

We would like to join the OpenJS Foundation because the LoopBack community is growing, and joining the Foundation will help clarify the legal status of the project and remove possible business concerns that could hinder adoption.

The LoopBack community is also a welcoming place for new collaborators as our core philosophy is to promote contributions from the community, rather than the core team pushing forward their own agenda.

Impact and users of the project

  • Who are the biggest users of the project?

    IBM is one of our biggest users of LoopBack. There is also a list of users on loopback.io web site: https://loopback.io/.

  • What is the potential long term impact and adoption?

    LoopBack is a mature enterprise framework. We anticipate the adoption will continue to grow and even more once it joins the OpenJS Foundation. We have public Slack channel, monthly maintainers’ call to embrace the open governance process.

    Technology-wise, the team has abstracting out the core platform and core functionalities that can be beneficial outside of the project. We’ll continue to collaborate with the community on RFC project to continue to build features.

  • How does it differ from other projects?

    • LoopBack is the only Node.js framework bundling the entire experience of building a REST API service:
      • REST API layer closely integrated with data-access layer (ORM) makes it much easier and faster to build CRUD-like APIs
      • CLI tooling to scaffold project artifacts makes that process even quicker
    • We are one of the very few frameworks to support proprietary databases like Oracle, Microsoft SQL, IBM DB2, etc.
    • We are probably the only framework providing an easy integration with SOAP services.
    • LoopBack can be leveraged as ecosystem of TypeScript pacakges to build large scale Node.js application on top of the API creation usage.

Desired Initial Project Phase

At Large

Project Website

https://loopback.io/

Social Media Accounts

Below are the social media accounts we currently have:

They will be rebranded as LoopBack specific accounts once LoopBack has accepted into the Foundation.

Official Communication Channels

Security Policy

Currently we suggest users to report security vulnerability issues to an IBM email address. We’re happy to adopt the process recommended by the Foundation. Here is our security policies: https://github.com/strongloop/loopback-next/security/policy, sourced from https://github.com/strongloop/loopback-next/blob/master/SECURITY.md.

Governance Structure

  • Is there a leadership team? Yes

  • Who are the members of the leadership team?

    We are in the process of forming a Technical Steering Committee. So far, we have:

  • How are members of the leadership team nominated?

    In the past, members of the leadership team are currently assigned, as they are project architects and development manager of the LoopBack team from IBM.

    Going forward, we are interested in adopting the open governance model and in the process of forming a Technical Steering Committee.

  • How are individuals outside of leadership given commit access?

    Maintainers are given commit access.

    In the past, there are two ways to be maintainers:

    • employed in the LoopBack development team as IBM employee
    • existing maintainers can nominate individuals who show sufficient amount of LoopBack knowledge and passion in maintaining this project to be maintainers.

    We recently have opened up the nomination process allowing other maintainers to nominate new maintainers.

  • Is the project open/willing to move to open governance, if not already in place?

    We have been practicing some of open governance methodology, and are willing to embrace the recommendation from the OpenJS Foundation.

  • Is the project willing to adopt the OpenJS Foundation Code of Conduct (CoC)?

    Our main repo loopback-next adopts Contributor Covenant Code of Conduct: https://github.com/strongloop/loopback-next/blob/master/docs/CODE_OF_CONDUCT.md, where other repos don’t have CoC. We’re happy to adopt Contributor Convenant in other repos that are joining the OpenJS Foundation.

  • Please share links to all existing documentation e.g. GOVERNANCE.md / CONTRIBUTING.md

    Here are the docs:

List of all repos that are part of the project

  1. Core
Repository Contribution Method (CLA/DCO) License (MIT/others)
loopback-next DCO MIT
loopback-datasource-juggler DCO MIT
strong-error-handler DCO MIT
explorer.loopback.io DCO MIT
  1. Commonly used connectors and common modules
Repository Contribution Method (CLA/DCO) License (MIT/others)
loopback-connector-mysql DCO MIT
loopback-connector-postgresql DCO Artistic-2.0
loopback-connector-mongodb DCO MIT
loopback-connector-rest DCO MIT
loopback-connector-mssql DCO MIT
loopback-connector-soap DCO MIT
loopback-connector-oracle DCO MIT
loopback-connector-cloudant DCO Artistic-2.0
loopback-connector-cassandra DCO MIT
loopback-connector-couchdb2 DCO Apache License, Version 2.0
loopback-connector-db2 DCO Artistic-2.0
loopback-ibmdb DCO Artistic-2.0
loopback-connector-dashdb DCO Artistic-2.0
loopback-connector-ibmi DCO Artistic-2.0
loopback-connector-grpc DCO MIT
loopback-connector-kv-redis CLA MIT
loopback-connector-openapi DCO MIT
loopback-connector-sqlite3 CLA Artistic-2.0
loopback-connector-elastic-search N/A MIT
loopback-connector-redis CLA MIT
loopback-connector-kv-extreme-scale CLA MIT
strong-soap DCO MIT
  1. Documentation, examples & extensions
Repository Contribution Method (CLA/DCO) License (MIT/others)
loopback.io DCO MIT
loopback4-example-shopping DCO MIT
loopback4-example-kafka N/A MIT
loopback4-extension-grpc DCO MIT
loopback-governance N/A N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment