Qualification of RTEMS SMP (ECSS)
Helder.Silva at edisoft.pt
Thu Dec 6 09:45:48 UTC 2018
Sorry, but I truly do not know currently how the RTEMS community repository is organized and we have not yet defined the way we would like to organize the part of the Qualification RTEMS SMP repository.
But from our previous experience, we would need a repository that would record all the deliverables of the qualification.
It includes documentation:
-RTEMS Code (if applicable)
-test plans (validation, integration and unit)
-test reports and document (several versions of it)
-Critical Analysis report
-Reference documentation (presentations, reports, etc)
WIP branches for Software Problem Reports resolution.
We intend to use the git.rtems.org, if possible for you.
Once again, my knowledge about the community repository organization is null. Do you have any Wiki that describes the "way of working" in the RTEMS community?
From: users [mailto:users-bounces at rtems.org] On Behalf Of Chris Johns
Sent: quinta-feira, 6 de dezembro de 2018 00:47
Cc: users at rtems.org
Subject: Re: Qualification of RTEMS SMP (ECSS)
On 05/12/2018 17:14, Sebastian Huber wrote:
> On 04/12/2018 17:53, Amaan Cheval wrote:
>> This is great news!
>> - Is there a way for other interested parties to join the effort (volunteers
>> from the community)?
> Yes, of course, however it will be not easy to coordinate. The development
> should follow the usual RTEMS development workflow, e.g. discussions on the
> mailing list, tickets, patches for review, etc.
There is a couple of points we need to consider.
Ideally the qualification effort needs to have a "zero cost" impact on the open
source RTEMS project. The term "zero cost" is fluid in an open source project
and it is an ideal that will be hard to meet but as a goal it is good to have.
There will be some monetary costs and there will be overheads added to the open
source project and how it operates. We will all need to wear two hats, a
qualification one and a community contributor hat.
As Joel as stated, the qualification process in the RTEMS project needs to
sustain itself. It's life cycle, processes and outcomes needs to run
independently of the RTEMS parts it depends on. Qualification could be viewed as
a specialised deployment of RTEMS. Anyone should be able to take the
qualification processes and use them to create the needed artefacts for
>> - Will all the work also be planned on public channels (devel@, public WIP
>> branches, etc.)?
> The project infrastructure is undecided. We probably need some extra Git
> repositories for WIP stuff. I am not sure if we want to add WIP branches to the
> main RTEMS repositories.
I would need to see some more detail on what you and others are considering as a
way of working before I can agree to adding branches. Branches are easy to
create, it is what happens to them and when that is the hard part.
Why not use master?
> Maybe we can host the WIP repositories on rtems.org or Github.
The RTEMS Project does not support the hosting of active repos on github, we
mirror repos we consider important. We host our repos on git.rtems.org. My
concern fragmenting what we have and where users find things.
users mailing list
users at rtems.org
More information about the users