Home/Magazine Archive/May 2022 (Vol. 65, No. 5)/It Takes a Community: The Open Source Challenge/Full Text Practice It Takes a Community: The Open Source Challenge By Reynold Xin, Wes McKinney, Alan Gates, Chris McCubbin Communications of the ACM, May 2022, Vol.
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Alan Gates
It Takes a Community
Current Issue Past Issues Topics November 17, 2021 Volume 19, issue 5 PDF Case Study The Open-source Challenge A discussion with Reynold Xin, Wes McKinney, Alan Gates, and Chris McCubbin Of the many challenges faced by open-source developers, among the most daunting are some that other programmers scarcely ever think about. And that's because most programmers work in settings where "other people" attend to such matters—people who work in the legal department or human resources, for example.
Mentors needed for Superset and Samoa
It is time for me to step down from the Incubator PMC. Before I officially depart I'd like to help the podlings I am currently mentoring, Superset and Samoa, find new mentors. If anyone has time and interest in mentoring these projects I would greatly appreciate their stepping in to replace me. "Superset is an enterprise-ready web application for data exploration, data visualization and dashboarding." The project has been growing the community and making regular releases and is nearing graduation.
[VOTE] Release SAMOA 0.5.0 (incubating) RC3
+1. I checked the disclaimer, license, and notice files, the hash and key signature. I did a build from source and ran the rat check. One note on the rat check, five files fail. One of those is s shell script that could have the license added, the others look like maybe they couldn't. But it would be nice to put those in the exclude list so the rat build succeeds. This can be done after this release. Alan.
[VOTE] Release SAMOA 0.5.0 (incubating) RC3
I’ll take a look this weekend or early next week. Alan. Sent from my iPhone > On Apr 10, 2020, at 17:53, Justin Mclean <jmclean@apache.org> wrote: > > Hi, > > Look like this needs another IPMC vote, can any IPMC member help?
[VOTE] Release Apache Superset (incubating) version 0.35.2
+1. I checked the LICENSE, NOTICE, and DISCLAIMER files, and the signatures. Looked for any files that weren't properly licensed and checked for any non-image binaries. One small note for next time, you should update the copyright notice in the NOTICE file to 2020. Alan.
Omid&Tephra -> Phoenix sub-project next steps
I think you should go ahead. Everyone's voted on it, no one made any comments on the discussion thread on general@, and Justin's been aware of what's going on the whole way. Alan. On Thu, Nov 14, 2019 at 8:32 AM Josh Elser <elserj@apache.org> wrote: > I'm a bit confused about where we go from this point. > > Given the doc[1] that Alan shared last time, we are good to move ahead > with the logistical changes.
Omid and Tephra graduating into Phoenix
I've reverted the change for now to avoid breaking any builds. Once we've either sorted out how to mark these as graduating or Phoenix has finished it's work and we have a link to resolve to, then I'll redo this. Alan. On Fri, Nov 8, 2019 at 2:26 PM Alan Gates <alanfgates@gmail.com> wrote: > Sorry, I don't mean I won't fix it, I'm just not sure how to fix it at > this point. > > Alan.
Omid and Tephra graduating into Phoenix
I found the instructions for that here: https://incubator.apache.org/guides/transferring.html I didn't put in the resolution link yet because there's no such link yet. Alan. On Fri, Nov 8, 2019 at 1:44 PM Dave Fisher <wave@apache.org> wrote: > Hi Alan, > > The podlings.xml change is not really correct.
Omid and Tephra graduating into Phoenix
Sorry, I don't mean I won't fix it, I'm just not sure how to fix it at this point. Alan. On Fri, Nov 8, 2019 at 2:21 PM Alan Gates <alanfgates@gmail.com> wrote: > I found the instructions for that here: > https://incubator.apache.org/guides/transferring.html > I didn't put in the resolution link yet because there's no such link yet. > > Alan. > > On Fri, Nov 8, 2019 at 1:44 PM Dave Fisher <wave@apache.org> wrote: > >> Hi Alan, >> >> The podlings.xml change is not really correct.
Omid and Tephra graduating into Phoenix
I've updated the status of Omid and Tephra to 'graduating' in podlings.xml. I've also updated the projects/${podling}.xml for each of them with info on the SGAs (which hadn't been put there) and on their status as graduating into Phoenix. I'll let the Phoenix PMC deal with github, JIRA, mailing lists, etc. Once this is done I can update the status to 'graduated' in podlings.xml. Alan. On Tue, Nov 5, 2019 at 6:08 PM Justin Mclean <justin@classsoftware.com> wrote: > Hi, > > > I don't think so.
Omid and Tephra graduating into Phoenix
I don't think so. I'll wait the 72 hours for the comment period to end (started this morning) and then add a note to the report that Omid and Tephra are graduating into Phoenix, unless Justin prefers something else. Alan. On Tue, Nov 5, 2019 at 5:14 PM Andreas Neumann <anew@apache.org> wrote: > Should Tephra still file a podling report this month?
Omid and Tephra graduating into Phoenix
Omid[1] and Tephra[2] have voted to join the Phoenix community as sub-projects. Phoenix has voted to accept them[3]. Per the instructions at [4], this email is notice of that. Unless any objections are raised in 72 hours the graduation will be considered accepted and both podlings will move ahead with the details. Alan. 1. https://lists.apache.org/thread.html/d996692f30b30eea68c1e8db3c5095d6eb4877f7b358e401851130b2@%3Cdev.omid.apache.org%3E 2.
[VOTE] Release Apache Superset (incubating) 0.35.0 [RC3]
Forwarding my +1 from the dev list. I checked the LICENSE, NOTICE, and DISCLAIMER files, the signature and hash, and checked for any improperly licensed or binary files (there are some font and image files, but these are ok). Alan. On Mon, Nov 4, 2019 at 1:33 AM daniel gaspar <danielvazgaspar@gmail.com> wrote: > Hi IPMC, > > The Apache Superset PPMC and IPMC recently passed a voting for RC2, > but I just realized there is a minor issue.
Re: Omid and Tephra
Regarding SGAs, here's the JIRA for Omid: https://issues.apache.org/jira/browse/OMID-2 According to https://svn.apache.org/repos/private/foundation/officers/grants.txt Cask (original creators of Tephra) submitted a SGA for it and it's one file, but I don't know where the referenced file is kept. Alan. On Wed, Oct 30, 2019 at 10:32 AM Alan Gates <alanfgates@gmail.com> wrote: > Bertand, thanks for bringing this up. I'll chase those down. > > Alan.
Re: Omid and Tephra
Bertand, thanks for bringing this up. I'll chase those down. Alan. On Wed, Oct 30, 2019 at 8:46 AM Bertrand Delacretaz < bdelacretaz@codeconsult.ch> wrote: > Hi, > > On Wed, Oct 30, 2019 at 3:55 PM Josh Elser <elserj@apache.org> wrote: > > ...My current expectation is that we'd just rename the existing Git > > repositories and change the LDAP group which are used to determine write > > access...
Re: Omid and Tephra
Makes sense. I've replied to the discussion in the Phoenix community so we know what terms Tephra and Omid are voting on. As soon as I hear from them I'll start votes in both communities. Alan. On Tue, Oct 29, 2019 at 3:47 PM Andreas Neumann <anew@apache.org> wrote: > I agree with Justin, I think we get - at least in the Tephra community - a > quorum.
Re: Omid and Tephra
There appears to be consensus on this thread, as well as in the Phoenix community[1] that it makes sense for Phoenix to adopt both Omid and Tephra. My mails to the Tephra and Omid communities[2][3] have gone unanswered, so I assume silence implies consent. According to [4] the first step of graduating into a sub-project of an existing TLP is a vote by the podling. Given that both podlings have very low activity I am not sure we will get the necessary votes to make this happen.
Omid and Tephra
Justin and mentors of Omid and Tephra, As Justin noted in his emails to these podlings this month both are very low activity, struggling to even file their reports, and appear to be candidates for retirement. The situation here is somewhat special because Phoenix uses one or both of these technologies (they are both transaction managers on top of HBase), so they may have an interest in their continued survival. Tephra briefly discussed this last June[1], though nothing came of it.
[VOTE] Release Apache Superset (incubating) 0.34.1 [RC2]
+1. Checked the LICENSE, NOTICE, and DISCLAIMER files. Checked to see there weren't any binary files and that all the code files had AL headers. Alan. On Mon, Oct 7, 2019 at 8:08 AM Ville Brofeldt <ville.v.brofeldt@gmail.com> wrote: > Dear IPMC, > > The Apache Superset community has voted on and approved a proposal to > release Apache Superset (incubating) 0.34.1 (rc2). This is a bug-fix > release to the inaugural Apache release of Superset in August 2019.
Shared Transactional Tables: The Foundation of Next Generation Big Data Warehousing
The next generation of big data warehousing is being built on transactional tables. Transactions, of course, enable new use cases that require updating, deleting, and merging rows of data.
[VOTE] Recommend 'Apache SINGA graduation to Top Level Project' resolution to the board
>From one of the mentors, +1. And congratulations to the Singa project! Alan. On Fri, Sep 13, 2019 at 1:38 PM Moaz Reyad <moaz@apache.org> wrote: > In the four and a half years that Apache SINGA (incubating) has been > a part of the Apache incubator, the community has grown, diversified, > and adapted to the Apache Way. We believe that the project is ready > to graduate to a TLP.
[Discuss] Graduate Apache SINGA (incubating) as a TLP
Ok, now that the SGA is filed, I'm +1 on this. Thanks for chasing this down. Alan. On Thu, Sep 5, 2019 at 2:36 AM Beng Chin OOI <ooibc@comp.nus.edu.sg> wrote: > > A number have joined Alibaba, Kyoto University, Zhejiang University and > other companies in > various countries, and some still continue to contribute. > > On Singapore side, IMDA https://www2.imda.gov.sg is pushing the system > for adoption by > the local industry/SME.
[Discuss] Graduate Apache SINGA (incubating) as a TLP
If I understand correctly, anytime software is brought into Apache as part of the incubating process there must be documentation from the previous owner of that software stating that they are donating it to Apache. Without that Apache's ownership of the code is not clear. Justin, Dave, others, please correct me if this understanding is wrong.
[Discuss] Graduate Apache SINGA (incubating) as a TLP
Yes, I saw that, but I can't find those papers. They should have been filed by the Apache secretary on the page I referenced. Either they were properly transferred and we need to find them so that they are properly posted in case anyone ever needs them, or, if they weren't sent, then we need to make sure a copy of them is sent. I guess the next step is to email the secretary and ask if he's aware of that transfer having taken place, unless anyone knows somewhere else I should be looking for them.
[Discuss] Graduate Apache SINGA (incubating) as a TLP
Sorry, I brought this up earlier on the dev list but didn't follow up. I can't find a copy of the code grant for the code that Singa brought into the Incubator. When I look at the Secretary's page[1] that lists all of the code grants I don't see one for Singa. Per the initial proposal[2] there was code imported from an existing github repo [3], which means we need to have a code grant from whom ever owned that code (National University of Singapore would be my guess).
[VOTE] Release Apache Superset (incubating) 0.34.0 [RC2]
+1. Alan. On Fri, Aug 23, 2019 at 12:56 PM Maxime Beauchemin < maximebeauchemin@gmail.com> wrote: > Hi IPMC, > > The Apache Superset PPMC and IPMC recently voted and passed a vote on RC1 > recently, only to realize that there's was a minor blocking. The blocker > was that the version was labelled `0.34.0rc1` inside the tarball, as > opposed to `0.34.0`, meaning that when installing from source, the Python & > npm packages would appear to be a `0.34.0rc1`.
[VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]
I would call a revote over that, it's not like you're changing anything of import. I'd just regen the package with the change, create the new hash, and let everyone know. I don't see any reason to drag back through the voting process on two lists over this. Alan. On Wed, Aug 21, 2019 at 10:43 PM Justin Mclean <justin@classsoftware.com> wrote: > Hi, > > > Oh here's something.
[VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]
Forwarding my +1 from the dev list. I checked the LICENSE, NOTICE, and DISCLAIMER files, as well as looking over the contents of the release for licenses and to make sure there weren't any binary files (beyond image files). Alan. On Sun, Aug 18, 2019 at 9:41 PM Maxime Beauchemin < maximebeauchemin@gmail.com> wrote: > Hi IPMC, > > The Apache Superset community has voted on and approved a proposal to > release > Apache Superset (incubating) 0.34.0 (rc1).
[VOTE] Release Apache Omid 1.0.1 (incubating)
+1. Did a build with a clean mvn repo and profile for HBase-2, looked at the LICENSE, NOTICE, and DISCLAIMER files, checked for any binary files in the distribution, and ran rat. Alan. On Tue, May 7, 2019 at 11:56 AM larsh@apache.org <larsh@apache.org> wrote: > Transferring my +1 from the Omid dev list. > On Sunday, May 5, 2019, 1:56:57 AM EDT, Yoni Gottesman < > yonigo@apache.org> wrote: > > The Apache Omid community has voted on and approved a proposal > to release Apache Omid 1.0.1-incubating.
[VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Forwarding my +1 from the dev list. Checked the NOTICE, LICENSE, and DISCLAIMER files. Did a quick check that everything had appropriate Apache License headers, and I didn't find any binaries in the RC. Alan.
[VOTE] Release apache-singa-incubating-2.0.0 (RC1)
Forwarding my +1 from the dev list. Checked signatures, sha, did a quick check to make sure files without headers were referenced in LICENSE or NOTICE, looked for binary files in the distribution. Alan. On Wed, Apr 10, 2019 at 6:21 PM Chonho Lee <leech@cmc.osaka-u.ac.jp> wrote: > Hi all, > > The SINGA community has voted on and approved a proposal to release Apache > SINGA 2.0.0 (incubating).
Does a new podling committer require notice to the IPMC?
Thanks Hitesh. Alan. On Thu, Dec 20, 2018 at 4:30 PM Hitesh Shah <hitesh@apache.org> wrote: > The notice is only for new PPMC members. Most podlings do not differentiate > between committers and PPMC so you would end up seeing notice emails for > new committers being sent to the IPMC.
Does a new podling committer require notice to the IPMC?
We used to require that a podling notify the IPMC after its PPMC had voted to invite a contributor to be a committer and before the candidate was notified. Do we still require that? I can't recall seeing any emails from other podlings on that lately and I couldn't find any docs on the incubator site one way or another. Alan.
[VOTE] Release Apache Omid 1.0.0 (incubating)
+1. Did a build with a clean mvn repo, checked the DISCLAIMER, NOTICE, and LICENSE files. Found the RAT issues already noted by Josh. Getting these fixed soon would be good as finding license issues is much harder by hand then with RAT. Alan.
[VOTE] Graduate Apache HAWQ (incubating)
+1. Alan. On Fri, Jul 27, 2018 at 7:13 PM Roman Shaposhnik wrote: > Hi! > > after a very positive discussion in the HAWQ community > and at the IPMC level: > > https://lists.apache.org/thread.html/67a2d52ef29cbf9e93d8050ed0193cc110a919962dd92f8436b343b7@%3Cdev.hawq.apache.org%3E > > https://lists.apache.org/thread.html/3a142d758ef5ae119e4210555571893615992ea5ee937b5d02007f5e@%3Cgeneral.incubator.apache.org%3E > > I'd like to bring the following resolution for a formal vote.
[VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]
+1. Did a build in a fresh repo, looked over the LICENSE and NOTICE files, ran rat. Rat initially fails, but on further inspection all the files it's complaining about are the other license files. I believe there's a way to exclude these files from the rat run. In the future it would be good to clean those up so that it's easy to see whether rat passes or fails. On Wed, May 23, 2018 at 3:57 PM Joe Witt wrote: > +1 (binding) > > Verified source bundle signature and hashes and disclaimer.
[VOTE] Release Apache Omid 0.9.0.0 (incubating)
Forwarding my +1 from the dev list. Alan.
Two new Samoa committers
When I got the email from root@apache it said: Please grant additional karma to the projects in your domain you wish the user to have commit to. Only PMC chairs can grant karma. If needed, please post to the general@/ dev@/private@ list of your project asking for someone with sufficient karma to grant access to 'pwawrzyniak'. If this is old and no longer applicable and there's nothing else to do, then feel free to ignore my request. Alan. On Thu, Mar 22, 2018 at 4:07 PM, John D.
MISS PRISTINE, by HEX
If you like HEX, you may also like:
[VOTE] Release Apache Omid 0.9.0.0 (incubating)
Forwarding my +1 from the dev list. Alan. On Thu, Mar 22, 2018 at 5:29 AM, Ohad Shacham wrote: > Hi, > > > The Apache Omid community has voted on and approved a proposal > to release Apache Omid 0.9.0.0-incubating.
Two new Samoa committers
John, can you grant karma on Samoa to Piotr Wawrzyniak (pwawrzyniak) and Maciej Grzenda (mgrzenda). Both have recently been voted in as committers. Their id's have been created but I do not have power to grant them karma. Thanks. Alan.
Apache HAWQ 2.3.0.0-incubating Release
Henk kindly pointed me to the KEYS file that I had missed, thank you. So, +1. I checked the signatures, the LICENSE, NOTICE, and DISCLAIMER files. Alan. On Tue, Mar 13, 2018 at 10:42 AM, Alan Gates wrote: > Per https://www.apache.org/dev/release-distribution#sigs-and-sums > correctly, the KEYS file is required, hence my comment. > > Alan. > > On Tue, Mar 13, 2018 at 10:34 AM, Henk P.
Apache HAWQ 2.3.0.0-incubating Release
Per https://www.apache.org/dev/release-distribution#sigs-and-sums correctly, the KEYS file is required, hence my comment. Alan. On Tue, Mar 13, 2018 at 10:34 AM, Henk P. Penning wrote: > On Tue, 13 Mar 2018, Alan Gates wrote: > > Date: Tue, 13 Mar 2018 18:04:08 +0100 >> From: Alan Gates >> To: general@incubator.apache.org >> Subject: Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release >> >> I can't find a KEYS file anywhere in HAWQ to check the key >> against.
Apache HAWQ 2.3.0.0-incubating Release
I can't find a KEYS file anywhere in HAWQ to check the key against. There is also no name associated with the key, so I'm not clear how to check the signature. Other than that release looks fine. On Mon, Mar 12, 2018 at 7:56 PM, Roman Shaposhnik wrote: > +1 (binding) > > * checked sigs and checksums > * checked licenses > * checked for archive matching git tag > > Thanks, > Roman.
[VOTE] Release of Apache Tephra-0.13.0-incubating [rc2]
?They have removed the LGPL code. Not removing the license as well is an oversight. Alan.? On Mon, Sep 18, 2017 at 5:08 PM, John D. Ament wrote: > Hi, > > I'm inclined to vote -1 unless someone convinces me otherwise. > > TEPHRA-231 was created to address issues identified, however it doesn't > seem to have been solved properly. > > - The changes to the NOTICE file don't match the NOTICE file for Guice. > There is no need to declare the license usage for single licensed code.
[VOTE] Release of Apache Tephra-0.13.0-incubating [rc2]
Forwarding my +1 from the dev list. Alan. Sent from my iPhone > On Sep 19, 2017, at 03:56, James Taylor wrote: > > +1. Transferring my vote over from the dev list vote. > >> On Mon, Sep 18, 2017 at 10:13 AM, Andreas Neumann wrote: >> >> Hi all, >> >> This is a call for a vote on releasing Apache Tephra 0.13.0-incubating, >> release candidate 2. This is the sixth release of Tephra. >> >> The Apache Tephra community has voted and approved the release.
Apache HAWQ 2.2.0.0-incubating Release
Forwarding my +1 from the dev list. Alan. On Sat, Jul 1, 2017 at 8:37 AM, Ruilong Huo wrote: > Hi IPMC member, > > > The PPMC vote for the Apache HAWQ 2.2.0.0-incubating release has passed. > We kindly request that the IPMC now vote on the release.
[NOTICE] Community Vote for Apache Atlas Graduation to TLP
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-118 Alan. On Mon, Jun 5, 2017 at 6:26 PM, John D. Ament wrote: > Suma, > > One more thing. I cannot find a podling name search on file for Atlas. > Has this been done? See also [1] > > John > > [1]: http://incubator.apache.org/guides/names.html#name-search > > On Thu, May 25, 2017 at 8:45 PM John D. Ament > wrote: > > > Hi Suma, > > > > Thanks for the heads up.
[VOTE] Release of Apache Tephra-0.12.0-incubating [rc1]
Forwarding my +1 from the dev list. Alan. On Fri, May 26, 2017 at 2:12 PM, Gokul Gunasekaran wrote: > Hi all, > > This is a call for a vote on releasing Apache Tephra 0.12.0-incubating, > release candidate 1. This is the fifth release of Tephra. > > Apache Tephra community has voted and approved the release.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Alan
Contact Alan, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack