CW-172: "Unpublish on two issues" mechanism causes old betas to become unrecoverable

[hobovsky]

Motivated by this post (but discovered some time ago already, but I cannot find any report):

To force new authors to curate their kata better, the mechanism has been introduced which causes beta kata to be auto-unpublished when they collect two issues during 24h (?) curation period after being published. The mechanism was meant to reduce the amount of newly published, bad kata, which can be fixed by authors and republished. However, it affects also old kata, when author is long gone, and there is no one to republish them.

To reproduce:

1. Find an old beta kata.
2. Do anything what causes update of its "modified" timestamp: approve a pending translation, create and approve a fork with a fix, edit it with kata editor and republish, etc.
3. Raise an issue or two on it (depending if it already has a pending issue or not), or use the "recalculate stats" mender action (if the kata has at least two issues).

At this point, the kata gets unpublished and moved to draft state. If its author is inactive, the kata cannot be recovered.

The effect is deemed to be undesired, because initially it was meant to handle only new kata, while their authors are still around, ready to react to issues.

[Blind4Basics]

another case here...: https://www.codewars.com/kata/55a9a6ffd7f21d7d000000e5/discuss

Author gone since 2015 / got unpublished with my issue...

---

edit: on the other hand, this one didn't get pushed to draft while dfhwze also raised an issue on it while both kata already add an old issue... => ??

[VanessaGreene]

Escalated to CW-172

[kazk]

This was introduced in June 2022:

Recently published kata (within the past 48h) is now automatically unpublished if it has 2 unresolved issues.
#2600 (comment)

We overlooked that the "last published at" timestamp is modified by actions other than the original author publishing the kata. Not sure what's best to do. I don't want to change this and affect other stuff, nor add a new field just to track when the original author published the kata.

If its author is inactive, the kata cannot be recovered.

Can you (a mod) publish the draft kata from the editor? Maybe I'm overlooking something, but I don't think I see anything preventing that. Note that we don't allow publishing draft kata with unresolved issues, as proposed in #2598, so the "Publish" button should be disabled until the issues are resolved.

[Kacarott]

Attempting to republish a draft with no issues initially looked like it was working, but then I found myself on a page "You do not have permissions to view this page", and the publish did not work.

[hobovsky]

Can you (a mod) publish the draft kata from the editor? Maybe I'm overlooking something, but I don't think I see anything preventing that.

I think it's never been possible?

I just tried and got the same result as Kacarott: the Publish button is clickable, but after clicking it I end up with "You do not have permissions to view this page" and kata state seems to be not changed.

[kazk]

Thanks for checking. It took me forever to find why mods can save, but not publish a draft kata you don't own 🤦‍♂️

I'll make these kata recoverable by allowing the mods to publish them like admins.

[hobovsky]

Would love to see the if which caused this :D

[Kacarott]

Will this also allow mods to publish even with open issues? This behaviour happens when some recently updated kata gets some new issues, so it would be nice to be able to directly republish without having to close the issues, republish, then re-open the issues. (especially if adding the issues again would revert it back to draft again lol)

[hobovsky]

When you close the issues, publish the draft, and re-raise the issues, the kata will get unpublished again :D (unless you merge the pending issues into one).

[kazk]

Will this also allow mods to publish even with open issues?

No, everything else stays the same. But I'm open to suggestions.

I forgot exactly why we decided to disable publishing with unresolved issues, but can't you confirm that the issue is resolved, close the issue, then republish? Isn't that what the author is doing?

[Blind4Basics]

can't you confirm that the issue is resolved, close the issue, then republish? Isn't that what the author is doing?

That's what's currently happening, yes.

I forgot exactly why we decided to disable publishing with unresolved issues

There were mostly 2 reasons (maybe I forgot some others, tho):

• Most (newbie) authors will insta-republish if they can, even without solving the issues, so the kata will definitely get retired even if it has potential. This "delay" makes the beta process less destructive for authors, and less upsetting for beta testers.
• At some point in the past, this also was an anti-troll-kata/author measure.