<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Additional text line in about window about what 'Community Edition' entails" href="https://bugs.documentfoundation.org/show_bug.cgi?id=139347#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Additional text line in about window about what 'Community Edition' entails" href="https://bugs.documentfoundation.org/show_bug.cgi?id=139347">bug 139347</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=139347#c2">comment #2</a>) > As noted <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - UI: LibreOffice product flavor Community branding" href="show_bug.cgi?id=139335">bug 139335</a> details were already present in the June work on > "Personal Edition" > > <a href="https://gerrit.libreoffice.org/c/core/+/97427">https://gerrit.libreoffice.org/c/core/+/97427</a> > > 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 <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - UI: LibreOffice product flavor Community branding" href="show_bug.cgi?id=139335">bug 139335</a> *** 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?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>