On Tue, Jan 3, 2017 at 8:57 AM, Pierre Smits <pierre.sm...@gmail.com> wrote:
> It will increase the workload on our volunteers > contributing, as the impact is far reaching: not only our documentation > must be revisited, but also elements in JIRA must be renamed. Our potential > adopters, and new comers in the development field will get confused, as > books out there are not in sync anymore. > This is not a direct response to Pierre's message: I am replying to some of the concepts because they are a good representation of a line of thought. Backward compatibility and the impact of change is always a factor for a software with 10+ years history and thousands of consumers. However in general I am not too concerned by the negative impact of change, even if it is about "minor" stuff like improving the name of our artifacts (like in this case): new consumers will judge our products by what they see now and if we have a cleaner system with better names then they will get a better feel. Existing books and materials will still be valid for the versions of the software they have been written for and the new version will open the opportunity to write new and improved versions of them (sell new copies, get new visits etc...). Of course existing consumers, that are used to the current codebase, may get some confusion initially but this community will help them: in fact the change may open drive more active people in the community. Jacopo
