Create "Drips License"

[KeyTamer]

Suggestion:

The "Drips License" should be an open-source software license designed to align with the Drips philosophy. This license should incorporate the following key elements:

Drip List Requirement: Users of software under the Drips License must include the project or its maintainers on a Drip List and allocate a specified percentage of funds or contributions to support the project, as defined by the Drips protocol.

Terms: In the process of creating this license, we should consider different variants of terms.

Ideas for Terms:

Set Percentage: Users can choose to allocate a fixed percentage of funds or contributions to the project, ensuring a consistent level of support.
Percentage in Relation to Code: Alternatively, users may opt for a percentage tied to the amount of code or specific features they utilize. This approach reflects a proportional contribution to the project's development.
Percentage Based on Hours Spent Developing: For contributors or organizations heavily involved in the project's development, a percentage based on the number of hours spent developing, reviewing, or maintaining the codebase may be a suitable option. This approach recognizes the value of direct labor contributions.

Purpose:
The purpose of creating the "Drips License" is to establish a clear and concise licensing framework for projects wishing to earn tokens through Drips or any other splitting contract. This license aims to enable any developer to put their work under a sustainable FOSS License.

License Draft:

Drips License

Permission is hereby granted, free of charge, to any person or organization obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software with the following conditions:

Drip List Requirement: The User agrees, as a condition of using this software, to include the Maintainer or the project on a Drip List, as defined by the Drips protocol, and allocate [X%] of any funds or contributions they make to support the Software.

Integration with Drips Protocol: The User acknowledges and agrees that this License is designed to integrate with the Drips protocol. The User shall take reasonable steps to ensure compliance with the Drip List requirement as outlined in the Drips protocol.

Redistributions of source code or any modifications to the Software must be accompanied by this License.

The Software is provided "as is," without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and non-infringement. The User uses the Software at their own risk.

In no event shall the Maintainer be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Software or the use or other dealings in the Software.

The above conditions and the Drip List requirement are subject to the Drips protocol, and this License shall be governed by and construed in accordance with the laws of [Jurisdiction].

[gh0stwheel]

Hey @KeyTamer -- this is a really neat idea! @lftherios and I have done some research into this type of FOSS licensing in the past and we both believe that there's a lot of potential there, with some significant challenges as well.

Would you be interested in hopping on a video call with us to brainstorm and discuss these ideas more?

If so, is there a day next week where you could meet sometime between 3pm - 5pm CET? Let me know and I can drop a link to a video chat here.

If you would prefer you can also find us in the Drips discord server and we can continue the conversation async there https://discord.gg/r8eJssZY3f