External user struggling to submit story to stories.jenkins.io

[timja]

Service(s)

Other

Summary

Go to https://stories.jenkins.io/admin/#/collections/user-story

Use netlify CMS to submit a story

Error is

Hypothesis is that it works for people who are members of the jenkins-infra org but not people that aren't

Reproduction steps

No response

[krisstern]

Let me see if I could follow up on this as an active maintainer of https://github.com/jenkins-infra/stories

[krisstern]

We currently have a relevant GSoC 2025 project idea at https://www.jenkins.io/projects/gsoc/2025/project-ideas/revamping-jenkins-io-website-success-stories-feature/. So maybe we can coordinate some effort on this front.

[dduportal]

We currently have a relevant GSoC 2025 project idea at https://www.jenkins.io/projects/gsoc/2025/project-ideas/revamping-jenkins-io-website-success-stories-feature/. So maybe we can coordinate some effort on this front.

Personal opinion: re-implementing the website only because there is a credential issue looks unusual and a waste of effort.
Unless there is something else? I'm having a hard time understanding what is the problem because we are lacking documentation or at least audit trail.

Adding a GSoC project on this "mix" means the focus must be set on documenting rather than (re)implementing otherwise we'll end up in the exact same situation in one year, e.g. it will fix this issue and will create another.

My SRE hat gives me a gut feeling that we are missing documentation only to unblock this particular issue and/or clear specification and problem statement if need to be re-implemented: persona, use cases, etc.

[krisstern]

No, the issue is more deep-rooted then simply because there is a credential issue. I don't think the previous maintainer has the capacity (mostly time) to work on the project anymore, or has very limited capacity to check in very rarely once in a while. I was going to take my time and re-work many things on this stories project since it looks like at least for now I will be an active (if not the sole) maintainer for it. But I think it may not be a bad idea to add a GSoC project on this mix since having someone else who is not bound by a full-time job like I am may accelerate the changes we will need to make for this feature to keep it functional and relevant.

IMO, the current workflow deviates much from one that would work well in case we would want to have more transparency (which is preferred for open source I think), especially for the part where people use to submit new stories. I actually just tried it myself and there seemed to have some other issue with the creating new stories as well as the loading of the old records using the link I was provided, even though I did not see the API error. So these signs points to some more tricky issues to be resolved by someone who may or may not respond over the short term (weeks or months) who may or may not know how. (I mean by Gavin Mogan if he will be available, if not then I think that person will be me.)

I would suggest an eventual revamp. But for sure I will need to dig around to see what I can and cannot do at this stage. Let me try and report back shortly.