>On Tue, Jan 9, 2018 at 1:47 PM, Robert Munteanu <[email protected]> wrote: >> ...- place it in the whiteboard and move it to a proper repo before its >> first release, with the release manager proposing a name.. > >+1, it's simple and leaves time to make a proper naming decision. > >-Bertrand
yes, this would avoid making the naming decision early, or even the decision to release it at all. on the other hand it makes it more difficult if the contribution was already developed in a standalone git repo outside the ASF and perhaps there is already a commit history we want preserve - getting this into the whiteboard master branch in a subdirectory is complicated. or do you propose a new branch for each contribution in the whiteboard, not related to it's master branch at all? having everything in the master branch also makes it difficult to split it later (yes i know, it's possible in git, but still requires more effort then just having one branch per module). having one branch per contrib/whiteboard module may seem unorthodox on the first sight, but might come very handy when it's moved later, and also for the first import. stefan
