Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What to do with the Storybook project? #286

Closed
2 of 3 tasks
robbertbos opened this issue Oct 28, 2024 · 0 comments · Fixed by #287
Closed
2 of 3 tasks

What to do with the Storybook project? #286

robbertbos opened this issue Oct 28, 2024 · 0 comments · Fixed by #287
Assignees

Comments

@robbertbos
Copy link
Member

robbertbos commented Oct 28, 2024

Description

We created a storybook project so we could use ROOS (and other NL Design projects) for reference. The project is not maintained or updated at the moment. It also is not actively used, as most of us use the (official) ROOS storybook.

What do we want to do with the project?

Some options:
a) we could archive it for now and remove the gh pages deployment
b) we could put auto-update in place to keep security issues away
c) we just leave it as is
d) yet another option

Preference for option a since:

  • We already use the official ROOS Storybook
  • Maintaining a parallel system creates unnecessary overhead
  • We do not need to spend time on re-evaluating this issue

Technical Implementation

@laurensWe laurensWe self-assigned this Dec 19, 2024
@laurensWe laurensWe transferred this issue from MinBZK/amt Jan 13, 2025
@laurensWe laurensWe linked a pull request Jan 13, 2025 that will close this issue
5 tasks
@laurensWe laurensWe moved this from 👷 In Progress to 👀 In Review in 👾 AI Validation Team Planning Jan 13, 2025
@github-project-automation github-project-automation bot moved this from 👀 In Review to ✅ Done in 👾 AI Validation Team Planning Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

2 participants