I'd like to share some reasons why I prefer using a monorepo for OpenDAL. First of all, after migrating the repositories to the ASF, we will lose admin permissions for them. This means that any operations requiring admin privileges will have to go through INFRA tickets unless they are supported by ASF tools. For example, configuring GitHub secrets or making CI run for every PR by default. Setting this up for multiple repositories could be very challenging.
Secondly, I find that keeping everything in the same monorepo makes it easier for the project to grow. Stars, issues, PRs, and discussions all happen in the same repository, making it easier to bring people together. This is especially important for a small and new project. We can always split the project later once we have a sufficient number of dedicated committers focusing on a specific area—for example, three committers who explicitly dedicate themselves to the Go SDK. Both setups work for me. On Fri, Feb 7, 2025, at 14:28, tison wrote: > cc in case you don't subscribe dev@ yet. > > You can reply with PonyMail also [1] > > [1] https://lists.apache.org/thread/zrn96nlg23r9353lr5tp2by2ggx4zxqc > > Best, > tison. > > tison <wander4...@gmail.com> 于2025年2月7日周五 11:30写道： > >> >> Hi, >> >> I'd continue the discussion from [1] about whether we'd set up a >> monorepo for all the Iggy's code, or continue the current multiple >> repositories solution. >> >> [1] https://lists.apache.org/thread/ppqjvygk8xs7v8no5dk6r6khm5m1vp71 >> >> The only thing I'd point out is that the ASF doesn't support >> fine-grained permissions so please make correct assumption. >> >> Either monorepo (OpenDAL's multilingual bindings [2]) or multiple >> repos (SkyWalking and its multilingual SDK [3]) works for me. >> >> [2] https://github.com/apache/opendal >> [3] https://github.com/apache?q=skywalking&type=all&language=&sort= >> >> Best, >> tison. -- Xuanwo https://xuanwo.io/
