From: Xue Fuqiao <xfq.free@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Nicolas Petton <nicolas@petton.fr>,
Artur Malabarba <bruce.connor.am@gmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Emacs logo proposal
Date: Mon, 26 Oct 2015 07:58:59 +0800 [thread overview]
Message-ID: <CAAF+z6F7zo2N7mz7E=p=2Okpn-RKBTvMFpfhPN=v9LNwpD97hw@mail.gmail.com> (raw)
In-Reply-To: <jwvpp024tlb.fsf-monnier+emacs@gnu.org>
Hi Stefan,
On Mon, Oct 26, 2015 at 3:56 AM, Stefan Monnier
<monnier@iro.umontreal.ca> 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.
next prev parent reply other threads:[~2015-10-25 23:58 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 19:26 Emacs logo proposal Nicolas Petton
2015-10-20 19:45 ` Jay Belanger
2015-10-20 19:58 ` Artur Malabarba
2015-10-21 8:04 ` Nicolas Petton
2015-10-20 20:05 ` Chris Van Dusen
2015-10-20 20:15 ` Kaushal Modi
2015-10-20 20:45 ` David Kastrup
2015-10-20 20:13 ` Dmitry Gutov
2015-10-21 8:06 ` Nicolas Petton
2015-10-23 15:35 ` Dmitry Gutov
2015-10-23 15:59 ` Nicolas Petton
2015-10-23 16:06 ` Dmitry Gutov
2015-10-23 16:14 ` Nicolas Petton
2015-10-23 16:55 ` Dmitry Gutov
2015-11-14 18:28 ` Mark Oteiza
2015-11-15 15:42 ` Dmitry Gutov
2015-11-17 0:13 ` John Wiegley
2015-10-20 20:44 ` Drew Adams
2015-10-21 8:09 ` Nicolas Petton
2015-10-20 21:30 ` Rasmus
2015-10-22 9:29 ` Aurélien Aptel
2015-10-22 9:40 ` Dani Moncayo
2015-10-22 9:49 ` Nicolas Petton
2015-10-23 6:31 ` Richard Stallman
2015-10-23 7:58 ` Nicolas Petton
2015-10-23 8:52 ` David Kastrup
2015-10-22 11:45 ` John Yates
2015-10-22 12:44 ` Juanma Barranquero
2015-10-22 12:30 ` Aurélien Aptel
2015-10-22 13:08 ` Nicolas Petton
2015-10-22 13:12 ` Kaushal Modi
2015-10-22 13:18 ` Daniel Pimentel
2015-10-22 13:24 ` David Kastrup
2015-10-22 13:27 ` Daniel Pimentel
2015-10-22 13:41 ` Daniel Pimentel
2015-10-22 17:52 ` David Caldwell
2015-10-22 14:53 ` Xue Fuqiao
2015-10-22 15:28 ` Nicolas Petton
2015-10-23 0:33 ` Xue Fuqiao
2015-10-23 8:02 ` Nicolas Petton
2015-10-23 9:10 ` Artur Malabarba
2015-10-23 11:23 ` Xue Fuqiao
2015-10-23 11:37 ` Nicolas Petton
2015-10-25 3:44 ` Stefan Monnier
2015-10-25 17:56 ` Nicolas Petton
2015-10-25 19:56 ` Stefan Monnier
2015-10-25 23:58 ` Xue Fuqiao [this message]
2015-10-26 8:00 ` Nicolas Petton
2015-10-22 17:50 ` (ELPA website design) " Nicolas Petton
2015-10-22 18:20 ` John Yates
2015-10-22 18:39 ` Kelvin White
2015-10-22 19:13 ` Drew Adams
2015-10-23 8:06 ` Nicolas Petton
2015-10-22 21:24 ` Rasmus
2015-10-23 8:07 ` Nicolas Petton
2015-10-23 1:05 ` Xue Fuqiao
2015-10-23 2:45 ` Yuri Khan
2015-10-23 3:31 ` Matthew Carter
2015-10-23 8:08 ` Nicolas Petton
2015-10-23 17:05 ` Nicolas Petton
2015-10-23 17:20 ` Eli Zaretskii
2015-10-24 1:32 ` Xue Fuqiao
2015-10-24 8:07 ` Nicolas Petton
2015-10-23 17:43 ` Aurélien Aptel
2015-10-23 18:13 ` Kelvin White
2015-10-23 18:37 ` Stephen Berman
2015-10-23 19:50 ` Nicolas Petton
2015-10-26 8:57 ` Nicolas Petton
2015-10-26 23:49 ` Xue Fuqiao
2015-10-27 3:39 ` Yuri Khan
2015-10-28 13:27 ` Xue Fuqiao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAF+z6F7zo2N7mz7E=p=2Okpn-RKBTvMFpfhPN=v9LNwpD97hw@mail.gmail.com' \
--to=xfq.free@gmail.com \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nicolas@petton.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).