This does not make sense from the charter of the Specification Project:
“The OSGi® Specification Project is an open source initiative to create new, and evolve existing, software specifications, implementations of those specifications, and Technology Compatibility
Kits (TCKs) for those specifications”
The osgi-test project is not a specification, it is not an implementation of a specification. If you squint really hard maybe you can declare it to be a TCK but it is not. It is just a (critical) dependency
of the TCK like Junit and assertj are.
So, I don’t think this proposal is supported by the charter of the Specification Project nor necessary. I don’t see a description of some technical problem which cannot be solved other than by moving the project.
I don’t see justification to support this proposal.
--
BJ Hargrave
Senior Technical Staff Member, IBM // office: +1 386 848 1781
Open Source Development // mobile: +1 386 848 3788
hargrave@xxxxxxxxxx
From:
osgi-technology-dev <osgi-technology-dev-bounces@xxxxxxxxxxx> on behalf of Stefan Bischof via osgi-technology-dev <osgi-technology-dev@xxxxxxxxxxx>
Date: Wednesday, October 23, 2024 at 13:04
To: osgi-technology-dev@xxxxxxxxxxx <osgi-technology-dev@xxxxxxxxxxx>, osgi-wg-specification-committee@xxxxxxxxxxx <osgi-wg-specification-committee@xxxxxxxxxxx>
Cc: Stefan Bischof <stbischof@xxxxxxxxxxx>
Subject: [EXTERNAL] [osgi-technology-dev] Proposal to Transfer the OSGi-Test Subproject to the OSGi-Specification Project
Dear OSGi Specification and OSGi Technology Project members,
I hope this message finds you well.
As discussed during our joint meeting on October 21, 2024, in Karlsruhe
(see meeting notes), we are proposing the transfer of the osgi-test
subproject and GitHub repository from the OSGi-Technology Project to the
OSGi-Specification Project.
The main reason for this transfer is that the osgi-test project is a
critical dependency for all TCKs and is more closely aligned with the
work of the OSGi-Specification Project. Additionally, this move will
help ensure that dependencies between the projects only flow in one
direction, from OSGi-Specification to OSGi-Technology, thus preventing
circular dependencies.
Meeting excerpt:
```
OSGi Test
This should be "given" to the specification project. It's a hard
dependency of all the TCKs and we wish to avoid a dependency from
org.osgi on org.eclipse.osgi-technology. The OSGi Test project will
still be managed as an externally available resource.
```
We would appreciate any feedback or questions you may have regarding
this proposal. If there are no objections, we aim to move forward with
this transfer soon.
I also opened an Issue in the emo-office of the eclipse-fdn:
https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/820
Thank you for your attention and continued support.
Best regards,
Stefan Bischof
_______________________________________________
osgi-technology-dev mailing list
osgi-technology-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
