Hi,@Bug: Thanks for taking the time to answer my questions.
The questions I raised are the ones I asked myself before deciding to go for the module name changes. Reviewing your answers to my three questions, you basically came to the same conclusion. There is no direct consequence for users e.g. issues with backward incompatible changes etc., which would have been a no go for me.
What made me a bit "angry" was your offending way of asking for the reason of the name change instead of formulating your question in a more polite and neutral way (without words like stupid) as you demanded for yourself in one of your last posts quoted below. Similar to your answer, I do not change module names just for fun and without considering possible side effects for users and customers beforehand.
Dear stefek, What justifies the name change:
... redirecting me to google kinda pisses me off as it suggests you think i am choosing the easy way and whitout thinking just putting in nonsense questions, this kind of behaviour here does not do much good to the reputation of the whole community.
I took over responsibility for my modules Anynews, Addon-File-Editor and Postits in February this year, after maintenance by previous forum members has stagnated for about 1.5 years and "modified" module versions with adaptions for latest WebsiteBaker or jQuery versions, and/or backwards incompatible changes (e.g. Anynews versions with changed function parameters) were spread around via the forum.
As a consequence, I decided in Februar 2012, to "fork" my own modules at GitHub to give them a new home with a public repository for better code and feature request tracking and easier possibilities for contributions (via GitHub fork/pull mechanism etc.), instead of the very user unfriendly way of searching the forum for "patches" and "latest versions". With the first new releases, I increased the major module version number to the next higher integer number to make the "fork" and the new start of maintenance support "visible". At this point in time I thought increasing the major version number would be sufficient.
A name change takes place most of the times in case of forking. AnyNews is a well known and long lasting module, so a name change should have a real purpose. If this version differs very much from the previous ones, you could see it as a fork, leaving regular AnyNews as it is.
Since February 2012, I added around 46'000 and removed 31'000 code lines from Anynews
(including Twig, header changes etc.).The list below gives a brief overview of the "new features" added since February:
- updated jQuery file inclusion to work with newer WB versions
- added new jQuery slider plugin: "Flexslider"
- made jQuery Plugins customizable without touching external plugin files
- moved all hardcoded Anynews output to template files
- fixed broken sort by comments feature added by another forum member
- added option to filter news not only by group but also by: page, section, and post id
- added option to filter news by page language
- introduced the much more flexible template parser Twig
- updated all templates to Twig
- reworked the entire README
The name change is finally a result of all the work I put into the "forked module" since February 2012, plus some branding with my domain cwsoft.de, plus the fact that "outdated" Anynews versions (not supporting WB 2.8.x) are listed at AMASP
without having control of updating the content as my request for a new AMASP account was refused, while receiving funny PMs or E-mails at the same time asking me to update those outdated modules.
Apart from that, two Anynews versions are listed at the actual WB Module repository
- both with the same module name, but one for WB 2.7, the other for WB 2.8.x series only. All this is from my point of view sub-optimimal and adds confusion.
The sum of all that made me finally believe that a name change (including my branding cwsoft) is well justified. At the end it is the decision of the module author (which it's me) to choose an appropriate module name
PLEASE NOTE: Please delete any possible existing previous Anynews module via the WebsiteBaker backend BEFORE installing the new version, as the database names have changed.
Uups, this statement was copied over from the announcement posts of the "cwsoft-postits" and "cwsoft-addon-file-editor modules". Anynews is a code snippet and does not add or change any database settings. However one should delete a previous installed Anynews module in order not to have two versions of it
for less advanced/experienced wb-users: unclearity if this is a totally new version, just an update or a new module possibly resulting in a chaotic maze of moduleversions and variations
I think the release of modules and patches via the forum is much more chaotic than the way I started at GitHub, as all my code changes can easily be traced online
(and reverted if needed). However, I do hope that some of the actual issues will sort out once the brand new WebsiteBaker repository
will be officially released and the "old module repository" is shut down. Think the new repository will only list newer modules (from 2.8.x onwards).
At the time the new repository is available I would have asked for splitting the Postits
threads at my initial GitHub announcement post and to create seperate threads with the new name "cwsoft-module-name"
My final words on this topic.