How are issues addressed in Hugo?

dev
1

From my limited experience with open source projects, issues (on Github) are handled like this…

  1. If they are a priority, they are addressed.
  2. If they are not a priority, they are left as is for future re-look.
  3. If they are difficult to implement, they are left as is.

Does Hugo work the same way? I saw many issues tagged as unscheduled. Like this issue, which many users might consider a priority.

2

That applies to the issue you linked to, and the use case is addressable via the base/block construct.

1 Like
3

Perhaps with the lead dev’s blessing, your method should be documented as the ‘official way’ to tackle something where applicable.

4

In short, an issue needs to be considered a priority by the maintainers of the project, and with open source these priorities compete with … life. I don’t think this is much different from other open source projects. Some times issues also just gets forgotten, which I guess was the primary motivation behind your post.

5

Do you mind sharing what criteria you use for this?

‘Forgotten’ wasn’t a reason I had in mind. After reading several comments in some past issues, it seemed what some users requested to be prioritised, was instead left open, with some issues going back 10 years. Hence my question.

I assume this means some of these issues need a lot of resources to implement.

6

I use my personal set of criterias; self interest, technical curiousity, etc. Nothing magical.

1 Like
7

Good criteria! So in the example I shared, I assume you are in agreement with @jmooring that some issues are just difficult to implement?

8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.