​
Open Source Distribution

Custom Fields is now open source! The source code is publicly available on GitHub under the AGPL-3.0 license.

​
Source Code Access

  • GitHub Repository: The complete source code is available at github.com/relaticle/custom-fields
  • License: AGPL-3.0 for open source use
  • Packagist: Available via Composer as relaticle/custom-fields

​
Distribution Guidelines

​
Open Source Projects (AGPL-3.0)

When using Custom Fields under the AGPL-3.0 license:

✅ You CAN:

  • Use Custom Fields in your open source projects
  • Modify and extend the codebase
  • Distribute your applications that use Custom Fields
  • Fork and create derivative works

⚠️ You MUST:

  • Keep your project open source under AGPL-3.0
  • Provide access to your source code
  • Include the AGPL-3.0 license
  • Preserve copyright notices
  • Document any changes you make

​
Commercial Projects

When using Custom Fields under a Commercial License:

✅ You CAN:

  • Use Custom Fields in closed-source applications
  • Modify the code without publishing changes
  • Distribute your application without source code
  • Keep your proprietary code private

❌ You CANNOT:

  • Redistribute the Custom Fields source code itself
  • Resell Custom Fields as a standalone product
  • Remove copyright or license notices
  • Share your commercial license with others

​
Contributing

We welcome contributions from the community!

​
How to Contribute

  1. Fork the repository on GitHub
  2. Create a feature branch for your changes
  3. Submit a pull request with a clear description
  4. Sign the CLA (Contributor License Agreement) if required

​
Contribution Guidelines

  • Follow the existing code style and conventions
  • Write tests for new features
  • Update documentation as needed
  • Keep pull requests focused and atomic

By contributing to Custom Fields, you agree that your contributions will be licensed under the same dual license model (AGPL-3.0 + Commercial).

​
Third-Party Packages

If you create packages or extensions for Custom Fields:

  • Open source packages: Must be AGPL-3.0 compatible
  • Commercial packages: Require end-users to have appropriate Custom Fields license
  • Always clearly state the licensing requirements

​
Questions?

For questions about code distribution, licensing, or contributing:

  • Email: customfieldsnext@gmail.com
  • GitHub Issues: For technical questions and bug reports
  • Documentation: Check our comprehensive docs first