Skip to content

Latest commit

 

History

History
35 lines (21 loc) · 2.19 KB

PACKAGING.md

File metadata and controls

35 lines (21 loc) · 2.19 KB
Raw

Packaging Guidelines for Daytona

The Daytona team appreciates any efforts to make our software more accessible to users on various platforms. While we encourage packaging and distribution of our open-source project, we have some important guidelines, particularly regarding naming.

Critical Naming Guideline

Important: While you are free to package and distribute our software, you MUST NOT name your package daytona or, in any way, suggest that, the package you distribute, is an official distribution of daytona. This restriction is to prevent confusion and maintain the integrity of our project identity.

  • Acceptable: "unofficial-daytona-package", "unofficial-daytona-distribution", etc.
  • Not Acceptable: "daytona", "official-daytona", etc.

General Guidelines

  1. License Compliance: Ensure that the Apache 2.0 license is included with the package and that all copyright notices are preserved.

  2. Version Accuracy: Use the exact version number of Daytona that you are packaging. Do not modify the version number or add custom suffixes without explicit permission.

  3. Dependencies: Include all necessary dependencies as specified in our project documentation. Do not add extra dependencies without consulting the project maintainers.

  4. Modifications: If you need to make any modifications to the source code for packaging purposes, please document these changes clearly and consider submitting them as pull requests to the main project.

  5. Standard Note: Please include the following standard note in your package description or metadata:

    This package contains an unofficial distribution of Daytona, an open source project 
developed by Daytona Platforms Inc. This package is not officially supported or endorsed 
by the Daytona project. For the official version, please visit https://github.com/daytonaio/daytona.

Feedback and Questions

If you have any questions about packaging Daytona or need clarification on these guidelines, especially regarding naming conventions, please open an issue in our GitHub repository.

We appreciate your contribution to making Daytona more accessible to users across different platforms, while respecting our project's identity!