[tc] Assuming control of GitHub organizations
jim at jimrollenhagen.com
Tue Jul 9 14:36:15 UTC 2019
On Thu, Jun 27, 2019 at 8:55 AM Thierry Carrez <thierry at openstack.org>
> Graham Hayes wrote:
> > On 27/06/2019 09:55, Thierry Carrez wrote:
> >> I have been considering our GitHub presence as a downstream "code
> >> marketing" property, a sort of front-end or entry point into the
> >> OpenStack universe for outsiders. As such, I'd consider it much closer
> >> to openstack.org/software than to opendev.org/openstack.
> >> So one way to do this would be to ask Foundation staff to maintain this
> >> code marketing property, taking care of aligning message with the
> >> content at openstack.org/software (which is driven from the
> >> osf/openstack-map repository).
> >> If we handle it at TC-level my fear is that we would duplicate work
> >> around things like project descriptions and what is pinned, and end up
> >> with slightly different messages.
> > I am not as concerned about this, the TC should be setting out our
> > viewpoint for the project, and if this is in conflict with the message
> > from the foundation, we have plenty of avenues to raise it.
> How about the TC controls which repo is replicated where (and which ones
> are pinned etc), but we import the descriptions from the openstack-map
> That would keep control on the TC side but avoid duplication of effort.
> In my experience it's already difficult to get projects to update
> descriptions in one place, so two...
This seems reasonable to me.
> Also, who is volunteering for setting up the replication, and then
> keeping track of things as they evolve ?
I'm up for it, can we get a couple more? I'd like to get this going soon.
> Thierry Carrez (ttx)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss