(Moving sqlline-dev to bcc.) Thanks for the reply, and the warm welcome, Rick.
>From what I can tell (if Derby, JDO, Cayenne are to be regarded as typical), sub-projects enter the DB project via the Incubator, sponsored by DB, and after completing incubation graduate into DB. And then the committers of the incubating sub-project become PMC members of DB. The Incubation process seems viable for us. I'm sure we can attract a few more regular contributors during incubation. The ‘teaching people the Apache Way’ aspect of the Incubator seems unnecessary, given that contributors to SQLLine have plenty of Apache experience; I took Calcite through incubation, and have mentored a half dozen projects through incubation. By the way, does that process require a Board vote? Or is it just a vote by the DB PMC? Would IP clearance be an alternative way to enter? I guess if we went that route, we would still have to earn our commit bits & PMC membership after entering DB, and in the interim, that would make releases a bit difficult. Julian On Oct 30, 2021, at 12:11 PM, Rick Hillegas <rick.hille...@gmail.com> wrote: Hey Julian, I think that the DB project would be a good home for SQLLine. DB already has a SQL REPL tool called ij, which can be deployed against any JDBC database. The ij REPL tool is part of the Derby toolset: https://db.apache.org/derby/docs/10.15/tools/ctoolsij34525.html There could be some interesting cross-pollination between SQLLine and ij. Craig Russell hangs out at the DB project. He has a wealth of experience incubating projects and can probably help guide you through the process. You probably already know much more about the Apache incubator than I do, given your stewardship of Calcite. At first blush, it sounds as though you need to sort out some IP issues and attract a couple more active contributors in order to pass the incubator hurdles. I don't know what you need from DB at this point. Maybe Craig can weigh in. Welcome and a big +1 to folding SQLLine into Apache DB. Cheers, -Rick On 10/28/21 8:49 PM, Julian Hyde wrote: Is the DB project interested in adding sub-projects? And if so, what are the criteria for acceptance, and what is the process? SQLLine [1] is an open-source project that provides a command-line shell for any JDBC data source. It is widely used, including in Apache projects such as Drill and Calcite, and even more widely forked (e.g. Hive’s Beeline). The project was founded in around 2002 [2] and around 2012 I adopted it, moved it to GitHub, and started making releases again [3]. We have two regular contributors (myself and Sergey Nuyanzin) and several occasional contributors, and make one or two releases per year. In the SQLLine project, we have recently started a conversation about governance, branding and IP ownership. Based on its GitHub URL, people tend to assume that it is a single-developer project, and that perception may hurt adoption and participation. We have been moving towards an ASF-style governance model based on a PMC and committers, but we are just short of critical mass. We think that SQLLine might be a good fit for the DB project. As a Java-based tool for interacting with databases it fits the mission perfectly; several of us are active in ASF projects and therefore know how things work in Apache. If accepted, we could contribute to the running of the DB project (voting on other sub-projects’ releases, for example). Please let us know whether you think it would be a good fit for our projects. Julian [1] https://github.com/julianhyde/sqlline [2] https://sourceforge.net/projects/sqlline/files/sqlline/ [3] https://github.com/julianhyde/sqlline/blob/master/HISTORY.md
