Hi Dave, Funnily enough I have that page in my recent browser history. " builds.apache.org" is indeed not the most practical in that sense. I guess we run into one of the top problems in engineering again, naming things. I need to be a in a more creative mood for that, as currently only "construction site" and "redibute" spring to mind. The latter being short for REpeatable DIstributable BUild and TEst... If anyone has a lightbulb moment...
Cheers, Sander On Sat, May 2, 2020, 17:57 Dave Fisher <[email protected]> wrote: > -1 on builds.apache.org. This sub domain is used for Infrastructure > Jenkins by almost every Apache project. I’m surprised you haven’t noticed. > > Sent from my iPhone > > > On May 2, 2020, at 5:02 AM, Sander Striker <[email protected]> wrote: > > > > On Sat, Apr 25, 2020 at 7:34 PM Daniel Shahaf <[email protected]> > > wrote: > > > >> Justin Erenkrantz wrote on Sat, 25 Apr 2020 15:39 +00:00: > >>> 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] ; > >> > >> The Incubator switched to dev@<podling>.incubator.apache.org and then > to > >> dev@<podling>.apache.org (e.g., https://nuttx.apache.org/community/). > >> > >>> 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. > >> > >> Sounds good to me, though we might want to give trademarks@ a heads up. > >> > > > > FYI, I gave trademarks@ a heads-up. > > > > > >> Cheers, > >> > >> Daniel > >> > > > > Cheers, > > > > Sander > >
