Hi, I think it would be positive to activate the mail notifications from gitlab and send them to this list. By activating them, you will be able to follow what is happening in our repos through mail.

Hi, ++ Meetings * This week the team at Codethink working on CIP has met f2f for the first time in Manchester, since three of us work remotely from home. ** Agreed on basic management processes we wil

Hi, as you probably know, the more features we backport, the higher will be the maintenance cost overtime so as a strategy, we need to be very conservative. I sent a mail some days ago about the featu

Hi, one of the key parts of the maintenance work is to follow the Common Vulnerabilities and Exposures (CVE)[1] and the fixes that comes out of them, in this case, to the kernel. We can check against

Hi, In the past Members Meeting, last Monday, this idea was discussed. Finally the decision taken was to stick to the (S)LTS term, that is, including the word support, instead of turning it into Maint

Hi, I had an issue with my e-mail client. Apologies for sending the mail twice.

Hi, Correction: the goal of the white paper is to provide an overview/status of CIP today.

Hi, I am writing a description for the wiki and this topic came to my mind. It is just a detail... I would like to propose that we say "maintenance" instead of "support" when referring to the activiti

Hi, if you have any update not included in this mail, feel free to add it. I do not intend to provide a full weekly report but to inform about the activity I am aware of. ++ Meetings * Members meeting

Hi, The ELCE 2016 video of the CIP talk has been published: https://www.youtube.com/watch?v=FcL2rc2o8-4&index=123&list=PLbzoR-pLrL6pRFP6SOywVJWdEHlmQE51q I added it to the events page of the wiki: htt

Dear CIP friends, At ELCE Thursday Oct 13th, the CIP group had a f2f meeting. After having lunch together, Board members met for about an hour. After that the rest of the members joined and discussed

Hi, in preparation to start reporting about the testing efforts, I have added some content to the wiki to provide context. Please let me know if there is anything wrong or that might be improved. Link

Hi, At LinuxCon EU, during the CIP talk it was announced that the first CIP kernel will be 4.4 Please find the slides of all the 2016 talks about CIP in our wiki[1]. [1] https://wiki.linuxfoundation.o

Hi, the slides[1] from the talk "Long-Term Maintenance, or how to (mis-)manage embedded systems for 10+ years" by Jan Luebbe are available. I assume by next week we will have the video. [1] http://eve

Hi, I think it is already there. Sent from mobile. Please excuse my brevity.

Hi, CIP ha set up a public wiki. It has very little content at this point and there is no policy yet to add editors. We are sorting things out. https://wiki.linuxfoundation.org/civilinfrastructureplat

Hi, Correction: Upstream fixes frequently change the kernel module API and/or ABI and backporting them in a way that is difficult and risky - CIP users set their own kernel configurations, so there wi

Hi, at CIP we need to have a clear view of what "Support" means in the context of the Super Long Term Support kernel. ++ What kind of support will CIP provide? To whom? CIP will support its members an

Hi, the below considerations were discussed during the Members meeting. There is no conclusion yet about how to proceed. ++ Security fixes +++ Out-of-tree drivers The embedded systems that CIP will be

Hi, a second consideration discussed during the meeting. Feel free to provide your opinions or considerations about them. ++ How should the kernel be released? +++ Binaries or sources While commercial