| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| *** | ChanServ sets mode: +v mchehab | [03:01] |
| .......................................................... (idle for 4h47mn) | ||
| hverkuil1 | I agree with pinchartl. It does need clarification w.r.t. mailinglists.
mchehab: I will look into the key issues with my signed tags later this week. Please don't postpone handling pull requests from me waiting for me to fix this. It will be done, once I have some time to figure out what's going on. And there is always the next pull request to test this :-) | [07:48] |
| .................................. (idle for 2h49mn) | ||
| mchehab | pinchartl: the more I read it, the more I become more concerned. IMHO, the previous CoC was *a lot* better
reading it behind lines, it actually makes maintainer responsible even for bad behaviors of someone on community events, including parties if someone gets drunk on a party and the maintainer does nothing, the maintainer can be pushished | [10:40] |
| pinchartl | you're reading too much into the code of conduct
that's not what the intent is | [10:42] |
| mchehab | I really don't think it is a maintainer's duty to do anything on such cases. If the drunk guy breaks the law, someone should call the police and the legal system will take care of it.
"whatever happens in Vegas, stays in Vegas". | [10:48] |
| pinchartl | the intent is to prevent maintainers from actively endorsing, promoting or exhibiting abusive behaviour | [10:49] |
| hverkuil | "This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community." | [10:50] |
| mchehab | I know the intent, but what's written there is completely different thing
it is amazingly badly written | [10:52] |
| pinchartl | there will likely be a FAQ that will clarify the intent. you should submit proposals for all items that you think require clarifications | [10:52] |
| mchehab | hverkuil, hverkuil1: with regards of the pull request, I was worried that this didn't came from you, as it doesn't match your GPG key | [10:53] |
| hverkuil | I don't think a party falls under that. But if someone would participate on a panel or give a presentation during a conference while drunk, and you learn about this, then you would have to take action. | [10:53] |
| mchehab | hverkuil: a party that it is part of an official agenda of a LF event falls under it | [10:54] |
| hverkuil | mchehab: I can repost without the signed tag if you like?
It might be Friday before I have time to look into this. | [10:54] |
| mchehab | I would really prefer if you sign with a gpg key I trust
e. g. a key I cross-signed - I'm pretty sure I signed your keys already in any case, let's reserve some time at the summit for a key party in case someone doesn't have a signed key | [10:55] |
| hverkuil | mchehab: can you post a RFP for that? I plan to put an initial draft ELCE agenda together on Monday. If it isn't in an RFP I'll forget :-) | [10:58] |
| mchehab | :-)
sent gah, I almost violated the CoC with that... (never heard about this - until I tried to check what's the proper name for this kind or party: https://www.urbandictionary.com/define.php?term=key%20party) in other words, I meant "key chain party" (and not the previous term I used before - with apparently has a completely different meaning) ops key signing party https://en.wikipedia.org/wiki/Key_signing_party uff... used the right term at the email's subject :-) Subject: [RFP] Key signing party at the media summit | [10:59] |
| hverkuil, is this your public key? key 66143B4C: "Hans Verkuil <hverkuil@xs4all.nl>"
That's the one I signed: $ gpg --list-sigs 66143B4C pub 4096R/66143B4C 2014-10-14 [expires: 2024-10-11] uid Hans Verkuil <hverkuil@xs4all.nl> sig 308AD4EC 2014-10-14 Sakari Ailus <sakari.ailus@iki.fi> sig 8EE4E115 2015-07-30 Mauro Carvalho Chehab <mchehab@kernel.org> sig 9C45B399 2015-07-30 Lars-Peter Clausen <lars@metafoo.de> sig 0D0D431C 2015-08-06 Shuah Khan <shuah@gonehiking.org> sig 6991256E 2015-07-30 Laurent Pinchart <laurent.pinchart@ideasonboard.com> sig 3 66143B4C 2014-10-14 Hans Verkuil <hverkuil@xs4all.nl> sig F8B36D28 2017-10-28 Gustavo Padovan <gustavo@padovan.org> sig 1524FAF8 2017-11-25 Alexandre Courbot <gnurou@gmail.com> sub 4096R/BA50EA2F 2014-10-14 [expires: 2024-10-11] sig 66143B4C 2014-10-14 Hans Verkuil <hverkuil@xs4all.nl> | [11:15] | |
| hverkuil | Correct, that's my public key. But I created a subkey for signing, and that appears not to be known. | [11:20] |
| .... (idle for 16mn) | ||
| $ gpg --fingerprint hverkuil@xs4all.nl
pub   rsa4096 2014-10-14 [SC] [expires: 2024-10-11]      052C DE7B C215 053B 689F  1BCA BD2D 6148 6614 3B4C uid           [ unknown] Hans Verkuil <hverkuil@xs4all.nl> sub   rsa4096 2014-10-14 [E] [expires: 2024-10-11] So the problem appears to be that the subkey is only marked for [E] when it should be [SE]. I need to be home to see if I can fix this mess. Will try this later today. | [11:36] | |
| pinchartl | hverkuil: the problem seems to be that you have signed your tag with an entirely different key
the key ID doesn't match your subkey either | [11:44] |
| hverkuil | Yes, I think I have different subkeys locally. I've no idea what happened.
For some reason I always manage to make a mess of these things. | [11:45] |
| pinchartl | (which reminds me that I have to update the expiration date on my subkeys) | [11:50] |
| ..... (idle for 20mn) | ||
| mchehab | hverkuil: first of all, why do you need a subkey for signing?
also, did you push the changes you've made to a keychain server? | [12:10] |
| hverkuil | To use the main key for signing I need to use my usb drive which contains the secret key. That was recommended last time for extra security so the secret key is not stored on your PC. But then you want a subkey for signing. And for some reason that subkey has a different expiry date and refuses to be exported on the main keyserver. | [12:15] |
| pinchartl | mchehab: it's a good practice to sign with a subkey, in order not to carry the master key around | [12:15] |
| hverkuil | I can probably (hopefully) fix it, but I need my master key, and that's at home. | [12:15] |
| ............................. (idle for 2h20mn) | ||
| hverkuil1 | mchehab: it looks like my usb drive with my master is in the Netherlands, and I won't be there until the weekend. For now I'll revert back to the old-fashioned pull requests until I have this sorted.
master -> master key | [14:35] |
| ....... (idle for 31mn) | ||
| mchehab: I think gpg --recv-key 1326E0CD23ABDCE5 might now work. Can you try again? | [15:07] | |
| pinchartl | hverkuil: much better | [15:08] |
| hverkuil1 | I think I originally forgot to export the subkeys to the server, and when I did that earlier today it took a while before the keys appeared (delayed mirroring?) | [15:09] |
| mchehab | yeah, now it got it | [15:09] |
| hverkuil1 | I still need to update them since the sign subkey expires next month | [15:09] |
| mchehab | will try to pull it on my server later, likely today | [15:09] |
| hverkuil1 | will do that next week. | [15:09] |
| mchehab | mchehab is busy with some other stuff atm
thanks for addressing it! | [15:09] |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |