Dynmap: Do you need a moderator?

[Psy-Virus]

Hey @mikeprimm,
a while ago, I wrote you a PM on the minecraft forum.
I sometimes strafe through the issues here and see 'from issuer unanswered issues, questions for basic and general support. already implemented feature requests'.

So my question: Do you need a moderator that cleans up that issue mess of close to 700 issues?
A moderator, that looks into the issues every once in a while and checks for support questions that shouldn't be handled here, cleans up all the old issues and tags them correctly. For example, if I think it's a bug, it gets a bug tag.

I'd be up to it.

Dynmap is a very popular modification. This is mirrored by the sheer amount of asking people and open issues.

I myself and some friends use Dynmap quite regularly since years and I simply want to give something back. So if you're interested, you know where to find me. Or simply promote me and I'll do my thing.

Thanks for reading

:)

[generrosity]

I'd love to help out too - @mikeprimm I hope you do take someone on to help you out tho - love your work as always.

There might be some first-tier-prevention in having a Issues/Feature request template. Tighten up the details on whats supported, more links to the download area, harden down on entitled assumptions.

Best of wishes!

[jwshields]

I'd say I agree that there should be cleanup here, many old issues, many solved issues that don't get closed.
Not that it's terrible overall per se; leaving them open is just a bit noisy, rather than any huge detriment to the repo (speaking from a viewpoint of github repos overall)

One thing I would get behind is issue/PR templates added to the repo in order to help people submit actual problems, versus "it's broken?!" - but there'd need to be a better FAQ & wiki/support system rather than trawling through old issues.

[generrosity]

Today on Twitter - GitHub preview for detecting existing duplicate cases at logging

https://twitter.com/github/status/1059866337801957376?s=19

Is the wiki GitHub pages, or outright editable? It might be "as easy" as code contribution (including a how2 edit how2s)

[mikeprimm]

Some help would be good :)

The wiki was locked due to some issues with being vandalized - I'm cool with adding specific people with edit rights: just not opening it publicly.

[mikeprimm]

@Psy-Virus You should have invite - I'm keeping the code branches locked: I only will accept code via PR from anyone else at this point, so nobody else needs push rights to the code branches, but it should give you roles enough for issues and wiki changes.

[Psy-Virus]

All righty, thanks for the invite :)

I'm keeping the code branches locked

I'm glad you do that. I wouldn't like to have write perms to that anyway, I'm not a Java dev, just a fan of your work who likes to give something back ^^

I'll probably start to go through the issues later that day. It's 6 am right now; need some sleep :D

If there's something important to know or if you need something else, pls don't hesitate to ask!

:)

[Psy-Virus]

@generrosity and @jwshields, thanks for the input.
@mikeprimm, is the wiki configured so people can send in PRs?
Would be cool if people could write their stuff and PR it then to the wiki itself. I'd approve and check it for grammar mistakes then, and merge it.
Otherwise we do it over issues tagged in a special way.
At least I know it was possible a while ago, idk how GH is handling it now but the last time I edited a wiki, I had to clone it locally, change it and PR it via the desktop or CLI Client.

[mikeprimm]

@generrosity I've added you as well - you guys should have issue and wiki access. Any code related things should still be via PRs. Thanks for the help!

[generrosity]

[salute] @mikeprimm, Glad to be onboard, sir.

I see @Psy-Virus is already closing off cases. Totally would recommend having a copy-pastable "This is older than a year, please use the lastest download from and relog if still a problem" etc.

[generrosity]

Is there a place like a Discord we could converse?

[Psy-Virus]

@generrosity, I currently list features that sound interesting. After that I'll go through them again and look for pearls.
What I currently want to achieve is to minimize and consolidate the issues/features. Old issues and support questions are closed with or without a short comment depending on the case.
This will take time and simply closing everything older than a year is probably not the right way because @mikeprimm does all this stuff in his free time, like probably everyone else here, and since he's the only one really developing since years, there will always be a backlog for some time. But we can minimize and organize it that way.

And right now, I'm totally okay with discussing the stuff in this thread^^

:)