Skip to content

Bug/problem reporting: use GitHub or use GNATS ? #102

@sskras

Description

@sskras

@bsiegert commented 5 hours ago on issue #101:

@sskras If your bug report was about a different problem, then it does not belong here.

I know. I just saw that both problems from me and @jgoerzen had something in common:

"I'm not quite sure where to go with all these things;"

So I used the opportunity to stress this generic question.

There is no SLO on replies to bug reports.

Thanks for the tip. Some more questions:

  1. How can I ping the related community for the possible fixes or at least direction of the needed research?

  2. Which place has wider audience of contributors / higher priority at looking at bugs: this repo or the Gnats system?
    I wonder if it be useful to replicate my pkg/56611 report on GitHub.

  3. What is the generic flow of fixing / lifecycle of the bug / ethics of fix management for pkgsrc:

  • Are bugs here allowed stay open forever ?
  • Can I offer patches based on different approaches (even hacks) without getting banned from being reviewed?
  • What is the patch reviewing procedure – is it a team or a single, dedicated person usually working on that?

Please excuse the newbie which got lost:)
Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions