Rename to SpecSharp? #194
Replies: 1 comment 2 replies
-
Thank you @markdav-is for the feedback. We have spent a lot of time with the naming. It is always hard. We have also considered many "Spec*" product names, including SpecSharp, but finally decided to not have a "Spec" prefix for several reasons:
At the end, it was a decision. I'm not sure it was the right one, but at least it was well thought. And I also had to realize that "renaming a product" is a horrible effort, much more than I expected (I have spent around 40 days). So I don't think it is economical to make another rename at this time, sorry. So my suggestion would be not to reopen the naming topic, but admit the situation we have now and concentrate to feature improvements. It took me some time to get used to the new name, but after a couple of month of working, now I automatically say Reqnroll when I think of it. So it will take time (I expect the full migration in the community to last for 2 years), but it will work. |
Beta Was this translation helpful? Give feedback.
-
I respect the big lift it is to name a product. We've been switching from SpecFlow to Reqnroll this year. Everyone stumbles over the name and we still refer to it as SpecFlow for the most part. On a whim I looked to see if SpecSharp.com was available today and it is. I'm going to grab that domain with the sole intention of giving it to this project and helping with a rename if the core team feels that would be a better name.
Beta Was this translation helpful? Give feedback.
All reactions