Re: Self Introduction: Boian Bonev
On Sat, Oct 03, 2020 at 11:29:43PM +0300, bbonev wrote: > Already did that in git yesterday, I will wait a couple of days to see if > something else is suggested and will update the bug. > > BTW. How it goes with review and sponsorship in Fedora community - do I > need to do something more or I have already done all that is needed and > just wait? You will need someone to sponsor you into the packaging group. See https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=PackageMaintainers/Join#How_to_join_the_Fedora_Package_Collection_Maintainers.3F -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Self Introduction: Boian Bonev
Hi Matthew, Already did that in git yesterday, I will wait a couple of days to see if something else is suggested and will update the bug. BTW. How it goes with review and sponsorship in Fedora community - do I need to do something more or I have already done all that is needed and just wait? With best regards, b. > > On Oct 3, 2020 at 20:31, Matthew Millerwrote: > > > On Sat, Oct 03, 2020 at 01:28:22AM +0300, Boian Bonev wrote: > Here I mean > the project name, which is iotop-c. I see no problem in > renaming the > binary. Yeah, I'd suggest just making it match -- `iotop-c` > > > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Self Introduction: Boian Bonev
On Sat, Oct 03, 2020 at 01:28:22AM +0300, Boian Bonev wrote: > Here I mean the project name, which is iotop-c. I see no problem in > renaming the binary. Yeah, I'd suggest just making it match -- `iotop-c`. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Self Introduction: Boian Bonev
Hi Rahul, On Fri, 2020-10-02 at 17:30 -0400, Rahul Sundaram wrote: > Hi > > On Fri, Oct 2, 2020 at 4:57 PM Boian Bonev wrote: > > I didn't start that project, just improved it, and somehow changing > > the > > > > name does not seem right to me :) Here I mean the project name, which is iotop-c. I see no problem in renaming the binary. > This isn't a minor change and the current name is a bit awkward and > because of a shared name, you have to deal with Conflicts or > alternatives neither of help with ease of use ex: I want to install > them both to compare them side by side. I would agree with Matthew > that a name change is warranted here. At the minimum, rename the > binary. Here is a parallel for that Thanks for your advise, I will wait to see if something else is proposed and will most probably go with renaming the binary. What would be the best choice (iotop-c, iotop_c or iotopc)? As long as this is a tool only for root (or a capped user), alternatives still seem better to me - it wouldn't at all concern unprivileged users, while allowing to run e.g. program-c or program-go and still have program symlinked to the preferred one, but of course I may miss something and be wrong here. > https://github.com/rpm-software-management/createrepo_c >From what I see, this have completely replaced the other project. I do not have that goal. My selfish desire is some day to be able to dnf install and use it, without compiling from source or copying a binary. With best regards, b. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Self Introduction: Boian Bonev
Hi On Fri, Oct 2, 2020 at 4:57 PM Boian Bonev wrote: > > I didn't start that project, just improved it, and somehow changing the > name does not seem right to me :) > This isn't a minor change and the current name is a bit awkward and because of a shared name, you have to deal with Conflicts or alternatives neither of help with ease of use ex: I want to install them both to compare them side by side. I would agree with Matthew that a name change is warranted here. At the minimum, rename the binary. Here is a parallel for that https://github.com/rpm-software-management/createrepo_c Rahul ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Self Introduction: Boian Bonev
Hi Matthew, On Fri, 2020-10-02 at 16:09 -0400, Matthew Miller wrote: > ... > > For start I have prepared iotop-c: > > https://bugzilla.redhat.com/show_bug.cgi?id=1878529 > > Looks pretty straightforward. One thing worth noting is that we > discourage > using "Conflicts:" > https://docs.fedoraproject.org/en-US/packaging-guidelines/Conflicts/ True, with my user hat on, I'd prefer both programs installed simulaneously. But implementing alternatives requires coordination from all involved project's maintainers and I just skipped that part; also both programs are not identical in terms of command line options and will most probably diverge more with time; on the other hand for non- interactive use the compatibility is there... My feeling is that implementing alternatives is better for interactive use, and as a second option, installing it under its current name is also an option (and removing the conflicts). I need advise for this; its OK for me to prepare a PR implementing alternatives for iotop. > I know it's a pretty descriptive name, but: I notice your program has > other > improvements rather than just being written in C. I wonder if finding > a new > name that isn't based on the language implementation might be the > best > long-term approach? I didn't start that project, just improved it, and somehow changing the name does not seem right to me :) With best regards, b. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Self Introduction: Boian Bonev
On Fri, Oct 02, 2020 at 10:56:09PM +0300, Boian Bonev wrote: > I am involved with couple of open source projects and plan to package > and maintain them for Fedora. Hi! Welcome -- that's awesome! > For start I have prepared iotop-c: > https://bugzilla.redhat.com/show_bug.cgi?id=1878529 Looks pretty straightforward. One thing worth noting is that we discourage using "Conflicts:" https://docs.fedoraproject.org/en-US/packaging-guidelines/Conflicts/ I know it's a pretty descriptive name, but: I notice your program has other improvements rather than just being written in C. I wonder if finding a new name that isn't based on the language implementation might be the best long-term approach? -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Self Introduction: Boian Bonev
Hello, I am involved with couple of open source projects and plan to package and maintain them for Fedora. My packaging skills are far from perfect, but on the other hand, since I am doing the upstream development+release it is convenient to do both. It would be better if someone is interested in co-maintaining with me. For start I have prepared iotop-c: https://bugzilla.redhat.com/show_bug.cgi?id=1878529 With best regards, b. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
