HubCAP: Difference between revisions

From CAPipedia
VisualWikitext
DavidDlugiewicz (talk | contribs)
CAP/FUG, CAP/TAG, Bureaucrats, Administrators
418 edits
Created page with "== <b>hubCAP</b> <br /> == === HubCAP…Announcing CAP’s new IT innovation portal! === Civil Air Patrol’s new innovation program is focused on highlighting and scaling i..."
 
DavidDlugiewicz (talk | contribs)
CAP/FUG, CAP/TAG, Bureaucrats, Administrators
418 edits
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
== <b>hubCAP</b> <br /> ==
<big><big>[[CAP_Innovation_Hub]]</big> <br/></big>
== <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 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/><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 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
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/><br/>
Phase 2: (August 2020)<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.
[[File:HUBCAP Logo.png|200px|thumb|left|HUBCAP Logo]]
<br/>
<big><big>[[CAP_Innovation_Hub]]</big> <br/></big>

Latest revision as of 03:42, 12 August 2020

CAP_Innovation_Hub

HUBCAP

HUBCAP…Announcing CAP’s new Innovation portal!

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 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 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 may meet a local operational challenge. 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 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 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.

Phase 2: (August 2020)
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 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.

HUBCAP Logo


CAP_Innovation_Hub

Retrieved from "https://capipedia.cap.gov/index.php?title=HubCAP&oldid=459"