The Enthusiast Coder License (EnCL)

Introduction

The Enthusiast Coder License (EnCL) was born from a simple reality: not everyone who writes and shares code is a professional developer. Many of us are business professionals, enthusiasts, and hobbyists who code because we love it, want to solve problems, or simply enjoy creating things. EnCL provides a framework for sharing this code honestly and openly.

License Comparison

Feature	MIT	Apache 2.0	GPL 3.0	BSD	EnCL
Free to use	✓	✓	✓	✓	✓
Commercial use allowed	✓	✓	✓	✓	✓
Must include license	✓	✓	✓	✓	✓
Can modify code	✓	✓	✓	✓	✓
Patent protection	-	✓	✓	-	-
Private use	✓	✓	✓	✓	✓
Share modifications	Optional	Optional	Required	Optional	Encouraged
Derivatives can use other licenses	✓	✓	-	✓	✓
Clear support expectations	-	-	-	-	✓
Explicit hobbyist context	-	-	-	-	✓
Support/maintenance commitment	-	-	-	-	Clearly None

When to Choose EnCL

Perfect For:

1. Startup and Business Prototypes

   • Proof-of-concept tools
   • Internal tools made public
   • MVP projects
   • Experimental features

2. Side Projects

   • Weekend projects
   • Personal tools
   • Learning experiments
   • Utility scripts

3. Professional's Hobby Code

   • Marketing tools
   • Business automation scripts
   • Data analysis tools
   • Workflow improvements

4. Learning Projects

   • Portfolio pieces
   • Tutorial outcomes
   • Educational projects
   • Skill demonstrations

Choose Another License When:

1. You need patent protection (Use Apache 2.0)
2. You're releasing official company software (Use MIT/Apache)
3. You need enterprise-grade legal protection (Use Apache 2.0)
4. You want maximum simplicity with minimal terms (Use MIT)
5. You need to legally enforce open source requirements (Use GPL)

Note: EnCL strongly supports and encourages open source development, but provides flexibility for derivative works to choose their own licensing path. This allows for broader adoption and use cases while still encouraging community contribution through other means.

Quick Start Guide

README.md Template

Here's a template for your project's README.md:

# Your Project Name

[Brief project description]

[![EnCL Licensed](https://img.shields.io/badge/License-EnCL-0291db.svg)](LICENSE.md)

## About This Project

This is a hobby/enthusiast project created to [your purpose here]. As an EnCL-licensed project:
- It's provided as-is without guaranteed support
- Updates and improvements happen based on author availability and interest
- Contributions and feedback are welcome
- Commercial use is allowed with attribution

## Getting Started

[Your setup instructions]

## Usage

[Your usage instructions]

## Contributing

Contributions are welcome! Please read the [contributing guidelines](CONTRIBUTING.md).

## License

This project is licensed under the Enthusiast Coder License (EnCL) - see the [LICENSE.md](LICENSE.md) file for details.

## Acknowledgments

[Your acknowledgments]

Using EnCL-Licensed Code

1. Review attribution requirements
2. Include proper credits
3. Document any modifications
4. Respect support limitations
5. Consider contributing improvements

Attribution Examples

In README.md

This project uses code from [Project Name] by [Author Name] (link to repository),
licensed under the Enthusiast Coder License (EnCL).

Modified components:
- Component A: Added feature X
- Component B: Optimized for Y

In Source Code

# This code includes work from [Project Name] by [Author Name]
# Original repository: [URL]
# Licensed under EnCL
# Modifications: [Brief description of changes]

In User Interface

<div class="about">
  <p>This application uses components from [Project Name] by [Author Name]</p>
  <p>Licensed under EnCL</p>
</div>

Commercial Product Template

[Product Name] incorporates code from [Project Name] by [Author Name], 
licensed under the Enthusiast Coder License (EnCL). The original code 
can be found at [repository URL]. While the original code is provided 
without warranty or support, [Your Company] provides full support for 
our implementation and modifications.

FAQ

General

Q: Why was EnCL created? A: To provide a license that honestly reflects the reality of hobby coding and sets clear expectations about support and maintenance.

Q: Can I use EnCL code commercially? A: Yes! Commercial use is allowed with proper attribution. Users are encouraged to support the open source community when deriving significant value.

Q: What makes EnCL different from other licenses? A: EnCL explicitly acknowledges the hobby/enthusiast nature of the code and sets clear expectations about support and maintenance.

License Details

Q: Can I change the license for my modifications? A: Yes, derivative works can use different licenses. The original code remains under EnCL.

Q: Can the original author change the license? A: Yes, for future versions. Existing versions remain under their original license terms permanently.

Q: Does EnCL require sharing modifications? A: No, but it's encouraged. You can keep modifications private or release them under different licenses.

Commercial Use

Q: Do we need to pay to use EnCL code? A: No, but if you derive significant commercial value, considering some form of giving back to the community is encouraged.

Q: Can we offer professional support for EnCL code? A: Yes! While the original author provides no guaranteed support, you can offer professional support for your implementation.

Best Practices

For Original Authors

1. Clear Communication

   • State the project's hobby nature
   • Document known limitations
   • Set support expectations
   • Provide usage examples

2. Documentation

   • Basic setup instructions
   • Known issues
   • Usage limitations
   • Contribution guidelines

3. Maintenance

   • Be clear about response times
   • Document your update process
   • Explain how you handle issues
   • Set realistic expectations

For Users

1. Before Using

   • Evaluate code thoroughly
   • Plan for self-maintenance
   • Document modifications
   • Respect project limitations

2. Contributing Back

   • Share improvements when possible
   • Report issues clearly
   • Provide complete information
   • Be patient with responses

For Commercial Users

1. Integration

   • Thorough testing
   • Clear attribution
   • Document modifications
   • Plan for maintenance

2. Community Support

   • Consider giving back
   • Share improvements
   • Acknowledge value
   • Support open source

The Spirit of EnCL

EnCL embodies several core principles:

1. Honesty

   • Clear about limitations
   • Transparent about support
   • Open about hobby nature

2. Community

   • Encouraging sharing
   • Supporting learning
   • Building connections
   • Fostering improvement

3. Fair Play

   • Proper attribution
   • Reasonable expectations
   • Mutual respect
   • Encouraging support

Future Considerations

1. Community Growth

   • EnCL project directories
   • Best practices evolution
   • Support networks
   • Knowledge sharing

2. Platform Integration

   • Development tools
   • Attribution automation
   • Community features
   • Usage tracking

Conclusion

EnCL bridges the gap between traditional licenses and the reality of hobby coding in today's world. It provides a framework for honest sharing while protecting both creators and users through clear expectations and guidelines.

Remember: EnCL is about making code sharing more accessible and honest for everyone who codes for the love of it.