ADBA feedback

[Douglas Surber]

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.

Douglas

> On Apr 27, 2018, at 3:12 AM, Lukas Eder <lukas.eder at gmail.com> wrote:
> 
> Since the existing version is ASL 2.0 licensed, I don't see any issues with forking - except perhaps for the name. As/if the fork evolves, it shouldn't be called AoJ as that is your original name.
> 
> Thanks for offering help with such a potential community effort.
>