[Members] Resurrecting the comms team

JC Brand jc at opkode.com
Thu Feb 22 13:08:23 UTC 2018


On Thu, Feb 22, 2018 at 10:59:42AM +0000, Kevin Smith wrote:
> On 21 Feb 2018, at 12:58, jc at opkode.com wrote:
> > I'm personally not interested in maintaining a newsletter on xmpp.org and making the implied time investment to learn the Pelican stack just so that I have to make a pull request every time an installment gets sent out. 
> 
> Is this related to a formal comms team or github access?

Both.

The way I see it, membership of a formal comms team provides a basis on which to provide (and revoke) access to the xmpp.org repo.

> I imagine that anything going up on xmpp.org’s going to end up needing to go through the github repo regardless of whether you can self-approve the PR?

Yes, I'm not disputing that.

I'm saying that if the process of writing to that repo is cumbersome (i.e. requiring a PR every time), then I'd rather create a separate repo and domain (i.e. not use xmpp.org for hosting the newsletter at all).

FWIW, I agree with Guus. Not formally acknowledging the comms team and not giving them access to the xmpp.org repo is adding unnecessary resistance to getting things done. It sends the wrong message IMO.


More information about the Members mailing list