Hi Jim, Documentation & L10N communities already endorse the Content Project and we'd like to see it continue forward (obviously). I thought that was clear from the short thread about unhiding the project? Why are you so keen to close this project? It is valid, sponsored, and has active contributors who are also active in the sponsoring communities. We have a few irons in the fire WRT to the VMware article update from Bill and Nacho continues his work to update translated version. I'd rather not see this go into the Advocacy area, when it already has appropriate sponsorship through docs. You are free to drop off as a leader if that suits you. I copy docs alias on this to see if others want to comment either way.
Thanks, Michelle Jim Grisanzio wrote: > Jim Grisanzio wrote: > >> Hi .... a little update: I migrated the Newsletter content from the >> Content Project over to the new Advocacy Community Group. All new >> newsletter content will be posted to the Advocacy CG. I'll ask Derek >> to put the url re-directs in for that newsletter content when he has a >> chance, and we'll delete the Content Project when we open the Advocacy >> CG. Probably in a couple of weeks. >> >> Jim > > > > Someone suggested to me another option for the Content Project. > > Instead of closing it, it's been suggested that perhaps the Content > Project can be re-vitalized and re-orged to be a project within the > Advocacy Community Group. Or more accurately, the Advocacy CG would > sponsor the effort and become associated with. I'm willing to give this > a shot, and I can't imagine anyone in the Advocacy CG would have a > problem with it. However, it would have to be proposed and approved > (casually, of course), and I can't do it alone. I'm happy to contribute > to the effort, but I need help. > > Offers? Thoughts? Good idea? Bad? > > Jim
