All of lore.kernel.org
 help / color / mirror / Atom feed
* [MPTCP] Re: Patchwork: "maintainer status"
@ 2019-10-23 20:38 Peter Krystad
  0 siblings, 0 replies; 12+ messages in thread
From: Peter Krystad @ 2019-10-23 20:38 UTC (permalink / raw)
  To: mptcp

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

On Tue, 2019-10-22 at 10:36 +0200, Matthieu Baerts wrote:
> 
> > > Patchwork maintainers are asking me to give them a list of usernames.
> > > With the web interface, I can only get your user ID and email address
> > > but not your username. May you reply to me in private (or to the list)
> > > with your username?
> > 
> > In a quite original fashion, mine is 'pabeni'
> 

For the first time in my life 'pkrystad' was already taken, so I am
'steve515'. Don't ask.

Peter.


> My pleasure!
> 
> Cheers,
> Matt

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [MPTCP] Re: Patchwork: "maintainer status"
@ 2019-11-04 13:56 Matthieu Baerts
  0 siblings, 0 replies; 12+ messages in thread
From: Matthieu Baerts @ 2019-11-04 13:56 UTC (permalink / raw)
  To: mptcp

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

Hi,

On 21/10/2019 15:13, Matthieu Baerts wrote:
> I contacted Patchwork maintainers and it seems they are OK to add MPTCP 
> to the list of projects.

Thanks to Jeremy from ozlabs.org, a new project has been created for us!

   https://patchwork.ozlabs.org/project/mptcp/

In theory, everything is setup, we should see all new patches listed there:

   https://patchwork.ozlabs.org/project/mptcp/list/

Everybody who answered to my previous message have been added to the 
maintainer list.

@Peter: It seems your email address is the @intel.com one. I guess it 
should be the @linux.intel.com one. Do not hesitate to contact Jeremy 
Kerr <jk(a)ozlabs.org> if there is an issue. Feel free to add me in cc if 
needed ;-)

Jeremy also asked me to forward this to the maintainers:

 > We have some tools that allow you to interact with patchwork from the
 > command-line (or automate through your preferred workflow). Check out
 > the git-pw, pwclient and pwnm-sync tools, at:
 >
 >      https://patchwork.readthedocs.io/en/latest/usage/clients/
 >
 > Please let your other maintainers know about that too. Keep me posted
 > if you need anything else set up for your patchwork instance.

Happy patchworking!

Cheers,
Matt
-- 
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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [MPTCP] Re: Patchwork: "maintainer status"
@ 2019-10-24  3:59 Matthieu Baerts
  0 siblings, 0 replies; 12+ messages in thread
From: Matthieu Baerts @ 2019-10-24  3:59 UTC (permalink / raw)
  To: mptcp

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


Hi Peter,
 
Wed Oct 23 22:38:47 GMT+02:00 2019 Peter Krystad :
 
> On Tue, 2019-10-22 at 10:36 +0200, Matthieu Baerts wrote:
> 
>> 
>>>> Patchwork maintainers are asking me to give them a list of usernames.
>>>> With the web interface, I can only get your user ID and email address
>>>> but not your username. May you reply to me in private (or to the list)
>>>> with your username?
>>>> 
>>> 
>>> In a quite original fashion, mine is 'pabeni'
>>> 
>> 
> 
> For the first time in my life 'pkrystad' was already taken, so I am
> 'steve515'. Don't ask.
 
It seems that you have two accounts: one with your @intel.com email address and one with your @linux.intel.com one. You can see that using the search feature, type "Krystad" and wait for the list to appear.
 
https://patchwork.ozlabs.org/project/netdev/list/?submitter=77742 [https://patchwork.ozlabs.org/project/netdev/list/?series=&submitter=77742&state=*&q=&archive=both&delegate=] 
https://patchwork.ozlabs.org/project/netdev/list/?submitter=77730 [https://patchwork.ozlabs.org/project/netdev/list/?series=&submitter=77730&state=*&q=&archive=both&delegate=] 
 
Because patchwork works with usernames, do you think we can use pkrystad and change the email address? Just to avoid delegating to "Steve" :)
 
Cheers,
Matt

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [MPTCP] Re: Patchwork: "maintainer status"
@ 2019-10-23  7:39 Matthieu Baerts
  0 siblings, 0 replies; 12+ messages in thread
From: Matthieu Baerts @ 2019-10-23  7:39 UTC (permalink / raw)
  To: mptcp

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

Hi Mat, Peter,

On 22/10/2019 23:28, Mat Martineau wrote:
> 
> On Tue, 22 Oct 2019, Matthieu Baerts wrote:
> 
>> Hi Mat,
>>
>> On 21/10/2019 22:12, Mat Martineau wrote:
>>> On Mon, 21 Oct 2019, Matthieu Baerts wrote:
>>>>
>>>>>   - are you able to subscribe <email> to your mailing list, without 
>>>> requiring a confirmation step?
>>>>
>>>> I guess that's a question for Mat :)
>>>
>>> The mailing list is currently configured to send a subscription 
>>> confirmation message with a URL, but I can turn that off if needed 
>>> (temporarily maybe?). I think the confirmation step is helpful for 
>>> preventing abuse.
>>
>> Is it not possible to force someone to be subscribed?
>>
>> If you disable the option you mentioned, I guess Patchwork maintainer 
>> will need to send an email with a specific message to our ML, right? 
>> (I don't know if what you mentioned is enough)
> 
> Oh, I misunderstood the question to be just about the confirmation part. 
> Yes, as a mailing list owner, I can add any email address without 
> confirmation.

Thank you for that! I hope we will be able to get an account soon.

@Peter: by chance, did you have the opportunity to create an account on 
https://patchwork.ozlabs.org ?
If yes, what's your username?

Cheers,
Matt
-- 
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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [MPTCP] Re: Patchwork: "maintainer status"
@ 2019-10-22 21:28 Mat Martineau
  0 siblings, 0 replies; 12+ messages in thread
From: Mat Martineau @ 2019-10-22 21:28 UTC (permalink / raw)
  To: mptcp

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


On Tue, 22 Oct 2019, Matthieu Baerts wrote:

> Hi Mat,
>
> On 21/10/2019 22:12, Mat Martineau wrote:
>> On Mon, 21 Oct 2019, Matthieu Baerts wrote:
>>>
>>>>   - are you able to subscribe <email> to your mailing list, without 
>>> requiring a confirmation step?
>>> 
>>> I guess that's a question for Mat :)
>> 
>> The mailing list is currently configured to send a subscription 
>> confirmation message with a URL, but I can turn that off if needed 
>> (temporarily maybe?). I think the confirmation step is helpful for 
>> preventing abuse.
>
> Is it not possible to force someone to be subscribed?
>
> If you disable the option you mentioned, I guess Patchwork maintainer will 
> need to send an email with a specific message to our ML, right? (I don't know 
> if what you mentioned is enough)

Oh, I misunderstood the question to be just about the confirmation part. 
Yes, as a mailing list owner, I can add any email address without 
confirmation.

--
Mat Martineau
Intel

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [MPTCP] Re: Patchwork: "maintainer status"
@ 2019-10-22  8:45 Matthieu Baerts
  0 siblings, 0 replies; 12+ messages in thread
From: Matthieu Baerts @ 2019-10-22  8:45 UTC (permalink / raw)
  To: mptcp

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

Hi Mat,

On 22/10/2019 10:34, Matthieu Baerts wrote:
> On 21/10/2019 22:12, Mat Martineau wrote:
>> On Mon, 21 Oct 2019, Matthieu Baerts wrote:

[...]

>>> Patchwork maintainers are asking me to give them a list of usernames. 
>>> With the web interface, I can only get your user ID and email address 
>>> but not your username. May you reply to me in private (or to the 
>>> list) with your username?
>>>
>>> (The username you used to log-in: https://patchwork.ozlabs.org )
>>>
>>> I didn't find any user account for Peter and Ossama. I don't know if 
>>> you would like to be added to the list of people who can change the 
>>> status of the pending patches for the kernel but if yes, you can 
>>> create an account on the website:
>>>
>>>  https://patchwork.ozlabs.org/register/
>>>
>>>>   - are you able to subscribe <email> to your mailing list, without 
>>> requiring a confirmation step?
>>>
>>> I guess that's a question for Mat :)
>>
>> The mailing list is currently configured to send a subscription 
>> confirmation message with a URL, but I can turn that off if needed 
>> (temporarily maybe?). I think the confirmation step is helpful for 
>> preventing abuse.
> 
> Is it not possible to force someone to be subscribed?
> 
> If you disable the option you mentioned, I guess Patchwork maintainer 
> will need to send an email with a specific message to our ML, right? (I 
> don't know if what you mentioned is enough)

I guess that if you turn that off, you can then subscribe anybody using 
this form: https://lists.01.org/postorius/lists/mptcp.lists.01.org/

Then no need to have manual interaction from their side, right?

Cheers,
Matt
-- 
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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [MPTCP] Re: Patchwork: "maintainer status"
@ 2019-10-22  8:36 Matthieu Baerts
  0 siblings, 0 replies; 12+ messages in thread
From: Matthieu Baerts @ 2019-10-22  8:36 UTC (permalink / raw)
  To: mptcp

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

Hi Paolo,

On 22/10/2019 09:55, Paolo Abeni wrote:
> On Mon, 2019-10-21 at 15:13 +0200, Matthieu Baerts wrote:
>> After the last meeting, we said it would be interesting to have
>> patchwork to easily list pending patches with their status and not
>> having to maintain the list manually.
>>
>> I contacted Patchwork maintainers and it seems they are OK to add MPTCP
>> to the list of projects. But they are asking 2 questions:
>>
>>   > - do you want all of your team to have maintainer status in
>> patchwork? (ie, should they all be able to update patch states?)
>>
>> I don't know exactly who would need to have this. I guess everybody who
>> did a review with an "accept" ("LGTM") should be able to directly change
>> the status, no?
> 
> I think that should be the preferred course of actions.

That would be great :)

>> Patchwork maintainers are asking me to give them a list of usernames.
>> With the web interface, I can only get your user ID and email address
>> but not your username. May you reply to me in private (or to the list)
>> with your username?
> 
> In a quite original fashion, mine is 'pabeni'

:)

Added to the list!

> Thank you for tacking care of this!

My pleasure!

Cheers,
Matt
-- 
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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [MPTCP] Re: Patchwork: "maintainer status"
@ 2019-10-22  8:34 Matthieu Baerts
  0 siblings, 0 replies; 12+ messages in thread
From: Matthieu Baerts @ 2019-10-22  8:34 UTC (permalink / raw)
  To: mptcp

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

Hi Mat,

On 21/10/2019 22:12, Mat Martineau wrote:
> On Mon, 21 Oct 2019, Matthieu Baerts wrote:
> 
>> Hi,
>>
>> After the last meeting, we said it would be interesting to have 
>> patchwork to easily list pending patches with their status and not 
>> having to maintain the list manually.
>>
>> I contacted Patchwork maintainers and it seems they are OK to add 
>> MPTCP to the list of projects. But they are asking 2 questions:
>>
>>> - do you want all of your team to have maintainer status in 
>>> patchwork? (ie, 
>> should they all be able to update patch states?)
>>
>> I don't know exactly who would need to have this. I guess everybody 
>> who did a review with an "accept" ("LGTM") should be able to directly 
>> change the status, no?
>>
> 
> Sure, that sounds reasonable. I think people will be responsible :)

Me too!

>> Patchwork maintainers are asking me to give them a list of usernames. 
>> With the web interface, I can only get your user ID and email address 
>> but not your username. May you reply to me in private (or to the list) 
>> with your username?
>>
>> (The username you used to log-in: https://patchwork.ozlabs.org )
>>
>> I didn't find any user account for Peter and Ossama. I don't know if 
>> you would like to be added to the list of people who can change the 
>> status of the pending patches for the kernel but if yes, you can 
>> create an account on the website:
>>
>>  https://patchwork.ozlabs.org/register/
>>
>>>   - are you able to subscribe <email> to your mailing list, without 
>> requiring a confirmation step?
>>
>> I guess that's a question for Mat :)
> 
> The mailing list is currently configured to send a subscription 
> confirmation message with a URL, but I can turn that off if needed 
> (temporarily maybe?). I think the confirmation step is helpful for 
> preventing abuse.

Is it not possible to force someone to be subscribed?

If you disable the option you mentioned, I guess Patchwork maintainer 
will need to send an email with a specific message to our ML, right? (I 
don't know if what you mentioned is enough)

Cheers,
Matt
-- 
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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [MPTCP] Re: Patchwork: "maintainer status"
@ 2019-10-22  8:25 Matthieu Baerts
  0 siblings, 0 replies; 12+ messages in thread
From: Matthieu Baerts @ 2019-10-22  8:25 UTC (permalink / raw)
  To: mptcp

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

Hi Florian,

On 21/10/2019 22:06, Florian Westphal wrote:
> Matthieu Baerts <matthieu.baerts(a)tessares.net> wrote:
>> I contacted Patchwork maintainers and it seems they are OK to add MPTCP to
>> the list of projects.
> 
> Thanks Matthieu.
> 
>> But they are asking 2 questions:
>>
>>> - do you want all of your team to have maintainer status in patchwork?
>> (ie, should they all be able to update patch states?)
>>
>> I don't know exactly who would need to have this. I guess everybody who did
>> a review with an "accept" ("LGTM") should be able to directly change the
>> status, no?
> 
> Note that anyone who has a patchwork account can change patch status of
> changes they submitted themselves.

Good to know, that's a useful feature!

>> Patchwork maintainers are asking me to give them a list of usernames. With
>> the web interface, I can only get your user ID and email address but not
>> your username. May you reply to me in private (or to the list) with your
>> username?
> 
> Mine is "strlen".

Thank you, added to the list!

Cheers,
Matt
-- 
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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [MPTCP] Re: Patchwork: "maintainer status"
@ 2019-10-22  7:55 Paolo Abeni
  0 siblings, 0 replies; 12+ messages in thread
From: Paolo Abeni @ 2019-10-22  7:55 UTC (permalink / raw)
  To: mptcp

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

On Mon, 2019-10-21 at 15:13 +0200, Matthieu Baerts wrote:
> After the last meeting, we said it would be interesting to have 
> patchwork to easily list pending patches with their status and not 
> having to maintain the list manually.
> 
> I contacted Patchwork maintainers and it seems they are OK to add MPTCP 
> to the list of projects. But they are asking 2 questions:
> 
>  > - do you want all of your team to have maintainer status in 
> patchwork? (ie, should they all be able to update patch states?)
> 
> I don't know exactly who would need to have this. I guess everybody who 
> did a review with an "accept" ("LGTM") should be able to directly change 
> the status, no?

I think that should be the preferred course of actions.

> Patchwork maintainers are asking me to give them a list of usernames. 
> With the web interface, I can only get your user ID and email address 
> but not your username. May you reply to me in private (or to the list) 
> with your username?

In a quite original fashion, mine is 'pabeni'

Thank you for tacking care of this!

Paolo

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [MPTCP] Re: Patchwork: "maintainer status"
@ 2019-10-21 20:12 Mat Martineau
  0 siblings, 0 replies; 12+ messages in thread
From: Mat Martineau @ 2019-10-21 20:12 UTC (permalink / raw)
  To: mptcp

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

On Mon, 21 Oct 2019, Matthieu Baerts wrote:

> Hi,
>
> After the last meeting, we said it would be interesting to have patchwork to 
> easily list pending patches with their status and not having to maintain the 
> list manually.
>
> I contacted Patchwork maintainers and it seems they are OK to add MPTCP to 
> the list of projects. But they are asking 2 questions:
>
>> - do you want all of your team to have maintainer status in patchwork? (ie, 
> should they all be able to update patch states?)
>
> I don't know exactly who would need to have this. I guess everybody who did a 
> review with an "accept" ("LGTM") should be able to directly change the 
> status, no?
>

Sure, that sounds reasonable. I think people will be responsible :)

> Patchwork maintainers are asking me to give them a list of usernames. With 
> the web interface, I can only get your user ID and email address but not your 
> username. May you reply to me in private (or to the list) with your username?
>
> (The username you used to log-in: https://patchwork.ozlabs.org )
>
> I didn't find any user account for Peter and Ossama. I don't know if you 
> would like to be added to the list of people who can change the status of the 
> pending patches for the kernel but if yes, you can create an account on the 
> website:
>
>  https://patchwork.ozlabs.org/register/
>
>>   - are you able to subscribe <email> to your mailing list, without 
> requiring a confirmation step?
>
> I guess that's a question for Mat :)

The mailing list is currently configured to send a subscription 
confirmation message with a URL, but I can turn that off if needed 
(temporarily maybe?). I think the confirmation step is helpful for 
preventing abuse.

--
Mat Martineau
Intel

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [MPTCP] Re: Patchwork: "maintainer status"
@ 2019-10-21 20:06 Florian Westphal
  0 siblings, 0 replies; 12+ messages in thread
From: Florian Westphal @ 2019-10-21 20:06 UTC (permalink / raw)
  To: mptcp

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

Matthieu Baerts <matthieu.baerts(a)tessares.net> wrote:
> I contacted Patchwork maintainers and it seems they are OK to add MPTCP to
> the list of projects.

Thanks Matthieu.

> But they are asking 2 questions:
> 
> > - do you want all of your team to have maintainer status in patchwork?
> (ie, should they all be able to update patch states?)
> 
> I don't know exactly who would need to have this. I guess everybody who did
> a review with an "accept" ("LGTM") should be able to directly change the
> status, no?

Note that anyone who has a patchwork account can change patch status of
changes they submitted themselves.

> Patchwork maintainers are asking me to give them a list of usernames. With
> the web interface, I can only get your user ID and email address but not
> your username. May you reply to me in private (or to the list) with your
> username?

Mine is "strlen".

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2019-11-04 13:56 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-23 20:38 [MPTCP] Re: Patchwork: "maintainer status" Peter Krystad
  -- strict thread matches above, loose matches on Subject: below --
2019-11-04 13:56 Matthieu Baerts
2019-10-24  3:59 Matthieu Baerts
2019-10-23  7:39 Matthieu Baerts
2019-10-22 21:28 Mat Martineau
2019-10-22  8:45 Matthieu Baerts
2019-10-22  8:36 Matthieu Baerts
2019-10-22  8:34 Matthieu Baerts
2019-10-22  8:25 Matthieu Baerts
2019-10-22  7:55 Paolo Abeni
2019-10-21 20:12 Mat Martineau
2019-10-21 20:06 Florian Westphal

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.