The conversation has been open for 2 weeks now, and I appreciate all of the feedback and conversation. I am going to summarize the conversations as they stand and outline what I believe next steps are based on the feedback.
RPMs I performed a quick tally of those that responded and essentially got the following counts on SCL vs. vendor. SCL: 4 Vendorizing: 2 Further, there appeared to be a lot of unanswered technical questions around how we maintain a vendorized stack with plugins that need to add dependencies. Based on this feedback, I believe the goal should be to create a new Rails SCL that we own and maintain. As for the plan, the how, of creating and maintaining this new SCL, I will start a new thread to discuss the plan and improvements we can make along the way. NPM Across the board, everyone appeared to be in favor of vendorizing our NPM modules to reduce the frequency of breakages and to allow the UI work that is on going across Foreman and plugins to continue at a rapid pace. I'll start a similar thread to outline and discuss the changes for this. Eric On Sun, Oct 29, 2017 at 5:43 PM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: > On Mon, Oct 23, 2017 at 09:52:39AM +0100, Greg Sutcliffe wrote: > >> On Mon, 2017-10-16 at 14:36 +0100, Greg Sutcliffe wrote: >> >>> >>> That said, I've not really been involved with the RPMs, so I'm unsure >>> if this causes a bigger headache for Yum users than Apt users. I'm >>> also unsure of the work required to create an SCL, but if it's non- >>> trivial then I'd be looking to CentOS to collaborate on a Rails SCL >>> for everyone to use - for just ourselves, then vendoring seems >>> easier. >>> >> >> I spoke to a few people I know about this, and it seems there's not >> much appetite for making new SCLs. We might be able to attract >> contributors once it's created, but I think we should assume the effort >> for creating/maintaining SCLs will fall on us initially. >> >> Do we have any conclusions on this thread? It's going to matter for >> 1.17 which is getting closer by the day. >> > > Personally I feel an updated RoR SCL is the way to go for 1.17 and to > prove that I'm willing to invest the time to make it a reality. After 1.16 > RC2 is out I'm going to spend time on it. > > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Eric D. Helms Red Hat Engineering -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
