Project Meeting July 2021

July 7 2021, 2:00 ET / 11:00 PT

Present: Jung, Samantha (recording), Eileen, Jess, Rebecca, Cori, Paul, Andrew, Cassie, Junette Regrets: Michael B, Aaron, Patrick

Icebreaker:

Tell us about a unique dessert in your location!

Updates:

• Paul was on the Developer podcast discussing Snowfakery
• Snowfakery training session on Friday (7/9) will include training session, demo and Q&A. 75 people have signed up.
• Snowfakery 2.0 is scheduled to launch tomorrow (7/8). Main changes include: (1) multi-processor (faster for large data loads); (2) new command line syntax; (3) ability to pull data from an org into a recipe - you can match new data to existing data; (4) new documentation for localized fake data; (5) some more minor things
• Jung is updating her recipe once per month. How to populate contact to campaign member by creating dependent objects underneath parent object. Bulkifying recipes using the command instead of the recipe. A lot of orgs have standard/persistent data (like Campaign Member Status values) so being able to pull in data from an org will be super userful, especially
• Sprint was a huge success - ~16 PRs [pull requests] which is LOT of amazing contributions. We focused entirely on Snowfakery recipe generation/cleanup this time around and did not put energy into docs/marketing/UX projects.
• Sprint report back from Eileen: completed most of the CCI trail (trailhead) prior to the sprint. Junette led the learning group. Even though she didn't know what was going on, she had lightbulb moments - the review session was really helpful - and then Eileen found a bug in a recipe and was able to contribute back to the project right away. Learned about branches and pull requests. "I don't know what I'm doing but I'm already being useful!" On the second day, she got to practice more Snowfakery and Github skills.

Agenda item: Q: Should we move split Snowfakery recipes into a stand-alone repo? A: Yes

• We previously moved recipes OUT of the Snowfakery Repo and into the Community Project repo. Now we are considering splitting the Community Project repo into two. One for Snowfakery Recipes, one for Data Gen project.
• Q: Does this have an impact on recipes being out of date with respect to CCI/Snowfakery updates? A: No, if there are problems with backwards compatibility, we will still have them either way.
• Q: Should we have different repos for each product? A: That would make some things easier, but other things harder. Decision: Stick with one recipe repo for now.
• Pros: (1) more direct access to recipes and easy access without clutter; (2)
• Cons: (1) short term more work; (2) slightly more work to explain what's going on with new contributors
• Steps: (1) email Cori to make a new repo; (2) fill out ReadMe; (3) move recipes to new repo; (4) update original repo to reference new repo

Questions/follow up:

• Is it possible to follow changes in a Pull Request? (Yes, but once it is merged, you can't follow changes to that specific file or line of code anymore)
• Q: Cori has a question for Paul about granting access to repos; A: we can have a "Group" that grants access to both of our repos
• Q: What is the most efficient way to spin up scratch orgs for testing Snowfakery recipes? A: ????
• Q: Would using MetaCI make things easier for us? A: Unclear if this product is available for community projects. Cori/Paul will follow up.
• We have a bunch of stale PRs. Jess volunteered to sweep. Paul mentioned that they might be waiting for the contributor to make further changes (ie not waiting on approval from us)