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