Re: How to get started with contribution
Hi Maxim! On Wed, Jan 12, 2022 at 3:51 AM Maxim Solodovnik wrote: > Hello All, > > Should I change my semi-automatic-answer? :) > Maybe add section or correct some wording? :) > 1st of all, nothing wrong at all regarding your semi-automatic-answer (using your own words :) ). On the contrary I do really thank you that you have the patience to keep responding to such emails in a friendly way and that you, in a good way, directing the senders to the right places. It is more about the root cause or the reason behind them keep sending to mentors@ which, IMHO, it can mean 1 of 2 things: - Either they get lost going through the Apache Community Development website - and/or the information is not clear enough For that I believe, and as sebb suggested which I agree with, making clear what channel(s) of communication to use, when and in what context, can help the sender directing them to the right place(s) from the very beginning. We still keep your friendly semi-automatic-answer as a last rest :D May I suggest something. How about you and I go through the Apache Community Development website, collect such content and cross check with each other as a sort of peer-review ? What are your thoughts about that ? > On Wed, 12 Jan 2022 at 08:23, Mohammad Noureldin > wrote: > > > > Hi, > > > > sebb, good idea! > > > > I will go through the Apache Community Development website, list all > emails > > with when to use and in what context as the content for that > section/page. > > > > On Wed, Jan 12, 2022 at 1:05 AM sebb wrote: > > > > > On Tue, 11 Jan 2022 at 23:54, Mohammad Noureldin > > > wrote: > > > > > > > > Hi, > > > > > > > > I've followed up on some of these emails that have been sent to > mentors@ > > > > asking the senders to give us feedback on where on the Apache > Community > > > > Development website [1] they have found that they need to/should > send an > > > > email to mentors@. > > > > > > > > IMHO we better 1st understand that before creating another mailing > list. > > > It > > > > could be that we only need to rephrase some information on that > website > > > or > > > > make it more clear where they should go with their > questions/inquiries. > > > > > > Maybe have a single section with all email addresses and what their > > > purpose is. > > > > > > If an email address is mentioned in isolation, the temptation is to > > > just use that without reading the surrounding text carefully. > > > And even if the list does not appear to be quite right, if one has not > > > found any other address then one might assume it is OK to use. > > > > > > When the addresses are listed together, it's much easier to choose the > > > correct list. > > > > > > > [1] https://community.apache.org > > > > > > > > > > > > On Tue, Jan 11, 2022 at 8:37 PM Paulo Motta < > pauloricard...@gmail.com> > > > > wrote: > > > > > > > > > Hi everyone, > > > > > > > > > > I would like to follow-up on this topic, given the recent student > > > seeking > > > > > GSoC information in the mentors list >. > > > > > > > > > > I would like to hear your opinions on creating a mixed student and > > > mentors > > > > > list for ASF-wide mentors to advertise > > > > > projects > > > > > to potentially interested students, as well as taking general > questions > > > > > about ASF participation in GSoC. > > > > > > > > > > If there's interest I can volunteer to set up the list with ASF > Infra, > > > and > > > > > work with Maxim to set it as a point of contact in ASF's GSoC page > (< > > > > > > > > > > > > > > https://summerofcode.withgoogle.com/archive/2021/organizations/5149287498907648 > > > > > >). > > > > > > > > > > Kind regards, > > > > > > > > > > Paulo > > > > > > > > > > > > > > > > > > > > Em sex., 19 de nov. de 2021 às 13:32, sebb > > > escreveu: > > > > > > > > > > > On Fri, 19 Nov 2021 at 15:19, Paulo Motta < > pauloricard...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > > Would it not be better to point to students@ ? > > > > > > > > > > > > > > Perhaps not if we want mentors to have visibility of > prospective > > > > > > students, since that list is restricted only to students afaik. > > > > > > > > > > > > There have not been many posts [1], but they are publicly > archived so > > > > > > I doubt it is restricted to students. It was created in June > 2013 [2] > > > > > > > > > > > > If the list name were promoted on the webpage it might help to > revive > > > > > > the list, otherwise it should perhaps be shut down. > > > > > > > > > > > > Sebb > > > > > > [1] https://lists.apache.org/list?stude...@community.apache.org > > > > > > [2] https://issues.apache.org/jira/browse/INFRA-6397 > > > > > > > > > > > > > Em sex., 19 de nov. de 2021 às 12:04, sebb > > > > > escreveu: > > > > > > >> > > > > > > >> On Fri, 19 Nov 2021 at 13:38, Paulo Motta < > > > pauloricard...@gmail.com> > > > > > > wrote: > > > > > > >> > > > > > > > >> > Good call Hans - I guess we should make that point to > > > dev@community > > > > >
Re: Tidelift
IMO, the foundation and the project should do nothing associated with this. It should neither encourage or condone it. In no way should we enter into any agreement, contract, whatever, w/ Tidelift. If Tidelift wishes to work independently and directly w/ people, that's fine. But having the ASF and/or the project involved at any level should be disallowed. We cannot also ignore the obvious self-serving nature of the request by Tidelift and if we are comfortable with them using this as an opportunity for promotion. > On Jan 11, 2022, at 4:49 PM, Ralph Goers 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. > > Some PMC members are interested in pursuing this but I am questioning a) > whether the agreement conflicts with ASF practices and b) whether the legal > agreement is too ambiguous. Two ASF members commented on the Logging Services > private list that they had concerns about the agreement. > > In response to these concerns I created > https://issues.apache.org/jira/browse/LEGAL-593. The guidance there seemed to > be that payment to the ASF by Tidelift would not be allowed but payment to > individuals might be. No guidance on the agreement was provided. It was > recommended I post here instead. > > In looking for more clarification from Tidelift about their agreement and who > could receive payment we received this response: > >Great follow up question, you are spot on. Each of the individuals on > the team page could become a lifter and the funds allocated for Log4j would > be split between them. > >Additional pieces of information to add nuance: > >* For someone to _start_ lifting a project with Tidelift, the > verification process involves us looking to official sources for > confirmation–such as the team page. After a project is lifted, the > verification process ultimately hinges on open communication between us and > whichever lifter has been nominated to be the primary contact (in full view > of all of the project's lifters so that we know there's shared agreement). > >* Funds can be split any way you see fit, evenly or otherwise. In most > cases, we see an even split. In cases where the funds are directed back to a > foundation, 100% of the funds go to the foundation and the share assigned to > the lifters is 0%. > >* This approach has allowed us to decouple any individual project's > governance from our own processes, and has proven to be effective in many > different contexts. As we grow, it may well be that our processes need to > evolve, so that's a conversation that I'm open to as we continue discussing > :o) > > So it is clear to me that Tidelift requires the project as a whole to approve > the agreement, even though only select individuals may choose to receive > payment, especially since one of the requirements is a public acknowledgment > of Tidelift on one of the project’s sites. > > I find this problematic as I cannot reconcile how it is OK for individuals to > receive payment so that the ASF is not officially involved while at the same > time the PMC must approve the agreement for individuals to be able to accept > payment. Furthermore, I still have no idea whether the terms of the agreement > would put a PMC in conflict with ASF policies or whether the ambiguities in > the agreement would put the ASF in a bad place. I realize the ASF’s argument > would be “We have nothing to do with this” but I suspect that wouldn’t fly > since the PMC has to agree to it. > > To be clear, I have no idea if this is the correct place to discuss this. > Personally, I was under the impression that a Legal Jira was where this kind > of stuff got resolved. But here I am. > > Thoughts? > > Ralph > > > > - > 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
Re: Tidelift
I agree that people should handle their affairs as they see fit RE Tidelift but how should this be allowed to trickle in on Apache WRT mentions in web sites and files like readme. IOW, should structs assets remove mentions of Tidelift? Gary On Wed, Jan 12, 2022, 08:52 Jim Jagielski wrote: > IMO, the foundation and the project should do nothing associated with > this. It should neither encourage or condone it. In no way should we enter > into any agreement, contract, whatever, w/ Tidelift. If Tidelift wishes to > work independently and directly w/ people, that's fine. But having the ASF > and/or the project involved at any level should be disallowed. > > We cannot also ignore the obvious self-serving nature of the request by > Tidelift and if we are comfortable with them using this as an opportunity > for promotion. > > > On Jan 11, 2022, at 4:49 PM, Ralph Goers > 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. > > > > Some PMC members are interested in pursuing this but I am questioning a) > whether the agreement conflicts with ASF practices and b) whether the legal > agreement is too ambiguous. Two ASF members commented on the Logging > Services private list that they had concerns about the agreement. > > > > In response to these concerns I created > https://issues.apache.org/jira/browse/LEGAL-593. The guidance there > seemed to be that payment to the ASF by Tidelift would not be allowed but > payment to individuals might be. No guidance on the agreement was provided. > It was recommended I post here instead. > > > > In looking for more clarification from Tidelift about their agreement > and who could receive payment we received this response: > > > >Great follow up question, you are spot on. Each of the > individuals on the team page could become a lifter and the funds allocated > for Log4j would be split between them. > > > >Additional pieces of information to add nuance: > > > >* For someone to _start_ lifting a project with Tidelift, the > verification process involves us looking to official sources for > confirmation–such as the team page. After a project is lifted, the > verification process ultimately hinges on open communication between us and > whichever lifter has been nominated to be the primary contact (in full view > of all of the project's lifters so that we know there's shared agreement). > > > >* Funds can be split any way you see fit, evenly or otherwise. In > most cases, we see an even split. In cases where the funds are directed > back to a foundation, 100% of the funds go to the foundation and the share > assigned to the lifters is 0%. > > > >* This approach has allowed us to decouple any individual > project's governance from our own processes, and has proven to be effective > in many different contexts. As we grow, it may well be that our processes > need to evolve, so that's a conversation that I'm open to as we continue > discussing :o) > > > > So it is clear to me that Tidelift requires the project as a whole to > approve the agreement, even though only select individuals may choose to > receive payment, especially since one of the requirements is a public > acknowledgment of Tidelift on one of the project’s sites. > > > > I find this problematic as I cannot reconcile how it is OK for > individuals to receive payment so that the ASF is not officially involved > while at the same time the PMC must approve the agreement for individuals > to be able to accept payment. Furthermore, I still have no idea whether the > terms of the agreement would put a PMC in conflict with ASF policies or > whether the ambiguities in the agreement would put the ASF in a bad place. > I realize the ASF’s argument would be “We have nothing to do with this” but > I suspect that wouldn’t fly since the PMC has to agree to it. > > > > To be clear, I have no idea if this is the correct place to discuss > this. Personally, I was under the impression that a Legal Jira was where > this kind of stuff got resolved. But here I am. > > > > Thoughts? > > > > Ralph > > > > > > > > - > > 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 > >
Re: Tidelift
On 1/12/22 09:16, Gary Gregory wrote: I agree that people should handle their affairs as they see fit RE Tidelift but how should this be allowed to trickle in on Apache WRT mentions in web sites and files like readme. IOW, should structs assets remove mentions of Tidelift? Yes. The arrangement is (or should be) between Tidelift and individuals, not between Tidelift and the project, or the Foundation. Jim is right here. On Wed, Jan 12, 2022, 08:52 Jim Jagielski wrote: IMO, the foundation and the project should do nothing associated with this. It should neither encourage or condone it. In no way should we enter into any agreement, contract, whatever, w/ Tidelift. If Tidelift wishes to work independently and directly w/ people, that's fine. But having the ASF and/or the project involved at any level should be disallowed. We cannot also ignore the obvious self-serving nature of the request by Tidelift and if we are comfortable with them using this as an opportunity for promotion. On Jan 11, 2022, at 4:49 PM, Ralph Goers 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. Some PMC members are interested in pursuing this but I am questioning a) whether the agreement conflicts with ASF practices and b) whether the legal agreement is too ambiguous. Two ASF members commented on the Logging Services private list that they had concerns about the agreement. In response to these concerns I created https://issues.apache.org/jira/browse/LEGAL-593. The guidance there seemed to be that payment to the ASF by Tidelift would not be allowed but payment to individuals might be. No guidance on the agreement was provided. It was recommended I post here instead. In looking for more clarification from Tidelift about their agreement and who could receive payment we received this response: Great follow up question, you are spot on. Each of the individuals on the team page could become a lifter and the funds allocated for Log4j would be split between them. Additional pieces of information to add nuance: * For someone to _start_ lifting a project with Tidelift, the verification process involves us looking to official sources for confirmation–such as the team page. After a project is lifted, the verification process ultimately hinges on open communication between us and whichever lifter has been nominated to be the primary contact (in full view of all of the project's lifters so that we know there's shared agreement). * Funds can be split any way you see fit, evenly or otherwise. In most cases, we see an even split. In cases where the funds are directed back to a foundation, 100% of the funds go to the foundation and the share assigned to the lifters is 0%. * This approach has allowed us to decouple any individual project's governance from our own processes, and has proven to be effective in many different contexts. As we grow, it may well be that our processes need to evolve, so that's a conversation that I'm open to as we continue discussing :o) So it is clear to me that Tidelift requires the project as a whole to approve the agreement, even though only select individuals may choose to receive payment, especially since one of the requirements is a public acknowledgment of Tidelift on one of the project’s sites. I find this problematic as I cannot reconcile how it is OK for individuals to receive payment so that the ASF is not officially involved while at the same time the PMC must approve the agreement for individuals to be able to accept payment. Furthermore, I still have no idea whether the terms of the agreement would put a PMC in conflict with ASF policies or whether the ambiguities in the agreement would put the ASF in a bad place. I realize the ASF’s argument would be “We have nothing to do with this” but I suspect that wouldn’t fly since the PMC has to agree to it. To be clear, I have no idea if this is the correct place to discuss this. Personally, I was under the impression that a Legal Jira was where this kind of stuff got resolved. But here I am. Thoughts? Ralph - 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..
Re: Tidelift
Over in the Apache HTTPD project, both the HTTP/2 and the new mod_tls modules were paid for by outside entities. That is, this entity wanted these modules to exist, contracted out w/ a 3rd party to write/develop them, and then backed away. There was no guarantee that these modules would even be accepted, that the code would be treated specially or differently, or anything at all like that. At no point was the PMC or the foundation involved at all. The only consideration was that whatever was being donated to the project was, in fact, being donated; that this external work-for-hire was allowed to be, and was intended to be, donated and used by the ASF under the ALv2. If Tidelift wishes to contract out to individuals, it is certainly within its rights and that's 100% A-OK. However, they must be aware that there is no guarantee that any work that the "lifters" provide will be included. There is no way nor guarantee that the lifters are able to direct or manage the project in a way that Tidelift and/or its customers would want. They are not paying for access nor are they paying for guaranteed improvements or inclusion. That must be clear. My understanding of the Tidelift arrangement is that they are providing some sort of assurance that these lifters are not only developing the code, but also "maintaining" it, which implies active, constant and "guaranteed" contribution. Any lifters involved with Apache projects cannot guarantee that. They cannot maintain it anymore, or any less, than anyone else, working within the confines of the project. > On Jan 12, 2022, at 9:16 AM, Gary Gregory wrote: > > I agree that people should handle their affairs as they see fit RE Tidelift > but how should this be allowed to trickle in on Apache WRT mentions in web > sites and files like readme. IOW, should structs assets remove mentions of > Tidelift? > > Gary > > On Wed, Jan 12, 2022, 08:52 Jim Jagielski wrote: > >> IMO, the foundation and the project should do nothing associated with >> this. It should neither encourage or condone it. In no way should we enter >> into any agreement, contract, whatever, w/ Tidelift. If Tidelift wishes to >> work independently and directly w/ people, that's fine. But having the ASF >> and/or the project involved at any level should be disallowed. >> >> We cannot also ignore the obvious self-serving nature of the request by >> Tidelift and if we are comfortable with them using this as an opportunity >> for promotion. >> >>> On Jan 11, 2022, at 4:49 PM, Ralph Goers >> 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. >>> >>> Some PMC members are interested in pursuing this but I am questioning a) >> whether the agreement conflicts with ASF practices and b) whether the legal >> agreement is too ambiguous. Two ASF members commented on the Logging >> Services private list that they had concerns about the agreement. >>> >>> In response to these concerns I created >> https://issues.apache.org/jira/browse/LEGAL-593. The guidance there >> seemed to be that payment to the ASF by Tidelift would not be allowed but >> payment to individuals might be. No guidance on the agreement was provided. >> It was recommended I post here instead. >>> >>> In looking for more clarification from Tidelift about their agreement >> and who could receive payment we received this response: >>> >>> Great follow up question, you are spot on. Each of the >> individuals on the team page could become a lifter and the funds allocated >> for Log4j would be split between them. >>> >>> Additional pieces of information to add nuance: >>> >>> * For someone to _start_ lifting a project with Tidelift, the >> verification process involves us looking to official sources for >> confirmation–such as the team page. After a project is lifted, the >> verification process ultimately hinges on open communication between us and >> whichever lifter has been nominated to be the primary contact (in full view >> of all of the project's lifters so that we know there's shared agreement). >>> >>> * Funds can be split any way you see fit, evenly or otherwise. In >> most cases, we see an even split. In cases where the funds are directed >> back to a foundation, 100% of the funds go to the foundation and the share >> assigned to the lifters is 0%. >>> >>> * This approach has allowed us to decouple any individual >> project's governance from our own processes, and has proven to be effective >> in many different contexts. As we grow, it may well be that our processes >> need to evolve, so that's a conversation that I'm open to as we continue >> discussing :o) >
Re: Tidelift
Hi, On Wed, Jan 12, 2022 at 3:58 PM Jim Jagielski wrote: > Over in the Apache HTTPD project, both the HTTP/2 and the new mod_tls > modules were paid for by outside entities. That is, this entity wanted > these modules to exist, contracted out w/ a 3rd party to write/develop > them, and then backed away. There was no guarantee that these modules would > even be accepted, that the code would be treated specially or differently, > or anything at all like that. At no point was the PMC or the foundation > involved at all. The only consideration was that whatever was being donated > to the project was, in fact, being donated; that this external > work-for-hire was allowed to be, and was intended to be, donated and used > by the ASF under the ALv2. > > If Tidelift wishes to contract out to individuals, it is certainly within > its rights and that's 100% A-OK. However, they must be aware that there is > no guarantee that any work that the "lifters" provide will be included. > There is no way nor guarantee that the lifters are able to direct or manage > the project in a way that Tidelift and/or its customers would want. They > are not paying for access nor are they paying for guaranteed improvements > or inclusion. That must be clear. > > My understanding of the Tidelift arrangement is that they are providing > some sort of assurance that these lifters are not only developing the code, > but also "maintaining" it, which implies active, constant and "guaranteed" > contribution. Any lifters involved with Apache projects cannot guarantee > that. They cannot maintain it anymore, or any less, than anyone else, > working within the confines of the project. > I have 2 questions: 1- How did that work in the case of Apache Struts ? Any details can be shared ? 2- Is the concept of "guarantying" here in the Legal sense ? or is it "guarantying" by approaching the "right individuals" ? By "right individuals" (double quoting is intentional) I mean (P)PMC Members for example. Though they, as mentioned here, can get funded as individuals who don't represent the ASF as an organization nor they represent the target project in any official way, but being a (P)PMC Member (by the definition of the ASF organization itself) show/guarantees that the approached individuals have the merit and the commitment towards that target project, hence guarantying that such funds will be used efficiently or in the right way (I am using 'efficiently' and 'the right way' in their broader sense). But even with that in mind, I believe there is a catch ? If any of those individuals, being (P)PMC member or not, stopped working on the target project for whatever reason, What happens then ? > > On Jan 12, 2022, at 9:16 AM, Gary Gregory > wrote: > > > > I agree that people should handle their affairs as they see fit RE > Tidelift > > but how should this be allowed to trickle in on Apache WRT mentions in > web > > sites and files like readme. IOW, should structs assets remove mentions > of > > Tidelift? > > > > Gary > > > > On Wed, Jan 12, 2022, 08:52 Jim Jagielski wrote: > > > >> IMO, the foundation and the project should do nothing associated with > >> this. It should neither encourage or condone it. In no way should we > enter > >> into any agreement, contract, whatever, w/ Tidelift. If Tidelift wishes > to > >> work independently and directly w/ people, that's fine. But having the > ASF > >> and/or the project involved at any level should be disallowed. > >> > >> We cannot also ignore the obvious self-serving nature of the request by > >> Tidelift and if we are comfortable with them using this as an > opportunity > >> for promotion. > >> > >>> On Jan 11, 2022, at 4:49 PM, Ralph Goers > >> 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. > >>> > >>> Some PMC members are interested in pursuing this but I am questioning > a) > >> whether the agreement conflicts with ASF practices and b) whether the > legal > >> agreement is too ambiguous. Two ASF members commented on the Logging > >> Services private list that they had concerns about the agreement. > >>> > >>> In response to these concerns I created > >> https://issues.apache.org/jira/browse/LEGAL-593. The guidance there > >> seemed to be that payment to the ASF by Tidelift would not be allowed > but > >> payment to individuals might be. No guidance on the agreement was > provided. > >> It was recommended I post here instead. > >>> > >>> In looking for more clarification from Tidelift about their agreement > >> and who could receive payment we received this response: > >>> > >>> Great follow up question, you are spot on. Each of the >
Re: Tidelift
Jim, While I agree with your conclusion I do disagree with how you get there. In your first message you seemed to think that the “self-serving nature” of what Tidelift is doing is any different than what many companies have been doing to the ASF. I am a member of the Flume PMC and my employer uses it as a critical component of our infrastructure, primarily at my doing. I was reluctant to have it graduate from the incubator since the PMC was 90%+ Cloudera employees. Well, Cloudera ghosted the project and many of the PMC members are now former Cloudera employees who, while interested in the project, have no time to spend on it. I view that model and outcome as worse than what Tidelift is proposing. I am now faced with doing a Flume update and release pretty much all on my own, although I am sure there are 3 PMC members active enough to approve the release. Unlike corporate backed projects, Tidelift doesn’t specify any particular development that must be done to qualify for funding. What they require is mostly stuff the ASF already requires - but the agreement is unclear if the ASF requirements are sufficient since the agreement is ambiguous. And, of course, the promotion of Tidelift could be a problem. Someprojects have pages similar to https://activemq.apache.org/support that list places where you can get commercial support. Many have “Thanks” pages to thank companies such as Jetbrains and Yourkit for donating their products to committers. So simply listing a commercial entity on the web site doesn’t seem to be the issue. For me, the issue is that Tidelift is paying developers with the requirement that they follow certain processes, one of which includes an advertisement. On its face I just don’t see how that flies with ASF policies. That said, if the Tidelift model for people to be funded was “Your project must adhere to all ASF process and guidelines AND you must have a minimum of 3 active committers (proven by them actually approving and merging PRs, committing fixes for bugs, etc) and an advertising requirement I might be more inclined to support it since the only real requirement is that the project be active. Ralph > On Jan 12, 2022, at 7:57 AM, Jim Jagielski wrote: > > Over in the Apache HTTPD project, both the HTTP/2 and the new mod_tls modules > were paid for by outside entities. That is, this entity wanted these modules > to exist, contracted out w/ a 3rd party to write/develop them, and then > backed away. There was no guarantee that these modules would even be > accepted, that the code would be treated specially or differently, or > anything at all like that. At no point was the PMC or the foundation involved > at all. The only consideration was that whatever was being donated to the > project was, in fact, being donated; that this external work-for-hire was > allowed to be, and was intended to be, donated and used by the ASF under the > ALv2. > > If Tidelift wishes to contract out to individuals, it is certainly within its > rights and that's 100% A-OK. However, they must be aware that there is no > guarantee that any work that the "lifters" provide will be included. There is > no way nor guarantee that the lifters are able to direct or manage the > project in a way that Tidelift and/or its customers would want. They are not > paying for access nor are they paying for guaranteed improvements or > inclusion. That must be clear. > > My understanding of the Tidelift arrangement is that they are providing some > sort of assurance that these lifters are not only developing the code, but > also "maintaining" it, which implies active, constant and "guaranteed" > contribution. Any lifters involved with Apache projects cannot guarantee > that. They cannot maintain it anymore, or any less, than anyone else, working > within the confines of the project. > >> On Jan 12, 2022, at 9:16 AM, Gary Gregory wrote: >> >> I agree that people should handle their affairs as they see fit RE Tidelift >> but how should this be allowed to trickle in on Apache WRT mentions in web >> sites and files like readme. IOW, should structs assets remove mentions of >> Tidelift? >> >> Gary >> >> On Wed, Jan 12, 2022, 08:52 Jim Jagielski wrote: >> >>> IMO, the foundation and the project should do nothing associated with >>> this. It should neither encourage or condone it. In no way should we enter >>> into any agreement, contract, whatever, w/ Tidelift. If Tidelift wishes to >>> work independently and directly w/ people, that's fine. But having the ASF >>> and/or the project involved at any level should be disallowed. >>> >>> We cannot also ignore the obvious self-serving nature of the request by >>> Tidelift and if we are comfortable with them using this as an opportunity >>> for promotion. >>> On Jan 11, 2022, at 4:49 PM, Ralph Goers >>> wrote: Hello all, Recently the Logging Services PMC was approached by Tidelift offering to >>> provid
Re: Tidelift
> On Jan 12, 2022, at 8:34 AM, Mohammad Noureldin > wrote: > > Hi, > > I have 2 questions: > 1- How did that work in the case of Apache Struts ? Any details can be > shared ? In the case of Struts it appears there is only a single active committer and he is the sole person receiving funds from Tidelift. It isn’t clear if the PMC was ever even consulted. > 2- Is the concept of "guarantying" here in the Legal sense ? or is it > "guarantying" by approaching the "right individuals" ? > > By "right individuals" (double quoting is intentional) I mean (P)PMC > Members for example. Though they, as mentioned here, can get funded as > individuals who don't represent the ASF as an organization nor they > represent the target project in any official way, but being a (P)PMC Member > (by the definition of the ASF organization itself) show/guarantees that the > approached individuals have the merit and the commitment towards that > target project, hence guarantying that such funds will be used efficiently > or in the right way (I am using 'efficiently' and 'the right way' in their > broader sense). Yes, this is the heart of the problem. How can you be funded solely as an individual if the agreement requires agreement from the PMC? > > But even with that in mind, I believe there is a catch ? If any of those > individuals, being (P)PMC member or not, stopped working on the target > project for whatever reason, What happens then ? > That is a great question. I guess Tidelift would find out when or if its customers started complaining. Ralph
Re: Tidelift
> On Jan 12, 2022, at 10:41 AM, Ralph Goers wrote: > > Jim, > > While I agree with your conclusion I do disagree with how you get there. > > In your first message you seemed to think that the “self-serving nature” of > what Tidelift is doing is any different than what many companies have been > doing to the ASF. I am a member of the Flume PMC and my employer uses it as a > critical component of our infrastructure, primarily at my doing. I was > reluctant to have it graduate from the incubator since the PMC was 90%+ > Cloudera employees. Well, Cloudera ghosted the project and many of the PMC > members are now former Cloudera employees who, while interested in the > project, have no time to spend on it. I view that model and outcome as worse > than what Tidelift is proposing. I am now faced with doing a Flume update and > release pretty much all on my own, although I am sure there are 3 PMC members > active enough to approve the release. > I agree that all companies are self-serving in that way... There is a class of lawyers colloquially known as "ambulance chasers". I submit that said class of lawyers are more "self serving" than the general populace of lawyers. PS: Regarding the example that you provide. If it was up to me, I'd say that Flume should be attic'ed then. If we need to split hairs to determine whether a project is healthy or if there are enough active PMC members, then we should, IMO, error on the side of caution and attic said project. Otherwise we are openly and willingly allowing, and even encouraging, the continued problems that we are trying to solve right now. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Tidelift
On Tue, Jan 11, 2022 at 4:50 PM Ralph Goers 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
Re: Tidelift
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 wrote: > > On Tue, Jan 11, 2022 at 4:50 PM Ralph Goers > 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
Re: Tidelift
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 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 wrote: >> >> On Tue, Jan 11, 2022 at 4:50 PM Ralph Goers >> 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
Re: MODERATE for ment...@community.apache.org
> On Jan 11, 2022, at 10:03 AM, Mohammad Noureldin > wrote: > > Hi Harjout, > > In addition to what has been suggested by Maxim, I would like your feedback > on something. > > Where on the Apache Community Development website [1] you've that you may > need to send an email to mentors@ ?. Your feedback is very valuable to make > our websites better. > > [1] https://community.apache.org > > > On Tue, Nov 16, 2021 at 3:50 PM Maxim Solodovnik > wrote: > >> Hello Harjot Singh, >> >> mentors@ is the list for mentors, not for students :) >> I can recommend you to check this page: >> https://community.apache.org/gsoc.html >> >> Then find the project you would like to participate in here: >> https://projects.apache.org/projects.html? >> language#Java >> >> Additionally you can search for the GSOC label in JIRA :) >> >> >> -- Forwarded message -- >> From: Harjot Singh >> To: ment...@community.apache.org >> Cc: >> Bcc: >> Date: Sun, 14 Nov 2021 19:03:21 +0530 >> Subject: How to get started with open source contribution. >> >> Respected sir/madam, >> >> I am Harjot Singh , a computer science undergrad. I am completely new >> to open source contributions but I am familiar with C++ , Java and >> Data Structures and Algorithms concepts. I would love to contribute to >> your organization but could you please tell me how to get started? >> >> Hoping to hear from you soon. >> >> Regards >> >> Harjot Singh >> >> >> >> -- >> Best regards, >> Maxim >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >> > > -- > Thanks > - Mohammad Noureldin > > "Life is like riding a bicycle. To keep your balance you must keep moving" > - Albert Einstein Craig L Russell c...@apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Tidelift
On 2022-01-12 at 10:41:22 UTC-0500 (Wed, 12 Jan 2022 08:41:22 -0700) Ralph Goers is rumored to have said: That said, if the Tidelift model for people to be funded was “Your project must adhere to all ASF process and guidelines AND you must have a minimum of 3 active committers (proven by them actually approving and merging PRs, committing fixes for bugs, etc) and an advertising requirement I might be more inclined to support it since the only real requirement is that the project be active. Agreed, except for the problem that this is an imaginary Tidelift in an alternate universe. They've clearly put a pile of effort into their current model and I suspect that they would not easily cede perfomance standards to the rather hit-or-miss baseline of being a healthy ASF project. We are the floor they are seeking to "lift" packages up from. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Tidelift
On 2022-01-12 at 08:51:37 UTC-0500 (Wed, 12 Jan 2022 08:51:37 -0500) Jim Jagielski is rumored to have said: IMO, the foundation and the project should do nothing associated with this. It should neither encourage or condone it. In no way should we enter into any agreement, contract, whatever, w/ Tidelift. If Tidelift wishes to work independently and directly w/ people, that's fine. But having the ASF and/or the project involved at any level should be disallowed. +1 It seems clear to me that the Tidelift business model is not compatible with the ASF's project structure. All of their documentation clearly only envisions supporting individual contributors or employers of individual contributors. I'd also be very leery of this as an individual. It is unclear what their performance standards are for "Lifters" under this clause of their agreement, in the section on termination: • failure to complete tasks set out in the Tidelift software platform (including ineffective or inaccurate completion) Since ASF projects have PMCs, not God-Kings, it's generally not possible for an individual commiter on an ASF project to commit to completing development tasks which are arbitrarily defined by a 3rd party seeking "support." And speaking from my extremely parochial POV as part of the SpamAssassin project, I know that our requests for "support" often amount to embedding special dispensation for sketchy practices, so I don't think anyone working on *OUR* project could "lift" it without telling subscribers "NO!" and being terminated. We cannot also ignore the obvious self-serving nature of the request by Tidelift and if we are comfortable with them using this as an opportunity for promotion. Right. They seem pretty lame at promotion, but they are clearly trying very hard. With my Sr. Sysadmin hat on, I cannot imagine actually paying them their prices for what they seem to be actually capable of providing. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Tidelift
يعني وش السالفة . شوفوا مودي طيب في الأربعاء، ١٢ يناير ٢٠٢٢ ٩:١٢ م Bill Cole < sa-bugz-20080...@billmail.scconsult.com> كتب: > On 2022-01-12 at 08:51:37 UTC-0500 (Wed, 12 Jan 2022 08:51:37 -0500) > Jim Jagielski > is rumored to have said: > > > IMO, the foundation and the project should do nothing associated with > > this. It should neither encourage or condone it. In no way should we > > enter into any agreement, contract, whatever, w/ Tidelift. If Tidelift > > wishes to work independently and directly w/ people, that's fine. But > > having the ASF and/or the project involved at any level should be > > disallowed. > > +1 > > It seems clear to me that the Tidelift business model is not compatible > with the ASF's project structure. All of their documentation clearly > only envisions supporting individual contributors or employers of > individual contributors. > > I'd also be very leery of this as an individual. It is unclear what > their performance standards are for "Lifters" under this clause of their > agreement, in the section on termination: > > • failure to complete tasks set out in the Tidelift software > platform (including ineffective or inaccurate completion) > > Since ASF projects have PMCs, not God-Kings, it's generally not possible > for an individual commiter on an ASF project to commit to completing > development tasks which are arbitrarily defined by a 3rd party seeking > "support." > > And speaking from my extremely parochial POV as part of the SpamAssassin > project, I know that our requests for "support" often amount to > embedding special dispensation for sketchy practices, so I don't think > anyone working on *OUR* project could "lift" it without telling > subscribers "NO!" and being terminated. > > > We cannot also ignore the obvious self-serving nature of the request > > by Tidelift and if we are comfortable with them using this as an > > opportunity for promotion. > > Right. They seem pretty lame at promotion, but they are clearly trying > very hard. With my Sr. Sysadmin hat on, I cannot imagine actually paying > them their prices for what they seem to be actually capable of > providing. > > > -- > Bill Cole > b...@scconsult.com or billc...@apache.org > (AKA @grumpybozo and many *@billmail.scconsult.com addresses) > Not Currently Available For Hire > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: Tidelift
> > 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? No. And this is something I would never be able to agree to because the agreement is with me not with PMC/project. But for example Astronomer and AWS sponsor the CI (AWS credits) for our CI and we did thank them for that in README. But this is for "Resources" for the project not for development And we are free to use it as we see fit for the project.. > What you are doing sounds fine to me simply because the agreement > you have doesn’t obligate the PMC to anything. Correct. And I believe PMC cannot be obliged to do anything in exchange for money. This is an important point of the discussion as I understand it. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Tidelift
> And speaking from my extremely parochial POV as part of the SpamAssassin > project, I know that our requests for "support" often amount to > embedding special dispensation for sketchy practices, so I don't think > anyone working on *OUR* project could "lift" it without telling > subscribers "NO!" and being terminated. BTW. I actually said "NO" several times (nothing serious) and was not terminated - quite the opposite. I was literally thanked for honesty and transparency and for providing "community perspective". My contracts were renewed and improved afterwards. I guess our stakeholders understand how the ASF community works. J - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-413) GSoC: Apache CouchDB and Debezium integration
[ https://issues.apache.org/jira/browse/COMDEV-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475113#comment-17475113 ] Hellakala Gamage Dineth Shan Gimhana commented on COMDEV-413: - Hi, I am Dineth from Sri Lanka, I am interested to work on this feature, I would like to where I can start? thanks > GSoC: Apache CouchDB and Debezium integration > - > > Key: COMDEV-413 > URL: https://issues.apache.org/jira/browse/COMDEV-413 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Balázs Donát Bessenyei >Priority: Major > Labels: CouchDB, couchdb, gsoc2021, mentor > > Apache CouchDB software is a document-oriented database that can be queried > and indexed in a MapReduce fashion using JavaScript. CouchDB also offers > incremental replication with bi-directional conflict detection and resolution. > Debezium is an open source distributed platform for change data capture. > Start it up, point it at your databases, and your apps can start responding > to all of the inserts, updates, and deletes that other apps commit to your > databases. Debezium is durable and fast, so your apps can respond quickly and > never miss an event, even when things go wrong. > > CouchDB has a change capture feed as a public HTTP API endpoint. Integrating > with Debezium would provide an easy way to translate the _changes feed into a > Kafka topic which plugs us into a much larger ecosystem of tools and > alleviates the need for every consumer of data in CouchDB to build a bespoke > “follower” of the _changes feed. > > The project for GSoC 2021 here is to design, implement and test a CouchDB > connector for Debezium. > > Required skills: > - Java > Nice-to-have skills: > * Erlang -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Comment Edited] (COMDEV-413) GSoC: Apache CouchDB and Debezium integration
[ https://issues.apache.org/jira/browse/COMDEV-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475113#comment-17475113 ] Hellakala Gamage Dineth Shan Gimhana edited comment on COMDEV-413 at 1/13/22, 5:28 AM: --- Hi, I am Dineth from Sri Lanka, I am interested to work on this feature, I would like to know where I can start? thanks was (Author: JIRAUSER283513): Hi, I am Dineth from Sri Lanka, I am interested to work on this feature, I would like to where I can start? thanks > GSoC: Apache CouchDB and Debezium integration > - > > Key: COMDEV-413 > URL: https://issues.apache.org/jira/browse/COMDEV-413 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Balázs Donát Bessenyei >Priority: Major > Labels: CouchDB, couchdb, gsoc2021, mentor > > Apache CouchDB software is a document-oriented database that can be queried > and indexed in a MapReduce fashion using JavaScript. CouchDB also offers > incremental replication with bi-directional conflict detection and resolution. > Debezium is an open source distributed platform for change data capture. > Start it up, point it at your databases, and your apps can start responding > to all of the inserts, updates, and deletes that other apps commit to your > databases. Debezium is durable and fast, so your apps can respond quickly and > never miss an event, even when things go wrong. > > CouchDB has a change capture feed as a public HTTP API endpoint. Integrating > with Debezium would provide an easy way to translate the _changes feed into a > Kafka topic which plugs us into a much larger ecosystem of tools and > alleviates the need for every consumer of data in CouchDB to build a bespoke > “follower” of the _changes feed. > > The project for GSoC 2021 here is to design, implement and test a CouchDB > connector for Debezium. > > Required skills: > - Java > Nice-to-have skills: > * Erlang -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Comment Edited] (COMDEV-413) GSoC: Apache CouchDB and Debezium integration
[ https://issues.apache.org/jira/browse/COMDEV-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475113#comment-17475113 ] Hellakala Gamage Dineth Shan Gimhana edited comment on COMDEV-413 at 1/13/22, 5:28 AM: --- Hi, I am Dineth from Sri Lanka, I am interested to work on this feature, I would like to know where I can start? thanks was (Author: JIRAUSER283513): Hi, I am Dineth from Sri Lanka, I am interested to work on this feature, I would like to know where I can start? thanks > GSoC: Apache CouchDB and Debezium integration > - > > Key: COMDEV-413 > URL: https://issues.apache.org/jira/browse/COMDEV-413 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Balázs Donát Bessenyei >Priority: Major > Labels: CouchDB, couchdb, gsoc2021, mentor > > Apache CouchDB software is a document-oriented database that can be queried > and indexed in a MapReduce fashion using JavaScript. CouchDB also offers > incremental replication with bi-directional conflict detection and resolution. > Debezium is an open source distributed platform for change data capture. > Start it up, point it at your databases, and your apps can start responding > to all of the inserts, updates, and deletes that other apps commit to your > databases. Debezium is durable and fast, so your apps can respond quickly and > never miss an event, even when things go wrong. > > CouchDB has a change capture feed as a public HTTP API endpoint. Integrating > with Debezium would provide an easy way to translate the _changes feed into a > Kafka topic which plugs us into a much larger ecosystem of tools and > alleviates the need for every consumer of data in CouchDB to build a bespoke > “follower” of the _changes feed. > > The project for GSoC 2021 here is to design, implement and test a CouchDB > connector for Debezium. > > Required skills: > - Java > Nice-to-have skills: > * Erlang -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
