Defining a scope here is also fairly important. For example, the apache.org domain name is fairly baked into a lot of unchangeable places such as Java package names, every single released artifact, the software license itself (which is used by tons of people outside of ASF), all the existing public URLs to things, email addresses, signing keys, the GitHub organization name, tons of infrastructure configuration, finance documents, corporate documents, trademarks, and surely other areas I'm forgetting.
If we have a name change and only update the places where it's easy to do so, the name Apache will still be highly visible in tons of key areas for the indefinite future. This isn't even considering downstream users of Apache software, either, who may or may not adopt a rename. These are some of the fairly intractable concerns I've had about a name change, and that's even after working with another OSS project that went through a name change and still has tons of references to its old names due to compatibility issues. On Thu, Apr 28, 2022 at 3:49 PM Christian Grobmeier <grobme...@apache.org> wrote: > > > On Thu, Apr 28, 2022, at 22:19, me wrote: > > Christian, > > > > Were you thinking of an internal poll? That’s actually a spectacular idea. > > Yes, that was I was thinking. Basically a poll on members@, since (I guess) > members would eventually decide on that proposal. > > > > > How do we go about kicking that off? > > I am not so sure either, but I guess writing the poll and proposing it to > community@ would be a first step. Once decided on the content we could vote > on sending it, and then send it to members@ > > Others may have different ideas, but that is my first idea on it. > > Thanks for calling my idea spectacular, it gives me a warm feeling, since I > didn't think of it as such :) > > Kind regards, > Christian > > > > > > > Ed Mangini > > m...@emangini.com > > > > > > From: Christian Grobmeier <grobme...@apache.org> > > Reply: dev@community.apache.org <dev@community.apache.org> > > Date: April 28, 2022 at 15:43:04 > > To: dev@community.apache.org <dev@community.apache.org> > > Subject: Re: It’s time to change the name > > > >> > >> Hello, > >> > >> > >> On Thu, Apr 28, 2022, at 20:57, me wrote: > >> > The desire to make the change is definitely there. I echo Walter’s > >> > passion and statements. > >> > >> +1 > >> > I also agree w/ Sam that this isn’t going to be easy to accomplish. > >> > >> +1 > >> > >> > Perhaps a starting point would be to answer these questions in concert: > >> > - what is the LOE to perform the rebranding/renaming? > >> > - are there enough volunteers within the organization willing to > >> > participate? > >> > - what does the community think? > >> > > >> > I want to emphasize that this last question is a point of no return. If > >> > we start creating surveys and asking about our brand, it’s going to > >> > chum the waters. > >> > >> Agreed. I would have thought to make a poll in the community first- > >> briefly explain the issue and see what the community (non-binding) vote is > >> - just checking sentiments. > >> > >> I am afraid there will be a lot of headwinds. But based on the outcome one > >> could decide if its more work to explain the issue or actually solve the > >> issue. > >> > >> Also a quick poll could stir up some people who are interested in helping. > >> > >> Cheers, > >> Christian > >> > >> > > >> > > >> > From: Walter Cameron <walter.li...@waltercameron.com> > >> > Reply: dev@community.apache.org <dev@community.apache.org> > >> > Date: April 28, 2022 at 01:29:03 > >> > To: dev@community.apache.org <dev@community.apache.org> > >> > Subject: Re: It’s time to change the name > >> > > >> > On Wed, Apr 27, 2022 at 6:40 PM Sam Ruby <ru...@intertwingly.net> wrote: > >> > > >> >> Walter: what are you personally willing to volunteer to do? What is > >> >> your plan? What resources do you need? > >> > > >> > > >> > Honestly Sam the extent of my plan was to bring attention to this issue > >> > and > >> > the harms it’s caused. Beyond that I’m kinda winging it but I appreciate > >> > your eagerness and openness to change. I had hoped I’d speak up, people > >> > would finally pull their heads out of the sand and work to undo the harm > >> > they’ve caused. > >> > > >> > ASF’s brand violates its own CoC. You would think that might spur effort > >> > for change by those perpetuating the harm, but if you want me to do the > >> > work I’ll do whatever I can. I’m not that familiar with the details of > >> > the > >> > organization, surely not as familiar as one of its Directors, so in a lot > >> > of ways I don’t fully understand the scope of what needs to be done, but > >> > I’m willing to volunteer a few weekends of my rudimentary technical and > >> > design skills to run a “Find & Replace…” and put together a new logo or > >> > whatever you think would be helpful in this effort. I haven’t designed a > >> > logo in probably 15 years but I’m willing to give it a try. > >> > > >> > I would have assumed that an organization with a paid staff and goals to > >> > increase the diversity of its contributors and continue receiving > >> > corporate > >> > donations would understand that the costs of inaction outweigh the costs > >> > of > >> > action here. > >> > > >> > Let me know what else I can do to help. > >> > > >> > Walter > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> For additional commands, e-mail: dev-h...@community.apache.org > >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
