ADBA feedback

[Douglas Surber]

I’m glad to hear this. 

While we don’t intend to continue active development of AoJ, I do intend to push changes to keep it in sync with ADBA. If there is anything I can do to make those changes more palatable to asyncjdbc, do let me know. I’m not an experienced git user so I have no idea what is possible. 

Douglas

> On May 2, 2018, at 8:44 AM, Mark Rotteveel <mark at lawinegevaar.nl> wrote:
> 
> To give an update, Dave and I created www.asyncjdbc.org and created a project on https://gitlab.com/asyncjdbc/asyncjdbc with a fork of the ADBA-over-JDBC code from Oracle (from https://github.com/oracle/oracle-db-examples)
> 
> We decided to call it asyncjdbc instead of AoJ or ADBA-over-JDBC because it is short but also clear about what it does.
> 
> We're still setting things up, and when we have reorganized the code a bit and maybe given the site a bit more polish (actual content, replaced some placeholder content, etc), we'll post a real announcement (hopefully later this week).
> 
> We chose GitLab instead of GitHub, as we hope some of their features will benefit the project. We may add a repository mirror on GitHub in the future if that is sensible (and not a maintenance nightmare), to that end we also reserved https://github.com/asyncjdbc.
> 
> Mark
> 
> On 1-5-2018 17:24, Mark Rotteveel wrote:
>> Thanks, I have reached out to Dave, and we are discussing things now.
>> On 27-4-2018 18:11, Lance Andersen wrote:
>>> Maybe sync up with Dave Cramer.  Please see https://github.com/pgjdbc/AoJ/
>>> 
>>> 
>>>> On Apr 27, 2018, at 11:53 AM, Mark Rotteveel <mark at lawinegevaar.nl <mailto:mark at lawinegevaar.nl>> wrote:
>>>> 
>>>> On 27-4-2018 16:36, Douglas Surber wrote:
>>>>> The world doesn’t need more than one implementation of AoJ. AoJ is purely a descriptive name; there is nothing creative about it. Perhaps our biggest goal in creating AoJ was to jump start a community project to create an AoJ implementation. So a community AoJ fork could (should) use the AoJ name though a different package.
>>>> 
>>>> I think idea this has a bootstrapping problem. There needs to be one such initiative (and - hopefully - only one), and there needs to be sufficient traction for that to remain alive.
>>>> 
>>>> I'm willing to create an organization on GitHub that contains such a fork, but - partly due to health issues - I really don't have the time and energy to be very actively contributing or involved in that for the foreseeable future. And that can easily be the downfall of such a fork.
>>>> 
>>>> Would there be any objections to create a GitHub organization called adba-community, or maybe jdbc-community (which would allow it to be broader than just AoJ and ADBA)?
> 
> 
> -- 
> Mark Rotteveel