Team - ja-guzzle/guzzle_docs GitHub Wiki
| Sr. No. | Team Member | Role | Details |
|---|---|---|---|
| * | Parth Mistry [email protected] | Solution Architect | He runs the solution design, manages build team, code quality, and detail design. Leads UI 2.0 changes and Architecture changes specically from devlivery standpoint |
| * | Gopal Ghanghar [email protected] | Lead | PQE, Leads Guzzle Security changes for Q2. And finally does R&D for new areas/techs we want to bring into Guzzle |
| * | Arpan Shah [email protected] | Developer | Contributes to build work of UI changes |
| * | Nikhil Tuck [email protected] | Developer | Contributes to build work of UI changes and/or any core modulse of Guzzle |
| * | Dashrath Gelot [email protected] | Developer | Contributes to build work of UI changes |
| * | Navin Gelot [email protected] | Developer | Dev-ops lead for Guzzle. Takes over existing Test-suite and makes sure its brought to completeness soon - we can do right refactoring of the current testcases and ensure we have good coverage and speed to build new testcases. We can go higher order from current features if that helps. Identify and build additional glue code /supports of missing technologies |
| * | Krunal Prajapati [email protected] | Developer | Assist's Navin in completing the test-suite |
| * | Mehul Rathod [email protected] | UI Designer | Looks at UX/UI for Guzzle |
| * | Pranav Shukla [email protected] | Solution Advisor | Playing consultant role to rest of Guzzle team ensuring they are getting right set of guidance on all the design and architecture decisions |
| * | Umesh Kakkad [email protected] | Product Manager | Product manager of pan-guzzle product suite. Will define all the specs, approve UI mockup, and key architectural decisions |
| * | Hemanta Banerjee [email protected] | Sponsor | Apart from approving the spending, ensure what is coming out is sellable and sustainable (extendable, deploy-able etc) |
Guzzle team -
Not very formal though. I wanted to pin down the primary hat that we will wearing though most of us will cut-across many roles.
Team - please ensure you define/refine your role.
| Sr. No. | Team Member | Role | Details |
|---|---|---|---|
| * | Hemanta Banerjee [email protected] | Sponsor | Apart from approving the spending, ensure what is coming out is sellable and sustainable (extendable, deploy-able etc) |
| * | Umesh Kakkad [email protected] | Program Manager | We may have few product manager (in future :) ), hence a program manager to own pan-guzzle product suite. Will contribute in other fronts as well including seeding the initial set of specs |
| * | Al John Mangahas [email protected] | Product Manager | having build first generation JA frameworks, John will box the functionalities that goes into each modules. Will also help out in the build as well. Also looks at manual testing of the modules and few of the admin bits |
| * | Jahan Balasubramaniam [email protected] | Product Manager | With vast experience of building similar framework Jahan will also play key role defining the specs, validate the devops and CI, technical design review. Jahan will be one of implmenter of Guzzle for real customer - so I expect him to give the first hand customer feedback |
| * | Rishav Sharma [email protected] | Pre-Sales Lead | With vast experience in data integration Rishav will contribute to the specs, techincal design and dev-ops review. He will be one who will test ride Guzzle for pre-sales /POC engagements. |
| * | Pranav Shukla [email protected] | Solution Architect | Though playing oversight role, we want Pranav to lead design and overall architecture of Guzzle along with Parth and selected help from Jahan, Umesh and Rishav |
| * | Parth Mistry [email protected] | Technical Lad | He runs the build and detail deign. |
| * | TBD | Developer | Detail design and build |