Add PaNOSC Research Software Stories - alpaka and PiConGPU

[srghosh56]

Fixes #355 & #356

Adds two PaNOSC Research Software Stories - alpaka and PiConGPU

[netlify]

✅ Deploy Preview for everse-rsqkit-testing ready!

Name	Link
🔨 Latest commit	547dac0
🔍 Latest deploy log	https://app.netlify.com/projects/everse-rsqkit-testing/deploys/698b3c66ea9397000818defb
😎 Deploy Preview	https://deploy-preview-584--everse-rsqkit-testing.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[sparkslabs]

Hi Srobona,

Thank you for this! There's quite a few issues here, some minor, some larger. I've captured them below.
Breaking down my feedback here in "needs addressing", "Ought to be addressed", "would be nice to address".
Some of the "nice to address" and "ought" could be deferred to a later iteration, but the "needs addressing" really should be dealt with before we merge this PR.

Needs addressing:

• FAIR & Open - other stories break this out each part of FAIR as separate bullets. If someone is unaware of what FAIR stands for, and they read the page it both educates and illustrates the purpose -- eg https://everse.software/RSQKit/acts_research_software_story
• Use of bare URLs - like this: https://github.com/ComputationalRadiationPhysics/picongpu can (and should) be turned simply into links using < and > - cf <https://github.com/ComputationalRadiationPhysics/picongpu> -- renders as https://github.com/ComputationalRadiationPhysics/picongpu
• There's no inline links, which is at odds with other stories. (a few is reasonable for a first iteration, but there's zero)
• You should include yourself as a contributor on the pages in the metadata - since you've been doing the editting :-)
• "{ alpaka / PIConGPU } is classified as Tier 1 Research Software Infrastructure" - this should be Tier 3
  • https://everse.software/RSQKit/three_tier_view - tier 1 is analysis, tier 3 is infrastructure
• Formatting error (text strike-through) on alpaka story for text Performance validation ensuring abstractions don't introduce overhead

Ought to be addressed:

• Tools and Links
  • There's no inline links, which is at odds with other stories. (needing more is OK for a future iteration, but zero is a problem)
  • One easy way of maintaining and using links is to use the [text in the link][LINKREF] syntax, with the [LINKREF] specified at the end of the document. You can see how this works here: https://raw.githubusercontent.com/EVERSE-ResearchSoftware/RSQKit/refs/heads/main/pages/research_software_stories/baler_research_software_story.md
  • No ETT tools links. (Ideally these would be in the first iteration, but that's not been universally true)
• There's lots of references to online resources in "Resources for developers" - but no links. Is it all private?

Would be nice to address:

• Titles repeat the description. This looks a little odd on the overview page. It would read better if the titles were "Research Software Story - alpaka" and "Research Software Story - PIConGPU" respectively.

Key Rationale:

• "Needs addressing - Blockers to merge - inaccuracies, if looks broken, template visible, large deviation from other stories (for unclear reasons), etc
• "Ought to be fixed" - Things that could be potentially addressed in a follow on PR, but either affect utility or maintainability of the PR.
• Links - The links to tools, techniques, tasks and processes helps other with similar needs learn from your story how to achieve similar benefits.

Pragmatically, take a look a this, and decide what you agree needs addressing, then please make changes, push to your branch to update the PR and then we can follow up. We can then decide what to merge!

Many thanks for this!

Michael.

[sparkslabs]

Larger comment on changes included in the discussion - which collates everything.

Generally this is a great addition - the requested changes are largely for consistency and integration :-) (but the "Needs to be addressed" really do need to be :) )

[sparkslabs]

Summarised comments here -- #584 (comment)
Many thanks! :)

[juckel]

@srghosh56 can you take a first shot at addressing all these valuable comments and tell me where you need input from me or the alpaka/PIConGPU maintainers?

[srghosh56]

Hello, @sparkslabs , thank you so much for the comments. I have addressed almost all of them. Can you please take a relook at them?

Hello, @juckel , do the maintainers want to be added as contributors?

[sparkslabs]

Hi @srghosh56 I'll take a look. On the note of contributors, the contributors who get added to a research software story page are those people who have directly contributed to the story - text, sanity/correctness checking etc,