RTEMS Project projects?

[Gedare Bloom]

On Mon, Jan 20, 2020 at 2:11 PM Joel Sherrill <joel at rtems.org> wrote:
>
>
>
> On Mon, Jan 20, 2020 at 2:56 PM Chris Johns <chrisj at rtems.org> wrote:
>>
>> On 21/1/20 4:15 am, Gedare Bloom wrote:
>> > Maybe just a hierarchical picture could be provided.
>
>
> I'd be thrilled to hear we have enough organizational structure to need a figure. :)
>
> Seriously, it couldn't hurt. We now have a number of separate repositories:
> rtems, rtems-libbsd, rtems-tools, rtems-libbsd, the release tools.
>
> That ignores web infrastructure, buildbot, Trac, etc.
>
> It can't do anything but help to get our hands around it all.
>
>>
>> >
>> > I'd also be OK with new "projects" using a different noun, such as "effort"
>> >
>> > As with Chris, I would not change established language (such as for
>> > RTEMS Tools Project). Nice Qualification is still getting off the
>> > ground, the language around it could change.
>>
>> Do we need to diverge from what we have? Is there some standards thing related
>> to the language I do not understand?
>
>
> I don't think there is any reason to move to sub-projects. The RTEMS Project is
> just a higher level use of the term. It encompasses all individual projects, tasks,
> tickets, processes, servers, etc.
>
Sorry, "language" is ambiguous, I did not mean "programming language"
I meant how we refer to the qualification effort/project. It can be
called something other than a "project" if so decided. But, I don't
see it as a strong need. We have "RTEMS Project" as an umbrella that
everything else falls under (in the open-source community
perspective).

If there are activities outside the scope of the RTEMS Project, i.e.,
in a closed/proprietary way, it would be mildly inappropriate to call
those "RTEMS Xyz Project"

> --joel
>
>>
>>
>> Chris
>>
>> >
>> > Gedare
>> >
>> > On Sun, Jan 19, 2020 at 10:29 PM Chris Johns <chrisj at rtems.org> wrote:
>> >>
>> >> On 3/1/20 11:30 pm, Sebastian Huber wrote:
>> >>> I work currently on the first chapters of the RTEMS Software Engineering manual.
>> >>> I came across the term "RTEMS Qualifaction Project" and also "RTEMS
>> >>> Documentation Project". What the "RTEMS Project" is, is more or less clear.
>> >>
>> >> Clear to whom? Yes to you and I and it should be after all these years. To
>> >> someone new it may not be as clear at all.
>> >>
>> >>> It
>> >>> is the community, infrastructure, and the free and open RTEMS itself. But, do we
>> >>> really have to emphasize that there are in addition an "RTEMS Qualifaction
>> >>> Project" and an "RTEMS Documentation Project"?
>> >>
>> >> I am fine with project, it is in common use. Webster defines it as "To form a
>> >> project; to scheme." and this seems to fit how we are using it.
>> >>
>> >>> For me these are merely
>> >>> activities and components inside the RTEMS Project. What would be the mission
>> >>> statement of the projects?
>> >>
>> >> These things are not precise. KDE refers to itself as a community and encourages
>> >> new users to start projects, Fedora is a project and talks about roles users can
>> >> take.
>> >>
>> >>> What about overlaps?
>> >>
>> >> There is overlap.
>> >>
>> >>> There is currently an RTEMS pre-qualification activity according to ECSS
>> >>> standards ongoing. So, a general term for this activity is useful. I am not sure
>> >>> if we should name this "RTEMS Qualification Project". I would name it
>> >>> "pre-qualification activity in the RTEMS Project" and short "pre-qualification
>> >>> activity".
>> >>
>> >> I am not in favor of this. The RTEMS Tools Project is in lots of places, too
>> >> many to change.
>> >>
>> >> The splitting up of these activities into projects helps us attract new users
>> >> who may think RTEMS is too complex and not accessible for them. Maybe focusing
>> >> on a smaller activity or project may be a way to get started.
>> >>
>> >> Chris
>> >> _______________________________________________
>> >> devel mailing list
>> >> devel at rtems.org
>> >> http://lists.rtems.org/mailman/listinfo/devel
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel