Philip Durbin 🚀 (Apr 03 2023 at 15:48): Philip Durbin 🚀 (Apr 03 2023 at 15:48):I just left the following comment on the proposal:
I would like to split up milestone A into GitHub issues that represent future pull requests.
For each issue I'd like to apply our standard sizes (3=two hours, 10=seven hours, 33=twenty-four hours) to indicated how much effort it is needed to get the pull request all the way through QA and merged.
For issues or features that are already completed, I'd like to indicate that it's done and link to issues or pull requests.
Especially for this first milestone, I would like for us to complete it with the smallest remaining scope possible. We've already done a lot! :tada:
I'm happy to discuss more here.
Partially, this comment was inspired by a question at standup this morning where it was asked how much more effort is needed to use containers for development. I asserted that I gave a demo two weeks ago and that if you have Java installed and are on Mac or Linux, the containers are ready for developers to build and use. For two weeks I've used the containerized environment to test and review pull requests.
I know there's a lot currently under milestone A. I think we should push a lot of it to future milestones.
What do YOU think? :happy:
Guillermo Portas (Apr 03 2023 at 17:01):I really like your idea, thanks @Philip Durbin.
Now that I'm reviewing milestone A, with a greater focus on limiting the scopes of the milestones, in my opinion some of its topics may not be directly related to the scope of "Dataverse in containers for a backend (Java) developer". I consider that the environment is already usable for development purposes by a backend developer, assuming that the developer is someone who clones and manages the Dataverse backend repository.
The advantages of pushing images to the registry, as well as auto-containing the Solr configuration in a custom image, are improvements more oriented to milestone B in my opinion, since they are more related to a setup where you don't want to clone the Dataverse repository, expecting all the dependencies and related configurations to be contained in pre-pushed remote images. (The use case for frontend devs, who would have their own docker-compose file in their particular frontend repository, pointing to these remote images).
So first, maybe I'd refine the scope of the milestones a bit, if you agree, or I'd appreciate your point of view on this. Maybe we can discuss this at the next container meeting.
The issue that I would perhaps create for the milestone A, before marking it as complete, is to build the image without maven. But it can be a nice to have, since strictly the scope of A is already reached in my opinion. I would transfer the enhancements that I have mentioned about custom images and pushes to registries to milestone B, and start working in that direction.
Philip Durbin 🚀 (Apr 03 2023 at 17:45):Yes! I think the primary things I want are:
I do think we should discuss this as a group.
Philip Durbin 🚀 (Apr 06 2023 at 15:40):We greatly reduced milestone A today and created other small milestones. The recording is up at https://ct.gdcc.io
Philip Durbin 🚀 (Apr 06 2023 at 15:42):You can see the diff here: https://github.com/gdcc/ct.gdcc.io/commit/22af1fc
Guillermo Portas (Apr 10 2023 at 16:01):Thanks for the nice work on the milestones reorganization, @Philip Durbin I just left a comment on the draft document about a small change.
Philip Durbin 🚀 (Aug 11 2023 at 15:22):We finished milestone A some week ago when we finished some docs: #9540. Resolving.
Notification Bot (Aug 11 2023 at 15:22):Philip Durbin has marked this topic as resolved.
Last updated: Oct 30 2025 at 05:14 UTC