We need to get the devfile gem in a production-ready state: https://gitlab.com/gitlab-org/remote-development/devfile-gem There are several issues open against the gem: https://gitlab.com/gitlab-org/remote-development/devfile-gem/-/issues In addition... - We have to figure out exactly how to do the multi-platform packaging, which is essentially to “make it like nokogiri”, and we can also take inspiration from the rust-based yrb gem Hannes made (although he relied on GitHub Actions some, which we can’t. - And we also need to set up a solid continuous versioning, delivery and release automation pipeline, like we’ve done for the VS Code fork. And also address the following: - [ ] The require should be in the file where the gem is used, in `devfile_processor.rb`, not in `desired_config_generator.rb`. Also, if we do it this way, we should put `require: false` in the Gemfile for this gem, so it's not required during rails init. - [~] (NO LONGER HAPPENING) @cwoolley-gitlab started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/112906#note_1308282553): > **suggestion:** RubyMine still shows a `No such file to load` warning on this require. > > That implies that we still don't have something right in the specification for the gem to get the `devfile.rb` on the load path properly. > > I know we have other cleanup to do on the gem and its spec for multiplatform/etc. > > Can we make sure we include looking into this require problem as an issue or a task on an existing issue for the gem cleanup?