Re: Being a part of the Cloud team
Hi Utkarsh, Em dom, 4 de ago de 2019 às 23:11, Utkarsh Gupta escreveu: > Hey, > > I have been meaning to be a part of the Cloud team for a while now. > At this DebConf, I had a word with Tomasz regarding the same. > And as asked, here are some points that I was asked to write to the list. > > I am a Debian Maintainer and a part of Ruby, JS, Golang, and the Perl team. > My QA page could be found here[1]. > Under Cloud team, for now, I am helping in packaging image-finder by > packaging it's dependencies listed here[2]. > Thanks for your work in helping to package up the image finder. We hope to make ASAP available for everyone to test. As discussed with Tomasz, I could help with the CI stuff, since I > maintain GitLab (along with Praveen, et al) in Debian so know a bit > about CI, et al. > Moreover, I write Python and also an upstream contributor, so I could > also help with the scripts that we discussed during DebConf, too. > I'd like to join you in to contribute to the scripts as soon as GSoC is done. With the cloud team meeting will be possible to map the needs and so we can work on them. > But at the moment, I am just helping in packaging here (since I am > mostly busy doing my GSoC, too). > But by this month end, I could help with the CI, scripting as well :D > > Let me know if there's anything else that needs to be added or cleared > out! :D > > > Best, > Utkarsh > --- > [1]: https://qa.debian.org/developer.php?login=guptautkarsh2...@gmail.com > [2]: https://salsa.debian.org/cloud-team/image-finder/issues/36 > > > Best, Arthur Diniz
Re: Regular meeting of the team
On Mon, Aug 05, 2019 at 05:57:57PM +0100, Marcin Kulisz wrote: > > 1900 UTC makes it 2100 Geneva time. I'd very much prefer something > > during work hours if possible. Or is it that the majority of us is doing > > this away from office hours? > > I suggested this time having in mind that quite a few ppl are in the US, but I > don't anticipate any issues with my own timetable if we'd make it a bit > earlier thus I'm fine with earlier time if this fits other ppl as well. I could go as early as 15:00 UTC. Later is better. :)
Re: Regular meeting of the team
On 2019-08-05 11:43:01, Thomas Goirand wrote: > On 8/2/19 8:55 PM, Marcin Kulisz wrote: > > On 2019-07-23 00:01:20, Tomasz Rybak wrote: > >> Last year, during sprint, we decided that regular > >> (altough virtual) team meeting would be beneficial. > >> > >> It did not work till now, but this topic was raised > >> again today during our BoF. So let's try to make it > >> happen. Let's start with IRC, to keep it simple. > >> > >> As most of team members are either in Europe or in USA > >> time zones, I propose to have our meetings at afternoon > >> or evening of European time (exact hour to be determined). > >> > >> Initially I propose to meet during second week of month. > >> First and last weeks, near beginning or end of month > >> might be risky - deadlines, projects, etc. might make > >> it harder to attend. For similar reasons (and to avoid > >> creating conflict between Debian and family life), I'd > >> like to avoid weekends - but if it's only me, I have > >> nothing against it. > > > > Ok, lets pick a date to have a 1st meeting somewhere next week, lets assume > > that not all of ppl will be able to attend it but having ball rolling will > > allow us to adjust time and dates for the future once we have something > > going. > > > > So I'd say Wednesday 7th of Aug at 1900UTC or maybe we could use something > > like > > doodle.com to coordinate this? > > 1900 UTC makes it 2100 Geneva time. I'd very much prefer something > during work hours if possible. Or is it that the majority of us is doing > this away from office hours? I suggested this time having in mind that quite a few ppl are in the US, but I don't anticipate any issues with my own timetable if we'd make it a bit earlier thus I'm fine with earlier time if this fits other ppl as well. -- |_|0|_| | |_|_|0| "Panta rei" | |0|0|0| kuLa | gpg --keyserver pgp.mit.edu --recv-keys 0x686930DD58C338B3 3DF1 A4DF C732 4688 38BC F121 6869 30DD 58C3 38B3 signature.asc Description: PGP signature
Re: Regular meeting of the team
On Sun, Aug 04, 2019 at 10:15:32PM +0200, Tomasz Rybak wrote: > > So I'd say Wednesday 7th of Aug at 1900UTC or maybe we could use > > something like > > doodle.com to coordinate this? > > I propose the same weekday (Wednesday) and hour (19:00 UTC), > but let's move to next week (so 2019-08-14). > 7th might be a bit too close for organize. > > Any objections or remarks? I can make either proposed date work, at 19:00 UTC. noah
Bug#932943: Missing SHA512 and gpg signature
On 2019-08-05 11:41:34 +0200 (+0200), Bastian Blank wrote: > On Sun, Aug 04, 2019 at 10:05:32PM +0100, Chris Boot wrote: > > On 04/08/2019 17:29, Bastian Blank wrote: [...] > > > No, don't. Use base64 like everyone else. > > > > I strongly disagree with this. Practically everyone else uses > > hexadecimal for plain checksums. A GPG signature is its own > > thing but is (generally) plaintext (I'm assuming clearsign). > > This is what we (as in the project) use for the archive and for > > ISOs. > > Everything current switches to base64. It's shorter and easier to > see changes. Hex only survives where people tend to read it. You mentioned Kubernetes (which I haven't really used so have yet to notice), but who else's "current" software encodes checksums in base64 besides the Kubernetes ecosystem? I'm honestly curious as I still only ever see checksums in hexidecimal notation. The sha512sum(1) manpage makes no mention of having support for verifying base64-encoded checksums, for example. There's something to be said for sticking with traditional standards; newer is not always better. -- Jeremy Stanley
Bug#932943: Missing SHA512 and gpg signature
On Sun, Aug 04, 2019 at 10:05:32PM +0100, Chris Boot wrote: > On 04/08/2019 17:29, Bastian Blank wrote: > > Only one of them. And I would go directly to SHA3 for new stuff. > > Buster doesn't have any SHA3 tools in coreutils. While I don't have > anything against calculating such checksums in addition to the usual > suspects, I want to make sure people with current distros can easily > check them. Okay, let's stay with sha-512 for now. Turns out it is also faster. > >> 3. Add a new mapping within the "data" mapping called "checksums" with > >> keys for each algorithm, e.g. "data.checksums.sha256". > > > > The usual way would be something like this: > > > > | data: > > | verify: > > | - name: sha3_256 > > | content: ABC= > > | - name: gpg > > | content: AAA= > > That kind of structure works for me. That way we *can*[1] have checksums > for multiple image formats and multiple algorithms, e.g. the raw image, > qcow2, compressed tarball, or whatever. We have one upload manifest per image file. I'm not sure yet why we would want to have different checksums. > > No, don't. Use base64 like everyone else. > I strongly disagree with this. Practically everyone else uses > hexadecimal for plain checksums. A GPG signature is its own thing but is > (generally) plaintext (I'm assuming clearsign). This is what we (as in > the project) use for the archive and for ISOs. Everything current switches to base64. It's shorter and easier to see changes. Hex only survives where people tend to read it. Regards, Bastian -- You can't evaluate a man by logic alone. -- McCoy, "I, Mudd", stardate 4513.3
Re: Regular meeting of the team
On 8/2/19 8:55 PM, Marcin Kulisz wrote: > On 2019-07-23 00:01:20, Tomasz Rybak wrote: >> Last year, during sprint, we decided that regular >> (altough virtual) team meeting would be beneficial. >> >> It did not work till now, but this topic was raised >> again today during our BoF. So let's try to make it >> happen. Let's start with IRC, to keep it simple. >> >> As most of team members are either in Europe or in USA >> time zones, I propose to have our meetings at afternoon >> or evening of European time (exact hour to be determined). >> >> Initially I propose to meet during second week of month. >> First and last weeks, near beginning or end of month >> might be risky - deadlines, projects, etc. might make >> it harder to attend. For similar reasons (and to avoid >> creating conflict between Debian and family life), I'd >> like to avoid weekends - but if it's only me, I have >> nothing against it. > > Ok, lets pick a date to have a 1st meeting somewhere next week, lets assume > that not all of ppl will be able to attend it but having ball rolling will > allow us to adjust time and dates for the future once we have something going. > > So I'd say Wednesday 7th of Aug at 1900UTC or maybe we could use something > like > doodle.com to coordinate this? 1900 UTC makes it 2100 Geneva time. I'd very much prefer something during work hours if possible. Or is it that the majority of us is doing this away from office hours? Thomas
Re: Regular meeting of the team
On 4 August 2019 21:15:32 BST, Tomasz Rybak wrote: >On Fri, 2019-08-02 at 19:55 +0100, Marcin Kulisz wrote: >> On 2019-07-23 00:01:20, Tomasz Rybak wrote: >> > Last year, during sprint, we decided that regular >> > (altough virtual) team meeting would be beneficial. >> > >> > It did not work till now, but this topic was raised >> > again today during our BoF. So let's try to make it >> > happen. Let's start with IRC, to keep it simple. >> > >> > As most of team members are either in Europe or in USA >> > time zones, I propose to have our meetings at afternoon >> > or evening of European time (exact hour to be determined). >> > >> > Initially I propose to meet during second week of month. >> > First and last weeks, near beginning or end of month >> > might be risky - deadlines, projects, etc. might make >> > it harder to attend. For similar reasons (and to avoid >> > creating conflict between Debian and family life), I'd >> > like to avoid weekends - but if it's only me, I have >> > nothing against it. >> >> Ok, lets pick a date to have a 1st meeting somewhere next week, lets >> assume >> that not all of ppl will be able to attend it but having ball rolling >> will >> allow us to adjust time and dates for the future once we have >> something going. >> >> So I'd say Wednesday 7th of Aug at 1900UTC or maybe we could use >> something like >> doodle.com to coordinate this? > >I propose the same weekday (Wednesday) and hour (19:00 UTC), >but let's move to next week (so 2019-08-14). >7th might be a bit too close for organize. > >Any objections or remarks? Not form me.
Bug#932943: Missing SHA512 and gpg signature
On 8/4/19 6:29 PM, Bastian Blank wrote: > On Sat, Aug 03, 2019 at 03:06:39PM +0100, Chris Boot wrote: >> - Which checksums should we include? Our Apt repos use MD5 and SHA-256, >> and our ISOs use MD5, SHA-1, SHA-256 and SHA-512. I'd be inclined to >> suggest SHA-256 and SHA-512 only, personally. > > Only one of them. And I would go directly to SHA3 for new stuff. Unfortunately, OpenStack Glance only shows SHA512, not SHA3, so even if we do both, we must keep SHA2 512. Cheers, Thomas Goirand (zigo)
Re: Resigning my cloud team delegation
On 4 August 2019 16:27:48 BST, Steve McIntyre wrote: >Hey folks, > >Although I mentioned this to folks at DebConf and in the cloud team >sessions there, I realise I haven't announced it more widely yet... > >Since I was delegated last year, I've taken on more commitments >elsewhere in Debian (and outside) and I've not been able to find the >time to do a reasonable job as a delegate. I'm therefore resigning >from this position effective immediately. Sorry. :-/ > >I'm not going *away* - I'll still be around if people need help/advice >with stuff, and I'll keep doing updates as needed for the existing >stretch and buster openstack images, But don't expect me to be driving >things at all from this point. I don't envisage going to the sprint >this year. Well, thanks Steve I can understand how you feel when stretched too much. Thanks for all you did till now, cu around and more importantly at the BBQ :-) Take care.
