Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[osgi-technology-dev] new Agenda.Item for 13.11.2024 Steering-Commitee

Hello,

i would add one point to the Agenda.

OSGi-Technology Projects in OSGi Organisation.
Projects:
  • https://github.com/osgi/osgi-test
  • https://github.com/osgi/slf4j-osgi
  • https://github.com/osgi/osgi.enroute
  • https://github.com/osgi/osgi.enroute.site

    Issue:

    Full Issue:
    https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5100

    Short:
    Things in technology.osgi are under the Eclipse Specification Development Process. This process has a more complex release process involving the specification committee. Things in technology.osgi-technology are under the more simple Eclipse Development process. This is why we originally created 2 projects for OSGi: spec things and normal open source projects. technology.osgi must be limited to specifications and TCKs of specifications. Implementations of specifications are welcome but not required to be in technology.osgi. All other OSGi related projects which are not specifications and not TCKs of specifications, such as osgi-test, MUST NOT be in technology.osgi and MUST be in technology.osgi-technology to be under the more simple Eclipse Development Process.

    If we would migrate this Projects to OSGi-Technology - Github-Organisation, this Project needs access to the Maven-Credentials for org.osgi.
    The Eclipse Security-Team would allow and this.


    More in the Discussion tomorrow.


    Stefan Bischof

  • Back to the top