keon94 commented on issue #2078: URL: https://github.com/apache/incubator-devlake/issues/2078#issuecomment-1346975147
> Good thinking, I would like to share my 2cents as well: > > 1. both go/python belongs to the Backend, while `go` acting as the dominating role controlling the whole operation and `python` serving as a optional helper for plugins, it makes more sense to put `python` inside the folder containing our `go` code. > 2. should we keep the backend/frontend code inside the same repo? there were discussion talking about extracting config-ui to another repo. > > It is big, let's do it step by step, finish the go module relocation first. 1. Yeah, it's just kind of awkward to mix go.* files with, say, requirements.txt or *.toml in the same top directory. If in the future we decide to add a third language as well it'll just get messier. How about backend/go/* and backend/python/*? backend-go/* and backend-py/* would achieve the same thing as well. I guess it's a matter of preference. 2. I agree, we should do that in another PR if we decide that. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
