Hi Peter, Am 24.10.24 um 20:44 schrieb Peter 'PMc' Much:
Sadly, missing in Your statement is the mainly relevant information: furtheron, participation in the list is restricted to customers of the Github corporation.[1] Ordinary people are therefore no longer allowed to participate.
So in this case "ordinary people" means those who absolutely don't want to have a GitHub account?
I understand your concern and nobody is forcing anyone into using GitHub. We will, of course, continue to accept reports and patches on the users mailing list in the future.
Our main point is that we don't want to keep an inactive mailing list. The devel list had 22 posts in 2022, 13 in 2023 and 8 in 2024 so far. There is not much going on, so we don't see why we should keep it. If you're not happy with GitHub discussions, just post to the users list what you would have posted to the devel list.
That may be the case and I won't argue with you in this point, because I don't care what some other random project might have done.In fact this is nothing out of the usual: many projects did already manage to reduce the amount of bugs by not allowing ordinary people to report them.
Nevertheless, I fail to see how we as Bareos are stopping you from reporting anything. I'll admit that we're advocating for the GitHub issue tracker, as that's easiest for us to handle. However, nobody is stopping you from
* posting on the users mailing list * using the contact form on our website * sending an e-mail to our direct contact address * sending an e-mail to one of our developers directly * posting your information to some forum (where we might never see it)If you have any advise what we can improve, feel free to share it. Maybe on the users mailing list where more people can get involved.
I still fail to see how we denied you anything. Also, even if you just do such things for fun, maybe post a link to the users list...Occasionally I do then resort to publishing the bugs on e.g. forum.freebsd.org or bsdforen.de or where I am still allowed to publish, usually for entertainment.
Let's look at some examples:
* In core/src/lib/alist.h we have a function/macro
foreach_alist(var, list)
[...]
* There is a job priority feature and an option allow-mixed. (Without
that option, the priority feature is of rather limited use.)
One would now expect that this feature would arrange jobs according to
their priorities. Only, it doesn't work.
After a thorough amount of searching I figured out why: while the
mixed-prio option does exist as an option switch, it isn't
fully implemented:
When a new job is started, the prio of that job gets compared to
the already running jobs, specifically to the *FIRST* of the
already running jobs. That would suffice if there were no
mixed-prio option - because then all the running jobs would have
the same prio.
But with mixed-prio one would need to compare against *EVERY* of
the already running jobs and find the highest prio among them. And
that part is missing.[2]
Thank you for taking the time to look into that.If you've tested your fix and are otherwise okay with it, would you prepare this with git format-patch, so I can make a pull request out of it while retaining your copyright? Also, feel free to add your name to the AUTHORS file, if you want to. As we value shared code-ownership I don't want to take your changes and publish them with my name-tag on them (unless you explicitly ask for that).
Best Regards, Andreas [1] https://github.com/bareos/bareos/pull/1859 -- Andreas Rogge andreas.ro...@bareos.com Bareos GmbH & Co. KG Phone: +49 221-630693-86 http://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz -- You received this message because you are subscribed to the Google Groups "bareos-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-devel+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bareos-devel/a312555a-2b11-4918-b054-d15340263b47%40bareos.com.
OpenPGP_signature.asc
Description: OpenPGP digital signature
