Hi discuss@, As posted on [email protected] [1], we'd like to begin migrating Buildstream over to the ASF. As mentors, Sander and I feel that the rough priority list should be as follows:
1) Migration of the relevant mailing lists 2) Migration of the source code to ASF (including CLAs/software grants as necessary) 3) Conducting a Buildstream release under the ASF auspices and rules 4) Migrate the website and other public documentation to ASF Once these items are completed, I believe that Buildstream would be able to stand on its own as a independent PMC. Until then, we'd keep in coordination with the Petri PMC. GUADEC 2020 is coming up in late July, so we'd like to demonstrate progress by then; I don't believe that we have to have everything completed by then, but it's a good milestone to work towards. For the lists, we'd like to avoid having to rename the lists and infrastructure at a later date. How does the Petri PMC feel about this? I know that the Incubator prefers an intermediate step of going to <podling>- [email protected] ; but, for existing OSS communities trying to come in, that'd be 2 additional changes. So, how do we feel about going straight to the eventual TLP domain? We can definitely have suitable disclaimers on the releases and websites until there is an independent PMC stood up. Sander and I have kicked around builds.apache.org as the eventual domain for Buildstream as we eventually seeing it become an umbrella PMC with other build-related projects - as such Buildstream as the TLP name might not be ideal. That said, there already exists a builds.apache.org for the ASF CI tooling...so, I think that we're open to other suggestions here - we'll also solicit feedback from the existing Buildstream community in parallel. Once we agree upon the domain name, we'd want to request creation of a dev@ and private@ list and then we can start on migrating traffic and begin coordination steps 2-4 above on those mailing lists. Cheers. -- justin 1. https://mail.gnome.org/archives/buildstream-list/2020-April/msg00010.html
