On Sun, 2005-07-24 at 20:12 -0300, bulia byak wrote:
On 7/24/05, Jon Phillips <jon@...235...> wrote:
Ok, send an msg. to the list when done and I will start hacking on the Press Release.
Apart from being (IMHO) a bit too wordy, the 0.41 press release made a very major error: it spoke about "planning for the 0.42 release", which left many people who read it quickly confused as to which version _this_ is. I saw it reported on some sites as 0.42 apparently because of that.
Ok, why don't you write the first draft. I'll re-edit.
Also, I have received in the past emails from magazines and press outlets that complain about lack of third person and the too personalized nature of Inkscape press releases and is one of the major reasons that I have professionalized past releases -- it works. Also, third person formal/professional releases is the standard. If you want to be picked up seriously by magazines, news agencies, and other agencies and be heard, this is the standard format.
Other people, companies, press outlets, etc, are not in our community and will not understand some of our community jargon.
Also, while a "formal" press release may be necessary for some markets (by the way which exactly?)
Look at the list in the wiki sir.
, I don't think we need to write a separate "informal" one as we did last time.
I disagree. I think this is part of our project growing...informal for local community and formal for formal press contacts. Realistically, the professional should be the primary release, but I think the dual strategy is a good compromise.
For the "informal", why don't we take the "In Brief" section from the release notes and just add the download & complete rel notes links at the end. Trying to rewrite these itemized highlights in prose will lose energy and focus. People like succinct itemized lists and hate marketing-sounding prose.
All people? That is a lot of people. I agree about not rewriting the prose. But please, look at professional PR from apple, etc, and see that the press release is not a bullet point list, but an overview...a press release is to send out as an announcement. The Changelog and release notes are the thing to show to everyone for more points, but not for the press release which is to sum it all up and highlight the major points...
It's very nice that this time, all our packagers are so prompt. Let's try to minimize the time span between posting the tarball and posting the binaries, this will help make the release more focused. As we are going to package the tarball late today, let's try to make the major packages (rpm, dmg, exe) available by tomorrow's night. Does it sound reasonable?
As this is a really major release, I'd like to ask everyone to do our post-release marketing really energetically this time. E.g. I think we well deserve a Slashdot story; who has experience posting news to Slashdot? I think we should always use the "informal" announcement by default, unless some place specifically requires the "formal" variety. For one thing, I think the guys on the w3c-svg list and in various Linux magazines will be much more interested in the informal announcement with a feature list.
Ok, not sure as to where are releaes process is at. It feels like our release will be tomorrow night with PR going out then.
Jon