Jarek, I expect I know the answer to this but do any of your sponsors require (or even request) that you mention them in the project web site or in the README?
What you are doing sounds fine to me simply because the agreement you have doesn’t obligate the PMC to anything. Tidelift’s business model is to generate funding for open source by getting commercial users to pay Tidelift to support open source projects. Tidelift doesn’t seem to have any developers of its own so it shares a portion of he money it gets with projects so it can add them to its catalog of supported projects. In some ways this could be a win-win-win scenario, if it actually accomplishes something. Ralph > On Jan 12, 2022, at 8:57 AM, Jarek Potiuk <ja...@potiuk.com> wrote: > > Fascinating discussion. My understanding is exactly what Jim explained. > > I also can explain how it works for me as an individual in Apache > Airflow. Apache Airflow has multiple stakeholders and I have regular > contracts with a few of them: Google, Astronomer. Also I got a > one-time GitHub Sponsorship from AWS. Each contract covers part of my > time. > > * The sponsorship was without any expectations. > * The contracts I have are mostly about "We do not oblige you to do > this and that. Those are our priorities for next year or so and we > would like you to focus on as an individual for part of your time, but > we are well aware the community makes decisions and nothing can be > done without community rules being followed. We understand that and > expect you to follow the rules." (not the exact wording but that's the > "gist" of it). > > I also do a lot of contributions in my "own" time so to speak which > cover much broader scope and project needs and other initiatives (If I > were to calculate it with regular rates) - and I treat seriously the > disclaimer that was mentioned in the Legal part of the discussion (I > believe Justin pointed to that). > > Those are my own private agreements with the stakeholders, PMC members > are aware of those (I am very transparent with that as you see), but > it has nothing to do with the PMC nor ASF.. > > I believe if Tidelift were to arrange similar contracts with whoever > are the people with "merit" in the project, they should be free to do > that - with similar conditions. > > J. > > On Wed, Jan 12, 2022 at 4:56 PM Sam Ruby <ru...@intertwingly.net> wrote: >> >> On Tue, Jan 11, 2022 at 4:50 PM Ralph Goers <ralph.go...@dslextreme.com> >> wrote: >>> >>> Hello all, >>> >>> Recently the Logging Services PMC was approached by Tidelift offering to >>> provide monetary support either to the project or individual committers. To >>> obtain that sponsorship the project has to agree to the terms at >>> https://support.tidelift.com/hc/en-us/articles/4406309657876-Lifter-agreement. >>> It appears that Struts has accepted this already. >> >> Perusing the agreement, I see talk of payment, license, and trademark. >> So let's cover that, and the topic we want to cover, the Apache Way. >> >> Let's be welcoming and friendly, and focus more on what they need to >> do, rather than on what they must not do >> >> Outline: >> >> * So you want to pay a contributor? Great! If that is something you >> wish to do, do so directly with each contributor as this is not a >> service the ASF provides. Just make sure that each contributori is >> aware of each of the five points listed on The Apache Way page[1]. In >> particular, be aware that each individual contribution will be >> evaluated on its merits and require consensus before being accepted. >> >> * All code must be licensed only under the Apache Software License, >> with no additional conditions. Should an individual contributor >> become a committer, they will be required to sign an ICLA. You are >> welcome to sign a CCLA. >> >> * You are welcome to make nominative use of our trademarks. If you >> require anything more, see out Trademark Policy[2]. >> >> [1] https://www.apache.org/theapacheway/ >> [2] https://www.apache.org/foundation/marks/ >> >> - Sam Ruby >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
