HubCAP - Revision history

DDlugiewicz56 at 08:42, 12 August 2020

2020-08-12T08:42:03Z

← Older revision		Revision as of 04:42, 12 August 2020
Line 1:		Line 1:
	<big>[[CAP_Innovation_Hub]]</big> <br/>		<big><big>[[CAP_Innovation_Hub]]</big> <br/></big>
	== <b>HUBCAP</b> <br /> ==		== <b>HUBCAP</b> <br /> ==

Line 33:		Line 33:
	crowdsourcing approach.		crowdsourcing approach.
	[[File:HUBCAP Logo.png\|200px\|thumb\|left\|HUBCAP Logo]]		[[File:HUBCAP Logo.png\|200px\|thumb\|left\|HUBCAP Logo]]
			<br/>
			<big><big>[[CAP_Innovation_Hub]]</big> <br/></big>

DDlugiewicz56 at 08:40, 12 August 2020

2020-08-12T08:40:11Z

← Older revision		Revision as of 04:40, 12 August 2020
Line 1:		Line 1:
	[[CAP_Innovation_Hub]] <br/>		<big>[[CAP_Innovation_Hub]]</big> <br/>
	== <b>HUBCAP</b> <br /> ==		== <b>HUBCAP</b> <br /> ==

DDlugiewicz56 at 15:41, 7 August 2020

2020-08-07T15:41:45Z

← Older revision		Revision as of 11:41, 7 August 2020
Line 1:		Line 1:
			[[CAP_Innovation_Hub]] <br/>
	== <b>HUBCAP</b> <br /> ==		== <b>HUBCAP</b> <br /> ==

Line 32:		Line 33:
	crowdsourcing approach.		crowdsourcing approach.
	[[File:HUBCAP Logo.png\|200px\|thumb\|left\|HUBCAP Logo]]		[[File:HUBCAP Logo.png\|200px\|thumb\|left\|HUBCAP Logo]]
	~~<br/><br/><br/>~~
	~~[[CAP_Innovation_Hub]]~~

DDlugiewicz56 at 15:39, 7 August 2020

2020-08-07T15:39:37Z

← Older revision		Revision as of 11:39, 7 August 2020
Line 32:		Line 32:
	crowdsourcing approach.		crowdsourcing approach.
	[[File:HUBCAP Logo.png\|200px\|thumb\|left\|HUBCAP Logo]]		[[File:HUBCAP Logo.png\|200px\|thumb\|left\|HUBCAP Logo]]
			<br/><br/><br/>
	[[CAP_Innovation_Hub]]		[[CAP_Innovation_Hub]]

DDlugiewicz56 at 15:39, 7 August 2020

2020-08-07T15:39:00Z

← Older revision		Revision as of 11:39, 7 August 2020
Line 32:		Line 32:
	crowdsourcing approach.		crowdsourcing approach.
	[[File:HUBCAP Logo.png\|200px\|thumb\|left\|HUBCAP Logo]]		[[File:HUBCAP Logo.png\|200px\|thumb\|left\|HUBCAP Logo]]

			[[CAP_Innovation_Hub]]

DDlugiewicz56 at 09:58, 3 August 2020

2020-08-03T09:58:07Z

← Older revision		Revision as of 05:58, 3 August 2020
Line 31:		Line 31:
	there will be no approval gates. These innovations will be evaluated through the same		there will be no approval gates. These innovations will be evaluated through the same
	crowdsourcing approach.		crowdsourcing approach.
	[[File:HUBCAP Logo.png\|thumb\|left\|HUBCAP Logo]]		[[File:HUBCAP Logo.png\|200px\|thumb\|left\|HUBCAP Logo]]

DDlugiewicz56 at 23:32, 30 July 2020

2020-07-30T23:32:34Z

← Older revision		Revision as of 19:32, 30 July 2020
Line 31:		Line 31:
	there will be no approval gates. These innovations will be evaluated through the same		there will be no approval gates. These innovations will be evaluated through the same
	crowdsourcing approach.		crowdsourcing approach.
			[[File:HUBCAP Logo.png\|thumb\|left\|HUBCAP Logo]]

DDlugiewicz56: /* hubCAP */

2020-07-30T23:08:29Z

hubCAP

DDlugiewicz56: /* hubCAP */

2020-02-06T01:08:09Z

hubCAP

← Older revision		Revision as of 21:08, 5 February 2020
Line 3:		Line 3:
	=== HubCAP…Announcing CAP’s new IT innovation portal! ===		=== HubCAP…Announcing CAP’s new IT innovation portal! ===

	Civil Air Patrol’s new innovation ~~program~~ is focused on highlighting and ~~scaling~~ innovative solutions that enhance mission execution and/or mission relevance ~~by honoring the contributions to innovation our members make every day~~. ~~HubCAP was designed~~ by the Technical Advisory Group – your Region IT leadership team~~. The new vehicle for sharing innovative ideas~~ will serve as an eServices ~~broker for~~ innovation ~~artifacts~~ with other CAP members. All active CAP members will have the ability to submit their ~~innovation artifacts~~ to the portal as well as browse the repository for posted solutions that may meet a local operational challenge ~~they are experiencing~~. HubCAP will be deployed in two phases:		Civil Air Patrol’s new innovation (HubCAP) is focused on honoring the contributions to innovation
			our members make every day by highlighting and making accessible innovative solutions that
	Phase 1: (Launched on 10 December)		enhance mission execution and/or mission relevance. Designed by the Technical Advisory Group –
			your Region IT leadership team, HubCAP will serve as an eServices repository where innovation
	Scope: IT solutions		solutions will be shared with other CAP members. All active CAP members will have the ability to
			submit their innovations to the portal, as well as browse the repository for posted solutions that
	How it works: Software developers who own a code repository, as are available in services such as GitHub, can submit a request to post a link on HubCAP. Members who submit their ideas will certify that their solution meets CAP regulation requirements and that they agree to allow free use of their solutions to other CAP members. The Technical Advisory Group will do a code ~~review and, if it presents~~ no security concerns, will approve the link. Members will then be able to access the code for reuse to support their local requirements. Members will also be able to rate the repository in order to assist others in identifying high value solutions. It is important to note that the TAG review is ~~only related to~~ security of the code. There is no evaluation of the “goodness” of an idea, no approval gates to pass. The goal is to determine the highest value solutions through ~~crowd sourcing~~ by members via their ratings and the volume of reuse.		may meet a local operational challenge. HubCAP will be deployed in two phases: <br/>
			Phase 1: (Launched on 10 December)<br/>
	Phase 2: (Spring Launch)		Scope: IT solutions<br/>
			How it works: Software developers who own a code repository, as are available in services such as
	Scope: Other Innovation Artifacts		GitHub, can submit a request to post a link on HubCAP. Members who submit their ideas will certify
			that their solution meets CAP regulation requirements and that they agree to allow free use of their
	How it works: HubCAP will be expanded beyond IT code, to allow for sharing of other types of innovative solutions. Again, members who submit their ~~artifacts~~ will ~~assert~~ that their solution does not violate CAP regulations and that they agree to allow free use of their solutions to CAP members. Approval for inclusion will be limited to cursory review for safety or security concerns but there will be no approval gates. These ~~artifacts~~ will be evaluated through the same ~~crowd sourcing~~ approach.		solutions to other CAP members. The Technical Advisory Group will perform a security review of
			linked code. If no security concerns are notated, the TAG will approve the link. Members will then
			be able to access the code for reuse to support their local requirements. Members will also be able
			to rate the repository in order to assist others in identifying high value solutions. It is important to
			note that the TAG review is focused on the security of the code, not functionality. There is no
			evaluation of the “goodness” of an idea, no approval gates to pass. The goal is to determine the
			highest value solutions through crowdsourcing by members via their ratings and the volume of
			reuse.<br/>
			Phase 2: (Spring Launch)<br/>
			Scope: Other Innovation Artifacts<br/>
			How it works: HubCAP will be expanded beyond IT code, to allow for sharing of other types of
			innovative solutions. Again, members who submit their innovations will certify that their solution
			does not violate CAP regulations and that they agree to allow free use of their solutions to CAP
			members. Approval for inclusion will be limited to cursory review for safety or security concerns but
			there will be no approval gates. These innovations will be evaluated through the same
			crowdsourcing approach.

DDlugiewicz56: Created page with "== hubCAP
== === HubCAP…Announcing CAP’s new IT innovation portal! === Civil Air Patrol’s new innovation program is focused on highlighting and scaling i..."

2020-01-30T17:13:19Z

Created page with "== hubCAP == === HubCAP…Announcing CAP’s new IT innovation portal! === Civil Air Patrol’s new innovation program is focused on highlighting and scaling i..."

New page

== hubCAP ==

=== HubCAP…Announcing CAP’s new IT innovation portal! ===

Civil Air Patrol’s new innovation program is focused on highlighting and scaling innovative solutions that enhance mission execution and/or mission relevance by honoring the contributions to innovation our members make every day. HubCAP was designed by the Technical Advisory Group – your Region IT leadership team. The new vehicle for sharing innovative ideas will serve as an eServices broker for innovation artifacts with other CAP members. All active CAP members will have the ability to submit their innovation artifacts to the portal as well as browse the repository for posted solutions that may meet a local operational challenge they are experiencing. HubCAP will be deployed in two phases:

Phase 1: (Launched on 10 December)

Scope: IT solutions

How it works: Software developers who own a code repository, as are available in services such as GitHub, can submit a request to post a link on HubCAP. Members who submit their ideas will certify that their solution meets CAP regulation requirements and that they agree to allow free use of their solutions to other CAP members. The Technical Advisory Group will do a code review and, if it presents no security concerns, will approve the link. Members will then be able to access the code for reuse to support their local requirements. Members will also be able to rate the repository in order to assist others in identifying high value solutions. It is important to note that the TAG review is only related to security of the code. There is no evaluation of the “goodness” of an idea, no approval gates to pass. The goal is to determine the highest value solutions through crowd sourcing by members via their ratings and the volume of reuse.

Phase 2: (Spring Launch)

Scope: Other Innovation Artifacts

How it works: HubCAP will be expanded beyond IT code, to allow for sharing of other types of innovative solutions. Again, members who submit their artifacts will assert that their solution does not violate CAP regulations and that they agree to allow free use of their solutions to CAP members. Approval for inclusion will be limited to cursory review for safety or security concerns but there will be no approval gates. These artifacts will be evaluated through the same crowd sourcing approach.

← Older revision		Revision as of 19:08, 30 July 2020
Line 1:		Line 1:
	== <b>~~hubCAP~~</b> <br /> ==		== <b>HUBCAP</b> <br /> ==

	=== ~~HubCAP…Announcing~~ CAP’s new ~~IT innovation~~ portal! ===		=== HUBCAP…Announcing CAP’s new Innovation portal! ===

	Civil Air Patrol’s new innovation (~~HubCAP~~) is focused on honoring the contributions to innovation		Civil Air Patrol’s new innovation (HUBCAP) is focused on honoring the contributions to innovation
	our members make every day by highlighting and making accessible innovative solutions that		our members make every day by highlighting and making accessible innovative solutions that
	enhance mission execution and/or mission relevance. Designed by the Technical Advisory Group –		enhance mission execution and/or mission relevance. Designed by the Technical Advisory Group –
	your Region IT leadership team, ~~HubCAP~~ will serve as an eServices repository where innovation		your Region IT leadership team, HUBCAP will serve as an eServices repository where innovation
	solutions will be shared with other CAP members. All active CAP members will have the ability to		solutions will be shared with other CAP members. All active CAP members will have the ability to
	submit their innovations to the portal, as well as browse the repository for posted solutions that		submit their innovations to the portal, as well as browse the repository for posted solutions that
	may meet a local operational challenge. ~~HubCAP~~ will be deployed in two phases: <br/>		may meet a local operational challenge. HUBCAP will be deployed in two phases: <br/><br/>
	Phase 1: (Launched on 10 December)<br/>		Phase 1: (Launched on 10 December)<br/>
	Scope: IT solutions<br/>		Scope: IT solutions<br/>
	How it works: Software developers who own a code repository, as are available in services such as		How it works: Software developers who own a code repository, as are available in services such as
	GitHub, can submit a request to post a link on ~~HubCAP~~. Members who submit their ideas will certify		GitHub, can submit a request to post a link on HUBCAP. Members who submit their ideas will certify
	that their solution meets CAP regulation requirements and that they agree to allow free use of their		that their solution meets CAP regulation requirements and that they agree to allow free use of their
	solutions to other CAP members. The ~~Technical Advisory Group~~ will perform a security review of		solutions to other CAP members. The Innovation Pit Crew will perform a security review of
	linked code. If no security concerns are notated, the TAG will approve the link. Members will then		linked code. If no security concerns are notated, the TAG will approve the link. Members will then
	be able to access the code for reuse to support their local requirements. Members will also be able		be able to access the code for reuse to support their local requirements. Members will also be able
Line 22:		Line 22:
	evaluation of the “goodness” of an idea, no approval gates to pass. The goal is to determine the		evaluation of the “goodness” of an idea, no approval gates to pass. The goal is to determine the
	highest value solutions through crowdsourcing by members via their ratings and the volume of		highest value solutions through crowdsourcing by members via their ratings and the volume of
	reuse.<br/>		reuse.<br/><br/>
	Phase 2: (~~Spring Launch~~)<br/>		Phase 2: (August 2020)<br/>
	Scope: Other Innovation Artifacts<br/>		Scope: Other Innovation Artifacts<br/>
	How it works: ~~HubCAP~~ will be expanded beyond IT code, to allow for sharing of other types of		How it works: HUBCAP will be expanded beyond IT code, to allow for sharing of other types of
	innovative solutions. Again, members who submit their innovations will certify that their solution		innovative solutions. Again, members who submit their innovations will certify that their solution
	does not violate CAP regulations and that they agree to allow free use of their solutions to CAP		does not violate CAP regulations and that they agree to allow free use of their solutions to CAP

HubCAP - Revision history

DDlugiewicz56 at 08:42, 12 August 2020

DDlugiewicz56 at 08:40, 12 August 2020

DDlugiewicz56 at 15:41, 7 August 2020

DDlugiewicz56 at 15:39, 7 August 2020

DDlugiewicz56 at 15:39, 7 August 2020

DDlugiewicz56 at 09:58, 3 August 2020

DDlugiewicz56 at 23:32, 30 July 2020

DDlugiewicz56: /* hubCAP */

DDlugiewicz56: /* hubCAP */

DDlugiewicz56: Created page with "== hubCAP == === HubCAP…Announcing CAP’s new IT innovation portal! === Civil Air Patrol’s new innovation program is focused on highlighting and scaling i..."

DDlugiewicz56: Created page with "== hubCAP
== === HubCAP…Announcing CAP’s new IT innovation portal! === Civil Air Patrol’s new innovation program is focused on highlighting and scaling i..."