psf-test-tcm's People
psf-test-tcm's Issues
Phase 3.2: Upload outputs of solution validation meeting
- Upload video of solution demo to
demo
folder with filenamedemo-video
Upon completion, test will be launched to confirm file has been uploaded
Phase 4.4: Validate published solution and close out project
To be completed by AWS PSA
Phase 4.3: Schedule solution publishing meeting
2 to 3-hour meeting with the following objectives:
1. Review Inputs:
a. Review the SIM submission
b. Review customer need
c. Review solution requirements
d. Partner demos solution
2. Plan listing and deployment strategy
3. List solution on AWS Solutions Library (for searchability) as well as AWS Marketplace and/or Partner's own website for purchasing.
a. For listing on AWS Marketplace, follow the Integration & Automation (I&A) team's AWS Builder Platform [Link TBD]
Phase 2.1: Schedule build kickoff workshop
2 to 3-hour meeting with the following objectives:
1. Review Inputs:
a. Review the SIM submission
b. Review customer need
c. Review solution requirements
d. Review solution design proposal including architecture diagram
2. Define MVP Solution and performance criteria and whether the partner wants to proceed to the next Build Hub phase (Validation) where we will validate their solution.
3. Define published solution capabilities and deployment/support method
4. Identify additional technical resources needed for build phase which may include:
a. Public and internal technical resources (V-Team SAs will select these)
b. Introduction to additional partners
c. Introduction to internal AWS builder teams
d. Introduction to ProServe
Phase 0.1: Submit SIM Ticket URL
Share the URL of the SIM ticket that was created for this PSF solution proposal
Upon completion, test will be launched to confirm file has been uploaded
Phase 4.1: Submit PR for merge with main branch
PR will launch remaining static and automated tests on project. All project files must be uploaded to the repository for validation.
Phase 1.2: Review architecture diagram
To be completed by AWS PSA
Phase 2.2: Upload outputs of build kickoff workshop
- Upload Solution User Guide to
guides
directory with filenamesolution-user-guide
- Upload finalized architecture diagram to
architecture
folder with filenamearchitecture-diagram-final.ppt
Upon completion, test will be launched to confirm file has been uploaded
Phase 1.1: Upload architecture diagram
Upload architecture diagram to architecture
folder with filename architecture-diagram.ppt
Upon completion, test will be launched to confirm file has been uploaded
Phase 3.1: Schedule solution validation meeting
2 to 3-hour meeting with the following objectives:
- Completion of validation meeting (2-3 hours)
a. Review Inputs:
i. Review the SIM submission
ii. Review customer need
iii. Review solution requirements
iv. Review solution design proposal including architecture diagram
v. Partner demos solution
b. Identify any issues that need to be addressed
c. Provide additional technical resources needed to addresses issues which may include:
i. Public and internal technical resources (V-Team SAs will select these)
ii. Introduction to additional partners
iii. Introduction to internal AWS builder teams
iv. Introduction to ProServe - Partner team addresses solution issues
- Validate finalized solution including deployment/support strategy
Phase 1.3: Create BuilderSpace project
To be completed by AWS PSA
- Create BuilderSpace project
- Add all relevant documents and links
- Decide which SAT team (and the corresponding TFC (Industry or Technical or both) is the best fit)
- Contact SAT PSF team lead (within Shashi’s team) directly with BuilderSpace link and confirm they can help.
- List matching TFC community in the BuilderSpace project
- Wait for SAT team (working in conjuction with their TFC) to confirm the project
- Proceed forward with the project phases (1: Design, 2: Build, 3: Validate, 4: Publish)
- Now any internal team (SAs PDMs, IBUs, etc.) have visibility into what projects are underway using a simple, existing mechanism (https://builderspace.proto.sa.aws.dev/).
Phase 4.2: Merge PR into main branch
To be completed by AWS PSA
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.