Re: Tidelift
Jim 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. This is exactly what I said on the LEGAL JIRA. So +1 to this framing. Now, personally, I think Tidelift can be a great ally of Open Source in general and as such I'm personally extremely willing to work with them to make sure they come up with tweaks for their model that make sense to us and other Open Source projects. More on that below: On Wed, Jan 12, 2022 at 7:56 AM 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 > Huge +1 to the above. I really feel that Tidelift is onto something here and am very much willing to work with them (even in my personal capacity). > 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/ I'd like to refocus this thread (or perhaps fork a new one) on expanding this useful list started by Sam. I also plan to talk to Tidelift later this week so having as much data points as I possibly can would be super useful. Anyone has anything else they feel like adding to the above list? Thanks, Roman.
[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=17476942#comment-17476942 ] Balázs Donát Bessenyei commented on COMDEV-413: --- [~gimhana.ds] : please contact the developer community at [d...@couchdb.apache.org|mailto:d...@couchdb.apache.org] > 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=17476942#comment-17476942 ] Balázs Donát Bessenyei edited comment on COMDEV-413 at 1/17/22, 3:39 AM: - [~gimhana.ds] : I suggest contacting the developer community at [d...@couchdb.apache.org|mailto:d...@couchdb.apache.org] was (Author: bessbd): [~gimhana.ds] : please contact the developer community at [d...@couchdb.apache.org|mailto:d...@couchdb.apache.org] > 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
Re: Open source
Hello Gunesh, please do not send personal emails write to the dev@ list instead :) you can subscribe to any public ASF mailing list as described here: https://www.apache.org/foundation/mailinglists.html#subscribing I can't recommend you the project Feel free to connect project developers to get recommendations :) On Mon, 10 Jan 2022 at 19:21, Gunesh wrote: > > Sir, now I am a member of the mailing list I have subscribed to it. > Now I can contribute? > Please guide me as I am new to open source or you can say a newbie. > > > > Regards > Gunesh > > On Mon, 10 Jan, 2022, 2:18 pm Gunesh, wrote: >> >> sir in C++ there are many projects and that is good >> but sir could you recommend me a project which of medium-hard level and not >> so hard. >> >> >> regards >> gunesh >> >> On Mon, Jan 10, 2022 at 2:15 PM Gunesh wrote: >>> >>> sir, >>> thank you so much sir . >>> how can i subscribe that mailing list? >>> >>> regards >>> gunesh >>> >>> On Mon, Jan 10, 2022 at 1:43 PM Maxim Solodovnik >>> wrote: Please don't forget to CC mailing list (you might need to subscribe first) here is the list of C++ projects: https://projects.apache.org/projects.html?language#C++ On Mon, 10 Jan 2022 at 15:10, Gunesh wrote: > > thank you so much sir for helping me out. > > sir just want to ask that i am new to open source and i am well aware of > C++ language only. > could you recommend me any project. > > regards > gunesh > > On Mon, Jan 10, 2022 at 10:01 AM Maxim Solodovnik > wrote: >> >> Hello Gunesh, >> >> 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 [1] :) >> >> Please send any additional questions to the dev@community mailing-list >> or better to the dev@ list of the particular Apache project you would >> like to contribute :) >> >> [1] https://issues.apache.org/jira/browse >> >> > >> > -- Forwarded message -- >> > From: Gunesh >> > To: ment...@community.apache.org >> > Cc: >> > Bcc: >> > Date: Sat, 8 Jan 2022 16:56:20 +0530 >> > Subject: Open source >> > Hello Sir/ma'am, >> > I am a computer science student. I am new to open source and want to >> > contribute in open source . I am well aware of C++ only. Hoping to >> > hear from you soon. >> > >> > >> > >> > >> > >> > Regards >> > Gunesh -- Best regards, Maxim -- Best regards, Maxim - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: How to get started with contribution
Hello Mohammad :) On Wed, 12 Jan 2022 at 17:12, Mohammad Noureldin wrote: > > 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. As non-native English speaker with no practice for 5+ years I would appreciate any help in correcting my email (or maybe some details can be added) > > 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 ? Unfortunately I have not much free time right now (2 small kids 24/7) I believe the main reason emails go to mentors@ : people are looking for mentors :) (same thing happens with dev@ list: users will write to dev@ to contact developers ) I'm not sure how this can be improved :( p.s. as Melissa use to say: I miss your smiley face :) Hope to see you at one of ApacheCon one day :) > >> >> 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 >> > > > 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 >> > > > > > >> > > > > > 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 >> >
