On Fri, Jul 15, 2016 at 6:22 PM, Sally Khudairi <[email protected]> wrote:
> Thanks, Todd. Hello Apache Kudu iPMC! > (note: this is actually on dev@ -- if it's better for press release purposes not to discuss a draft in public, we can move it to private@ - let us know) > > We will work together to issue a formal ASF press release --here's a great > opportunity to solicit quotes/testimonials from the Apache Kudu community > to demonstrate the project's robustness and breadth of deployment. > > TLP announcements have ranged from having single quotes (VP of the > project) to several perspectives from the PMC to multiple endorsements from > the community. [1] and [2] are examples that you might find useful. > > Organizations supporting/using Kudu are welcome to issue their own, > standalone "hurrah, Apache Kudu!" blog or press release at that time as > well (we love it when multiple announcements come out to support a > podling's graduation!). We just need to make sure that we coordinate > messaging/timing/etc. > Sounds great. I imagine my employer would be interested in such a "hurrah" post. I'll work with the press people on our side to coordinate with you off-list, if that's the recommended way to go about it. > > So our next steps here are for you (and the PMC) to: > > 0) identify a primary point-of-contact; > 1) help me draft the announcement (mostly filling in the "what is > Kudu"/features+functionality bits --I'll do the headline/subhead/opening > paragraph); > I'll volunteer for the above two. Is a google doc a good way to collaborate? (I think we did this for Parquet and Arrow iirc) > 2) decide whether you'd like to include supporting testimonials from the > community (and solicit them); and > This sounds like a great idea to me. I'll send some emails out to some of our early adopter users and contributors. If anyone on the dev@ list is interested in contributing a quote, feel free to jump in here. > 3) work together that our formal press/public and internal/developer/list > timing is in synch (it's best to have everything roll out within a 24-48 > hour timeframe, rather than announce the project's graduation on your dev > list or [email protected], followed by a press release several weeks > later) > > Before anything goes out on the media/analyst news channels, > kudu.apache.org needs to be live so that our pointers are active. All > references to "incubating" on the Website, social media, and related > properties will need to be updated when we go live. > OK. kudu.apache.org is already live, actually -- but we do need to remove 'incubating'. I'll take point on that as well, as soon as the actual graduation resolution is passed. We'll also be sure not to be too noisy about announcing the board meeting results until the press release is out. > > We also need to lock in the announcement date --we usually issue press > releases on Tuesdays, as that garners the best global media > exposure/coverage, followed by Mondays, then Wednesdays. So in this > instance, the earliest we can issue the press release would be the Monday > following the 20 July Board meeting, i.e., 25 July. > > Thanks in advance for your help. Feel fee to ping me if you need anything. > > No, thank you! Glad to be working with someone who has done this way more times than any of us. -Todd
