Licenses, Attributions, and Third-Party Acknowledgments

What Would You Do? (WWYD) builds on the work of individuals, organizations, and communities throughout the software, research, and open-source ecosystems. We are grateful for the tools, libraries, services, and other resources that make this project possible.

We believe transparency includes identifying the origins of the technologies we use, acknowledging their creators, and helping visitors find authoritative information about applicable licenses and terms.

This page documents third-party software, development tools, infrastructure services, and other resources known to be relevant to the WWYD website. It also establishes a framework for documenting additional components as the project evolves.

We distinguish among several types of information:

Software licenses govern the use, modification, and distribution of software under their respective terms.
Copyright and attribution notices identify creators, copyright holders, and sources.
Service acknowledgments identify external services used to develop, build, host, or operate the project.
Trademark acknowledgments identify names and marks belonging to their respective owners.
Other third-party resources may include datasets, images, fonts, container images, AI models, and other materials.

This page is intended to support transparency and responsible reuse. It does not replace the full text of applicable licenses, service agreements, or other legal terms. Nor does it, by itself, establish that every licensing obligation associated with every component has been satisfied.

0. Naming

Founder Mark Daniel Ward received an inspiring email on Thursday, 1 October 2026. Mark’s colleague said:

We immensely appreciate you and the amazing things you’ve built, the many talented engineers and scientists you’ve prepared and equipped!

I’m so inspired by your example, very much in alignment with this wild-eyed coaching question: "what would you do, if you knew you could not fail?" Thank you for daring greatly, my friend. Your big vision is worth it!"

At the time, Mark had not (yet) encountered this question before. Mark had been searching for a name for a collaborative website. Almost immediately, Mark purchased whatwouldyoudo.org without looking up the original source of this question.

Upon further investigation, Mark learned that Robert Harold Schuller had asked this question numerous times, in various forms, over a period of several decades.

The WWYD team is thankful for this inspiring question. The WWYD team’s work is neither affiliated with nor endorsed by the Schuller family.

1. Website Generation and Presentation

Antora Site Generator

Purpose: Antora generates the WWYD website from AsciiDoc content, configuration files, and content organized across Git repositories.

Official website: Antora

Source repository: Antora source code

License: Mozilla Public License, version 2.0 (MPL-2.0).

Full license text: Mozilla Public License 2.0

Official copyright and license information: Antora copyright and license documentation

Use in this project: Antora is used to assemble and generate the WWYD website.

Relationship to the user interface: The Antora site generator is distinct from the Antora Default UI, which is documented separately below.

The Antora project and its contributors retain their applicable rights. The relevant license and notices govern the software covered by that license.

Antora Default UI

Purpose: Provides the foundation for the WWYD website’s user interface, including its layout and presentation.

Original project: Antora Default UI source repository

License: Mozilla Public License, version 2.0 (MPL-2.0).

Full license text: Mozilla Public License 2.0

Source code in this project: The ui/ directory in the main-website repository contains the upstream UI source used to build the website, including WWYD customizations.

Modifications: The Antora Default UI is being customized for WWYD. Modifications to source files covered by the MPL-2.0 are subject to the applicable requirements of that license.

Build process: The UI is built in GitHub Actions using Node.js and npm. The resulting UI bundle is used by Antora when generating the website.

The Antora Default UI and the Antora site generator are separate components. This distinction is reflected in their separate entries on this page.

The UI’s license does not automatically determine the licenses of all third-party packages used to build it. Those dependencies are addressed separately below.

AsciiDoc

Purpose: AsciiDoc is the markup language used to author WWYD website content.

Project website: AsciiDoc

Use in this project: Website pages and navigation content are authored in AsciiDoc and processed by Antora during site generation.

Trademark acknowledgment: AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc., as identified in Antora’s published copyright and license information.

Additional information: Antora copyright, license, and trademark information

This acknowledgment concerns the name of the markup language used by WWYD. It does not imply that the Eclipse Foundation sponsors, endorses, or is affiliated with WWYD.

2. Software Build and Development Tools

Node.js

Purpose: Node.js provides the JavaScript runtime used by the automated build process for the Antora Default UI.

Official website: Node.js

Source repository and license information: Node.js source repository

Use in this project: The GitHub Actions workflow installs Node.js and uses it to run the UI’s build tooling.

Licensing: Node.js includes software distributed under its own license, as well as externally maintained components with their own licensing terms. The applicable license and third-party notices should be consulted for the version used.

This acknowledgment identifies a build tool used by the project. It does not imply that Node.js is incorporated into every published website file or that all components of Node.js share a single license.

npm

Purpose: npm is used to install the dependencies needed to build the Antora Default UI.

Official website: npm

Documentation: npm documentation

Official license information: npm license and additional terms

Use in this project: The automated workflow runs npm ci to install the dependencies recorded in the UI’s lockfile and then invokes the UI build process.

The npm application has its own published license and additional terms. Packages installed through npm are independently licensed; they are not automatically covered by npm’s license.

npm Package Dependencies

Purpose: The Antora Default UI uses packages that provide functionality required by its build process.

Dependency manifests: The ui/package.json and ui/package-lock.json files in the main-website repository record the declared dependencies and locked package versions.

Use in this project: The GitHub Actions workflow installs these dependencies and builds the customized UI.

Licensing status: A complete license audit of every direct and transitive npm dependency has not yet been documented on this page.

Individual packages may have different licenses, copyright notices, attribution requirements, or redistribution conditions. The MPL-2.0 license of the Antora Default UI should not be assumed to cover every dependency.

The dependency manifests and lockfile provide a starting point for identifying the packages that need to be reviewed. They do not, by themselves, establish that all applicable licensing obligations have been satisfied.

As the project evolves, we intend to review the dependency tree, identify relevant license and notice requirements, and preserve the information needed for responsible redistribution.

3. Source Hosting and Development Services

GitHub

Purpose: GitHub provides source-code hosting and development collaboration infrastructure for WWYD.

Official website: GitHub

Use in this project: WWYD uses GitHub repositories to store and manage website configuration, source code, and content.

GitHub also supports the project’s collaborative development and automated build workflow.

GitHub Desktop: GitHub Desktop is used as a graphical interface for local Git operations.

Acknowledgment: GitHub is identified here as a development and source-hosting service.

This acknowledgment is not an assertion that GitHub requires WWYD to publish its original code or content under a particular license. The terms applicable to GitHub services are distinct from the licenses governing individual software components and WWYD-authored materials.

GitHub’s name and product names identify the services used by the project. This acknowledgment does not imply sponsorship or endorsement.

GitHub Actions

Purpose: GitHub Actions automates the website’s build and deployment workflow.

Official documentation: GitHub Actions documentation

Use in this project: The WWYD workflow runs in GitHub Actions. It checks out the website repository, obtains the necessary repository access, sets up Node.js, installs UI dependencies, builds the customized UI, generates the Antora website, and executes the configured deployment steps.

Configuration: The workflow is defined in .github/workflows/deploy.yml in the main-website repository.

Acknowledgment: GitHub Actions is a hosted automation service used in the project’s development and publication process. It is not treated here as a single software package incorporated into the published website.

4. Hosting and Deployment Infrastructure

Cloudflare

Purpose: Cloudflare provides infrastructure used in the publication and operation of the WWYD website.

Official website: Cloudflare

Developer documentation: Cloudflare developer documentation

Use in this project: The WWYD deployment configuration includes Cloudflare-related configuration and deployment steps. The specific services involved should be understood in the context of the active deployment configuration and the services enabled for the domain.

Acknowledgment: Cloudflare is identified as an infrastructure provider. This acknowledgment does not imply that Cloudflare licenses WWYD’s original content or unrelated third-party software.

Trademark information: Cloudflare trademark guidelines

Cloudflare’s name is used to identify the provider and its services. This acknowledgment does not imply sponsorship, endorsement, or an affiliation beyond the services actually used.

The terms applicable to Cloudflare services govern their use. A service acknowledgment does not replace those terms or the licenses applicable to separately incorporated software.

5. Website Repositories and Content

WWYD organizes its website and content across Git repositories. The licensing status of a repository, or of an individual file within it, should not be inferred solely from its public availability.

Main Website Repository

Purpose: Contains the central Antora playbook, website configuration, navigation, page content, custom UI source, and automated build and deployment workflow.

Repository: WWYD main-website repository

Licensing distinction: The repository contains third-party software and original project material. The applicable license for each component depends on its origin and licensing terms.

The presence of a file in this repository does not mean that every file is governed by the same license.

Community Content Repository

Purpose: Provides community-oriented content incorporated into the Antora website.

Repository: WWYD community repository

Licensing distinction: Original WWYD community content and incorporated third-party material may have different rights holders and licensing terms.

The applicable license for original community content should be stated in the relevant repository or content where appropriate. Public availability does not, by itself, establish permission for unrestricted reuse.

As additional content repositories are introduced, we intend to document their purpose, provenance, applicable licenses, and any incorporated third-party material.

6. Original WWYD Code and Content

WWYD may contain original software, documentation, educational material, research, community contributions, and other content created specifically for the project.

The licensing status of original WWYD material is distinct from the licenses governing third-party tools, libraries, and services.

This page does not establish a blanket license for original WWYD code, documentation, artwork, or other content.

As the project develops, we intend to clarify the licensing of original contributions where appropriate. Different categories of material, such as software, documentation, and community contributions, may warrant different licensing choices.

Any future license statement should identify:

The material covered by the license.
The copyright holder or party authorized to license it.
The specific license and version.
Any exclusions for third-party material.
The location of the full license text and any required notices.

Third-party licenses continue to apply to their respective components regardless of the licensing chosen for original WWYD material.

7. Future Third-Party Components

WWYD may incorporate additional software, services, datasets, container images, AI models, fonts, icons, illustrations, and other resources.

As these components are adopted, we intend to document their origins and applicable terms where appropriate. The following subsections describe the information we intend to track; they are not assertions that every category listed is already incorporated into the website.

Container Images and Base Images

For container images used or distributed by WWYD, we intend to record, where applicable:

Image name and publisher.
Image version, tag, or immutable digest.
Source repository and official project page.
Base image and significant inherited components.
Applicable licenses and copyright notices.
Source-availability information where required.
Redistribution conditions, attribution requirements, and relevant restrictions.

A container image may contain many independently licensed components. The license associated with an image publisher or base image should not be assumed to cover every component inside the image.

Python Packages and Other Software Libraries

For additional software dependencies, we intend to record, where appropriate:

Package name and version.
Original project and source repository.
License identifier and link to the license text.
Direct or transitive dependency status.
Required copyright or attribution notices.
Relevant source-availability and redistribution requirements.

Dependency manifests and lockfiles can support this work, but they do not replace reviewing the applicable license terms and notices.

Artificial Intelligence Models and Services

For AI models and services used in WWYD software, research, or community activities, we intend to document, as applicable:

Model or service name and provider.
Version or model identifier.
Official source and documentation.
Applicable model license, usage terms, or service agreement.
Attribution and redistribution conditions.
Restrictions on use, modification, hosting, or distribution.
Relevant data provenance and other conditions associated with model use.

Terms such as open source, open weights, and publicly available are not interchangeable. We intend to identify the actual license or terms applicable to each model or service rather than infer permissions from its availability.

Datasets and Research Resources

For datasets and other research materials, we intend to record:

Original source and creator, where known.
Dataset name and version or date.
Applicable license or terms of use.
Attribution and citation requirements.
Conditions governing access, redistribution, and derivative works.
Privacy, confidentiality, or other restrictions that affect use.

A dataset being accessible on the internet does not necessarily mean that it can be redistributed or used without restriction.

Fonts, Icons, Images, and Other Media

For externally sourced visual or media assets, we intend to record, as appropriate:

Asset name and original creator.
Source and version.
Applicable license or permission.
Required attribution or credit.
Restrictions on modification, commercial use, or redistribution.

Assets obtained from different sources may have different licensing terms, even when they are used together on the same page.

Code Examples and Adapted Material

When code, documentation, or other material is copied or adapted from a third-party source, we intend to identify the original source and preserve applicable notices.

Where appropriate, the record should explain which portions were adapted and identify the license governing the original material.

A citation to the source is good practice, but attribution alone does not necessarily satisfy the conditions of a software license or other permission.

8. License and Provenance Documentation Practices

To support transparency and maintainability, we intend to follow these practices as the project evolves.

Identify the source. Record the original project, creator, publisher, or provider whenever reasonably possible.
Record versions. Identify the version or release used when that information is available and relevant.
Identify applicable terms. Link to the authoritative license, terms of use, or permission governing the component.
Preserve notices. Retain copyright notices, license texts, and other notices required by applicable terms.
Track modifications. Record meaningful modifications to third-party software when relevant to licensing or provenance.
Distinguish software from services. Avoid describing a hosted service as though it were a single software dependency or assuming that service use imposes an attribution requirement.
Review dependencies. Periodically examine dependency manifests and lockfiles for licensing and security considerations.
Document exceptions. Record components with custom terms, restrictions, unclear provenance, or unresolved licensing questions.
Update the record. Revisit entries when versions, dependencies, hosting arrangements, or project uses change.

These practices are intended to make our use of third-party resources more transparent. They do not guarantee that every possible licensing issue has been identified or resolved.

9. Scope and Limitations

This page is an evolving record of third-party components and services known to be relevant to WWYD.

It is not necessarily a complete inventory of every dependency, transitive package, system utility, hosted service, or other resource involved in building or operating the website.

In particular:

A service acknowledgment does not mean that the provider requires public attribution.
An attribution does not replace a required license notice or other license condition.
A link to a license does not, by itself, demonstrate compliance with every requirement of that license.
The license of one component does not automatically govern other components used alongside it.
Public availability does not automatically grant permission to reproduce, modify, or redistribute material.
The absence of an entry should not be interpreted as confirmation that a component has no applicable licensing requirements.

Where a component’s licensing or provenance is uncertain, we intend to investigate it and update this page as appropriate.

This page provides general project information and is not legal advice.

10. Acknowledgment

We are grateful to the developers, maintainers, researchers, designers, and communities whose work supports open technologies and collaborative knowledge creation.

We aim to acknowledge that work accurately, preserve the notices and permissions that apply, and make it easier for visitors to discover the origins of the resources on which WWYD depends.

As the project grows, this page will grow with it.