Its probably because you are distributing the full ST library which is probably against the licensing agreement. I believe Mitchell said something similar in your previous post.
You should instead publish your changes Patches, Diffs, or Overrides. Modifying the core source of any library is generally bad practice as it makes staying up to date, applying, or unapplying the changes cumbersome as the core library team releases updates and fixes.
I for one would not consider using your changes just because it directly modifies the source.
As far as distributing the entire source instead of just the diffs.. All the diffs are listed in the Github commits section: https://github.com/mgcrea/sencha-touch/commits/master
And the library is freely available for anyone to download from sencha.com, so what's wrong with making it available at different places around the Internet? Surely the Sencha team isn't able to keep track of all the places their javascript library is on the web.
I'm not saying the patches you have written are not beneficial, I'm just guessing why the admins closed your thread and suggesting an alternate, much more accommodating way you could have posted your beneficial changes.
Again, this repo only aims at helping early adopters with blocking bugs preventing them to move to ST2.0, i guess the more people start using ST2.0 today, the more this (amazing) product gets a strong footprint on the web.
I would rather publish plugins & extensions, but for now we are quite stuck with blocking bugs.
I understand that this conflicts somehow with the global/commercial policy your company has, and i'm thankful i've not been asked to take it down yet, as I really think it is good for everyone at the moment.
It is not aimed to last beyond beta, and it will be taken down if you want it to (your product / business -> your call).
ST2 community patches repository
Reply With Quote
