fix 'non-wellform' hashtag and remove trailing spaces

fix hashtag program not to generate TAG-.md

Change-Id: I739505b2da699214a03516161394ac5702a8fa11

forum/201705-bos/TAG-action-item.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-log-messages: 128:     If the error message is not useful - then we need a bug on the error message  ##action-item ##LCOO
+https://etherpad.openstack.org/p/BOS-forum-log-messages: 128: If the error message is not useful - then we need a bug on the error message  ##action-item ##LCOO
 

forum/201705-bos/TAG-action.md

@@ -1,28 +1,28 @@
-https://etherpad.openstack.org/p/BOS-API-WG-BOF: 38: 			* ##ACTION ITEM: asettle to add some API contrib stuff to contributor-guide w/ Anne Gentle
+https://etherpad.openstack.org/p/BOS-API-WG-BOF: 38: * ##ACTION ITEM: asettle to add some API contrib stuff to contributor-guide w/ Anne Gentle
 
-https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds: 25: 		* Identify maturity of projects for public clouds - ##action  collect into a spread sheet
+https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds: 25: * Identify maturity of projects for public clouds - ##action  collect into a spread sheet
 
-https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds: 61: 		* Find better ways of raising awareness of new features / projects / bugs / whatever that are potentially applicable to other Public Cloud operators ##action
+https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds: 61: * Find better ways of raising awareness of new features / projects / bugs / whatever that are potentially applicable to other Public Cloud operators ##action
 
-https://etherpad.openstack.org/p/BOS-forum-large-deployment-team: 41: 			* ##action mdorman to follow up ML post to clarify LDT position on this
+https://etherpad.openstack.org/p/BOS-forum-large-deployment-team: 41: * ##action mdorman to follow up ML post to clarify LDT position on this
 
 https://etherpad.openstack.org/p/BOS-forum-log-messages: 132: ##Action Item    Need developer to revise middleware and all clients to pass a single user selected reqID through the entire project chain so all messages for a user initiated requirest will have that reqID (global)
 
 https://etherpad.openstack.org/p/BOS-forum-log-messages: 134: ##Action Item:  Youtube on how to navigate Launchpad to specific project and file bug against project for operators
 
-https://etherpad.openstack.org/p/BOS-forum-ops-catch-up: 35: 	Edgar Magana will work with William Vera to build the local team and make the event possible! ##action
+https://etherpad.openstack.org/p/BOS-forum-ops-catch-up: 35: Edgar Magana will work with William Vera to build the local team and make the event possible! ##action
 
-https://etherpad.openstack.org/p/BOS-forum-ops-catch-up: 37: 	1.1 Digital Culture Center - August 9th/10th <-- SELECTED AS THE VENUE AND DATE!!!! ##action
+https://etherpad.openstack.org/p/BOS-forum-ops-catch-up: 37: 1.1 Digital Culture Center - August 9th/10th <-- SELECTED AS THE VENUE AND DATE!!!! ##action
 
-https://etherpad.openstack.org/p/BOS-forum-ops-catch-up: 76:       - check with Erin or Claire on which option is the most cost efficient ##action
+https://etherpad.openstack.org/p/BOS-forum-ops-catch-up: 76: - check with Erin or Claire on which option is the most cost efficient ##action
 
-https://etherpad.openstack.org/p/BOS-forum-ops-catch-up: 77:       - get with designer ##action
+https://etherpad.openstack.org/p/BOS-forum-ops-catch-up: 77: - get with designer ##action
 
-https://etherpad.openstack.org/p/BOS-forum-uc-governance-and-support-of-wgs: 50: 	* ##action ##uc get documents into gerrit
+https://etherpad.openstack.org/p/BOS-forum-uc-governance-and-support-of-wgs: 50: * ##action ##uc get documents into gerrit
 
-https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations: 137: 		* ##action: Document the status of drivers
+https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations: 137: * ##action: Document the status of drivers
 
-https://etherpad.openstack.org/p/pike-forum-cloud-applications: 10: 	* ##action everyone review Keystone policy roadmap specs
+https://etherpad.openstack.org/p/pike-forum-cloud-applications: 10: * ##action everyone review Keystone policy roadmap specs
 
-https://etherpad.openstack.org/p/pike-forum-cloud-applications: 20: 		* ##action mordred, zaneb to come up with preliminary description of this (not spec level of detail) to make sure the API key idea is leading in the right direction
+https://etherpad.openstack.org/p/pike-forum-cloud-applications: 20: * ##action mordred, zaneb to come up with preliminary description of this (not spec level of detail) to make sure the API key idea is leading in the right direction
 

forum/201705-bos/TAG-actionitem.md

@@ -1,74 +1,84 @@
-https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 95: 				* Recommended configurations to setup basic common security practices  ##actionitem ##compliance
+https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 95: * Recommended configurations to setup basic common security practices  ##actionitem ##compliance
 
 https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 142: Documented OpenStack security gaps  ##actionitem ##compliance
 
 https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 143: Guidelines for securing openstack  ##actionitem ##compliance
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 127: 	* set up and publish slack channel ##actionitem ##lcoo --> https://lcoo.slack.com >> publish this on wiki
+https://etherpad.openstack.org/p/BOS-forum-LCOOGetToKnow: 49: * Define governance model in LCOO and it is allined with UC ##actionitem#lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 128: 	* derive short term win ##actionitem ##lcoo
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 127: * set up and publish slack channel ##actionitem ##lcoo --> https://lcoo.slack.com >> publish this on wiki
 
-https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements: 76: 	* Collaborate with other WG and bring requirements together, identify commonalities, with further gap analysis ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 128: * derive short term win ##actionitem ##lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 44: 					* Looking for reference architecture on how to configure and design the underlying cloud to support to upper workload ##actionitem ##ewg
+https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements: 76: * Collaborate with other WG and bring requirements together, identify commonalities, with further gap analysis ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 45: 					* Link the workload reference architecture to architecture design guide ##actionitem ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 44: * Looking for reference architecture on how to configure and design the underlying cloud to support to upper workload ##actionitem ##ewg
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 46: 					* Continue to work/colloborate with Docs team on guidance ##actionitem ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 45: * Link the workload reference architecture to architecture design guide ##actionitem ##ewg
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 48: 			* Defining who we are??? ##ewg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 46: * Continue to work/colloborate with Docs team on guidance ##actionitem ##ewg
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 49: 				* define EWG scope  ##ewg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 48: * Defining who we are??? ##ewg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 48: 			* new to openstack - how do you get involved  ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 49: * define EWG scope  ##ewg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 51: 		* target (welcome) newer large operators ##LCOO ##pwg ##onboarding ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 48: * new to openstack - how do you get involved  ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 54: 		* encourage more sigs ##rbac  ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 51: * target (welcome) newer large operators ##LCOO ##pwg ##onboarding ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 58: 	* Post-forum Analysis +1+1  ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 54: * encourage more sigs ##rbac  ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 60: 		* template for response from moderators to send as summary   ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 58: * Post-forum Analysis +1+1  ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 61: 		* Mine hashtag data ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 60: * template for response from moderators to send as summary   ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 65: 	* Notify moderators to give feedback on Forum sessions ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 61: * Mine hashtag data ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 66: 	* How do we identify organization to help with this wg ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 65: * Notify moderators to give feedback on Forum sessions ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 192: 	1. Monthly IRC meeting of the WG chairs introducing the happenngs of the last period ##actionitem ##nfv
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 66: * How do we identify organization to help with this wg ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 201: 	1. Wiki or similar to keep track of the related WGs and their work scope   ##actionitem ##nfv
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 123: What could the communiity do to help in place n+2 upgrades?.##all-projects#actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 202: 	1. Regular face2face meeting on the Summits and PTG-s ##actionitem ##nfv
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 124: * Better release notes for all projects would help to identfiy what has changed.##all-projects#actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 64: 	* Set base expectations on the group openness & output  ##actionitem ##requirements
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 125: * Better description of what happens with mixed versions, i.e agents behind one or two versions.##all-projects#actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 65: 	* have discussions in shared place (general mailing list?)  ##actionitem ##uc
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 126: * TODO: call out projects that are doing upgrade impacts but not documenting them in the release notes.##all-projects#actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 77: 		* finding ways to steer member companies contributing developers to focus on the identified goals  ##wg ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 192: 1. Monthly IRC meeting of the WG chairs introducing the happenngs of the last period ##actionitem ##nfv
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 24: 			* review what was initially implemented  ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 201: 1. Wiki or similar to keep track of the related WGs and their work scope   ##actionitem ##nfv
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 25: 			* review what was has been proposed since initial implementation  ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 202: 1. Regular face2face meeting on the Summits and PTG-s ##actionitem ##nfv
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 26: 			* what has not been added as a criteria that needs to be  ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 64: * Set base expectations on the group openness & output  ##actionitem ##requirements
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 27: 				* writing it in uc vs tc terms  ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 65: * have discussions in shared place (general mailing list?)  ##actionitem ##uc
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 28: 				* make a link of which repos fall under uc governance  ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 77: * finding ways to steer member companies contributing developers to focus on the identified goals  ##wg ##uc ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 45: 			* extra-AUC? Not need for new repo - Add a txt file    ##uc ##actionitem +1
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 24: * review what was initially implemented  ##uc ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 46: 				* repo for self-nomination +1  ##uc ##actionitem ##emagana (I will take it)+1
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 25: * review what was has been proposed since initial implementation  ##uc ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal: 56: 			* lbragstad to go to the Product Working group about getting people to work on this ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 26: * what has not been added as a criteria that needs to be  ##uc ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal: 58: 			* mordred to take on massaging the spec  ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 27: * writing it in uc vs tc terms  ##uc ##actionitem
 
-https://etherpad.openstack.org/p/TrackChair: 24: 			* Ask track chairs to share best practices to share with incoming group   ##trackchair ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 28: * make a link of which repos fall under uc governance  ##uc ##actionitem
 
-https://etherpad.openstack.org/p/TrackChair: 30: 	* Clarifying Alternates and Lightning Talks  ##trackchair ##actionitem 
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 45: * extra-AUC? Not need for new repo - Add a txt file    ##uc ##actionitem +1
 
-https://etherpad.openstack.org/p/TrackChair: 34: 			* dicussion on track-chair mail-ilst   ##trackchair ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 46: * repo for self-nomination +1  ##uc ##actionitem ##emagana (I will take it)+1
+
+https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal: 56: * lbragstad to go to the Product Working group about getting people to work on this ##actionitem
+
+https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal: 58: * mordred to take on massaging the spec  ##actionitem
+
+https://etherpad.openstack.org/p/TrackChair: 24: * Ask track chairs to share best practices to share with incoming group   ##trackchair ##actionitem
+
+https://etherpad.openstack.org/p/TrackChair: 30: * Clarifying Alternates and Lightning Talks  ##trackchair ##actionitem
+
+https://etherpad.openstack.org/p/TrackChair: 34: * dicussion on track-chair mail-ilst   ##trackchair ##actionitem
 

forum/201705-bos/TAG-actionitemlcoo.md

@@ -1,2 +0,0 @@
-https://etherpad.openstack.org/p/BOS-forum-LCOOGetToKnow: 49: 	* Define governance model in LCOO and it is allined with UC ##actionitem#lcoo
-

forum/201705-bos/TAG-actions.md

@@ -0,0 +1,2 @@
+https://etherpad.openstack.org/p/BOS-forum-developer-openstack-org: 11: 1. Help take notes by adding ##<actions> and "+1" any good ideas with which you agree.
+

forum/201705-bos/TAG-all-projects.md

@@ -0,0 +1,10 @@
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 79: * Better release notes for all projects would help to identfiy what has changed.##all-projects
+
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 123: What could the communiity do to help in place n+2 upgrades?.##all-projects#actionitem
+
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 124: * Better release notes for all projects would help to identfiy what has changed.##all-projects#actionitem
+
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 125: * Better description of what happens with mixed versions, i.e agents behind one or two versions.##all-projects#actionitem
+
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 126: * TODO: call out projects that are doing upgrade impacts but not documenting them in the release notes.##all-projects#actionitem
+

forum/201705-bos/TAG-apiwg.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 98: 	* Folks tend to look to Nova versus the guidelines ##apiwg
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 98: * Folks tend to look to Nova versus the guidelines ##apiwg
 

forum/201705-bos/TAG-best-practice.md

@@ -1,30 +1,30 @@
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 113: 		* Why only Large/telco WGs? ##best-practice
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 113: * Why only Large/telco WGs? ##best-practice
 
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 141: 	* What is the best way to present needed OpenStack features to the community for discussion? ##best-practice
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 141: * What is the best way to present needed OpenStack features to the community for discussion? ##best-practice
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 19: 			* Combined newsletter? ##best-practice ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 19: * Combined newsletter? ##best-practice ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 20: 			* An open session simliar to this one, but focused on the WG leads to spend a few minutes describing their group to the attendees might help ##best-practice ##wgchairs - let's always think about scale, i.e. why not describe the groups centrally and consistently communicate to point folks in addition
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 20: * An open session simliar to this one, but focused on the WG leads to spend a few minutes describing their group to the attendees might help ##best-practice ##wgchairs - let's always think about scale, i.e. why not describe the groups centrally and consistently communicate to point folks in addition
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 22: 			* Superuser TV/articles ##best-practice ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 22: * Superuser TV/articles ##best-practice ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 30: 				* weekly newsletter sent out to openstack-dev ML  ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 30: * weekly newsletter sent out to openstack-dev ML  ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 71: 			* made a brochure ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 71: * made a brochure ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 72: 			* made cards ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 72: * made cards ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 73: 			* made a presentation ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 73: * made a presentation ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 74: 			* submit a Summit BoF session to induct new members ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 74: * submit a Summit BoF session to induct new members ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 75: 			* Ask Flanders <flanders@openstack.org> ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 75: * Ask Flanders <flanders@openstack.org> ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 76: 			* Write a SuperUser article ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 76: * Write a SuperUser article ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 77: 			* have co-chairs in different countries, e.g. Scientific-WG has 3x co-chairs from Australia, UK and USA. ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 77: * have co-chairs in different countries, e.g. Scientific-WG has 3x co-chairs from Australia, UK and USA. ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 78: 			* have a WG social/party, e.g. Scientific-has a social each summit where it invites vendors to sponsor the drinks for the evening. ##best-practice ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 78: * have a WG social/party, e.g. Scientific-has a social each summit where it invites vendors to sponsor the drinks for the evening. ##best-practice ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 79: 			* Involve the community by letting people know of the work we are doing (Meetups, conferences, small outreach)  ##best-practice ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 79: * Involve the community by letting people know of the work we are doing (Meetups, conferences, small outreach)  ##best-practice ##wgchairs
 

forum/201705-bos/TAG-call.md

@@ -1,4 +1,4 @@
-https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 33: 			* ##call for public cloud operators to read proposal for keystone specs on 'unified limits' see BOS-forum-quotas
+https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 33: * ##call for public cloud operators to read proposal for keystone specs on 'unified limits' see BOS-forum-quotas
 
-https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 47: 			* ##call for public cloud deployers to support the new maintainer fo rthe VPN as a Service feature.
+https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 47: * ##call for public cloud deployers to support the new maintainer fo rthe VPN as a Service feature.
 

forum/201705-bos/TAG-compliance.md

@@ -1,12 +1,12 @@
-https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 75: 		* Call-To-Action: fill out the ethercalc - https://ethercalc.openstack.org/BOS-forum-Compliance-Security-Certification  ##compliance
+https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 75: * Call-To-Action: fill out the ethercalc - https://ethercalc.openstack.org/BOS-forum-Compliance-Security-Certification  ##compliance
 
-https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 88: 		* Understanding the 12 PCI DSS Requirements - https://www.pcisecuritystandards.org/pdfs/pci_dss_saq_navigating_dss.pdf  ##compliance
+https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 88: * Understanding the 12 PCI DSS Requirements - https://www.pcisecuritystandards.org/pdfs/pci_dss_saq_navigating_dss.pdf  ##compliance
 
-https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 95: 				* Recommended configurations to setup basic common security practices  ##actionitem ##compliance
+https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 95: * Recommended configurations to setup basic common security practices  ##actionitem ##compliance
 
-https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 127: 			* openSCAP is the testing tool: https://www.open-scap.org  ##compliance
+https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 127: * openSCAP is the testing tool: https://www.open-scap.org  ##compliance
 
-https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 128: 			* existing tests for Ubuntu: https://github.com/GovReady/ubuntu-scap  ##compliance
+https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 128: * existing tests for Ubuntu: https://github.com/GovReady/ubuntu-scap  ##compliance
 
 https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification: 142: Documented OpenStack security gaps  ##actionitem ##compliance
 

forum/201705-bos/TAG-concern.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 62: 		* ##concern ##usersurvey ways of getting qualified data (curated list [focus group] vs the world)
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 62: * ##concern ##usersurvey ways of getting qualified data (curated list [focus group] vs the world)
 

forum/201705-bos/TAG-crossproject.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 35: 		* Project deletions? ##crossproject ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 35: * Project deletions? ##crossproject ##painpoint
 

forum/201705-bos/TAG-dialogue.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 101: 		* OpenStack Shared|Special Interest Groups ##vote ##dialogue
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 101: * OpenStack Shared|Special Interest Groups ##vote ##dialogue
 

forum/201705-bos/TAG-discoverability.md

@@ -1,4 +1,4 @@
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 103: 	* Go beyond the summit ##discoverability
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 103: * Go beyond the summit ##discoverability
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 106: 			* collaborative document ##discoverability
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 106: * collaborative document ##discoverability
 

forum/201705-bos/TAG-documentation.md

@@ -1,4 +1,4 @@
-https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 44: 	* Write a document describing how to integrate keystone with a set of applications folks would like to see working this way ##keystone ##documentation
+https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 44: * Write a document describing how to integrate keystone with a set of applications folks would like to see working this way ##keystone ##documentation
 
-https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 85: 	* Best Practices? ##documentation ##upgrades
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 85: * Best Practices? ##documentation ##upgrades
 

forum/201705-bos/TAG-emagana.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 46: 				* repo for self-nomination +1  ##uc ##actionitem ##emagana (I will take it)+1
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 46: * repo for self-nomination +1  ##uc ##actionitem ##emagana (I will take it)+1
 

forum/201705-bos/TAG-etsinfv.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 68: 		* ETSI NFV (Network Functions Virtualisation) ##ETSINFV
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 68: * ETSI NFV (Network Functions Virtualisation) ##ETSINFV
 

forum/201705-bos/TAG-ewg.md

@@ -1,34 +1,34 @@
-https://etherpad.openstack.org/p/Achieving_Resiliency_at_Scales_of_1000+: 37: 			* Can ##pwg or ##ewg help with this?
+https://etherpad.openstack.org/p/Achieving_Resiliency_at_Scales_of_1000+: 37: * Can ##pwg or ##ewg help with this?
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 40: 			* good cadence on ebook ##feedback ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 40: * good cadence on ebook ##feedback ##ewg
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 44: 					* Looking for reference architecture on how to configure and design the underlying cloud to support to upper workload ##actionitem ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 44: * Looking for reference architecture on how to configure and design the underlying cloud to support to upper workload ##actionitem ##ewg
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 45: 					* Link the workload reference architecture to architecture design guide ##actionitem ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 45: * Link the workload reference architecture to architecture design guide ##actionitem ##ewg
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 46: 					* Continue to work/colloborate with Docs team on guidance ##actionitem ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 46: * Continue to work/colloborate with Docs team on guidance ##actionitem ##ewg
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 47: 				* Any discussion on using general tools such as terraform other than heat ##feedback ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 47: * Any discussion on using general tools such as terraform other than heat ##feedback ##ewg
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 48: 			* Defining who we are??? ##ewg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 48: * Defining who we are??? ##ewg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 49: 				* define EWG scope  ##ewg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 49: * define EWG scope  ##ewg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 58: 			* Align with Summit cycle seems reasonable ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 58: * Align with Summit cycle seems reasonable ##ewg
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 61: 				* e.g. High Throughput Computing (CERN, Tim Bell) +1 ##ewg ##goal 
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 61: * e.g. High Throughput Computing (CERN, Tim Bell) +1 ##ewg ##goal
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 62: 					* Scientific WG could already have a lot of the data required/needed to complete in parallel with other goal(s) ##ewg ##goal
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 62: * Scientific WG could already have a lot of the data required/needed to complete in parallel with other goal(s) ##ewg ##goal
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 64: 					* Scientific WG could already have a lot of the data required/needed to complete in parallel with other goal(s)  ##ewg ##goal
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 64: * Scientific WG could already have a lot of the data required/needed to complete in parallel with other goal(s)  ##ewg ##goal
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 65: 				* e.g. Containers/Kubernetes (IBM Tong Li, Interop Challenge Heat template, Cockroach DB is sample app). Megan's input: Describe how to use individual OpenStack services with Kubernetes (this may be better as a separate series of articles or briefs). Such as Keystone, Cinder, Kuryr.   ##ewg ##goal ##interop
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 65: * e.g. Containers/Kubernetes (IBM Tong Li, Interop Challenge Heat template, Cockroach DB is sample app). Megan's input: Describe how to use individual OpenStack services with Kubernetes (this may be better as a separate series of articles or briefs). Such as Keystone, Cinder, Kuryr.   ##ewg ##goal ##interop
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 70: 				* How container intersect with OpenStack ##ewg ##wishlist
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 70: * How container intersect with OpenStack ##ewg ##wishlist
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 76: 			* Regional meeting? biweekly meeting? ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 76: * Regional meeting? biweekly meeting? ##ewg
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 77: 			* need to work on scope/purpose prior to outreach ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 77: * need to work on scope/purpose prior to outreach ##ewg
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 82: 		* Providing assistance to financial wg on execution ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 82: * Providing assistance to financial wg on execution ##ewg
 

forum/201705-bos/TAG-featuretracker.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap: 55: ##featuretracker - Follow up on developing a community resource for requesting and rating feature requests. 
+https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap: 55: ##featuretracker - Follow up on developing a community resource for requesting and rating feature requests.
 

forum/201705-bos/TAG-feedback.md

@@ -1,4 +1,4 @@
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 40: 			* good cadence on ebook ##feedback ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 40: * good cadence on ebook ##feedback ##ewg
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 47: 				* Any discussion on using general tools such as terraform other than heat ##feedback ##ewg
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 47: * Any discussion on using general tools such as terraform other than heat ##feedback ##ewg
 

forum/201705-bos/TAG-femdc.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 85: 		* Massively Distributed Clouds WG ##FEMDC
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 85: * Massively Distributed Clouds WG ##FEMDC
 

forum/201705-bos/TAG-gap.md

@@ -1,24 +1,24 @@
-https://etherpad.openstack.org/p/Achieving_Resiliency_at_Scales_of_1000+: 31: 		* ##gap Performance gate
+https://etherpad.openstack.org/p/Achieving_Resiliency_at_Scales_of_1000+: 31: * ##gap Performance gate
 
-https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality: 32: 		* ##gap Resource reservation
+https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality: 32: * ##gap Resource reservation
 
-https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality: 44: 		* ##gap Resource change events
+https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality: 44: * ##gap Resource change events
 
-https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality: 47: 		* ##gap Interpretation of alarms
+https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality: 47: * ##gap Interpretation of alarms
 
-https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality: 48: 		* ##gap Capacity management fragments
+https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality: 48: * ##gap Capacity management fragments
 
-https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds: 55: 			* Where are patches of interest to public cloud operators aggregated? Drop a link in -publiccloud IRC maybe? ##gap
+https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds: 55: * Where are patches of interest to public cloud operators aggregated? Drop a link in -publiccloud IRC maybe? ##gap
 
 https://etherpad.openstack.org/p/BOS-forum-i18n-translation-feedback-from-users: 19: ##I18n ##translation ##user-invoice ##gap
 
-https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 58: 			* Are there any container projects or something for Tempest?   ##newfeature, ##gap ?
+https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 58: * Are there any container projects or something for Tempest?   ##newfeature, ##gap ?
 
-https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 71: 			* Changes in devstack many times break env  ##painpoint, ##uservoice, ##gap 
+https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 71: * Changes in devstack many times break env  ##painpoint, ##uservoice, ##gap
 
-https://etherpad.openstack.org/p/TrackChair: 3: 		* Maybe get some feedback from the submitter to make sure the proposed change makes sense  ##gap ##trackchair
+https://etherpad.openstack.org/p/TrackChair: 3: * Maybe get some feedback from the submitter to make sure the proposed change makes sense  ##gap ##trackchair
 
-https://etherpad.openstack.org/p/TrackChair: 8: 		* Tags might help  ##trackchair ##gap
+https://etherpad.openstack.org/p/TrackChair: 8: * Tags might help  ##trackchair ##gap
 
-https://etherpad.openstack.org/p/TrackChair: 12: 		* Way to collect feedback from the audience about usefulness of previous tracks  ##trackchair ##gap
+https://etherpad.openstack.org/p/TrackChair: 12: * Way to collect feedback from the audience about usefulness of previous tracks  ##trackchair ##gap
 

forum/201705-bos/TAG-gaps.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 66: 		* Expected changes on the UC charter for WGs  ##uc ##gaps
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 66: * Expected changes on the UC charter for WGs  ##uc ##gaps
 

forum/201705-bos/TAG-gnocchi.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 45: 	* grafana support  (both pointed at gnochi for users to pull their own data, and pointed at prometheus and just restricted to cloud admins?) ##keystone ##grafana ##gnocchi
+https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 45: * grafana support  (both pointed at gnochi for users to pull their own data, and pointed at prometheus and just restricted to cloud admins?) ##keystone ##grafana ##gnocchi
 

forum/201705-bos/TAG-goal.md

@@ -1,8 +1,8 @@
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 61: 				* e.g. High Throughput Computing (CERN, Tim Bell) +1 ##ewg ##goal 
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 61: * e.g. High Throughput Computing (CERN, Tim Bell) +1 ##ewg ##goal
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 62: 					* Scientific WG could already have a lot of the data required/needed to complete in parallel with other goal(s) ##ewg ##goal
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 62: * Scientific WG could already have a lot of the data required/needed to complete in parallel with other goal(s) ##ewg ##goal
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 64: 					* Scientific WG could already have a lot of the data required/needed to complete in parallel with other goal(s)  ##ewg ##goal
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 64: * Scientific WG could already have a lot of the data required/needed to complete in parallel with other goal(s)  ##ewg ##goal
 
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 65: 				* e.g. Containers/Kubernetes (IBM Tong Li, Interop Challenge Heat template, Cockroach DB is sample app). Megan's input: Describe how to use individual OpenStack services with Kubernetes (this may be better as a separate series of articles or briefs). Such as Keystone, Cinder, Kuryr.   ##ewg ##goal ##interop
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 65: * e.g. Containers/Kubernetes (IBM Tong Li, Interop Challenge Heat template, Cockroach DB is sample app). Megan's input: Describe how to use individual OpenStack services with Kubernetes (this may be better as a separate series of articles or briefs). Such as Keystone, Cinder, Kuryr.   ##ewg ##goal ##interop
 

forum/201705-bos/TAG-grafana.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 45: 	* grafana support  (both pointed at gnochi for users to pull their own data, and pointed at prometheus and just restricted to cloud admins?) ##keystone ##grafana ##gnocchi
+https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 45: * grafana support  (both pointed at gnochi for users to pull their own data, and pointed at prometheus and just restricted to cloud admins?) ##keystone ##grafana ##gnocchi
 

forum/201705-bos/TAG-heidijoy.md

@@ -1,4 +1,4 @@
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 57: 	* Role/responsibilities for upcoming User Survey and timeline ##heidijoy  ##usersurvey
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 57: * Role/responsibilities for upcoming User Survey and timeline ##heidijoy  ##usersurvey
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 58: 		* has been documented ##heidijoy
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 58: * has been documented ##heidijoy
 

forum/201705-bos/TAG-infra.md

@@ -1,4 +1,4 @@
-https://etherpad.openstack.org/p/Achieving_Resiliency_at_Scales_of_1000+: 52: 		* ##infra team to store data and graph it
+https://etherpad.openstack.org/p/Achieving_Resiliency_at_Scales_of_1000+: 52: * ##infra team to store data and graph it
 
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 64: 			* ##infra It provides a forum to perform CI with adjacent communities and frameworks for validation of use cases 
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 64: * ##infra It provides a forum to perform CI with adjacent communities and frameworks for validation of use cases
 

forum/201705-bos/TAG-interop.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 65: 				* e.g. Containers/Kubernetes (IBM Tong Li, Interop Challenge Heat template, Cockroach DB is sample app). Megan's input: Describe how to use individual OpenStack services with Kubernetes (this may be better as a separate series of articles or briefs). Such as Keystone, Cinder, Kuryr.   ##ewg ##goal ##interop
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 65: * e.g. Containers/Kubernetes (IBM Tong Li, Interop Challenge Heat template, Cockroach DB is sample app). Megan's input: Describe how to use individual OpenStack services with Kubernetes (this may be better as a separate series of articles or briefs). Such as Keystone, Cinder, Kuryr.   ##ewg ##goal ##interop
 

forum/201705-bos/TAG-ironic).md

@@ -1,2 +0,0 @@
-https://etherpad.openstack.org/p/BOS-forum-101: 32: 				* You can use ##<tag> to highlight anything that needs to be shared with a team not present in the session (e.g. ##uservoice, ##ironic) and a group of people will share it in a mailing list summary after the event
-

forum/201705-bos/TAG-ironic.md

@@ -1,14 +1,16 @@
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 43: 	* - Port selection on multi physical switches. ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-101: 32: * You can use ##<tag> to highlight anything that needs to be shared with a team not present in the session (e.g. ##uservoice, ##ironic) and a group of people will share it in a mailing list summary after the event
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 51: 	* no concept of locality ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 43: * - Port selection on multi physical switches. ##ironic ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 52: 		* I would like to see this happen for per rack (leaf) etc conductors ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 51: * no concept of locality ##ironic ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 55: 		*  https://specs.openstack.org/openstack/ironic-specs/priorities/pike-priorities.html#deploy-steps ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 52: * I would like to see this happen for per rack (leaf) etc conductors ##ironic ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 71: 			* Sync power state against 50,000 nodes takes a while. I'm all the way back on Juno though, so there are probably some changes that've happened that i've missed. ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 55: *  https://specs.openstack.org/openstack/ironic-specs/priorities/pike-priorities.html#deploy-steps ##ironic ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 73: 	* Running DHCP/HTTP/etc for instance provisioning out of the Ironic Conductor machines provides some large security holes. This means that datacenter nodes have logical access to one of the most crucial pieces of the OpenStack control plane. We've moved DHCP, TFTP, HTTP for provisioning to another set of nodes. However the conductor expects to write this to local disk. A driver based interface with an API to write these files remotely is necessary. ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 71: * Sync power state against 50,000 nodes takes a while. I'm all the way back on Juno though, so there are probably some changes that've happened that i've missed. ##ironic ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 74: 	* Need a reference architecture and best practises on how to deploy Ironic in 100/200/1000/5000 nodes ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 73: * Running DHCP/HTTP/etc for instance provisioning out of the Ironic Conductor machines provides some large security holes. This means that datacenter nodes have logical access to one of the most crucial pieces of the OpenStack control plane. We've moved DHCP, TFTP, HTTP for provisioning to another set of nodes. However the conductor expects to write this to local disk. A driver based interface with an API to write these files remotely is necessary. ##ironic ##painpoint
+
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 74: * Need a reference architecture and best practises on how to deploy Ironic in 100/200/1000/5000 nodes ##ironic ##painpoint
 

forum/201705-bos/TAG-k8s.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 35: 		* TODO: sit down and map out similarities and differences between namespaces and project/domains ##keystone ##k8s
+https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 35: * TODO: sit down and map out similarities and differences between namespaces and project/domains ##keystone ##k8s
 

forum/201705-bos/TAG-keystone.md

@@ -1,8 +1,8 @@
-https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 35: 		* TODO: sit down and map out similarities and differences between namespaces and project/domains ##keystone ##k8s
+https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 35: * TODO: sit down and map out similarities and differences between namespaces and project/domains ##keystone ##k8s
 
-https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 44: 	* Write a document describing how to integrate keystone with a set of applications folks would like to see working this way ##keystone ##documentation
+https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 44: * Write a document describing how to integrate keystone with a set of applications folks would like to see working this way ##keystone ##documentation
 
-https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 45: 	* grafana support  (both pointed at gnochi for users to pull their own data, and pointed at prometheus and just restricted to cloud admins?) ##keystone ##grafana ##gnocchi
+https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 45: * grafana support  (both pointed at gnochi for users to pull their own data, and pointed at prometheus and just restricted to cloud admins?) ##keystone ##grafana ##gnocchi
 
-https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 46: 	* keystoneclients in other languages +1 ##keystone ##multilanguage
+https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 46: * keystoneclients in other languages +1 ##keystone ##multilanguage
 

forum/201705-bos/TAG-lcoo.md

@@ -1,24 +1,26 @@
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 61: 	* Containerized control plane  ##roadmap ##lcoo
+https://etherpad.openstack.org/p/BOS-forum-LCOOGetToKnow: 49: * Define governance model in LCOO and it is allined with UC ##actionitem#lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 66: 			* Yes - we definately will include Kolla and OpenStack-Helm and others in the Gap Analysis.  We have started 2 different Development Proposals (above) and from an LCOO perspective there should not be an assumption that we have chosen the solution. What we hoped to do next with the Containerized Control Plane user stories was to have an introduction from the Kolla knowledgeable SMEs and also form teh OpenStack-Helm SMEs to help us get started with Gap Analysis.  ##lcoo ##
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 61: * Containerized control plane  ##roadmap ##lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 76: 	* Extreme (Destructive) Testing: ##roadmap ##lcoo 
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 66: * Yes - we definately will include Kolla and OpenStack-Helm and others in the Gap Analysis.  We have started 2 different Development Proposals (above) and from an LCOO perspective there should not be an assumption that we have chosen the solution. What we hoped to do next with the Containerized Control Plane user stories was to have an introduction from the Kolla knowledgeable SMEs and also form teh OpenStack-Helm SMEs to help us get started with Gap Analysis.  ##lcoo ##
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 116: 	* Older releases in production - Skip level upgrading +1+1 ##roadmap ##lcoo
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 76: * Extreme (Destructive) Testing: ##roadmap ##lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 118: 	* Telemetry / SNAP  ##roadmap ##lcoo
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 116: * Older releases in production - Skip level upgrading +1+1 ##roadmap ##lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 120: 	* Logging  ##roadmap ##lcoo
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 118: * Telemetry / SNAP  ##roadmap ##lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 127: 	* set up and publish slack channel ##actionitem ##lcoo --> https://lcoo.slack.com >> publish this on wiki
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 120: * Logging  ##roadmap ##lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 128: 	* derive short term win ##actionitem ##lcoo
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 127: * set up and publish slack channel ##actionitem ##lcoo --> https://lcoo.slack.com >> publish this on wiki
 
-https://etherpad.openstack.org/p/BOS-forum-log-messages: 128:     If the error message is not useful - then we need a bug on the error message  ##action-item ##LCOO
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 128: * derive short term win ##actionitem ##lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 51: 		* target (welcome) newer large operators ##LCOO ##pwg ##onboarding ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-log-messages: 128: If the error message is not useful - then we need a bug on the error message  ##action-item ##LCOO
 
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 95: 		* Large Contributing OpenStack Operators (LCOO) ##LCOO
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 51: * target (welcome) newer large operators ##LCOO ##pwg ##onboarding ##actionitem
+
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 95: * Large Contributing OpenStack Operators (LCOO) ##LCOO
 
 https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 123: Jamey McCabe <jamemcc@gmail.com> ##LCOO
 

forum/201705-bos/TAG-multilanguage.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 46: 	* keystoneclients in other languages +1 ##keystone ##multilanguage
+https://etherpad.openstack.org/p/BOS-forum-consumable-keystone: 46: * keystoneclients in other languages +1 ##keystone ##multilanguage
 

forum/201705-bos/TAG-newfeature.md

@@ -1,16 +1,16 @@
-https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 24: 		* Self-service signup - +1+1+1 ##painpoint ##newfeature
+https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 24: * Self-service signup - +1+1+1 ##painpoint ##newfeature
 
-https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 29: 		* Domain level quote management: domain admin can create users  ##newfeature
+https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 29: * Domain level quote management: domain admin can create users  ##newfeature
 
-https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 42: 		* Volume multi-attach ##newfeature
+https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 42: * Volume multi-attach ##newfeature
 
-https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 58: 			* Are there any container projects or something for Tempest?   ##newfeature, ##gap ?
+https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 58: * Are there any container projects or something for Tempest?   ##newfeature, ##gap ?
 
-https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 95: 		* Check status of services  ##newfeature, ##uservoice
+https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 95: * Check status of services  ##newfeature, ##uservoice
 
-https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 31: *Many very large operators, running highly available, complex OpenStack environments, are running on old versions of (OpenStack Icehouse, Juno, Kilo...). The reason is because upgrading is highly painful and stabilizing platforms has often been the greater priority. How can they catch up and realize the benefits found in current releases? ##uservoice ##newfeature 
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 31: *Many very large operators, running highly available, complex OpenStack environments, are running on old versions of (OpenStack Icehouse, Juno, Kilo...). The reason is because upgrading is highly painful and stabilizing platforms has often been the greater priority. How can they catch up and realize the benefits found in current releases? ##uservoice ##newfeature
 
-https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 69: 		* ##newfeature Skip-level upgrading. How many versions? Is there a path to where the number of versions does not matter?
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 69: * ##newfeature Skip-level upgrading. How many versions? Is there a path to where the number of versions does not matter?
 
-https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 70: 		* ##newfeature Live upgrades would help ease the pain in doing upgrades. Need to clarify the definition of "live". what do you accept and what you do not. (e.g. API down time, service down time, migration of workload, etc)
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 70: * ##newfeature Live upgrades would help ease the pain in doing upgrades. Need to clarify the definition of "live". what do you accept and what you do not. (e.g. API down time, service down time, migration of workload, etc)
 

forum/201705-bos/TAG-nfv.md

@@ -1,8 +1,8 @@
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 115: 			* There are other orchestrators out there we should also look at. ##painpoint ##nfv
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 115: * There are other orchestrators out there we should also look at. ##painpoint ##nfv
 
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 192: 	1. Monthly IRC meeting of the WG chairs introducing the happenngs of the last period ##actionitem ##nfv
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 192: 1. Monthly IRC meeting of the WG chairs introducing the happenngs of the last period ##actionitem ##nfv
 
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 201: 	1. Wiki or similar to keep track of the related WGs and their work scope   ##actionitem ##nfv
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 201: 1. Wiki or similar to keep track of the related WGs and their work scope   ##actionitem ##nfv
 
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 202: 	1. Regular face2face meeting on the Summits and PTG-s ##actionitem ##nfv
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 202: 1. Regular face2face meeting on the Summits and PTG-s ##actionitem ##nfv
 

forum/201705-bos/TAG-onboarding.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 51: 		* target (welcome) newer large operators ##LCOO ##pwg ##onboarding ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 51: * target (welcome) newer large operators ##LCOO ##pwg ##onboarding ##actionitem
 

forum/201705-bos/TAG-opnfv.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 58: 		* OPNFV (open platform for NFV) ##OPNFV
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 58: * OPNFV (open platform for NFV) ##OPNFV
 

forum/201705-bos/TAG-opstags.md

@@ -0,0 +1,2 @@
+https://etherpad.openstack.org/p/BOS-forum-ops-tags-wg-session: 11: *##opstags - Feedback from session on best practices and areas for improvement
+

forum/201705-bos/TAG-outreach.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 42: 		* connecting with smaller operators ##pwg ##outreach
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 42: * connecting with smaller operators ##pwg ##outreach
 

forum/201705-bos/TAG-painpoint.md

@@ -1,32 +1,32 @@
-https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 24: 		* Self-service signup - +1+1+1 ##painpoint ##newfeature
+https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 24: * Self-service signup - +1+1+1 ##painpoint ##newfeature
 
-https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 35: 		* Project deletions? ##crossproject ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 35: * Project deletions? ##crossproject ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds: 24: 				* ##painpoint - maintaining patches that aren't reviewed
+https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds: 24: * ##painpoint - maintaining patches that aren't reviewed
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 43: 	* - Port selection on multi physical switches. ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 43: * - Port selection on multi physical switches. ##ironic ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 51: 	* no concept of locality ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 51: * no concept of locality ##ironic ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 52: 		* I would like to see this happen for per rack (leaf) etc conductors ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 52: * I would like to see this happen for per rack (leaf) etc conductors ##ironic ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 55: 		*  https://specs.openstack.org/openstack/ironic-specs/priorities/pike-priorities.html#deploy-steps ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 55: *  https://specs.openstack.org/openstack/ironic-specs/priorities/pike-priorities.html#deploy-steps ##ironic ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 71: 			* Sync power state against 50,000 nodes takes a while. I'm all the way back on Juno though, so there are probably some changes that've happened that i've missed. ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 71: * Sync power state against 50,000 nodes takes a while. I'm all the way back on Juno though, so there are probably some changes that've happened that i've missed. ##ironic ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 73: 	* Running DHCP/HTTP/etc for instance provisioning out of the Ironic Conductor machines provides some large security holes. This means that datacenter nodes have logical access to one of the most crucial pieces of the OpenStack control plane. We've moved DHCP, TFTP, HTTP for provisioning to another set of nodes. However the conductor expects to write this to local disk. A driver based interface with an API to write these files remotely is necessary. ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 73: * Running DHCP/HTTP/etc for instance provisioning out of the Ironic Conductor machines provides some large security holes. This means that datacenter nodes have logical access to one of the most crucial pieces of the OpenStack control plane. We've moved DHCP, TFTP, HTTP for provisioning to another set of nodes. However the conductor expects to write this to local disk. A driver based interface with an API to write these files remotely is necessary. ##ironic ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 74: 	* Need a reference architecture and best practises on how to deploy Ironic in 100/200/1000/5000 nodes ##ironic ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-ironic-feedback: 74: * Need a reference architecture and best practises on how to deploy Ironic in 100/200/1000/5000 nodes ##ironic ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 41: 	* PWG Composition and Participation - how to make PWG more impactful ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 41: * PWG Composition and Participation - how to make PWG more impactful ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 48: 			* Is there ay framework or way to automate the configuration options for Tempest? ##painpoint  ##uservoice
+https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 48: * Is there ay framework or way to automate the configuration options for Tempest? ##painpoint  ##uservoice
 
-https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 50: 			* How to handle resource changes which is like removals of the existing flavors/networks, etc? ##painpoint
+https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 50: * How to handle resource changes which is like removals of the existing flavors/networks, etc? ##painpoint
 
-https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 71: 			* Changes in devstack many times break env  ##painpoint, ##uservoice, ##gap 
+https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 71: * Changes in devstack many times break env  ##painpoint, ##uservoice, ##gap
 
-https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 77: 		* ##painpoint ##uservoice Never change a running system: if a release does not provide additional wanted functionalities, why do the risk in upgrading to this release?
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 77: * ##painpoint ##uservoice Never change a running system: if a release does not provide additional wanted functionalities, why do the risk in upgrading to this release?
 
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 115: 			* There are other orchestrators out there we should also look at. ##painpoint ##nfv
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 115: * There are other orchestrators out there we should also look at. ##painpoint ##nfv
 

forum/201705-bos/TAG-painpoints.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 52: 		* PWG connecting with devs and users, gathering ##painpoints and helping to define priorities
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 52: * PWG connecting with devs and users, gathering ##painpoints and helping to define priorities
 

forum/201705-bos/TAG-publiccloud.md

@@ -1,6 +1,6 @@
 https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 9: ##publiccloud
 
-https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 23: 			* ##PublicCloud has created google spreadsheet listing issues for public clouds, requesting feedback,
+https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds: 23: * ##PublicCloud has created google spreadsheet listing issues for public clouds, requesting feedback,
 
 https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds: 16: ##publiccloud
 

forum/201705-bos/TAG-pwg.md

@@ -1,30 +1,30 @@
-https://etherpad.openstack.org/p/Achieving_Resiliency_at_Scales_of_1000+: 37: 			* Can ##pwg or ##ewg help with this?
+https://etherpad.openstack.org/p/Achieving_Resiliency_at_Scales_of_1000+: 37: * Can ##pwg or ##ewg help with this?
 
-https://etherpad.openstack.org/p/BOS-forum-advanced-instance-scheduling: 96: 	* describe the pre-empttive use cases also as a ##pwg development proposal?
+https://etherpad.openstack.org/p/BOS-forum-advanced-instance-scheduling: 96: * describe the pre-empttive use cases also as a ##pwg development proposal?
 
-https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements: 76: 	* Collaborate with other WG and bring requirements together, identify commonalities, with further gap analysis ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements: 76: * Collaborate with other WG and bring requirements together, identify commonalities, with further gap analysis ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 42: 		* connecting with smaller operators ##pwg ##outreach
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 42: * connecting with smaller operators ##pwg ##outreach
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 48: 			* new to openstack - how do you get involved  ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 48: * new to openstack - how do you get involved  ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 51: 		* target (welcome) newer large operators ##LCOO ##pwg ##onboarding ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 51: * target (welcome) newer large operators ##LCOO ##pwg ##onboarding ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 54: 		* encourage more sigs ##rbac  ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 54: * encourage more sigs ##rbac  ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 55: 	* Making the community aware that "these are the things" important for users  ##pwg
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 55: * Making the community aware that "these are the things" important for users  ##pwg
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 58: 	* Post-forum Analysis +1+1  ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 58: * Post-forum Analysis +1+1  ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 60: 		* template for response from moderators to send as summary   ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 60: * template for response from moderators to send as summary   ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 61: 		* Mine hashtag data ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 61: * Mine hashtag data ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 65: 	* Notify moderators to give feedback on Forum sessions ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 65: * Notify moderators to give feedback on Forum sessions ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 66: 	* How do we identify organization to help with this wg ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 66: * How do we identify organization to help with this wg ##pwg ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 81: 		* Product Working Group (PWG) ##pwg
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 81: * Product Working Group (PWG) ##pwg
 
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 131: 				* write a Development Proposals (previously known as “OpenStack User Story”) in PWG ##pwg
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 131: * write a Development Proposals (previously known as “OpenStack User Story”) in PWG ##pwg
 

forum/201705-bos/TAG-qa.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/Achieving_Resiliency_at_Scales_of_1000+: 50: 		* ##QA - performance on single node to extra performance under load for various API calls
+https://etherpad.openstack.org/p/Achieving_Resiliency_at_Scales_of_1000+: 50: * ##QA - performance on single node to extra performance under load for various API calls
 

forum/201705-bos/TAG-rbac.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 54: 		* encourage more sigs ##rbac  ##pwg ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session: 54: * encourage more sigs ##rbac  ##pwg ##actionitem
 

forum/201705-bos/TAG-requirements.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 64: 	* Set base expectations on the group openness & output  ##actionitem ##requirements
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 64: * Set base expectations on the group openness & output  ##actionitem ##requirements
 

forum/201705-bos/TAG-roadmap.md

@@ -1,12 +1,12 @@
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 61: 	* Containerized control plane  ##roadmap ##lcoo
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 61: * Containerized control plane  ##roadmap ##lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 76: 	* Extreme (Destructive) Testing: ##roadmap ##lcoo 
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 76: * Extreme (Destructive) Testing: ##roadmap ##lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 116: 	* Older releases in production - Skip level upgrading +1+1 ##roadmap ##lcoo
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 116: * Older releases in production - Skip level upgrading +1+1 ##roadmap ##lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 118: 	* Telemetry / SNAP  ##roadmap ##lcoo
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 118: * Telemetry / SNAP  ##roadmap ##lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 120: 	* Logging  ##roadmap ##lcoo
+https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap: 120: * Logging  ##roadmap ##lcoo
 
-https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap: 16: 	* ##roadmap - Feedback from sessions on how to improve the community generated roadmap process
+https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap: 16: * ##roadmap - Feedback from sessions on how to improve the community generated roadmap process
 

forum/201705-bos/TAG-sig.md

@@ -1,12 +1,12 @@
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 63: 	* Need a clear scope and goal  ##uc ##wg ##sig
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 63: * Need a clear scope and goal  ##uc ##wg ##sig
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 70: 	* One or two levels ?  ##sig
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 70: * One or two levels ?  ##sig
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 71: 		* sigs as a higher concept? tom   ##sig
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 71: * sigs as a higher concept? tom   ##sig
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 72: 		* working groups with a defined goal/dissolution vs. sigs/teams with an ongoing charter (example, from uc charter 'teams' vs 'working groups': https://governance.openstack.org/uc/reference/charter.html#structure-functional-teams )   ##wg ##sig
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 72: * working groups with a defined goal/dissolution vs. sigs/teams with an ongoing charter (example, from uc charter 'teams' vs 'working groups': https://governance.openstack.org/uc/reference/charter.html#structure-functional-teams )   ##wg ##sig
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 73: 		* make it clear that having a group complete its task and dissolve to move on to other tasks is acceptable/positive  ##wg ##sig
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 73: * make it clear that having a group complete its task and dissolve to move on to other tasks is acceptable/positive  ##wg ##sig
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 74: 		* We need to make sure those featrures get maintained by the dev after finishing the WG.  Would higher level group be the one to look after those long term? ##wg ##sig
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 74: * We need to make sure those featrures get maintained by the dev after finishing the WG.  Would higher level group be the one to look after those long term? ##wg ##sig
 

forum/201705-bos/TAG-suggestion.md

@@ -1,16 +1,16 @@
-https://etherpad.openstack.org/p/TrackChair: 16: 		* Consider 3-5 minute video from submissions   ##trackchair ##suggestion (make it optional) --> already in existing submission tool, maybe rephrase the sentence and clarify the purpose
+https://etherpad.openstack.org/p/TrackChair: 16: * Consider 3-5 minute video from submissions   ##trackchair ##suggestion (make it optional) --> already in existing submission tool, maybe rephrase the sentence and clarify the purpose
 
-https://etherpad.openstack.org/p/TrackChair: 19: 		* Consider leads for each Track Chair group ##trackchair ##suggestion
+https://etherpad.openstack.org/p/TrackChair: 19: * Consider leads for each Track Chair group ##trackchair ##suggestion
 
-https://etherpad.openstack.org/p/TrackChair: 22: 		* Define a process/guidelines/best practices for a successful track chair ##trackchair ##suggestion
+https://etherpad.openstack.org/p/TrackChair: 22: * Define a process/guidelines/best practices for a successful track chair ##trackchair ##suggestion
 
-https://etherpad.openstack.org/p/TrackChair: 32: 		* One list versus several  ##trackchair ##suggestion
+https://etherpad.openstack.org/p/TrackChair: 32: * One list versus several  ##trackchair ##suggestion
 
-https://etherpad.openstack.org/p/TrackChair: 38: 			* Could we add another queue (would no limit on personal selections help?) ##trackchair ##suggestion
+https://etherpad.openstack.org/p/TrackChair: 38: * Could we add another queue (would no limit on personal selections help?) ##trackchair ##suggestion
 
-https://etherpad.openstack.org/p/TrackChair: 41: 		* Show total # of track-chair that have selected a presentation (like 5 out of 5 have selected this talk) and rank them ##trackchair ##suggestion
+https://etherpad.openstack.org/p/TrackChair: 41: * Show total # of track-chair that have selected a presentation (like 5 out of 5 have selected this talk) and rank them ##trackchair ##suggestion
 
-https://etherpad.openstack.org/p/TrackChair: 45: 	* Do we have a group to assist people with their presentations?  ##trackchair ##suggestion  
+https://etherpad.openstack.org/p/TrackChair: 45: * Do we have a group to assist people with their presentations?  ##trackchair ##suggestion
 
-https://etherpad.openstack.org/p/TrackChair: 46: 	* Suggestion to require a track chair at the tracks they select   ##trackchair ##suggestion
+https://etherpad.openstack.org/p/TrackChair: 46: * Suggestion to require a track chair at the tracks they select   ##trackchair ##suggestion
 

forum/201705-bos/TAG-tacker.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 112: 		* Tacker ##tacker
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 112: * Tacker ##tacker
 

forum/201705-bos/TAG-tag.md

@@ -0,0 +1,2 @@
+https://etherpad.openstack.org/p/BOS-forum-101: 32: * You can use ##<tag> to highlight anything that needs to be shared with a team not present in the session (e.g. ##uservoice, ##ironic) and a group of people will share it in a mailing list summary after the event
+

forum/201705-bos/TAG-tc.md

@@ -1,4 +1,4 @@
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 67: 		* More joint meetings between UC/TC (IRC) +1  ##uc ##tc 
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 67: * More joint meetings between UC/TC (IRC) +1  ##uc ##tc
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 68: 			* Feel free to crash each others meetings for the meantime ##uc ##tc
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 68: * Feel free to crash each others meetings for the meantime ##uc ##tc
 

forum/201705-bos/TAG-telcowg.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 79: 		* Ops Telco/NFV WG ##telcowg
+https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration: 79: * Ops Telco/NFV WG ##telcowg
 

forum/201705-bos/TAG-trackchair.md

@@ -1,30 +1,30 @@
-https://etherpad.openstack.org/p/TrackChair: 1: 	* Moving sessions before voting- causes issues with number of sessions in each track/etc  ##trackchair 
+https://etherpad.openstack.org/p/TrackChair: 1: * Moving sessions before voting- causes issues with number of sessions in each track/etc  ##trackchair
 
-https://etherpad.openstack.org/p/TrackChair: 3: 		* Maybe get some feedback from the submitter to make sure the proposed change makes sense  ##gap ##trackchair
+https://etherpad.openstack.org/p/TrackChair: 3: * Maybe get some feedback from the submitter to make sure the proposed change makes sense  ##gap ##trackchair
 
-https://etherpad.openstack.org/p/TrackChair: 8: 		* Tags might help  ##trackchair ##gap
+https://etherpad.openstack.org/p/TrackChair: 8: * Tags might help  ##trackchair ##gap
 
-https://etherpad.openstack.org/p/TrackChair: 12: 		* Way to collect feedback from the audience about usefulness of previous tracks  ##trackchair ##gap
+https://etherpad.openstack.org/p/TrackChair: 12: * Way to collect feedback from the audience about usefulness of previous tracks  ##trackchair ##gap
 
-https://etherpad.openstack.org/p/TrackChair: 16: 		* Consider 3-5 minute video from submissions   ##trackchair ##suggestion (make it optional) --> already in existing submission tool, maybe rephrase the sentence and clarify the purpose
+https://etherpad.openstack.org/p/TrackChair: 16: * Consider 3-5 minute video from submissions   ##trackchair ##suggestion (make it optional) --> already in existing submission tool, maybe rephrase the sentence and clarify the purpose
 
-https://etherpad.openstack.org/p/TrackChair: 19: 		* Consider leads for each Track Chair group ##trackchair ##suggestion
+https://etherpad.openstack.org/p/TrackChair: 19: * Consider leads for each Track Chair group ##trackchair ##suggestion
 
-https://etherpad.openstack.org/p/TrackChair: 22: 		* Define a process/guidelines/best practices for a successful track chair ##trackchair ##suggestion
+https://etherpad.openstack.org/p/TrackChair: 22: * Define a process/guidelines/best practices for a successful track chair ##trackchair ##suggestion
 
-https://etherpad.openstack.org/p/TrackChair: 24: 			* Ask track chairs to share best practices to share with incoming group   ##trackchair ##actionitem
+https://etherpad.openstack.org/p/TrackChair: 24: * Ask track chairs to share best practices to share with incoming group   ##trackchair ##actionitem
 
-https://etherpad.openstack.org/p/TrackChair: 30: 	* Clarifying Alternates and Lightning Talks  ##trackchair ##actionitem 
+https://etherpad.openstack.org/p/TrackChair: 30: * Clarifying Alternates and Lightning Talks  ##trackchair ##actionitem
 
-https://etherpad.openstack.org/p/TrackChair: 32: 		* One list versus several  ##trackchair ##suggestion
+https://etherpad.openstack.org/p/TrackChair: 32: * One list versus several  ##trackchair ##suggestion
 
-https://etherpad.openstack.org/p/TrackChair: 34: 			* dicussion on track-chair mail-ilst   ##trackchair ##actionitem
+https://etherpad.openstack.org/p/TrackChair: 34: * dicussion on track-chair mail-ilst   ##trackchair ##actionitem
 
-https://etherpad.openstack.org/p/TrackChair: 38: 			* Could we add another queue (would no limit on personal selections help?) ##trackchair ##suggestion
+https://etherpad.openstack.org/p/TrackChair: 38: * Could we add another queue (would no limit on personal selections help?) ##trackchair ##suggestion
 
-https://etherpad.openstack.org/p/TrackChair: 41: 		* Show total # of track-chair that have selected a presentation (like 5 out of 5 have selected this talk) and rank them ##trackchair ##suggestion
+https://etherpad.openstack.org/p/TrackChair: 41: * Show total # of track-chair that have selected a presentation (like 5 out of 5 have selected this talk) and rank them ##trackchair ##suggestion
 
-https://etherpad.openstack.org/p/TrackChair: 45: 	* Do we have a group to assist people with their presentations?  ##trackchair ##suggestion  
+https://etherpad.openstack.org/p/TrackChair: 45: * Do we have a group to assist people with their presentations?  ##trackchair ##suggestion
 
-https://etherpad.openstack.org/p/TrackChair: 46: 	* Suggestion to require a track chair at the tracks they select   ##trackchair ##suggestion
+https://etherpad.openstack.org/p/TrackChair: 46: * Suggestion to require a track chair at the tracks they select   ##trackchair ##suggestion
 

forum/201705-bos/TAG-uc.md

@@ -1,52 +1,56 @@
 https://etherpad.openstack.org/p/BOS-forum-developer-openstack-org: 16: ##UC <-- goes to the UC chairs as suggestion.
 
-https://etherpad.openstack.org/p/BOS-forum-uc-governance-and-support-of-wgs: 50: 	* ##action ##uc get documents into gerrit
+https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap: 32: * How can the projects indicate that they are ready for deployment - defining the maturity level##uc
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 62: 	* ways to measure success/failure of proposed process(es)/plan(s)  ##uc ##wg
+https://etherpad.openstack.org/p/BOS-forum-uc-governance-and-support-of-wgs: 50: * ##action ##uc get documents into gerrit
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 63: 	* Need a clear scope and goal  ##uc ##wg ##sig
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 62: * ways to measure success/failure of proposed process(es)/plan(s)  ##uc ##wg
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 65: 	* have discussions in shared place (general mailing list?)  ##actionitem ##uc
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 63: * Need a clear scope and goal  ##uc ##wg ##sig
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 66: 	* Is there a need for a formal application process ?  ##uc
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 65: * have discussions in shared place (general mailing list?)  ##actionitem ##uc
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 77: 		* finding ways to steer member companies contributing developers to focus on the identified goals  ##wg ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 66: * Is there a need for a formal application process ?  ##uc
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 19: 	* Revising AUC criteria and documenting program motives/goals ##uc
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 77: * finding ways to steer member companies contributing developers to focus on the identified goals  ##wg ##uc ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 21: 			* it would be great if we can see the statistics in stackalystics  ##uc 
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 11: *##uc - Feedback from session and open items
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 22: 		* AUC criteria  ##uc
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 19: * Revising AUC criteria and documenting program motives/goals ##uc
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 24: 			* review what was initially implemented  ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 21: * it would be great if we can see the statistics in stackalystics  ##uc
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 25: 			* review what was has been proposed since initial implementation  ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 22: * AUC criteria  ##uc
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 26: 			* what has not been added as a criteria that needs to be  ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 24: * review what was initially implemented  ##uc ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 27: 				* writing it in uc vs tc terms  ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 25: * review what was has been proposed since initial implementation  ##uc ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 28: 				* make a link of which repos fall under uc governance  ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 26: * what has not been added as a criteria that needs to be  ##uc ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 45: 			* extra-AUC? Not need for new repo - Add a txt file    ##uc ##actionitem +1
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 27: * writing it in uc vs tc terms  ##uc ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 46: 				* repo for self-nomination +1  ##uc ##actionitem ##emagana (I will take it)+1
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 28: * make a link of which repos fall under uc governance  ##uc ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 52: 			* Send request to WGs chair to review the list of members  ##uc ##wg
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 45: * extra-AUC? Not need for new repo - Add a txt file    ##uc ##actionitem +1
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 59: 		* expanding the user survey WG  ##uc ##usersurvey
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 46: * repo for self-nomination +1  ##uc ##actionitem ##emagana (I will take it)+1
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 60: 		* do we intend to have a large survey again? ##uc
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 52: * Send request to WGs chair to review the list of members  ##uc ##wg
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 61: 		* how deep the reporting will be? ##uc
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 59: * expanding the user survey WG  ##uc ##usersurvey
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 66: 		* Expected changes on the UC charter for WGs  ##uc ##gaps
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 60: * do we intend to have a large survey again? ##uc
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 67: 		* More joint meetings between UC/TC (IRC) +1  ##uc ##tc 
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 61: * how deep the reporting will be? ##uc
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 68: 			* Feel free to crash each others meetings for the meantime ##uc ##tc
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 66: * Expected changes on the UC charter for WGs  ##uc ##gaps
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 70: 		* Agreed to weekly meetings ##uc
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 67: * More joint meetings between UC/TC (IRC) +1  ##uc ##tc
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 71: 		* Agreed to be more consistant as 5 UC members ##uc
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 68: * Feel free to crash each others meetings for the meantime ##uc ##tc
+
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 70: * Agreed to weekly meetings ##uc
+
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 71: * Agreed to be more consistant as 5 UC members ##uc
 

forum/201705-bos/TAG-ucwg.md

@@ -0,0 +1,2 @@
+https://etherpad.openstack.org/p/BOS-forum-uc-governance-and-support-of-wgs: 11: *##ucwg - Feedback from session and open items
+

forum/201705-bos/TAG-upgrades.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 85: 	* Best Practices? ##documentation ##upgrades
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 85: * Best Practices? ##documentation ##upgrades
 

forum/201705-bos/TAG-usersurvey.md

@@ -1,10 +1,12 @@
-https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey: 16: 	* ##usersurvey - Feedback from sessions on how to improve the user survey
+https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey: 16: * ##usersurvey - Feedback from sessions on how to improve the user survey
 
-https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey: 30: 		* The networking question is getting confusing with ML2 and underlying technologies. Can we revisit it? ##usersurvey
+https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey: 26: * Have someone from the user Survey WG take on the task of collecting data around a certain theme and work on making it non-confidential to be able to share more broadly##usersurvey
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 57: 	* Role/responsibilities for upcoming User Survey and timeline ##heidijoy  ##usersurvey
+https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey: 30: * The networking question is getting confusing with ML2 and underlying technologies. Can we revisit it? ##usersurvey
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 59: 		* expanding the user survey WG  ##uc ##usersurvey
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 57: * Role/responsibilities for upcoming User Survey and timeline ##heidijoy  ##usersurvey
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 62: 		* ##concern ##usersurvey ways of getting qualified data (curated list [focus group] vs the world)
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 59: * expanding the user survey WG  ##uc ##usersurvey
+
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 62: * ##concern ##usersurvey ways of getting qualified data (curated list [focus group] vs the world)
 

forum/201705-bos/TAG-uservoice.md

@@ -1,28 +1,28 @@
-https://etherpad.openstack.org/p/BOS-forum-101: 32: 				* You can use ##<tag> to highlight anything that needs to be shared with a team not present in the session (e.g. ##uservoice, ##ironic) and a group of people will share it in a mailing list summary after the event
+https://etherpad.openstack.org/p/BOS-forum-101: 32: * You can use ##<tag> to highlight anything that needs to be shared with a team not present in the session (e.g. ##uservoice, ##ironic) and a group of people will share it in a mailing list summary after the event
 
 https://etherpad.openstack.org/p/BOS-forum-developer-openstack-org: 15: ##uservoice <-- observations on the way C/PaaS, SDKs and AppProvisioning are used.
 
 https://etherpad.openstack.org/p/BOS-forum-developer-openstack-org: 63: ##uservoice @Flanders contact emily to get PoV.
 
-https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback: 54: 	* Delegating permissions and fixing admin-ness  ##uservoice
+https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback: 54: * Delegating permissions and fixing admin-ness  ##uservoice
 
-https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback: 57: 	* Debugging federation is a pain  ##uservoice
+https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback: 57: * Debugging federation is a pain  ##uservoice
 
-https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback: 59: 	* Document moving to wsgi ##uservoice
+https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback: 59: * Document moving to wsgi ##uservoice
 
-https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 45: 			* Is there any way/start point to integrate the tests from other community with tempest framework or plugin? ##uservoice
+https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 45: * Is there any way/start point to integrate the tests from other community with tempest framework or plugin? ##uservoice
 
-https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 48: 			* Is there ay framework or way to automate the configuration options for Tempest? ##painpoint  ##uservoice
+https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 48: * Is there ay framework or way to automate the configuration options for Tempest? ##painpoint  ##uservoice
 
-https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 53: 			* How we can visualize the test results? (success and fail counts)  ##uservoice
+https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 53: * How we can visualize the test results? (success and fail counts)  ##uservoice
 
-https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 71: 			* Changes in devstack many times break env  ##painpoint, ##uservoice, ##gap 
+https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 71: * Changes in devstack many times break env  ##painpoint, ##uservoice, ##gap
 
-https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 95: 		* Check status of services  ##newfeature, ##uservoice
+https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins: 95: * Check status of services  ##newfeature, ##uservoice
 
-https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 31: *Many very large operators, running highly available, complex OpenStack environments, are running on old versions of (OpenStack Icehouse, Juno, Kilo...). The reason is because upgrading is highly painful and stabilizing platforms has often been the greater priority. How can they catch up and realize the benefits found in current releases? ##uservoice ##newfeature 
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 31: *Many very large operators, running highly available, complex OpenStack environments, are running on old versions of (OpenStack Icehouse, Juno, Kilo...). The reason is because upgrading is highly painful and stabilizing platforms has often been the greater priority. How can they catch up and realize the benefits found in current releases? ##uservoice ##newfeature
 
-https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 77: 		* ##painpoint ##uservoice Never change a running system: if a release does not provide additional wanted functionalities, why do the risk in upgrading to this release?
+https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading: 77: * ##painpoint ##uservoice Never change a running system: if a release does not provide additional wanted functionalities, why do the risk in upgrading to this release?
 
 https://etherpad.openstack.org/p/BOS-forum-special-hardware: 72: ##uservoice Need a guide for how to manage GPUs in a cloud - best practices etc.
 

forum/201705-bos/TAG-vote.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 101: 		* OpenStack Shared|Special Interest Groups ##vote ##dialogue
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 101: * OpenStack Shared|Special Interest Groups ##vote ##dialogue
 

forum/201705-bos/TAG-wg.md

@@ -1,18 +1,18 @@
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 62: 	* ways to measure success/failure of proposed process(es)/plan(s)  ##uc ##wg
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 62: * ways to measure success/failure of proposed process(es)/plan(s)  ##uc ##wg
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 63: 	* Need a clear scope and goal  ##uc ##wg ##sig
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 63: * Need a clear scope and goal  ##uc ##wg ##sig
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 72: 		* working groups with a defined goal/dissolution vs. sigs/teams with an ongoing charter (example, from uc charter 'teams' vs 'working groups': https://governance.openstack.org/uc/reference/charter.html#structure-functional-teams )   ##wg ##sig
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 72: * working groups with a defined goal/dissolution vs. sigs/teams with an ongoing charter (example, from uc charter 'teams' vs 'working groups': https://governance.openstack.org/uc/reference/charter.html#structure-functional-teams )   ##wg ##sig
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 73: 		* make it clear that having a group complete its task and dissolve to move on to other tasks is acceptable/positive  ##wg ##sig
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 73: * make it clear that having a group complete its task and dissolve to move on to other tasks is acceptable/positive  ##wg ##sig
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 74: 		* We need to make sure those featrures get maintained by the dev after finishing the WG.  Would higher level group be the one to look after those long term? ##wg ##sig
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 74: * We need to make sure those featrures get maintained by the dev after finishing the WG.  Would higher level group be the one to look after those long term? ##wg ##sig
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 75: 	* how do we get on the agenda/cycle of a project  ##wg
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 75: * how do we get on the agenda/cycle of a project  ##wg
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 76: 		* people in the group put out resources and drive or influence from outside  ##wg
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 76: * people in the group put out resources and drive or influence from outside  ##wg
 
-https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 77: 		* finding ways to steer member companies contributing developers to focus on the identified goals  ##wg ##uc ##actionitem
+https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements: 77: * finding ways to steer member companies contributing developers to focus on the identified goals  ##wg ##uc ##actionitem
 
-https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 52: 			* Send request to WGs chair to review the list of members  ##uc ##wg
+https://etherpad.openstack.org/p/BOS-forum-user-committee-session: 52: * Send request to WGs chair to review the list of members  ##uc ##wg
 

forum/201705-bos/TAG-wgchairs.md

@@ -1,28 +1,28 @@
 https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 11: ##wgchairs - Feedback from session on best practices and areas for improvement
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 19: 			* Combined newsletter? ##best-practice ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 19: * Combined newsletter? ##best-practice ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 20: 			* An open session simliar to this one, but focused on the WG leads to spend a few minutes describing their group to the attendees might help ##best-practice ##wgchairs - let's always think about scale, i.e. why not describe the groups centrally and consistently communicate to point folks in addition
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 20: * An open session simliar to this one, but focused on the WG leads to spend a few minutes describing their group to the attendees might help ##best-practice ##wgchairs - let's always think about scale, i.e. why not describe the groups centrally and consistently communicate to point folks in addition
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 22: 			* Superuser TV/articles ##best-practice ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 22: * Superuser TV/articles ##best-practice ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 30: 				* weekly newsletter sent out to openstack-dev ML  ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 30: * weekly newsletter sent out to openstack-dev ML  ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 71: 			* made a brochure ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 71: * made a brochure ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 72: 			* made cards ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 72: * made cards ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 73: 			* made a presentation ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 73: * made a presentation ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 74: 			* submit a Summit BoF session to induct new members ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 74: * submit a Summit BoF session to induct new members ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 75: 			* Ask Flanders <flanders@openstack.org> ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 75: * Ask Flanders <flanders@openstack.org> ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 76: 			* Write a SuperUser article ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 76: * Write a SuperUser article ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 77: 			* have co-chairs in different countries, e.g. Scientific-WG has 3x co-chairs from Australia, UK and USA. ##best-practice  ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 77: * have co-chairs in different countries, e.g. Scientific-WG has 3x co-chairs from Australia, UK and USA. ##best-practice  ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 78: 			* have a WG social/party, e.g. Scientific-has a social each summit where it invites vendors to sponsor the drinks for the evening. ##best-practice ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 78: * have a WG social/party, e.g. Scientific-has a social each summit where it invites vendors to sponsor the drinks for the evening. ##best-practice ##wgchairs
 
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 79: 			* Involve the community by letting people know of the work we are doing (Meetups, conferences, small outreach)  ##best-practice ##wgchairs
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 79: * Involve the community by letting people know of the work we are doing (Meetups, conferences, small outreach)  ##best-practice ##wgchairs
 

forum/201705-bos/TAG-win.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 53: 			* being asked by NASA for help! ##win
+https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews: 53: * being asked by NASA for help! ##win
 

forum/201705-bos/TAG-wishlist.md

@@ -1,2 +1,2 @@
-https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 70: 				* How container intersect with OpenStack ##ewg ##wishlist
+https://etherpad.openstack.org/p/BOS-forum-enterprise-wg-working-session: 70: * How container intersect with OpenStack ##ewg ##wishlist
 

forum/README.rst

@@ -0,0 +1,18 @@
+Working with ##hashtag Program
+==============================
+
+* Retrieve etherpad content
+
+  $python get_etherpads.py
+
+  This will download list of etherpads to local directory.
+  Files are prefix with "PAD-<etherpad-name>".
+
+* Generate ##hashtag result
+
+  $python extract_tags.py
+
+  This will read the content from the list of downloaded files
+  from previous step, then extract the ##hashtag from each lines,
+  and output to a list of "TAG-<##hashtag>.md".
+

forum/extract_tags.py

@@ -0,0 +1,114 @@
+#    Licensed under the Apache License, Version 2.0 (the "License"); you may
+#    not use this file except in compliance with the License. You may obtain
+#    a copy of the License at
+#
+#         http://www.apache.org/licenses/LICENSE-2.0
+#
+#    Unless required by applicable law or agreed to in writing, software
+#    distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+#    WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+#    License for the specific language governing permissions and limitations
+#    under the License.
+
+#!/usr/bin/env python
+
+import re
+import os
+
+# remove all generated output file that begin with 'TAG' in filename
+def cleanup_files(dir_path):
+  files_to_remove = [ f for f in os.listdir(dir_path) if f.startswith("TAG") ]
+  for f in files_to_remove:
+    os.remove(f)
+
+# read all files that begin with 'PAD' in filename
+def get_files(dir_path):
+  files = [f for f in os.listdir(dir_path) if f.upper().startswith("PAD")]
+  # print files
+  return sorted(files)
+
+# write the generated output to a file, prefix with 'TAG' in filename
+def write_md_report(hashtag, etherpad, text, line_number):
+  with open ("TAG-" + hashtag + ".md", "a") as hashtag_file:
+    hashtag_file.write('%s: %d: %s\n\n' %(create_link(etherpad), line_number, text))
+
+# create the etherpad hyperlink
+def create_link(etherpad):
+  etherpad_link = "https://etherpad.openstack.org/p/" + etherpad
+  return etherpad_link
+
+# skip all lines beginning with these words,
+# which assumed to be the ##hashtag explanation notes
+def skip_line(line):
+  skip_words = [
+  '##<hashtag>',
+  '##hashtag',
+  '##newfeature - Proposal for a new feature',
+  '##gap - Feature gap that does not have a solution yet',
+  '##uservoice - Feedback from users and operators',
+  '##painpoint - Functional challenges/problems (either real or perceived)',
+  '##<workload-type>',
+  '##<project-name> ',
+  '##<working-group/team-name>']
+
+  for word in skip_words:
+    if line.find(word) != -1:
+      return 1
+
+  return 0
+
+# the main procedure
+# 1. Cleanup previously generated files that prefix with 'TAG'
+# 2. Read all files prefix with 'PAD'.
+#    These 'PAD' files are downloaded from 'get_etherpads.py'
+# 3. For every lines in each PAD files, extract the ##hastag
+# 4. Write the line with ##hashtag to a file 'TAG-<##hashtag>'
+def run():
+  dir_path = os.path.abspath('')
+
+  # Remove previously generated files
+  cleanup_files(dir_path)
+
+  hash_set = set([])
+
+  rep_chars = ["##", ":", ",", "+1", "?", "<", ">", "(", ")"]
+
+  # read each etherpad content, line by line
+  for file in get_files(dir_path):
+    with open (file, 'rt') as f:
+      line_number = 1
+
+      for line in f:
+        # trim whitespace characters
+        line = line.strip()
+
+        if skip_line(line) != 1:
+          try:
+            for hashtag in re.findall(r'#{2}\S*', line.lower()):
+              # hack to workaround ##hashtag that was not properly formed
+              # eg: '##something#action' instead of '##something #action'
+              # if hashtag.find('<') != -1:
+              #   print hashtag
+              for tag in hashtag.split('#'):
+                for char in rep_chars:
+                  tag = tag.replace(char, "").lower()
+
+                if tag != "":
+                  hash_set.add(tag)
+
+                  # the filename is the etherpad link that downloaded locally
+                  # prefix with 'PAD-'
+                  # simply replace 'PAD-' will give you the etherpad name
+                  write_md_report(tag, file.replace("PAD-",""), line,
+                    line_number)
+
+          except AttributeError:
+            line = ""
+
+        line_number += 1
+
+  print sorted(hash_set)
+
+if __name__ == "__main__":
+    run()
+

forum/get_etherpads.py

@@ -0,0 +1,54 @@
+#    Licensed under the Apache License, Version 2.0 (the "License"); you may
+#    not use this file except in compliance with the License. You may obtain
+#    a copy of the License at
+#
+#         http://www.apache.org/licenses/LICENSE-2.0
+#
+#    Unless required by applicable law or agreed to in writing, software
+#    distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+#    WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+#    License for the specific language governing permissions and limitations
+#    under the License.
+
+#!/usr/bin/env python
+
+import re
+import os
+import urllib2
+import urllib
+
+# remove previously downloaded files that prefix with 'PAD-'
+def cleanup_files(dir_path):
+  files_to_remove = [ f for f in os.listdir(dir_path) if f.startswith("PAD-") ]
+  for f in files_to_remove:
+    os.remove(f)
+
+def run():
+  dir_path = os.path.abspath('')
+
+  cleanup_files(dir_path)
+
+  # connect to a URL that contain list of etherpads
+  wiki = urllib2.urlopen("https://wiki.openstack.org/wiki/Forum/Boston2017")
+
+  # read html code
+  html = wiki.read()
+
+  # slice the needed section only
+  start_index = html.index("Event intro")
+  end_index = html.index("(old) Brainstorming");
+  html = html[start_index:end_index]
+
+  # use re.findall to get all the links
+  links = re.findall('"(https?://.*?)"', html)
+
+  for link in sorted(links):
+    if "etherpad" in link:
+      filename = "PAD-" + link.split('/')[-1]
+      url = link + "/export/txt"
+
+      urllib.urlretrieve(url, filename)
+
+if __name__ == "__main__":
+    run()
+