**WE ARE CHANGING OUR NAME** Vote Now on the New Name for our Standard #20
Replies: 3 comments 3 replies
-
Thank you for opening the discussion. I'm surprise to see that there is the word "food" in every proposed name. I thought we agree that the standard was also designed to support non food items (like soap or jewelry for instance)? Also I'm wondering if "data standard" is a good choice because the standard is also defining technical rules (so for me it's more than rules only on data). I have some questions and remarks about the voting procedure. I'm confused about what this vote will lead to? Is it something official? For now as we didn't work on any procedures, I would consider this vote only as a survey. Moreover we don't see who has voted, right? And we did not define who is eligible to vote (maybe we forgot some people?). What happen if someone propose an alternative name? Do we vote again? I would also like to propose to use the Majority judgment which allow to give a note to the different choices. What do you think? |
Beta Was this translation helpful? Give feedback.
-
Hi all - as I mentioned on a call with Garethe, Maxime, and Baptiste today - I fully understand and support the rationale behind the name change idea, but I would like to suggest that we consider holding off on an official name change for at least another 6 - 12 months. In North America, we are just now building serious interest in adopting and supporting the 'DFC standard,' particularly in the context of the OpenTEAM ecosystem. Changing the name at this particular point in time would be really inconvenient. The work we’ve been doing to promote engagement and adoption of the 'DFC standard' over the last couple of years is gathering momentum quickly in the context of OpenTEAM's USDA-funded Partnerships for Climate-Smart Commodities project, which OFN and Startin’Blox offically joined this quarter: https://www.wolfesneck.org/partnerships-for-climate-smart-commodities/. I'd really rather avoid confusing people, by changing the standard’s name right at the moment when they are getting interested in it, and starting to understand what it could do to support their own work and initiatives. I think it would be much more productive if we just focused our energies on promoting adoption and financial and technical support for the standard, rather than spending a lot of hours clarifying that, “Yes, the ‘new SFSDS’ is actually the ‘old DFC standard’” etc… over and over again in a variety of different contexts. Along the same lines: I think it would be smart to look at any name change as a major rebranding exercise that has to be planned, financed, and maintained. Simply choosing the new name seems like the easy part to me. Communicating the name change, and ensuring that people understand the underlying continuity between the new ‘SFSDS standard’ and the old ‘DFC standard’ will be the hard part. (A name change would also likely necessitate the creation and maintenance of a new 'SFSDS' website. Who would take this on? With what budget and HR resources?) In my opinion, the particular string of letters that we use to name the standard is way less important than the fact that people understand what we mean when we use these letters. Given resource contraints, I think we should keep our energies focused on the essential things - and return to dicussion of rebranding and renaming at such a time as we have a budget and strategy to support that work in an ongoing and sustainable way. |
Beta Was this translation helpful? Give feedback.
-
This has been shelved for now due to lack of bandwidth within the team. |
Beta Was this translation helpful? Give feedback.
-
In the previous discussion (#14), everyone supported the idea that we need a new name, so @RachL & I have kicked a few ideas around and come up with some options (more details are in this jamboard). We hope you like at least one of them, but if not... please suggest alternatives in the comments!
A few notes on the options we came up with:
Option 1 draws on the EU standardisation around the term "Short Food Systems" and could help us make sense in that space.
Option 2 was inspired by the work of one of our partners in the UK Food Data Collaboration project: Duncan Catchpole (of Cambridge Organic Food Co) has written about Local Food Ecosystems as the future of food. There is also an amazing film from Scotland: Rooted that talks about LFE's
Option 3 comes from comments by some of our partners that the TLA "DFC" has been difficult to get people to notice & remember, but now they are remembering it, it would be preferable not to change it.
Option 4 draws on the work done by Growing Communities in the UK around Food Zones, which are very applicable to what we're trying to support with the standard.
Important
This poll will be open for 2 weeks (until Tuesday 5th March/Mardi 5ème Mars), please submit your votes (& comments) before then.
9 votes ·
Beta Was this translation helpful? Give feedback.
All reactions