About

Open Source

A decentralized software development methodology focused on public collaboration.

A decentralized software development methodology focused on public collaboration.

It's about sharing

• code
• development effort
• roadmap
• design decisions
• accountability

It not (only) about making source code public.

It not (only) about making source code public.

Is there any, better or worse, alternative?

How can I assess the quality / maturity / robustness of the project?

What if the maintainers die tomorrow, can someone take over?

Why go Open Source?

Why go Open Source?

• Deliver higher quality software
• Attract talents
• Bring transparency
• Spread accountability
• Ensure longevity

Our ecosystem

Going Open Source

Legal

Marketing

Product

Community

Community

Engineering

Open Source For

Legal / Finance

↳ Advise & accelerate growth of key projects

• Coordinate with community / partnerships on grants for key projects
• Define reusable legal templates and processes for open source projects
• Help coordinate (bug or feature) bounties programs
• Assist projects with legal conflicts and license infringements
• Define reusable financial templates and methodologies for open source projects (e.g. ledger on blockchain)
• Assist projects with accounting & regulations, especially with Ada

Open Source For

Marketing

↳ Amplify the visibility of key actors and projects

• Targeted social media nudges: Twitter repost, Twitter threads, Twitter spaces, Discord group discussions, Reddit boosts etc…
• Help advertise bounties for chosen issues or tasks
• Drive the development and promotion of an open “marketplace” for ecosystem projects
• Help writing and promoting open source content: blog posts, guides, etc..
• Coordinate with engineering & community to publish a weekly ‘Cardano Open Source’ newsletter
• Advise on go-to-market strategies for key Open Source projects

Open Source For

Community

↳ Foster collaboration & sharing

• Conduct & promote ecosystem surveys (e.g. annual dev ecosystem survey)

• Organize Twitter spaces and discord discussions on hot topics

• Coordinate the definition of objective criteria for assessing “favorite projects” to then promote to partners.

• Interview key community members and help gather their feedback while also giving them more visibility.

• Identify gaps in documentations, user guides and coordinate with the education department & the community into fixing them.

Open Source For

Partnerships

↳ Brings new actors & identify barriers to entry

• Coordinate with the open source, integration & engineering departments to address issues raised by partners.

• List and maintain most recurring pain points from on-boarding partners

• Sign deals / convince partners to use and sponsors key open source projects

• Keep and curate a list of good on-boarding media resources for Cardano

Open Source For

Integration

↳ Help actors navigate through the ecosystem

• Conduct regular touchpoints with exchanges and business partners to identify their problems and recommend "favorite" solutions from the ecosystem

• Help define priorities for tooling & features for ecosystem builders (e.g. CBIA)

• Help identify existing project workstream worth sponsoring or setting bounties for

• Be present on the Cardano StackExchange and encourage partners to formulate their questions there instead of private channels

• Open detailed issues on relevant community projects (feature requests, bug reports, etc..)

Open Source For

Education

↳ Train actors & monitor education resources

• Rewrite / fix https://docs.cardano.org

• Monitor & evaluate publicly available education resources

• Identify gaps in existing educational resources, fix them when possible

• Gather lists of good (and free) educational material about Cardano

• Design and run an ‘Open Source’ masterclass (internal & external)

Open Source For

Infra

↳Increase accessibility & reduce operational risks

• Help packaging software solutions to various targets (e.g. docker, aptitude, brew, nix, ...)
• Inform and guide about best practices for software operation and packaging
• Provide reusable for setting setup / operating / orchestrating open source software solutions 
• Assess security risks / vulnerabilities of existing projects, directly or indirectly
• Provide low-level command-line tools or scripts to automate specific tasks

• Develop open source software to address identified gaps in the ecosystem
• Open detailed issues on relevant community projects (feature requests, bug reports, etc..)
• Engage with the CIP process (reviews & document drafts)
• Engage with Open Source maintainers in design discussions of software we depend on
• Contribute / lead discussions on open standards or protocols
• Meet with community builders, share ideas & collect feedback

↳ Lead by example