Re: [MPTCP] Community Coordination

Re: [MPTCP] Community Coordination

[Matthieu Baerts]

[-- Attachment #1: Type: text/plain, Size: 2656 bytes --]

On Mon, Mar 5, 2018 at 11:37 PM, Mat Martineau <mathew.j.martineau(a)linux.
intel.com> wrote:

>
> On Mon, 5 Mar 2018, Matthieu Baerts wrote:
>
> Hi Mat,
>>
>> Thank you for this very nice email!
>> I agree with what you said. Here is just one more idea and one comment:
>>
>> On Fri, Mar 2, 2018 at 11:45 PM, Mat Martineau <
>> mathew.j.martineau(a)linux.intel.com> wrote:
>>       Coordinating amongst ourselves is a very challenging aspect of this
>> project. In my past kernel projects, collaboration among
>>       industry peers took place on a subsystem mailing list that was a
>> gateway to upstream. Similarly, mptcp-dev is a gateway to
>>       the multipath-tcp.org kernel. In both cases the roles are clearer
>> because there is direct interaction between the
>>       contributor and gatekeepers.
>>
>>
>> Speaking about mptcp-dev, may I suggest you to forward this email to this
>> list?
>> When we talked about the this ML 2 weeks ago in Louvain-la-Neuve, not so
>> many people knew about it. Maybe other people from mptcp-dev ML
>> are interesting to contribute to this project.
>>
>
> Good idea, I'll send a (re)introduction message to mptcp-dev. We had a
> brief upstreaming discussion there last year, but reviewing the archives I
> see that I didn't update that thread after establishing mptcp(a)lists.01.org
>

Thank you!

I just found the messages you sent last year, I forgot about them. I guess
a reintroduction would then be good :-)

Best regards,
Matthieu
-- 
[image: Tessares SA] <http://www.tessares.net> Matthieu Baerts | R&D
Engineer
matthieu.baerts(a)tessares.net
Tessares SA | Hybrid Access Solutions
www.tessares.net
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium
<https://www.google.com/maps?q=1+Avenue+Jean+Monnet,+1348+Ottignies-Louvain-la-Neuve,+Belgium>

-- 

------------------------------
DISCLAIMER.
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you have received this email in error please notify the system manager. 
This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited.

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5011 bytes --]

Re: [MPTCP] Community Coordination

[Mat Martineau]

[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]


On Mon, 5 Mar 2018, Matthieu Baerts wrote:

> Hi Mat,
> 
> Thank you for this very nice email!
> I agree with what you said. Here is just one more idea and one comment:
> 
> On Fri, Mar 2, 2018 at 11:45 PM, Mat Martineau <mathew.j.martineau(a)linux.intel.com> wrote:
>       Coordinating amongst ourselves is a very challenging aspect of this project. In my past kernel projects, collaboration among
>       industry peers took place on a subsystem mailing list that was a gateway to upstream. Similarly, mptcp-dev is a gateway to
>       the multipath-tcp.org kernel. In both cases the roles are clearer because there is direct interaction between the
>       contributor and gatekeepers.
> 
> 
> Speaking about mptcp-dev, may I suggest you to forward this email to this list?
> When we talked about the this ML 2 weeks ago in Louvain-la-Neuve, not so many people knew about it. Maybe other people from mptcp-dev ML
> are interesting to contribute to this project.

Good idea, I'll send a (re)introduction message to mptcp-dev. We had a 
brief upstreaming discussion there last year, but reviewing the archives I 
see that I didn't update that thread after establishing mptcp(a)lists.01.org

>
>       Matthieu has offered to set up regular meetings, which I think will make it easier to plan our efforts and stay informed
>       about what everyone is working on. We should make sure each meeting has a designated notetaker who can post a summary to the
>       mailing list, so we have a record of what was discussed and people who couldn't attend or prefer written communication can
>       stay up to date. Watch the list for scheduling information.
> 
> 
> Thank you for accepting to participate!
> I proposed to have a first meeting this Thursday 8th of March at 17:00 UTC/GMT: 9am PST time zone, 6pm CET time zone. I am going to send
> a separate email for this meeting.
> Please tell if you want me to also send you the calendar invitation. I can also share this calendar invitation to this Mailing List.
> 
> Good idea for the notes, I can start taking them if it is fine for everyone.

That would be very helpful, thank you.

--
Mat Martineau
Intel OTC

Re: [MPTCP] Community Coordination

[Matthieu Baerts]

[-- Attachment #1: Type: text/plain, Size: 2946 bytes --]

Hi Mat,

Thank you for this very nice email!
I agree with what you said. Here is just one more idea and one comment:

On Fri, Mar 2, 2018 at 11:45 PM, Mat Martineau <mathew.j.martineau(a)linux.
intel.com> wrote:

> Coordinating amongst ourselves is a very challenging aspect of this
> project. In my past kernel projects, collaboration among industry peers
> took place on a subsystem mailing list that was a gateway to upstream.
> Similarly, mptcp-dev is a gateway to the multipath-tcp.org kernel. In
> both cases the roles are clearer because there is direct interaction
> between the contributor and gatekeepers.
>

Speaking about mptcp-dev, may I suggest you to forward this email to this
list?
When we talked about the this ML 2 weeks ago in Louvain-la-Neuve, not so
many people knew about it. Maybe other people from mptcp-dev ML are
interesting to contribute to this project.

Matthieu has offered to set up regular meetings, which I think will make it
> easier to plan our efforts and stay informed about what everyone is working
> on. We should make sure each meeting has a designated notetaker who can
> post a summary to the mailing list, so we have a record of what was
> discussed and people who couldn't attend or prefer written communication
> can stay up to date. Watch the list for scheduling information.
>

Thank you for accepting to participate!
I proposed to have a first meeting this Thursday 8th of March at 17:00
UTC/GMT: 9am PST time zone, 6pm CET time zone. I am going to send a
separate email for this meeting.
Please tell if you want me to also send you the calendar invitation. I can
also share this calendar invitation to this Mailing List.

Good idea for the notes, I can start taking them if it is fine for everyone.

Best regards,
Matthieu
-- 
[image: Tessares SA] <http://www.tessares.net> Matthieu Baerts | R&D
Engineer
matthieu.baerts(a)tessares.net
Tessares SA | Hybrid Access Solutions
www.tessares.net
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium
<https://www.google.com/maps?q=1+Avenue+Jean+Monnet,+1348+Ottignies-Louvain-la-Neuve,+Belgium>

-- 

------------------------------
DISCLAIMER.
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you have received this email in error please notify the system manager. 
This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited.

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5233 bytes --]

[MPTCP] Community Coordination

[Mat Martineau]

[-- Attachment #1: Type: text/plain, Size: 2158 bytes --]


Hello everyone -


Matthieu brought something up a couple of days ago that I'd like to get 
back to:


On Wed, 28 Feb 2018, Matthieu Baerts wrote:

> What we also think is that this upstreaming job is not easy. The best is 
> certainly to well organise that and prepare as a team here questions/RFC 
> to netdev. I am personally not used to work on big changes on the same 
> subject between different organisations but we guess it would be helpful 
> to organise regular (virtual) meetings to share plans of what can be 
> done by who.


Coordinating amongst ourselves is a very challenging aspect of this 
project. In my past kernel projects, collaboration among industry peers 
took place on a subsystem mailing list that was a gateway to upstream. 
Similarly, mptcp-dev is a gateway to the multipath-tcp.org kernel. In both 
cases the roles are clearer because there is direct interaction between 
the contributor and gatekeepers.

In our case, mptcp(a)lists.01.org does not have any gatekeepers. It's a 
place for peer contributors with a common goal to collaborate and seek 
consensus. Participation is voluntary and the recommendations made on the 
list are shared in the hope that they are helpful, but are not binding.


I think it will be effective to share patch sets on this list and conduct 
email code reviews (in typical kernel mailing list format), so we can help 
each other refine patches before posting to netdev.

Matthieu has offered to set up regular meetings, which I think will make 
it easier to plan our efforts and stay informed about what everyone is 
working on. We should make sure each meeting has a designated notetaker 
who can post a summary to the mailing list, so we have a record of what 
was discussed and people who couldn't attend or prefer written 
communication can stay up to date. Watch the list for scheduling 
information.


We currently have a few threads going, and with more proposals and code on 
the way there will be plenty of fuel for constructive discussion. Thank 
you for your past and future contributions!


Regards,

--
Mat Martineau
Intel OTC