|Re: [osgi-dev] Specification process for the project|
----- Original message -----
From: BJ Hargrave/Austin/IBM
Subject: Specification process for the project
Date: Fri, Mar 19, 2021 18:07
Following on to the decision to use git branches for requirements and design work, I wrote up the process for CONTRIBUTING.md in https://github.com/osgi/osgi/pull/165. Please review and comment.--
Senior Technical Staff Member, IBM // office: +1 386 848 1781
OSGi Fellow and OSGi Specification Project lead // mobile: +1 386 848 3788
hargrave@xxxxxxxxxx----- Original message -----
From: David Bosschaert <david.bosschaert@xxxxxxxxx>
Sent by: "osgi-dev" <osgi-dev-bounces@xxxxxxxxxxx>
To: OSGI Developer discussions <osgi-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [osgi-dev] Minutes of the OSGi Specification Project meeting, 17th March 2021
Date: Fri, Mar 19, 2021 09:25
Note that I made a small type at the end of the minutes.Next meeting should be:Wednesday March 31st, at 1400 UTC (correct for your own timezone / daylight saving time)
Meeting location: https://eclipse.zoom.us/j/93367977807On Fri, 19 Mar 2021 at 08:42, David Bosschaert <david.bosschaert@xxxxxxxxx> wrote:Hi all,The minutes for the first OSGi Specification Project meeting are now on the wiki:If there's anything I missed, let me know.Kind regards,David----2021-03-17 Call
Attendees: BJ Hargrave, James Hunt, David Bosschaert, Tom Watson, Tim Ward, Kai Hackbarth, Ray Augé, Todor Boev, Jürgen Albert, Karl Pauls, Mark Hoffman
This is the first OSGi Specification Project call held at Eclipse.
BJ opens the meeting.
Question: what do we do with existing OSGi Compendium R8 specs that are in-flight?
We need to create issues for each of these specs in the project which point to where the work is going on.
Requirements, design and API will be done in a branch on the main osgi/osgi repository. Requirements and design will be done in Markdown or Asciidoc files on this branch. People can file PRs on these and they automatically get rendered by github.
[after meeting edit: diagrams can be included via plant uml embedding in either format, see https://github.com/rotty3000/design/blob/rotty3000-patch-1/ditaa.md for an example]
Action for everyone involved in an OSGi R8 compendium spec chapter:
create a pointer issue for your spec in flight
Tom suggests to post an agenda in advance of this meeting going forward.
Next meeting: Wednesday October 31st, at 1400 UTC (correct for your own timezone / daylight saving time)
Meeting location: https://eclipse.zoom.us/j/93367977807_______________________________________________
osgi-dev mailing list
To unsubscribe from this list, visit https://accounts.eclipse.org
Back to the top