Open danialfarid opened 8 years ago
+1
Same problem here: https://github.com/percolatestudio/atmosphere/issues/413
Unfortunately no answer yet. It's also disappointing that there is now way to flag a package.
hello @danialfarid, I'm sorry to ear there are problems like this one on atmosphere.
Since I'm a MOD
I could easily flag the package but this won't solve the problem.
I think there's no way at the moment to get in touch with a meteor developer user.
cc to other MODs: @tmeasday @dburles @dominicnguyen @sachag @dandv
Thanks for the cc @splendido. It appears that ng-file-upload was published by an organization under your name. There's currently no way to transfer packages to other users so the two approaches are:
I understand that both of these choices are less than ideal. I'll circle back with the others and see what we can do.
I have created/published the package here: https://atmospherejs.com/danialf/ng-file-upload
I've flagged the other package. When a package is flagged its score is reduced such that it appears lower in the search results and shows a red flag to warn users about using the package.
On Wed, Dec 2, 2015 at 12:31 PM Danial Farid notifications@github.com wrote:
I have created/published the package here: https://atmospherejs.com/danialf/ng-file-upload
— Reply to this email directly or view it on GitHub https://github.com/percolatestudio/atmosphere/issues/415#issuecomment-161424607 .
https://atmospherejs.com/danialfarid/ng-file-upload I am the owner of that github module and It is published here by another user and the version is very outdated so lots of people are having problem following the new release readme files with the old version of the package that is published here.
Could you delete that package or give me access so I can publish latest versions?