Remove reference to bi-weekly newsletter
The bi-weekly SIGs update idea was encoded in governance yet never got put into use in the year since it was devised. Remove the reference for now so as to avoid confusion. It can always be added back if these start happening at some point in the future. Change-Id: I391e80bb7d87049f4d4fdbb6680e81eae6bee013
This commit is contained in:
parent
4720d63f46
commit
5b1a589464
|
@ -52,22 +52,6 @@ channel. Refer to https://github.com/ekmartin/slack-irc for a
|
|||
Slack+IRC connector; a docker image is also available at
|
||||
https://github.com/mrhillsman/dockerize-slack-irc.
|
||||
|
||||
Bi-weekly Newsletter/Summary
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
We are suggesting to follow a great `tradition
|
||||
<https://www.openstack.org/blog/?p=490>`_ started for the `openstack-dev
|
||||
mailing list
|
||||
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>`_, by
|
||||
sending out a newsletter summarising SIG activity on a bi-weekly
|
||||
basis. In order to reduce the work on individuals writing and/or reading
|
||||
summaries for SIGs, we have `an etherpad
|
||||
<https://etherpad.openstack.org/p/openstack-sigs-weekly>`_ which will be
|
||||
compiled bi-weekly and sent to the `openstack-sigs mailing list
|
||||
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs>`_
|
||||
and other relevant places. We ask that SIG leaders provide updates as
|
||||
they see fit to the etherpad; this is not a requirement.
|
||||
|
||||
Process to create a SIG
|
||||
=======================
|
||||
|
||||
|
|
Loading…
Reference in New Issue