Unless there are other projects out there that are using OpenSRF (and I'm not aware of any), I think it makes sense to merge them. Having a single repository and install process would be a huge benefit, and I don't really see any downsides. The feeling at the dev meeting was that the merge should happen after OpenSRF migrates to Redis (https://bugs.launchpad.net/opensrf/+bug/2017941), which seems like a reasonable timeline to me.
In other words: I love this plan! I'm excited to be a part of it! Let's do it! Jeff ________________________________________ From: Evergreen-dev <evergreen-dev-boun...@list.evergreen-ils.org> on behalf of Bill Erickson via Evergreen-dev <evergreen-...@list.evergreen-ils.org> Sent: Tuesday, September 12, 2023 1:24 PM To: Evergreen Development Discussion List; Evergreen Discussion Group Subject: [Evergreen-dev] Merging OpenSRF & Evergreen Into One Project Hi All, At today's IRC developer meeting, we discussed a proposal to merge OpenSRF and Evergreen into a single codebase / project. The initial proposal: https://bugs.launchpad.net/opensrf/+bug/2032835 IRC logs from today's meeting: http://irc.evergreen-ils.org/evergreen/2023-09-12#i_533091 At the meeting, we reached a provisional thumbs-up on the concept. This is a big change, though, and the discussion warrants more space, time, and coverage than an IRC meeting can accommodate, so I'm hoping to migrate the conversation to the list. Thoughts, concerns, questions on the proposal? At this point, we're still at the "should we do this?" stage, but I'm also happy to discuss specifics regarding potential planning and implementation. Thanks! -b This message originated from outside the M365 organisation. Please be careful with links, and don't trust messages you don't recognise. _______________________________________________ Evergreen-general mailing list Evergreen-general@list.evergreen-ils.org http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
