Prep Pantry
What is Prep Pantry?
Prep Pantry is a process for Product teams to work with Data Platform Engineering and Data Persistence SRE to launch faster and safely by building on curated and well-supported architectures for data processing and serving.
Is Prep Pantry right for you?
✓ If you're a Product Manager working on a new experience and thinking of:
- Using cross-wiki user activity, like "How many people have seen an article edited by the user?"
- Extracting structured information from article contents or metadata, like "Which paragraphs are lacking references?"
- Providing low-latency feedback loops, like "Notify a user when a page they've recently edited is trending."
✓ If you're an engineer working with a Product Manager and:
- You're considering Maintenance Scripts or the Job Queue to transform large amounts of data.
- You're considering loading data from outside of MediaWiki into MariaDB so you can access it from MediaWiki.
✗ You don't need us if you are already working with the Machine Learning team to develop and serve ML-based experiences. The ML team already collaborates with us directly.
What you get from Prep Pantry
We want to help you:
- Write a technical design for your experience, building on curated and well-understood architectures.
- Onboard into individual pieces of that architecture so you can focus on your logic and experimentation.
You'll come out of the Prep Pantry with:
- A reliable production-ready setup for your launch! 🚀
- Fewer product compromises: we can help you process and serve more data, in more interesting ways, to more users.
- Clear support stories, with Service Level Objectives that guarantee things like:
- Uptime (API availability), so your experience is there when users need it.
- Latency (API response time), so your experience feels fast and responsive.
- Data freshness and quality, so you know users will see accurate and up-to-date information.
- Defined ownership status for your production components.
How to engage Prep Pantry
We're can help in different ways, depending on where you are in the product lifecycle. Consider this simplified model:
- Kickoff: Brainstorming, ideation. The main user journey and scoping decisions are being made.
- Prototype: A proof of concept or early A/B test not requiring a full production setup.
- Design: The engineering team is working on a technical design for the production feature.
- Implementation: The engineering team is implementing the design.
- Scaling: The feature is being enabled on one or more wikis.
- Retrofit: The feature is deployed, operational and scaled, but has operational or functional shortcomings.
Here's how to reach us and how we can help:
| Where you are | What we do | How to reach us |
|---|---|---|
| Kickoff | 🟢 We love to get involved early!
👩🍳 Have you checked out Test Kitchen? |
Please reach out to Guilherme. |
| Prototype | ||
| Design | 🟢This is our main entry point!
|
Please use our intake form. |
| Implementation | 🟡 We may need to go back to the drawing board.
|
TODO(Guilherme): Ticket template. |
| Scaling | 🔴 We currently don't support this stage as we are focusing on helping teams build new experiences. | N/A |
| Retrofit | 🔴 We currently don't support this stage as we are focusing on helping teams build new experiences. | N/A |
Prep Pantry and the APP
We prefer to structure our work using the Annual Planning Process by owning or collaborating on Hypotheses under existing KRs, and will give precedence to projects tracked under this system. We'll recommend specific hypotheses along the process.
Please ensure KR owner for your project is aware of Prep Pantry and willing to integrate our work into their planning.
Projects
We usually publish user and technical documentation for completed projects to this wiki.
See Category:Prep Pantry Projects for an index of those.