should we migrate CI scripts to another toolchain and/or reduce the scope of CI actions?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 106
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
the current CI scripts rely on the Rakefile, which in turn relies on Ruby::RDF.
It does number of things, like checking that the examples are valid according to the current state of the spec.
We probably can not count on the fact that Ruby::RDF will be updated to continuously implement the current state of the spec, and therefore be appropriate for us to use in CI...
Can we count on any implementation to follow closely the spec? If not, we probably want to review how our CI actions work...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Rakefile and tracing how Ruby::RDF is used by the current CI scripts, especially for validating examples against the current spec. Review the existing CI actions and determine whether the implementation can track the spec closely enough; done means a decided toolchain and documented CI scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100