Hi I sent this message to Evolution list but no body cared about it, I really want to help in Gnome so I think this is the way to sell (I mean marketing for Gnome)
Just think about it , what we will lose if we just create on going survey after every release (and include it with Gnome packages) to ask the users few questions about how do they use gnome (Enterprise, home, school, ...etc) and what they think about the current release and how to improve it) after that you will get a very good statistic about where gnome are and where gnome going also you will know what you will need to improve to get more and more customers This is the way that every big company works to sell there products ---------- Forwarded message ---------- From: regatta <[EMAIL PROTECTED]> Date: Sep 25, 2005 8:26 PM Subject: Re: [Evolution] How do you vote for a bug ? To: Shreyas Sriniavasan <[EMAIL PROTECTED]> Cc: Andre Klapper <[EMAIL PROTECTED]>, [email protected] Another thing guys, Who decide what to be in the next release (http://go-evolution.org/Evo2.6) ? Are the customers involved in making this plan or it's only by the developers ? What I mean is that evolution is made for the customers so you should make the customers decide what they need to be improved and not what the developer think it's better for example if you ask me (as a customer) if I'm interested in Evo 2.6, I will tell you NO, and probably I will not install it (Ok, maybe if I have a free time :) ) , because nothing there make me interest to download it , for EXAMPLE , I don't care about Hula I don't mean Hula is bad or anything , what I mean not many people will be interest on this new future because not many people are using it, this is just EXAMPLE and I mean not many people because most of the people are using other system like exchange in Enterprise environment (specially if you plan to import evolution to windows) and pop/imap in Home user environment I really liked what Ben Goodger said in his blog about KDE and apple ( http://www.zdnet.com.au/news/software/0,2000061733,39191656,00.htm ) In summary : *- I know I'm very new in here , but listen to me as a customer how really love your work :) *- You need to think about what your customers want , not about what the developers think the customers want or how the developer need to make the source code more perfect. *- Think about making a live survey to make the user decide what they need to improve in the next release (make the survey included with evolution when they run it in the first time of maybe after they run it more than 30 time). Note: this can apply to Evolution and Gnome also On 9/25/05, Shreyas Sriniavasan <[EMAIL PROTECTED]> wrote: > On Sun, 2005-09-25 at 15:05 +0200, Andre Klapper wrote: > [snip] > > in gnome's bugzilla you cannot, so send gifts to the developers or spend > > them a beer on the next gnome conference. ;-) > > heh, could work :-) but on a slightly serious note i think we need a > venue for discussion. I do agree with regatta that a lot of old bugs may > need re-thinking. We need to take a stance on them and decide on their > priority, if a few of them are beaten old bugs that we dont see the need > to fix then we should atleast close them. Keeping them open just looks > really bad. > > What do you guys think of having a "Hack Fest" where we close/ fix/ kill > al/ most bugs which are pre-2.0. I am just thinking out aloud, if a lot > of people > are convinced then we can do something like that. > > For interaction we can have people posting bugs they feel passionate > about > on the list and have a healthy discussion about the need to push a fix > for > the same. Although i dont know if its in the scope of the mailing list. > > Cheers, > Shreyas > > _______________________________________________ > Evolution-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/evolution-list > -- Best Regards, -------------------- -*- If Linux doesn't have the solution, you have the wrong problem -*- -- marketing-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/marketing-list
