Hi Sebastian … As you formulated your proposal as a consensus based decision, and we’ve had enough time for others to speak up, I think you should be good to request a new repo.
However we should probably discuss the name … apache-plc4x-go (isprobably the ideal option as it keeps the full project name in the repo name. Apache-plc4go would be the cooler option, but we slightly loose the „plc4x“ … I know other projects don#t really care about keeping the project relation, but personally I’d opt for the apache-plc4x-go variant to make it clear where the repo belongs. Chris Von: Tom NewChao <[email protected]> Datum: Montag, 27. Juli 2026 um 16:33 An: [email protected] <[email protected]> Betreff: Re: breakout plc4go in seperate repo > I would propose to split out plc4go into a seperate repo. (Same could be done for other languages if desired). +1 (non-binding) from my side. I'm currently working on reviving the .NET implementation (plc4net), and Christofer's point about having code-generation be part of the language's own tool stack resonates strongly with my experience — the C# code generator is currently written in Java and lives in the monorepo, which makes it unnatural for .NET contributors to improve. Having plc4go as the first split would set a good precedent and pattern for other language implementations to follow. - Tom Sebastian Rühl <[email protected]> 于2026年7月27日周一 21:21写道： > I would propose to split out plc4go into a seperate repo. (Same could be > done for other languages if desired). > > Any objections? > > FYI: There was a consensus and discussion back then about this > > - Sebastian >
