From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Xue Fuqiao Newsgroups: gmane.emacs.devel Subject: Re: Emacs logo proposal Date: Mon, 26 Oct 2015 07:58:59 +0800 Message-ID: References: <876121mjdw.fsf@petton.fr> <8737x2ncqw.fsf@petton.fr> <87io5yko5t.fsf@petton.fr> <87r3ki7ryf.fsf@petton.fr> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1445817557 31244 80.91.229.3 (25 Oct 2015 23:59:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 25 Oct 2015 23:59:17 +0000 (UTC) Cc: Nicolas Petton , Artur Malabarba , emacs-devel To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 26 00:59:09 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZqVBp-0007ia-5I for ged-emacs-devel@m.gmane.org; Mon, 26 Oct 2015 00:59:05 +0100 Original-Received: from localhost ([::1]:49914 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZqVBo-0000u2-Fk for ged-emacs-devel@m.gmane.org; Sun, 25 Oct 2015 19:59:04 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49083) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZqVBl-0000tm-7n for emacs-devel@gnu.org; Sun, 25 Oct 2015 19:59:02 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZqVBk-0002rN-75 for emacs-devel@gnu.org; Sun, 25 Oct 2015 19:59:01 -0400 Original-Received: from mail-ig0-x235.google.com ([2607:f8b0:4001:c05::235]:35458) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZqVBk-0002rH-2g for emacs-devel@gnu.org; Sun, 25 Oct 2015 19:59:00 -0400 Original-Received: by igbkq10 with SMTP id kq10so47934721igb.0 for ; Sun, 25 Oct 2015 16:58:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jq165/ZjwlvDUT0POW5x1bgB9529nImTb9gZP8DbIy4=; b=jwTmu8yN12WuEHN0LH38xi8Obpqb0tnObxINqki7HFuAUhM7oKl3i2Z0chiRfmp0rV a2z/IK5iQvEV9RsgG4PXQBafWTAVfww1bHJWOzPNqt7kJcDSgtID4Q5WPXOYy392H39r KOEgzWt2+dSbzZ8/EXhVmclFSFprnOKkf+1GxplXvjpbl6bTo9Ae6E4l/ycLC7YweF8D wnRJFNr3xXICf6hiOmJ8byOocBBIPlUoEIfkS0gSc+DAqmPp6C8igaqrqKl5/+mGb5Vb gi32d3A4xh+gaAX7QllZzw1yL3/3h2YklyoIQNIFTrUdhQAnE0wGWIasNPg+DqV+RUCa 9b8A== X-Received: by 10.50.50.179 with SMTP id d19mr16452363igo.91.1445817539461; Sun, 25 Oct 2015 16:58:59 -0700 (PDT) Original-Received: by 10.79.94.2 with HTTP; Sun, 25 Oct 2015 16:58:59 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4001:c05::235 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:192630 Archived-At: Hi Stefan, On Mon, Oct 26, 2015 at 3:56 AM, Stefan Monnier wrote: > You have to request access to it at sysadmin@gnu.org, IIRC. > And currently it's setup in a very naive way, where you basically need > root access (via sudo) to do anything, so I don't like to give access > to people too easily. > > OTOH an "official admin" would be *very* welcome. What are responsibilities and qualifications of the official admin? > Also it'd be good to setup a cron job that does something like copying > the web-site files from elpa.git/html to /var/www. Yet at the same time, > we have to be careful since lots and lots of people have write access to > elpa.git, and we don't want this to give them indirectly access to > elpa.gnu.org. Agreed. That's why I suggested that we set up a set up a "staging/development site". The changes to elpa.git/html will only be deployed to the staging/development site regularly, and if we decided to release a new version of elpa.gnu.org website, then the official admin deploys it to /var/www. Just like a master branch and a release branch. I don't know how to set up a staging site under gnu.org, but (if you agree) I can help set up one on GitHub or on my own server.