Being public or not will entirely depend on the affected. However, a repo of cases and resolutions like a small list can be helpful so people can also ready potential solutions to the problems they face.

Being public or not will entirely depend on the affected. However, a repo of cases and resolutions like a small list can be helpful so people can also ready potential solutions to the problems they face.
+1

I think this ticket is almost the same as the #5 filing cases and building a data base is technically the same. I'm setting this as fixed since actions to fill a data base are already been taken.

@tatica I think this one is actually different from #5. #5 is mostly focusing on "what if" instead of "what happened". I think having some kind of place to log things that happen or received reports, does make sense. I'd be +1 for keeping this ticket open to come up with a solution for responsibly and safely logging all reports that we may receive.

No problem, didn't saw it that way but if it can work by separate, that's fine by me. The more the info the better we will build a base :)

@tatica @amsharma After playing with the staging repo on Pagure as detailed in #3, I think this ticket is actually more of a duplicate of #3. :open_mouth: I would be +1 to closing this ticket and instead migrating this discussion to #3 (so people report issues the same place that we can file tickets of incidents or cases that come to us). I think keeping these things together will make them easier to find when needed (as compared to digging through reports by community members vs. reports filed by Diversity Team members).

@jflory7 , I think this can be merged with #5 and not #3 ?
+1 to merge it with #5

Either way, I think we can agree that this topic will be covered by other tickets. Going to close this after all, @tatica was right all along. :grin: