[SAC] uncommitted osgeo6 (mail) changes

On osgeo6 machine the whole of /etc is under a git repository.
Right now there are uncommitted changes, could responsible of
the change please commit their own changes ?

Uncommitted changes summary is:

  - planet alias
  - mapserver alias
  - grass redirects (apache)
  - mailman config change (done by jef, according to comment)

--strk;

On Tue, Mar 6, 2018 at 10:22 AM, Sandro Santilli <strk@kbt.io> wrote:
...

Uncommitted changes summary is:

...

  - grass redirects (apache)

Done.

Markus

Sandro Santilli wrote:

On osgeo6 machine the whole of /etc is under a git repository.

Folks, if I'm not mistaken, this is a quick overview of GIT'ted /etc/
directories on OSGeo machines:

backup:
    /etc/bacula/

download:
    /etc/apache2/

osgeo6:
    /etc/
    /etc/drone/
    /etc/apache2/

secure:
    /etc/init.d/

tracsvn:
    /etc/trac/
    /etc/apache2/
    /etc/fail2ban/

web:
    /etc/fail2ban/
    /etc/apache2/

webextra:
    /etc/letsencrypt/
    /etc/apache2/

wiki:
    /etc/php5/

This smells a little bit like "hey I'm cool, I've invented yet another
GIT'ted config directory."

From my perspective it would be strongly indicated at least to define, maybe

even establish a standard on how to git /etc/ directories *before* everybody
tries to enforce their own. The current state looks a little bit bizarre.

Cheers,
  Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------

On Tue, Mar 06, 2018 at 10:58:09AM +0000, Martin Spott wrote:

From my perspective it would be strongly indicated at least to define, maybe
even establish a standard on how to git /etc/ directories *before* everybody
tries to enforce their own. The current state looks a little bit bizarre.

Trying to estabilish rules in SAC didn't prove effective in
the past, so I took the liberty to adopt the do-ocracy tipical
of free software development. It's a mess ? Yes, a bit of a mess.
Is it useful ? I think it is.

Now, I'm happy to follow other rules if you are able to document
them. The current non-centrally-documented rule is: try "git status"
whenever you change something. The login message was added by Jurgen
(thanks!) and was the start of some documentation.

--strk;