4 ms·

What are the Github issue IDs for these 4 problems?

by nednar 6y ago

bartvk 6y ago
What are you trying to say here? Your comment feels a bit passive-aggressive.
- nednar 6y ago
  > What are you trying to say here? I want to look at the problems. But I don't want to do a guessing game with the 159 open issues, which one may relate to one of these points or not.
qbasic_forever 6y ago
Where are the four unit tests in podman's codebase that should be catching these issues? I find it very strange that your reaction is, "the software is infallible, it is _YOU_ who have failed the software by not logging bugs!" It is perfectly reasonable to have a conversation about the quality or issues with a piece of software SEPARATE TO the logging or finding of bugs in said software.
yobert 6y ago
I agree with the sentiment that I should go find them. But I also agree with the sentiment that if RHEL 8 is going to make it hard to install docker and promote podman instead as a drop-in replacement, it's a bit frustrating.
- nednar 6y ago
  > I agree with the sentiment that I should go find them. I can sympathize with feeling overwhelmed when searching for similar Issues in a bug database, as I was in a similar situation in the past. What happend was this: I went to the central starting point of the repo's database (e.g., https://github.com/containers/podman/issues https://github.com/containers/podman/issues), removed the filters like `is:open` from the search bar, and entered one or two keywords that for me sounded similar to the problem I faced. As I didn't find any Issues that seemed similar, I just created a new one. Of course, I was worried about creating a possible duplicate, but I figured that it would still be a valuable contribution by adding more keywords (with the maintainers linking my duplicate to the ticket where the problem gets resolved) for others to search for. And last but not least, I thought this would also add additional debugging information for the developers, as well as an indication of the community-wide impact of the problem for the release management team. In the end, I was quite happy I went this way, because I didn't just make a small impact on a project that would be useful for me, but it also enabled me to connect to the amazing people that build the tools I use on a daily basis. I hope that you can also find a way that gives you some happiness in dealing with your situation, yobert.

What are the Github issue IDs for these 4 problems?

by nednar 6y ago

What are the Github issue IDs for these 4 problems?

bartvk 6y ago

What are you trying to say here? Your comment feels a bit passive-aggressive.

nednar 6y ago
> What are you trying to say here? I want to look at the problems. But I don't want to do a guessing game with the 159 open issues, which one may relate to one of these points or not.

qbasic_forever 6y ago

Where are the four unit tests in podman's codebase that should be catching these issues? I find it very strange that your reaction is, "the software is infallible, it is _YOU_ who have failed the software by not logging bugs!" It is perfectly reasonable to have a conversation about the quality or issues with a piece of software SEPARATE TO the logging or finding of bugs in said software.

yobert 6y ago

I agree with the sentiment that I should go find them. But I also agree with the sentiment that if RHEL 8 is going to make it hard to install docker and promote podman instead as a drop-in replacement, it's a bit frustrating.

nednar 6y ago
> I agree with the sentiment that I should go find them. I can sympathize with feeling overwhelmed when searching for similar Issues in a bug database, as I was in a similar situation in the past. What happend was this: I went to the central starting point of the repo's database (e.g., https://github.com/containers/podman/issues https://github.com/containers/podman/issues), removed the filters like `is:open` from the search bar, and entered one or two keywords that for me sounded similar to the problem I faced. As I didn't find any Issues that seemed similar, I just created a new one. Of course, I was worried about creating a possible duplicate, but I figured that it would still be a valuable contribution by adding more keywords (with the maintainers linking my duplicate to the ticket where the problem gets resolved) for others to search for. And last but not least, I thought this would also add additional debugging information for the developers, as well as an indication of the community-wide impact of the problem for the release management team. In the end, I was quite happy I went this way, because I didn't just make a small impact on a project that would be useful for me, but it also enabled me to connect to the amazing people that build the tools I use on a daily basis. I hope that you can also find a way that gives you some happiness in dealing with your situation, yobert.