how to help with docker.io ?
Dear all, Few days back I saw this bug #908868 . I asked the maintainer and he told me the debian-go is the proper place to ask about things. I would like to see docker.io remain in Debian at least till Debian hits buster i.e. stable. Now I don't know any coding but I do know my way about git a bit and have used both docker and cowbuilder to help developers. Somebody would need to tell me what it needed and guide me a bit and I hope I can play my bit part to see docker remain in Debian at least till Buster is released. Look forward to know how to proceed. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Re: how to help with docker.io ?
[+cc docker-maint, Arnaud (who did substantial work on docker and its dependencies), Dmitry (who last touched the package)] Arnaud, Dmitry, any advice as to how people can best help with docker? On Wed, Sep 26, 2018 at 7:36 PM shirish शिरीष wrote: > Dear all, > > Few days back I saw this bug #908868 . I asked the maintainer and he > told me the debian-go is the proper place to ask about things. I would > like to see docker.io remain in Debian at least till Debian hits > buster i.e. stable. > > Now I don't know any coding but I do know my way about git a bit and > have used both docker and cowbuilder to help developers. Somebody > would need to tell me what it needed and guide me a bit and I hope I > can play my bit part to see docker remain in Debian at least till > Buster is released. > > Look forward to know how to proceed. > > -- > Regards, > Shirish Agarwal शिरीष अग्रवाल > My quotes in this email licensed under CC 3.0 > http://creativecommons.org/licenses/by-nc/3.0/ > http://flossexperiences.wordpress.com > EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 > > -- Best regards, Michael
Re: how to help with docker.io ?
Thanks for forwarding this email to us, Michael. We've already exchanged few emails with shirish. On Thursday, 27 September 2018 6:53:11 AM AEST Michael Stapelberg wrote: > [+cc docker-maint, Arnaud (who did substantial work on docker and its > dependencies), Dmitry (who last touched the package)] Although Arnaud helped a lot, I did substantial work on Docker and its dependencies (not merely "last touched the package"). > Arnaud, Dmitry, any advice as to how people can best help with docker? IMHO most of the effort is with Docker's enormous dependency tree so we always have to package new dependencies (they keep adding more with every release, not caring the slightest about code bloat); take care of bugs, tests and everything. One have to remember that Docker is more than 100 packages that need good maintenance hence team effort is the only sustainable way to ensure good health of those packages. I'm planning to eventually retire from Docker maintenance. > On Wed, Sep 26, 2018 at 7:36 PM shirish शिरीष wrote: > > Now I don't know any coding but I do know my way about git a bit and > > have used both docker and cowbuilder to help developers. Somebody > > would need to tell me what it needed and guide me a bit and I hope I > > can play my bit part to see docker remain in Debian at least till > > Buster is released. We need more man power, not great skills. :) https://mentors.debian.net/qa is a good source of maintainer's wisdom and whatever questions you have, you are welcome to ask here - I'm sure everybody will be happy to help. Welcome. :) -- All the best, Dmitry Smirnov. --- On one level, wisdom is nothing more profound than an ability to follow one’s own advice. -- Sam Harris, Waking Up: A Guide to Spirituality Without Religion signature.asc Description: This is a digitally signed message part.
Re: RFS: golang-github-rivo-tview
On Sat, Sep 08, 2018 at 04:46:03AM +0900, Jongmin Kim wrote: > On Fri, Sep 07, 2018 at 10:05:45AM -0400, Alexandre Viau wrote: > > What did you use to choose the branch names? > > > > I don't see a "master" branch, so this is probably the new workflow? > > > > However, the new workflow does not use the "debian" branch: > > - https://go-team.pages.debian.net/workflow-changes.html > > > > Please either use a repository as created by dh-make-golang or use the > > new workflow according to the spec on the team's website. > > I will follow the new workflow for this package. Thank you! > > > On Fri, Sep 07, 2018 at 10:07:48AM -0400, Alexandre Viau wrote: > > I'd like to avoid repeating the same comments twice, maybe you should > > focus on one ITP and then proceed to the next? > > Great! I will focus on 'tview' first. > > > On Fri, Sep 07, 2018 at 11:29:27AM -0700, Felix Lechner wrote: > > On Fri, Sep 7, 2018 at 11:26 AM Alexandre Viau wrote: > > > On 2018-09-07 01:48 PM, Jongmin Kim wrote: > > > > 'master' is the default for pristine-tar branches, right? > > > > How do you think about renaming to 'debian/sid'? > > > > > > > > As Alexandre commented, 1.4 in our team's workflow change proposal > > > > suggests new workflow to adopt DEP-14, which recommends 'debian/master' > > > > or 'debian/'. And our team's proposal suggests that the > > > > default > > > > branch should be named 'debian/sid'. > > > > > > > > I think I have to rename it to 'debian/sid'. > > > > > > Yes, I agree. This is what the document suggests. > > > > > > Note that, technically, debian/master would also work, but I think > > > debian/sid or debian/unstable is clearer in the case of Debian. > > > > > > See DEP14: https://dep-team.pages.debian.net/deps/dep14/ > > > > Yes, 'debian/sid' makes the most sense. I agree with Alex. Thank you! > > Thanks a lot for all! > > > To Alexandre, > > Would you review my namespace [1] first? A bunch of mistakes might be > came out, including which need controlling the protected branches. After > your careful review, I will push all the things into our team's repository. > Sorry for taking back what I said. > > Or, could you please remove the 'debian' branch from our team's repo? > I don't have a right for removing it. I will push 'debian/sid' there. > > Thank you! Hi, During waiting for review, I made some updates: * Rename branch 'debian' to 'debian/sid' in our team's repo. * Merge upstream version 'bc39bf8d'. I pushed all things into our team's repo [1]. Please review team repo. Thank you! [1] https://salsa.debian.org/go-team/packages/golang-github-rivo-tview -- Jongmin Kim OpenPGP key located at https://jmkim-pgp.github.io/keys/pubkey.D39D8D29BAF36DF8.Jongmin_Kim.asc OpenPGP fingerprint: 012E 4A06 79E1 4EFC DAAE 9472 D39D 8D29 BAF3 6DF8 signature.asc Description: PGP signature
Re: how to help with docker.io ?
On Thu, Sep 27, 2018 at 6:05 AM Dmitry Smirnov wrote: > IMHO most of the effort is with Docker's enormous dependency tree so we > always have to package new dependencies (they keep adding more with every > release, not caring the slightest about code bloat); take care of bugs, tests > and everything. One have to remember that Docker is more than 100 packages > that need good maintenance hence team effort is the only sustainable way to > ensure good health of those packages. > Is there a todo list? on gobby.d.o, Debian wiki, etc. -- Shengjing Zhu
Re: RFS: golang-github-rivo-tview
On Thursday, 27 September 2018 12:24:18 PM AEST Jongmin Kim wrote: > * Rename branch 'debian' to 'debian/sid' in our team's repo. Perhaps it would have been better to rename it to "master"? -- Cheers, Dmitry Smirnov. --- In questions of science, the authority of a thousand is not worth the humble reasoning of a single individual. -- Galileo Galilei signature.asc Description: This is a digitally signed message part.
Re: how to help with docker.io ?
On Thursday, 27 September 2018 12:34:47 PM AEST Shengjing Zhu wrote: > Is there a todo list? on gobby.d.o, Debian wiki, etc. One TODO is in the "docker.io" package; others derive from bug reports and testing removals; some bundled packages may be packaged separately - that's a constant thing about Docker... Not sure if dependency hygiene needs a special TODO... -- Regards, Dmitry Smirnov. --- A man does what he must - in spite of personal consequences, in spite of obstacles and dangers and pressures - and that is the basis of all human morality. -- Winston Churchill signature.asc Description: This is a digitally signed message part.
Re: RFS: golang-github-rivo-tview
On Thu, Sep 27, 2018 at 02:12:45PM +1000, Dmitry Smirnov wrote: > On Thursday, 27 September 2018 12:24:18 PM AEST Jongmin Kim wrote: > > * Rename branch 'debian' to 'debian/sid' in our team's repo. > > Perhaps it would have been better to rename it to "master"? Thank you, Dmitry. Alexandre already pointed it out [1]. I've discussed with him and Felix. 3rd quote of [2] is a part of discussion. 1.4 in our team's workflow change proposal [3] suggests new workflow to adopt DEP-14 [4], which recommends 'debian/master' or 'debian/'. And our team's proposal suggests that the default branch should be named 'debian/sid'. So I did name it 'debian/sid'. Thank you! [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905240#47 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905240#57 [3] https://go-team.pages.debian.net/workflow-changes.html#wf-2017-11-dep14 [4] https://dep-team.pages.debian.net/deps/dep14/ -- Jongmin Kim OpenPGP key located at https://jmkim-pgp.github.io/keys/pubkey.D39D8D29BAF36DF8.Jongmin_Kim.asc OpenPGP fingerprint: 012E 4A06 79E1 4EFC DAAE 9472 D39D 8D29 BAF3 6DF8 signature.asc Description: PGP signature
