Re: [Openrocket-devel] Announcement: End of my role as maintainer of the parts database

[Neil W. <nei...@gm...>]

Thanks for your work in putting this DB together in the first place,
maintaining it, and letting us use it.  It's a big asset to the app and to
the community at large.

We'll certainly have some more discussion about this going forward.  I
suspect that forking the repo and integrating it into our build process is
mostly mechanical; keeping the database up-to-date in the future is a more
interesting question that we'll have to think about.

- Neil

On Wed, Mar 20, 2024 at 12:34 PM Dave Cook <cav...@gm...> wrote:

> Hi everyone,
>
> Hopefully this reaches everyone that needs to know, as this list has been
> very quiet for the last 18 months.
>
> I would like to announce that after working on it since 2015, I am
> stepping down from further regular development and maintenance of the parts
> database in github.com/dbcook/openrocket-database.  There really have
> been very few PRs and issues over the last year, and no difficult ones.
> Overall I think the database is fairly mature, and for reasons outlined in
> the readme, continuing comprehensive coverage of the Estes product line is
> infeasible given the offshore manufacturing methods.
>
> At present the OR build pulls directly from my repo as a submodule.  What
> needs to happen now is for OR to create a fork of my repo in its own github
> account, assign some maintainers and point the build to that fork.  I have
> no intention of taking my repo down; I'm just letting you know to not
> expect many future updates, and that I may no longer respond to PRs/issues
> against my repo quickly, or at all.
>
> I'd also like to call attention to a license compliance issue with the
> packaged installers.  After installation of the OR package (on Mac at
> least), there is no LICENSE file present for either the GPL used by the
> main OR code base nor the Apache 2.0 for my database.  Both licenses
> require that any distribution must include a copy of the applicable
> license.  The packaged installer builds need to be modified to include
> copies of both licenses in user-visible locations (i.e. buried in the Mac
> OpenRocket.app resource bundle is not OK).  I trust that this will be
> fairly easy and can be done for the next release.
>
> I'm sure this handover will trigger at least some discussion and I'll
> undertake to respond promptly.
>
> Best regards,
> Dave Cook
> NAR 21953 L3
> _______________________________________________
> Openrocket-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openrocket-devel
>