We had a discussion about getting a Shepherd to assist with Structured streaming SPIP a few hours ago.
As an active member I am proposing a move to replace the current terminology "SPIP Shepherd" with the more respectful and inclusive term "SPIP Mentor." We have over the past few years have tried to replace some past terminologies with more acceptable ones. While some may not find "Shepherd" offensive, it can unintentionally imply passivity or dependence on community members, which might not accurately reflect their expertise and contributions. Additionally, the shepherd-sheep dynamic might be interpreted as hierarchical, which does not align with the collaborative and open nature of Spark community. *"SPIP Mentor"* better emphasizes the collaborative nature of the process, focusing on supporting and guiding members while respecting their strengths and contributions. It also avoids any potentially offensive or hierarchical connotations. Great if you share your thoughts and participate in discussion to consider this proposal and discuss any potential challenges or solutions during the transition period.in SPIP (assuming we accept this or another alternative proposal). HTH Mich Talebzadeh, Dad | Technologist | Solutions Architect | Engineer London United Kingdom view my Linkedin profile <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> https://en.everybodywiki.com/Mich_Talebzadeh *Disclaimer:* The information provided is correct to the best of my knowledge but of course cannot be guaranteed . It is essential to note that, as with any advice, quote "one test result is worth one-thousand expert opinions (Werner <https://en.wikipedia.org/wiki/Wernher_von_Braun>Von Braun <https://en.wikipedia.org/wiki/Wernher_von_Braun>)".
