Re: [Xenomai] [RFC] RTnet, Analogy and the elephant in the room

["Stéphane LOS" <slos@hilscher.com>]

Hi,

Wouldn't integrating both projects make sense ?

It seems both share a significant amount of work and similar lack of 
resources.

Sorry, talking about the "Real Time Linux" project and "Xenomai"...

And sorry for the noise added automagically to my emails. :-(
I should use some other mail account.

Best Regards,
Cordialement,

Stéphane LOS
slos@hilscher.com
Support technique

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hilscher France
12, rue du 35ème Régiment d'Aviation
Miniparc du Chêne
69500 BRON
France
Tél. : +33 (0) 4 72 37 98 40
Fax  : +33 (0) 4 78 26 83 27
http ://www.hilscher.fr
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Le 24/11/2017 à 09:52, Stéphane LOS a écrit :
> Hi,
>
> Wouldn't integrating both projects make sense ?
>
> It seems both share a significant amount of work and similar lack of 
> resources.
>
> Best Regards,
> Cordialement,
>
> Stéphane LOS
> slos@hilscher.com
> Support technique
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Hilscher France
> 12, rue du 35ème Régiment d'Aviation
> Miniparc du Chêne
> 69500 BRON
> France
> Tél. : +33 (0) 4 72 37 98 40
> Fax  : +33 (0) 4 78 26 83 27
> http ://www.hilscher.fr
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Le 23/11/2017 à 21:45, Philippe Gerum a écrit :
>> On 11/22/2017 09:26 PM, Jan Kiszka wrote:
>>> On 2017-11-21 18:11, Philippe Gerum wrote:
>>>> So, let's talk about the elephant in the room: the current 
>>>> situation of
>>>> the Xenomai project is not viable in the long run. I can only 
>>>> encourage
>>>> people who feel concerned about it to discuss openly the practical 
>>>> steps
>>>> to best address this challenge.
>>> Thanks for bringing this frankly on the table! For those who follow the
>>> project, it's likely no news. So we were working on this issue also
>>> internally, with users of Xenomai inside Siemens. And we have the
>>> backing to enhance our involvement in upstream work. Right now we are
>>> working on making this concrete.
>>>
>>> There are many areas where contributions can be beneficial for the
>>> project and its community, and many do not require deepest 
>>> understanding
>>> of the core, like around CI, test automation, distro packaging,
>>> documentation, or user support. But some essential elements in my 
>>> eyes are
>>>
>>>   - building up a core team of kernel maintainers for Cobalt
>>>
>>>   - offloading work from the shoulders of our extremely valuable
>>>     maintainer
>>>
>>> The second part will be achieved to a certain degree by the first 
>>> one as
>>> Philippe can probably confirm.
>> Yes, extending "Cobalt" to the pipeline. A significant portion of the
>> overall maintenance involves the I-pipe. Hence the work on rethinking
>> how the interrupt pipeline is integrated into the Linux kernel, how we
>> can make the former a regular feature of the latter instead of an
>> add-on, with the goal of simplifying the maintenance, but also making
>> the whole thing way more natural, easier to grasp.
>>
>



Hilscher France S.a.r.l.   |  12, rue du 35ième Régiment d’Aviation – Miniparc du Chêne  |  69500 Bron  |  France  |  www.hilscher.com
Hot Line: +33 (0) 472 379 843  |  Centre de formation agréé  |  RandD: +33 (0) 472 379 840
N° de TVA intracommunautaire: FR 43 449 481 779  |  N° de SIRET: 449 481 779 00014
Dirigeant: Christophe Levra

Important Information:
This e-mail message including its attachments contains confidential and legally protected information solely intended for the addressee. If you are not the intended addressee of this message, please contact the addresser immediately and delete this message including its attachments. The unauthorized dissemination, copying and change of this e-mail are strictly forbidden. The addresser shall not be liable for the content of such changed e-mails.

Hilscher cannot be held responsible of whatever nature, resulting from alteration, falsifying or using of the information contained in this message and disclaims all liability in case of contamination of the computer hardware of the addressee resulting from the distribution of a virus or other computing infections.


Information Importante:
Ce message électronique incluant les pièces jointes contient des informations confidentielles et protégées par la loi qui sont à l’intention exclusive de son destinataire. Si vous n'êtes pas le destinataire  de ce message, merci de contactez immédiatement l'expéditeur et de supprimer ce message incluant les pièces jointes. Toute diffusion ou copie ou modification de ce message électronique, totale ou partielle, non autorisée est strictement interdit. L'expéditeur ne peut être tenu responsable du contenu de tels messages électroniques qui auraient été modifies.

Hilscher ne pourra être tenue responsable de quelque dommage, de quelque nature qu’il soit, résultant de l’altération, de la falsification ou de l’utilisation des informations contenues dans ce message et décline toute responsabilité en cas de contamination des matériels informatiques du destinataire résultant de la propagation d'un virus ou autres infections informatiques.