I'm only putting it as task out here. If this should happen or not.. and what the text should be.. is primarily matter of the decision at BoD.

I'm not really inclined to an additional open discussion.. taking far to long.. to many opinions.. and expect discontent one way or another.

But I even see the question 'how to handle' this matter a topic of the board. 
So my 2 cents. 

I only want clear cut, final decisions. And hoping the BoD being able to handle the hopefully hypothetically angry mob in a kind of professional manner. 

Please count to 10 (.. minutes, so 600 seconds, maybe even longer). Don't get infuriated. Maybe even prepare a default statement from BoD as whole. So BoD members can send the same statement and being able to repeat it over and over.. without going individual responses. And if inclined to answer,  don't answer yourself.. but the BoD will get back to you (with formal statement). 

But me brainstorming advise, without real world experience :P

As noted bug 139335 details were already present in the June work on "Personal Edition"

https://gerrit.libreoffice.org/c/core/+/97427

They'll get another look as Italo marshals the marketing effort. No sense in spinning off all these related tasks.

*** This bug has been marked as a duplicate of bug 139335 ***

(In reply to V Stuart Foote from comment #2)
> As noted bug 139335 details were already present in the June work on
> "Personal Edition"
> 
> https://gerrit.libreoffice.org/c/core/+/97427
> 
> They'll get another look as Italo marshals the marketing effort. No sense in
> spinning off all these related tasks.
> 
> *** This bug has been marked as a duplicate of bug 139335 ***

Split out only because it technically all separate decisions/discussions. The are building blocks for the marketing effort, but few of them can hypothetically dropped without jeopardizing everything

No actual preference how should be presented in the bugtracker. Only two practically implication
(A) people potentially replying. A single topic with multiple elements is painful (and messy).  
(B) separate bug might be practical if if some adjustment must be made as follow up (so kind of reopening).

However if the instructions are clear and precise and everything handled internally.. also fine.. 

But well kind of preferring that all elements will be decided by BoD without any (additional) community input in advance. But not able to gauge how 'surprised' and badly tempered the community would be by such a move. 

The branding is a name was a thing.. But Community the brand is kind of implementation details, except I like a vote of BoD. So everybody involved - except the BoD - having clean hands (whatever you're personal take might be. So maybe implementing Community title without really liking it yourself). 
The burden for defending it should be ultimately at BoD who represents everybody (formally and hopefully practically).

Yes, I'm moving BoD kind of in the middle of it. But well, it comes with job description, not?

(In reply to Telesto from comment #3)

Sorry, but implementation issues have always been and remain preview of the ESC, 
and as here the Marketing team.

The BoD made the decision and "Community" it is. Now the doers will do. 

No cover is needed, and as the framework for branding was already laid out by Miklos & Heiko for the 97427 patch, that gives an accurate preview of what is forthcoming. 

Sure some tweaks may be needed--but nothing should go back to the BoD, they have other responsibilities than implementation issues.

(In reply to V Stuart Foote from comment #4)
> The BoD made the decision and "Community" it is. Now the doers will do. 

Thanks for the info; and sorry for the noise. If that's the existing procedure.. fine.. IMHO I expect the (full) original approach (except the ugly font & personal label). Hope the do'ers having their elephant skin prepared, just in case.