I see the point of including the kogito-examples in the release, but I think it would be better to not put them in the tools repo:
1. java code under the tools repository ended up on being managed by pnpm, and that surely would be an issue for all the people that have no need nor interest in spending time to set up their machine for such stack 2. more in general terms, the examples are still not ASF compliant AFAIK, or, at least, they are not reproducible - and that's the reason why they have been excluded initially 3. I think that putting everything in one single repo is more sort-of anti-pattern, from source-code management point, that a real improvement: the bigger and "mixed" a repo is, the harder the work for IDE to even open it (and for developer to work on it) So, back to topic, I think we should 1. fix or double check their "compliance" with ASF requirements 2. add them as last "ring" of our CI "chain" @Francisco Regarding mono-repo, I hope we'll focus more on the real problems that make that "mono-repo" an apparent solution (while it would be just the final sign of inability to manage our code-base properly, IMO). About "but I have the feeling that there is a majority in favour of that": TBH I do not think it is really so M2C Il giorno mar 7 gen 2025 alle ore 17:21 Jason Porter <jpor...@ibm.com.invalid> ha scritto: > Easier in the sense that there’s only one place to look for examples > (maybe docs too?), the actual source, and to understand the project. Also > easier for them to eventually become contributors. I’ll admit those reasons > are minor however. > > -- > Jason Porter > Software Engineer > He/Him/His > > IBM > > > From: Francisco Javier Tirado Sarti <ftira...@redhat.com> > Date: Tuesday, January 7, 2025 at 04:52 > To: dev@kie.apache.org <dev@kie.apache.org> > Subject: [EXTERNAL] Re: [DISCUSS] Missing kogito-examples update for the > 10.0.0 release! > Hi, > I can see why it is easier, from a technical point of view, since some > examples rely on tooling, to move all examples to tooling repo. > However, I hardly see why this makes users' experience better. > Let me elaborate, With examples repo, we currently have a place where users > can browse all examples starting from the repo root. > With tooling repo, I guess they will start browsing under examples > directory? > If we are going for technical simplicity, I guess it is probably time to be > coherent and move all KIE content under the same repo (I'm not for it, but > I have the feeling that there is a majority in favour of that, so probably > time to vote?). > Which I feel is really awkward is to have different strategies under the > same label (some content in some separate repos and gradually moving > everything to a repo named "tools" which is not really just "tools" > anymore) > > > On Mon, Jan 6, 2025 at 5:26 PM Jason Porter <jpor...@ibm.com.invalid> > wrote: > > > I know it makes for a larger repo, but I’m all for fewer repositories, > and > > an easier setup for not only contributors, but all users. > > > > -- > > Jason Porter > > Software Engineer > > He/Him/His > > > > IBM > > > > > > From: Alex Porcelli <porce...@apache.org> > > Date: Monday, January 6, 2025 at 03:01 > > To: dev@kie.apache.org <dev@kie.apache.org> > > Subject: [EXTERNAL] [DISCUSS] Missing kogito-examples update for the > > 10.0.0 release! > > Happy new 2025, everyone! > > > > As we discussed when we started the 10.0.0 release process, the > > kogito-examples repository was neither included in the release nor fully > > integrated into CI. Although some PR checks consider kogito-examples, > this > > gap ultimately led to absent examples for the 10.0.0 release. > > > > Currently: > > > > - The stable branch remains on versions 1.44 and 8.44 > > - The main branch is on 999-SNAPSHOT > > > > Given that many of the kogito-examples rely on container images and Dev > UI, > > we'd need to incorporate the repository into our CI system to improve the > > current situation, which might take some time and will likely impact the > > upcoming releases. > > > > Alternatively, we could move the examples to kie-tools (a repo that > already > > hosts all images and DevUI) so no CI changes would be required. > > > > I would love to hear your thoughts, alternative ideas, or concerns so we > > can have an actionable plan to do better in the next release. > > > > Regards, > > Alex > > >
