Skip to content

Project Team Meeting June 2023

Allison Letts edited this page Jun 9, 2023 · 7 revisions

Present

Paul P, Jung M, Aaron C, Eileen K, Jennifer C, Jay D, Cori O

The main topic of discussion was reviewing Goals List started last meeting.

Goal: Develop new sample recipes for new Cloud data models

  • Education Cloud (data model available now)
  • Nonprofit Cloud (data model not yet released to the community, only to partners)

Goal: Finish plug-in things related to Educ + NP data

  • Paul created a Pull Request to Add educational and non-profit fakers; though it is not yet merged (Ref. https://github.com/SFDO-Tooling/Snowfakery/pull/897 )
    • It includes realistic-sounding school names, nonprofit org names, departments
    • The merge process should automatically update the Snowfakery documentation (but we'll check to make sure, then promote the news widely)
  • Allison, Aaron, and Paul are still working on Diverse name provider

Goal: Update outdated documentation

  • Update outdated documentation
  • in our project Wiki, Python version has been updated to say version 3.10 (Ref. https://github.com/SFDO-Community-Sprints/DataGenerationToolkit/wiki/Monthly-maintenance-tasks-for-Data-Gen-Toolkit-volunteers)
  • in the Trailhead (Unit Install CumulusCI) it no longer refers to Python, instead it provides a link to CumulusCI's official documentation
  • in CumulusCI's official documentation, it says: Download the latest Python 3.9 release; should say 3.10
  • Aaron is recommending that Windows users go with one release prior to the latest Python release (especially the first few months after new Python comes out, which is typically October each year, until CCI gets updated, which is typically later November)
  • Eileen (working on Windows) offered to help Paul in working on updating the installation docs for Windows
    • Specifically, many of the screenshots are from an older edition and need updating
    • Also: Dear Python Project.  That box should be checked by default!

Goal: Ease the onboarding path for new Snowfakery users

  • Aaron described recently helping an MVP get started in Snowfakery, suggested a useful addition to our recipe library would be a narrative introduction and a suggested navigation path starting with a small number of the simplest recipes, then let the user proceed on their own path
  • This is still fairly new so I'm repeating it here: Allison created a new tag for “onboarding” issues (suggested improvements) in our repo
  • Ideas for including Snowfakery and/or Data Generation in future Sprint events
    • People can review and test the ‘getting setup’ process and documentation and make notes about where they are getting stuck, because that seems to be a pain point and you would have a base of users with no existing installs to get info from
    • Or having tasks that anyone can contribute to if they don’t have experience…what docs or processes can people review or test?

Salesforce vs non-Salesforce use of Snowfakery

  • Snowfakery documentation is good in a way that it is not centered around Salesforce. Maybe expand the SF examples there?
  • Should we keep up the effort to have Snowfakery be generic and not primarily (or exclusively) geared to Salesforce?
  • This discussion to be continued in future meetings.

Continue with regular monthly meetings 😊

  • Next meeting is TBD, as we may have a combined July-August meeting for the summer. Stay tuned!
Clone this wiki locally