Re: How was it? Community of friendly equal gekkos?
On Sun, Dec 20, 2020 at 7:14 PM Simon Lees <simon@simotek.net> wrote:
On 12/21/20 3:14 AM, Stefan Brüns wrote:
On Sonntag, 20. Dezember 2020 17:03:49 CET Mark Stopka wrote:
On Sun, Dec 20, 2020 at 3:11 PM Neal Gompa <ngompa13@gmail.com> wrote:
We have ways to do conflict resolution, this isn't it.
Because repeatedly with no reasonable justification rejecting requests for access to a project you are a CO-MAINTAINER, not OWNER is, as well as rejecting update requests for a package that was not touched in 4 years by anybody else without any meaningful justification either.
I gave justification several times. Everyone can submit requests, not just maintainers, so while not being a maintainer you can still contribute.
Maintainers role is curating, and for this you have to know packaging policies. A newcomer should show they are knowing these rules, and this can be done by doing proper SRs.
I somewhat agree, but also somewhat disagree, if no one is looking after a package and someone wants to including taking over being the bugowner I don't see too many problems with a newer contributor taking over, this happens in many places, when I started maintaining enlightenment I only had half an idea what I was doing and learned as I went. Afterall we have a separate review team and a bunch of bots that will generally catch anything that gets missed.
At the point nobody is looking after it and it has no obvious maintainer working on it, then I could see that. But in this case, the maintainer clearly still cares.
As a side note can you please use the proper list addresses so that my mail filters work and I have some idea which lists i'm replying to :-)
Err, it seemed like you didn't quite Cc the list correctly? I got the most "interesting" list of CC addresses. :) -- 真実はいつも一つ！/ Always, there's only one truth!
On Mon, Dec 21, 2020 at 1:41 AM Neal Gompa <ngompa13@gmail.com> wrote: <snip>
I somewhat agree, but also somewhat disagree, if no one is looking after a package and someone wants to including taking over being the bugowner I don't see too many problems with a newer contributor taking over, this happens in many places, when I started maintaining enlightenment I only had half an idea what I was doing and learned as I went. Afterall we have a separate review team and a bunch of bots that will generally catch anything that gets missed.
At the point nobody is looking after it and it has no obvious maintainer working on it, then I could see that. But in this case, the maintainer clearly still cares.
The maintainer cares so much that he did not update the package in 4 years? I repeat once again, while Stefan is one of the few maintainers of the repository itself, he is not maintainer of the package that the SR belongs to, I requested a maintainer role for the entire repo so I can easily set-up all other additional packages, IN ADDITION to submiting a SR for this package... https://build.opensuse.org/package/show/electronics/yosys
As a side note can you please use the proper list addresses so that my mail filters work and I have some idea which lists i'm replying to :-)
Err, it seemed like you didn't quite Cc the list correctly? I got the most "interesting" list of CC addresses. :)
-- 真実はいつも一つ！/ Always, there's only one truth!
On 12/21/20 11:10 AM, Neal Gompa wrote:
On Sun, Dec 20, 2020 at 7:14 PM Simon Lees <simon@simotek.net> wrote:
On 12/21/20 3:14 AM, Stefan Brüns wrote:
On Sonntag, 20. Dezember 2020 17:03:49 CET Mark Stopka wrote:
On Sun, Dec 20, 2020 at 3:11 PM Neal Gompa <ngompa13@gmail.com> wrote:
We have ways to do conflict resolution, this isn't it.
Because repeatedly with no reasonable justification rejecting requests for access to a project you are a CO-MAINTAINER, not OWNER is, as well as rejecting update requests for a package that was not touched in 4 years by anybody else without any meaningful justification either.
I gave justification several times. Everyone can submit requests, not just maintainers, so while not being a maintainer you can still contribute.
Maintainers role is curating, and for this you have to know packaging policies. A newcomer should show they are knowing these rules, and this can be done by doing proper SRs.
I somewhat agree, but also somewhat disagree, if no one is looking after a package and someone wants to including taking over being the bugowner I don't see too many problems with a newer contributor taking over, this happens in many places, when I started maintaining enlightenment I only had half an idea what I was doing and learned as I went. Afterall we have a separate review team and a bunch of bots that will generally catch anything that gets missed.
At the point nobody is looking after it and it has no obvious maintainer working on it, then I could see that. But in this case, the maintainer clearly still cares.
Yeah in this case Stefan is obviously interested in maintaining the "electronics" project, which is fair, but to me if Mark is submitting mostly new packages, or is working on packages Stefan isn't really touching then it may make sense for him to be the maintainer of those packages. In many cases devel project maintainers are only really meant to step in if no one else cares about the package, although if someone maintains a large number of packages it often makes sense for them to become a project maintainer.
As a side note can you please use the proper list addresses so that my mail filters work and I have some idea which lists i'm replying to :-)
Err, it seemed like you didn't quite Cc the list correctly? I got the most "interesting" list of CC addresses. :)
Thats the List I got from Stefan's email, I did the same thing as normal in thunderbird, so no idea what he or the list software did with his email. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
participants (3)
-
Mark Stopka -
Neal Gompa -
Simon Lees