Makes sense to me. Yes, I know it's 4/1 but I would support this proposal.
Craig
> On Apr 1, 2022, at 5:44 PM, Julian Hyde wrote:
>
> Going through the incubator makes sense. I would probably be champion and a
> mentor, and given the experience of the project members, there’s not much
>
Going through the incubator makes sense. I would probably be champion and a
mentor, and given the experience of the project members, there’s not much
Apache Way to be taught. We can complete the necessary admin tasks (IP check,
name search, etc.) and make a release via the Incubator.
In the
Hi,
The hard part about bringing in sub-projects is what the incubator focuses on:
importing the code base into apache repositories
getting the proper licensing in place for the code
making releases with attention to vetting, voting, and staging
working as a community
If we have suitable mentors
Petri seems to be intended for prospective top-level projects, and for projects
that have no experience with the Apache Way. Neither of those are true for
SQLLine. I would like to hear Craig’s opinion in light of the discovery that
the bylaws allow the PMC to create sub-projects.
> On Apr 1,
I would be happy to call a vote on adding SQLLine as a DB sub-project.
However, it seems to me that SQLLine must first pass the hurdles of some
process which verifies its community support and IP. If Craig thinks
that Petri is an adequate fast-track process, then that sounds like the
next
By the way, I know that DB is due to send a report for this month's ASF Board
meeting. I think it would be appropriate to mention that SQLLine has approached
the project with a view to joining as a sub-project.
On 2022/04/01 20:07:18 Julian Hyde wrote:
> Thanks for raising this, Carl. I think
Thanks for raising this, Carl. I think the SQLLine project members would be
interested in joining the DB project by this means. Given the members'
experience with Apache this low-friction approach makes sense.
Julian
On 2022/03/30 19:25:11 Carl Steinbach wrote:
> I'm a longtime user of both
