I opened an issue on Github several months ago. The issue was discussed and in the thread it was decided that it should be worked on. Earlier today I got an email that the issue was closed as ‘completed’ even though there was no link to a PR or commit.
It has been several months since I have worked on anything related to Exercism so I had forgotten about the readme stating that new issues should be discussed on the forum. I made a comment stating the the issue was still present on the website. I received a reply telling me to direct my attention to the ‘readme’, which comes off as hostile and condescending.
It would have been more appropriate to simply tell me to open an a new topic on the forum
I would like to add that in my experience is somewhat unusual for an open source project to have its code on Github, and completely forbid discussion of the project on Github. The maintainers should keep this in mind.
Thanks for that. I agree it is not typical, but there is a lot of discussion as to when this transitioned.
Unfortunately, the changes were only partially put in place on github/exercism/exercism, when the transition of work went from there to where it was indicated on the README, and issues were not closed at that point in time, and automatically closed later, as is done on many tracks in the Exercism organization.
I wonder if the issue can be moved to the new repository, where it can be tracked better as well. I will see if I can do so, I might not have enough Oomph, but I know it has happened before (years ago) but unsure how much that has change, as it has been a while since I have needed to reorganize by moving an issue to another repository.
A link to the discussion on the forums was not found in that issue, though. Can you supply more detail? Feel free to comment in the issue that you did link here.
I thought I wrote to “please direct” so that the reasons were not needed to be repeated, and honestly to help set the tone. Written communication lacks that to a large degree, and I apologize if it was blunt. I can re-write it though, if you have a better way to write it, as it is likely going to be posted (around 500 e-mails went out) when others have a question about it.
I did not want to have this effect on you, and I do not want to have the same effect on others.
I don’t have permissions to re-open the issue. Existing issues with ongoing discussion/work probably shouldn’t be closed out.
Changes to the website tend to not be open to PRs from outside the Exercism staff and their availability to work on website improvements has been very limited lately.
Right, I was caught up on all of these issue closures as well. I had some issues from before the transition closed as complete without indication they were actually completed or if the issue needed to be refiled elsewhere. Perhaps, these were issues that should have been marked as not planned or left open, but I’m not sure what triaging efforts occurred before the mass closure. If I had received a heads up that this was coming, I would have been glad to help triage what I could.
This indicates that it is being tracked internally, but I believe I can move it (or Jeremy can when he is ready) to where internal things are being tracked.
Do you mean the linked issue? I don’t see a linked PR – but I might just be overlooking it.
I see a mention that iHiD understands the issue and will address it; I don’t see any indication that there is a separate issue tracking it. iHiD could be relying on this issue to handle things, too.
Yeah, the closures were done based on the README, some new activity on a retired repository finally tipping the inertia to action to hopefully reduce that.
Having 499 issues open on a retired repository where we are asking people to not do so seems to welcome more of that kind of activity there. I knew it would cause some noise, hopefully more on the “We still have this pending and want it” side of things, while reducing what we do not want in the long term.
If you want to bubble them up, I can move them if they would need to be. I can also reopen them, but it is the wrong place.
Maybe to revive them, (maybe even after the holidays) talk about the things in the forums, and see if they come out as issues or if Jeremy has them on his radar?
@PatrickMcSweeny sorry we didn’t give you more feedback. It was discussed outside of the PR and I also personally mentioned it is something we must do. Jeremy indicated it will be done, but it interferes with the current work which is touching a lot of the UI pages and there is no bandwidth to add more review.
Whilst he’s happy for someone else to do it, it would just be done in vain and sit in review for months, as the team works towards the next big changes: a new product for Exercism and the big translation project.
I see a mention that iHiD understands the issue and will address it; I don’t see any indication that there is a separate issue tracking it. iHiD could be relying on this issue to handle things, too.
