#3321: geoserver-builds@osgeo.org private mailing list
----------------------+---------------------------
Reporter: jive | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin | Keywords:
----------------------+---------------------------
We noticed that random build updates have a single bus factor and would
like to setup a private mailing list, or alias list, for this
communication?
We have something similar setup for geoserver-secruity for example.
- torbenbarsballe@gmail.com
- andrea.aime@geosolutionsgroup.com
- jody.garnett@gmail.com
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3321>
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3321: geoserver-builds@osgeo.org private mailing list
----------------------+----------------------------
Reporter: jive | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin | Resolution:
Keywords: |
----------------------+----------------------------
Comment (by robe):
@jive Would a private discourse list suffice?
So would be something like geoserver-build@discourse.osgeo.org
the list would be by invitation only and would have only you three.
Since you are an admin of discourse you can do this yourself.
Just set the custom address to the above.
If you want allow anonymous people to post to it, then just check the
"anonymous"
--
Ticket URL: <#3321 (geoserver-builds@osgeo.org private mailing list) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3321: geoserver-builds@osgeo.org private mailing list
----------------------+----------------------------
Reporter: jive | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin | Resolution:
Keywords: |
----------------------+----------------------------
Comment (by jive):
I did not consider it, but yes that should work.
Is that a good use of the forum? Like it is being used with build-bots to
send notifications - so I expect to fill up over time. Read only in
emergencies for troubleshooting etc...
--
Ticket URL: <#3321 (geoserver-builds@osgeo.org private mailing list) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3321: geoserver-builds@osgeo.org private mailing list
----------------------+------------------------
Reporter: jive | Owner: jive
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin | Resolution:
Keywords: |
----------------------+------------------------
Changes (by jive):
* owner: sac-tickets@… => jive
--
Ticket URL: <#3321 (geoserver-builds@osgeo.org private mailing list) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3321: geoserver-builds@osgeo.org private mailing list
----------------------+------------------------
Reporter: jive | Owner: jive
Type: task | Status: closed
Priority: normal | Milestone: Unplanned
Component: SysAdmin | Resolution: fixed
Keywords: |
----------------------+------------------------
Changes (by jive):
* resolution: => fixed
* status: new => closed
--
Ticket URL: <#3321 (geoserver-builds@osgeo.org private mailing list) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3321: geoserver-builds@osgeo.org private mailing list
----------------------+----------------------------
Reporter: jive | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin | Resolution:
Keywords: |
----------------------+----------------------------
Comment (by jive):
Looks like you can create a group with an incoming email address:
https://meta.discourse.org/t/custom-incoming-email-address-for-
groups/37897
--
Ticket URL: <#3321 (geoserver-builds@osgeo.org private mailing list) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.