From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pjotr Prins Subject: Re: website: say what Guix is at the very top Date: Fri, 16 Mar 2018 08:14:47 +0100 Message-ID: <20180316071447.GA28748@thebird.nl> References: <87inc0gzoz.fsf@elephly.net> <87efmixtl7.fsf@gmail.com> <867es94zfj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39472) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ewjdu-0006UP-1Q for guix-devel@gnu.org; Fri, 16 Mar 2018 03:19:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ewjdq-00071U-3E for guix-devel@gnu.org; Fri, 16 Mar 2018 03:19:10 -0400 Received: from mail.thebird.nl ([95.154.246.10]:50547) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ewjdp-0006yl-SB for guix-devel@gnu.org; Fri, 16 Mar 2018 03:19:06 -0400 Content-Disposition: inline In-Reply-To: <867es94zfj.fsf@gmail.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: myglc2@gmail.com Cc: guix-devel@gnu.org On Mon, Jan 22, 2018 at 11:43:12AM -0500, myglc2@gmail.com wrote: > Agreed. The first step: STOP calling Guix a "package manager". Why? > Users aren't shopping for a package manager. They either already have > one, or expect one to come with the software they are looking for. They > will think, "I don't need one." > > So calling Guix a "package manager" sets up a marketing problem like > selling transmissions to car drivers :-( > > How can we avoid this? Call it something else! What? > > Ricardo called Guix a "software environment manager". This is a better > term and we can apply it to both Guix and GuixSD ;-) I am dealing with things like https://github.com/openjournals/joss-reviews/issues/583#issuecomment-373621538 As the scope of the packages is much larger (in terms of # deployments) than GuixSD I think we should take a really hard look at how we present Guix to newcomers. That is what the front page should address. Maybe we should make a strong shift towards running Guix in containers. Or create a website that treats that topic individually. See it as a marketing gimmick. Container use is growing rapidly and allows for leaving bare metal. There are even routers running containers today! Containers are also building blocks for pipelines, that is going to be huge. See, for example the PDF at https://grants.nih.gov/grants/rfi/NIH-Strategic-Plan-for-Data-Science.pdf Guix is a step up from everything else when it comes to containers. And now we can even run GuixSD in a container ;) Pj.