On 03/03/2016 09:37 AM, William L. Thomson Jr. wrote: > > Its not just mine, its a sentiment that has existed for years, shared by many.
I think debate and discussion are healthy but it needs to be done without these types of hyperbole. How many is "many"? Did you take a survey? Or are you merely expressing what you feel should be accurate because you believe your opinions are shared by Alchaemist from Wikipedia (who put the "Disadvantages" bits into the article in the first-place)? > Though allot have moved on. How many of them moved on? Did you take another survey of them? > Also do not confused developer/maintainer with > author. People have taken over development of ASSP, but they are not the > original Author, John Hannah. I suspect if they were still around things would > have been broken up long ago. Did John ask you to speak for him on this matter? What makes you think that John would have done what you want? > I do not believe there are many currently contributing > to ASSP development. If you're referring to code contributions, then it's actually possible to count that number. Feel free to do that instead of referring to nebulous terms like "many". However, software development contributions also come in the form of user feedback such as you're doing now. It's valuable stuff. But, again, it's possible to count that. > What might the reason be for lack of interest in helping to develop or further > ASSP? Let's presume that you are correct - although I necessarily agree with you - but let's presume that you are correct... lack of interest in helping to further develop the software may be because they don't see anything wrong with it or requiring further development. I can code, for example. Why don't I contribute code developments to ASSP? Because I don't see anything that requires me to do that. > Dictatorship vs community lead project. I believe ASSP is the communities not > any one persons, no matter who wrote the code, currently maintains it, or is > looking to further it. I think that you misunderstand open-source code development. While the code may very-well be public domain or "free", that does not mean that everyone has equal-access to that code used by everyone else. You're free to alter and develop *your* copy of the software. You're free to share that with others. Thomas has shared his copy. You don't have to use it if you don't like it. > > In the past this lead to 2 different releases of ASSP. Did it? This issue is what led to that fork? > Fritz release and the > community. Many projects do fracture or fork. I would not want to see that > happen to ASSP. I'm not sure what would be wrong with forking. In the git world it's known as "branching". It's done constantly in open-source software development and is not generally considered to be a bad thing except when someone is trying to use it as a threat. > I would also like to see others contributing to ASSP so the > entire load is not falling on Thomas. Feel free. Develop what you like. Share it. > If Thomas gets bored with ASSP and moves on, who will take over? Somebody will... or nobody will. It doesn't matter. You still will have your copy, though, won't you? I will have mine. And we can continue to add features and stuff if/when we need to. Isn't open-source nice that way? Thanks, Lee. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
