Re: world of gnome..
Maybe you could have an article category What's on the whiteboards today?, with a clear icon, so readers knows the information is a snapshot of a work in progress. And maybe, the direction of the article could be inviting readers to discuss pros and cons. (rather than promising a future plan) Just an idea. On 18 October 2012 02:59, alex diavatis alexis.diava...@gmail.com wrote: Hello Matthias, On Thu, Oct 18, 2012 at 2:50 AM, Matthias Clasen matthias.cla...@gmail.com wrote: Yes, worldofgnome is fantastic in the amount of very positive GNOME posts they get out every day. Sometimes, it goes a little overboard though, when early research screenshots get blown out as the latest design, within hours of being added to the wiki [1]. Can we maybe come to some form of understanding about asking first before interpreting stuff as the latest and greatest design? Sure, I will ask authors before I publish again early work.If this is Ok for you. But I am trying to be careful, I always say this is an early design, and that's why I have the full links in Gnome live (Design/Whiteboards/Selections). It's whiteboard, it is clear it is early work. Anyway, sorry! [1] http://worldofgnome.org/text-handling-under-gnome-os/ - alex -- marketing-list mailing list marketing-list@gnome.org https://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org https://mail.gnome.org/mailman/listinfo/marketing-list
Re: world of gnome..
On 18 October 2012 02:50, Matthias Clasen matthias.cla...@gmail.com wrote: Yes, worldofgnome is fantastic in the amount of very positive GNOME posts they get out every day. Sometimes, it goes a little overboard though, when early research screenshots get blown out as the latest design, A solution at the source would be to not make early research look like its done. This is a recurring situation in GUI design, when people present early research with all the little shadows, gradients and glares. People understand it is done. So such articles and interpretations are logical. A more concerning aspect in making research look like its done, is that it prevents people to focus on what really matters. It's like showing a house with all the wallpapers, grandmother's portrait and lights on, when the discussion is about the internal structure of the building. Then the discussions focus on the color of the wallpaper rather than on the size of the beams. The temptation to polish early sketches, and make them look like its done, is understandable, it certainly gives a strong feeling of achievement. Though it shifts the focus and hinder more in depth reviews. There is an excellent article on the subject from Creating Passionate Users, that can be summarised as: - Don't make the Demo look Done - How 'done' something looks should match how 'done' something is. - The better it looks, the more narrow the feedback http://headrush.typepad.com/creating_passionate_users/2006/12/dont_make_the_d.html within hours of being added to the wiki [1]. Can we maybe come to some form of understanding about asking first before interpreting stuff as the latest and greatest design? [1] http://worldofgnome.org/text-handling-under-gnome-os/ -- marketing-list mailing list marketing-list@gnome.org https://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org https://mail.gnome.org/mailman/listinfo/marketing-list
Re: marketing calendar
On Mon, Mar 26, 2012 at 11:47, Allan Day allanp...@gmail.com wrote: On Sun, Mar 25, 2012 at 11:04 AM, Tobias Mueller mue...@cryptobitch.de wrote: Bonjour :) Bonjour ! On Fri, Mar 23, 2012 at 07:11:25PM -0600, Christy Eller wrote: Yes, but I think what Allan was looking for was a reminder email. Well, it should be rather easy to convert Events from a standard format like ical to emails. So if you provide a .ical file, one can parse that rather easily and send emails based on the results. My requirements: * Not exposing the calendar too much on the site. Why? Isn't GNOME an open collaborative project? gnome.org is for public consumption, and this calendar is very much for internal purposes only (as much as we ever have something that is internal) * Keeping track of changes. It would be annoying if changes were made to the calendar and it wasn't clear what those changes were or who had made them. This is a problem that Git and the GNOME infrastructure has solved... Allan -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: GNOME Annual Report Deadline
April 23rd On Mon, Mar 26, 2012 at 14:57, Brian Cameron brian.came...@oracle.com wrote: Telling us on the 24th that the deadline is on the 23rd? Is that an error? Brian On 03/24/12 09:17 AM, Emily Gonyer wrote: Hi everyone, just wanted to let everyone know that the deadline for reports for the 2010/2011 Annual Report is April 23rd. Please ensure all articles you are working on have been submitted by then! Thanks! Emily -- Whatever you can do, or dream you can, begin it. Boldness has genius, power and magic in it. - Goethe Be who you are and say what you feel because those who mind don't matter and those who matter don't mind. - Dr.Seuss Not everything that can be counted counts, and not everything that counts can be counted. - Albert Einstein -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Thu, Mar 8, 2012 at 13:10, Andre Klapper ak...@gmx.net wrote: On Thu, 2012-03-08 at 10:57 +, Allan Day wrote: On Thu, Mar 8, 2012 at 10:47 AM, Andre Klapper ak...@gmx.net wrote: On Thu, 2012-03-08 at 09:59 +, Allan Day wrote: We might struggle to do it for this release, but having a separate press release and some kind of release notes for the release candidate could be a good way to get the word out. Release Candidate = two weeks before the release. Oh? The schedule [1] says it's one week before the release. Argh. So much for my reading skills. :) Sometimes it's one week and sometimes it's two weeks, also depends on external influences on the schedule (releases vs public holidays; no freezes yet when conferences like GUADEC or hackfests take place; etc). It was just an idea. But I don't see why we couldn't aim to have *something* (it doesn't have to be the full, finished release notes) ready a week in advance. I agree, but I'm afraid that reality (and its manpower) will bite us. (We also dream of documentation freezes for translators. :-) Yes! :-) -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Thu, Mar 8, 2012 at 23:53, Sriram Ramkrishna s...@ramkrishna.me wrote: On Thu, Mar 8, 2012 at 11:59 AM, Allan Day allanp...@gmail.com wrote: On Wed, Mar 7, 2012 at 10:25 PM, Sriram Ramkrishna s...@ramkrishna.me wrote: On Wed, Mar 7, 2012 at 1:08 PM, Andre Klapper ak...@gmx.net wrote: I was thinking of switching from Docbook to Mallard for 3.6 (I didn't have time to prepare this for 3.4 already). The advantages of GNOME 3 page style are unclear to me currently, Advantages of moving over to using Wordpress for the release notes (that I can think of): My main objection would be translation. One of the problems is that I would like to see our content/news/release notes translated so that we can have greater coverage. I feel that english makes us somewhat limited. At least, let's agree that if we do it on wordpress that we have it in English and Spanish. IMHO translation is essential for introductions, presentations, overviews, news, release notes and such. These are the documents that can reach people who do not know/use GNOME. There should not be language barriers for potential new adopters. I like all the WP benefits listed, though it would be a severe regression to leave translation behind. So, what does supporting translation implies? Is it about 1. getting the right plugin https://www.google.com/search?q=wordpress+multilingual 2. interfacing with DL workflow (po files, git) Or? sri 1. The notes will be on gnome.org rather than under library.gnome.org/misc (why are the notes for our new release in a 'library'? why are they 'miscellaneous'?) 2. Avoid the bookishness of the format (sub-headings everywhere, boxes of links interrupting the flow of the document), which is rather stilted. 3. Allow embedding of richer media, such as lightboxes, image galleries and videos. 4. Allow flexible design, facilitating a more stylish and attractive layout. 5. Allow division of the notes into separate pages, rather than being a single *huge* page. however I would first have to know what markup language this move would imply, Wordpress reduces the need for markup. The only markup you need is html for formatting and embedding media, plus for bits of fancier page layout. plus if anybody would be actually willing to prepare this move. Actually writing the notes and doing the markup would be less work than with Docbook or Mallard, so in that respect we'd save time and effort. However, we would need a bit of extra help on the web development side if we wanted to make the notes look really nice. I'm interested in this as well. As Shaun noted about translations I would like to see this translated in as many languages as possible. We'll need to start on this soon. Most of the pieces are in place to make gnome.org translatable using the standard GNOME infrastructure. We just need to hook it up to damn lies [1]. I've spoken to Vinicius and he's confident that we can have it ready in time to get the release notes translated. Allan [1] https://bugzilla.gnome.org/show_bug.cgi?id=671647 -- IRC: aday on irc.gnome.org Blog: http://afaikblog.wordpress.com/ -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Are there some community/marketing indicators defined?
2011/9/22 J. Félix Ontañón fonta...@emergya.es El 21 de septiembre de 2011 12:23, Luc Pionchon pionchon@gmail.comescribió: 2011/9/9 J. Félix Ontañón fonta...@emergya.es El día 8 de septiembre de 2011 12:24, Luc Pionchon pionchon@gmail.com escribió: Hello Félix, 2011/9/8 J. Félix Ontañón fonta...@emergya.es El día 8 de septiembre de 2011 10:22, Allan Day allanp...@gmail.com escribió: Hi Félix, 2011/9/8 J. Félix Ontañón fonta...@emergya.es: Hi Marketing Team! I've been diving into live.gnome.org (up again! it's a good thing!) looking for some indicators, kpi, metrics or something related the way you measure the success of the activities the marketing team does and how they help to achieve the objectives. That's because many communities have an activity roadmap based on objectives and i'm just figuring out the best practices measuring the success, for my own use. The point is that neither the Ubuntu Community nor the Open Knowledge Foundation, same for Gnome, seems to have it. It would be certainly interesting to have methods to measure success, and to clarify what success means for the community. Of course, I think this is a starting point for a marketing plan: to define goals clearly so the achievement of them would lead to success. What i've found related with gnome-marketing goals are spread between the key activities[1] and the target markets[2], being the key activities something like goals and the target markets as the place to apply the activities, result of the segmentation study[3], in the quest for the success, [1] https://live.gnome.org/GnomeMarketing/#Key_activities [2] https://live.gnome.org/GnomeMarketing/TargetMarkets you forgot your [3] reference ;) Sorry[3] ... It's also a draft from 2008 [3] https://live.gnome.org/GnomeMarketing/MarketSegmentation it seems that most of GNOME marketing needs more love. Maybe going through the material and clarify what is up-to-date or obsolete would be a good starting point? Note: when browsing through live.gnome.org, you have to keep in mind that some of its content may be several year old and forgotten by most people. Check the page info. It's important also to get in touch with people currently involved. And updating the pages accordingly would be fantastic. Got it. Could you point us at a few communities that you feel most relevant? The point is that I started with some big and consolidated communities as GNOME, Ubuntu and OKFN and I found nothing. It might be worth to keep investigating around. Just out of my mind you may want to check out mozilla (and maybe wikipedia). Also the projects backed up by companies, like ubuntu/canonical for example, though I do not know how they would be open with their marketing methods. Would you be motivated to help developing such methods for GNOME? Wow! it would be amazing. I'm not a real expert in market research but i've some ideas about it and about digital strategy. Do you really think it worths the effort? There are only a few GNOME people who are real experts in what they do for the project (at least when they got started). The others use willingness and collaboration.This is the strength of the GNOME community. I don't doubt it, i'm on the willingness side :) Just go ahead! You must find your way and when you end up with valuable marketing techniques, you will certainly draw a lot of interest and support from the community. I'm willing to put some letters together as soon as posible. Is a good practice to start a wiki page on live.gnome.org? I've access there: https://live.gnome.org/FelixOntanon I think live.gnome.org is a good place to get started I'll be watching with interest Go ahead! -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: New look for live.gnome.org
On Sun, Sep 11, 2011 at 20:31, Andreas Nilsson nisses.m...@home.se wrote: Hi! Just a heads up that I'm making some touchups of live.gnome.org to match the rest of the website. http://www.andreasn.se/**diverse/temp/mockup-wiki.pnghttp://www.andreasn.se/diverse/temp/mockup-wiki.png http://www.andreasn.se/**diverse/temp/mockup-wiki.svghttp://www.andreasn.se/diverse/temp/mockup-wiki.svg Great! \o/ I wonder if there should be a clear visual difference still, so the pages are not mistaken with official pages. Because for example some pages may be outdated, or have prospective content, etc. Some visual to show that it's live content. Maybe a ruler looking like teared paper? or? What do you think? Luc - Andreas -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/**listinfo/marketing-listhttp://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Are there some community/marketing indicators defined?
Hello Félix, 2011/9/8 J. Félix Ontañón fonta...@emergya.es El día 8 de septiembre de 2011 10:22, Allan Day allanp...@gmail.com escribió: Hi Félix, 2011/9/8 J. Félix Ontañón fonta...@emergya.es: Hi Marketing Team! I've been diving into live.gnome.org (up again! it's a good thing!) looking for some indicators, kpi, metrics or something related the way you measure the success of the activities the marketing team does and how they help to achieve the objectives. That's because many communities have an activity roadmap based on objectives and i'm just figuring out the best practices measuring the success, for my own use. The point is that neither the Ubuntu Community nor the Open Knowledge Foundation, same for Gnome, seems to have it. It would be certainly interesting to have methods to measure success, and to clarify what success means for the community. Could you point us at a few communities that you feel most relevant? Would you be motivated to help developing such methods for GNOME? Also I feel it would be really great if you post again in this list to share your findings and when you have identified interesting and best practices! -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: bad press in the G+ circles/press
Hi, On Fri, Aug 5, 2011 at 11:40, Allan Day allanp...@gmail.com wrote: Sriram Ramkrishna s...@ramkrishna.me wrote: We've been getting a slew of psots on G+ and in the press. Started by Linus, has now caused a stampede of well known Linux kernel developers feeling the need to reject Gnome 3 in public. Since the press now senses red meat, I wonder if we might be ready with canned messages if at the Desktop Summit we are approached to comment on Linus and other's rants against Gnome 3? The main thing is to set out our positive story rather than to tackle the negativity head on. There's a standard line that goes something like: 1. GNOME 3 was a change, there were always going to be some people who didn't like it. 2. But it has been a huge success. Insert evidence: - We've been regularly contacted by people telling us how much they like it. - There have been good reviews in the press. - Fedora received a massive boost in popularity due to including it. - We've subsequently seen other major OSs following the same design trajectories - FOSS leading rather than following for once. 3. But we know there's more to do. 3.0 was the first step; it will get better and better with subsequent releases. The most damaging thing that's been said so far - which we need to counter where possible - is the suggestion that no one likes GNOME 3. That's a really nasty meme. A straight statement along the lines of 'X is entitled to his/her opinion, but it goes against the reality that GNOME 3.0 was hugely successful for that kind of release' is needed. I don't really like these canned answers. So one says G3 is an unholy mess the other one says G3 is hugely successful. It sounds to me like keep talking, I don't listen. It's like a discussion between two death persons. It is perfectly fair to say G3 is bad without any argument, it's freedom of speech. The answers of GNOME people I could read were not fair. (We could wonder why GNOME people are so sensitive on the subject.) What about? - be open - listen to the feedback, - don't give canned answers - engage in constructive discussion, - avoid derision - show interest in feedback - get to the facts; - go to the source, tackle rumors; what is it founded on? - if needed, go through a few levels of why to reach the point - use numbers - avoid vague quantities so many, a lot, several, etc. - encourage people to report more formal feedback (mailing list, buzilla, wiki) - really, listen to the feedback I did not see much of this in the unholy threads mentioned above, sadly. -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: bad press in the G+ circles/press
On Fri, Aug 5, 2011 at 12:59, Allan Day allanp...@gmail.com wrote: Luc Pionchon pionchon@gmail.com wrote: What about? - be open - listen to the feedback, - don't give canned answers - engage in constructive discussion, - avoid derision - show interest in feedback - get to the facts; - go to the source, tackle rumors; what is it founded on? - if needed, go through a few levels of why to reach the point - use numbers - avoid vague quantities so many, a lot, several, etc. - encourage people to report more formal feedback (mailing list, buzilla, wiki) - really, listen to the feedback That's a really good list! (It would be awesome if you or anybody else wanted to do a wiki page on dealing with feedback... ;) ) This is easy to do. Where would you put it? One thing I would say though - some of those things (constructive discussion, get to the facts, go to the source) don't work so well on public discussions in my experience. They're great things to do, but they only tend to work when you're have a discussion with a small group or even on a one to one basis. I don't quite get it (sorry). Do you mean that discussion between many passionate partisans tend to be messy? What I mean is that, if you enter the discussion, do it in a constructive way. It's about tackling empty, fallacious, or too vague statements ; and get to the point. It's about pro-actively extracting valuable feedback. Unhappy users clearly have something to say. But they do not have to wear white gloves and serve it to you on a plate. It is their freedom to just vomit it. On the other hand the authors of a project should be open to feedback, it's then up to them to go and extract the feedback. -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
