I would say that we need to do a survey of users of foresight not just developers. From helping people that have first used linux only because they have bought KPCs with Foresight on them I wouldn't say that we are NOT ready (linux in general) for windows users just thrown linux. My reason for this are the following:
- Linux is very different from the windows workflow - Installing Applications is different - We have a terminal - Gaming - Codecs - 'Freedom' However, we are a good distro for people actively looking to switch from Windows to Linux and now the costs/differences. I would say our current target user base should be people looking for an alternative to Windows but not the same thing as Windows. Our Strenghts: - User Guide - Community - Conary - Default Applications Our Weaknesses: - Lack of packages - PackageKit - Lack of Medium to Advance Level Documentation - Repo Browsing - Conary (Yes it is a strenght and a weakness, mainly its unfamiliarity) - Lack of QA Process (Its better but still not perfect) - Different/New Workflow from Windows We are working on fixing some of these and a lot of these weakness can be fixed or have their impact lessened for new users. For example, conary and the work flow differences could easily be documented and added to the user guide or in a seperate guide. If you need more explanination on some of my listings just let me know and I will go into more detail. Kevin On Mon, Jul 28, 2008 at 11:44 AM, Paul Cutler <[EMAIL PROTECTED]> wrote: > We have an opportunity to get some help with Foresight's branding and > artwork. > > As part of that help, we need to define Foresight's target audience. > Going through this process will help develop an overall brand, > including look and feel. > > I have started a wiki page for this discussion at > https://wiki.foresightlinux.org//x/XIBU (Note, I will be heavily > moderating this discussion). > > To set an expectation, Foresight's target audience is focused on new > Linux users migrating from Windows. > > What needs to be done is to further define this, and even define who > we don't want to be. This also includes a discussion of what we like > about Foresight, and what we don't, or needs to be improved to get us > to our goal. > > Please add your thoughts to the wiki page. If the page does get > off-topic, I will start a parking lot section, and move ideas there as > well if they don't pertain to the discussion. > > Please share your thoughts, everyone is welcome! Especially for those > of us who use and develop Foresight every day, I want to make sure we > have a wide range of ideas, to avoid the forest for the trees > syndrome. > > If you have any questions, please let me know. > > Paul > > Paul Cutler > Community Manager, Foresight > [EMAIL PROTECTED] > _______________________________________________ > Foresight-devel mailing list > Foresight-devel@lists.rpath.org > http://lists.rpath.org/mailman/listinfo/foresight-devel > -- specialKevin Kevin Harriss http://www.foresightlinux.org _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
