search

percolatestudio / atmosphere

Atmosphere - Meteor Packages
https://atmospherejs.com
59 stars 4 forks source link

Not official and broken package of FuelUX #413

Open medihack opened 8 years ago

medihack commented 8 years ago

There is a package named exacttarget:fuelux in Atmosphere that wraps the Fuel UX frontend widget library. Unfortunately the Atmosphere package is not working at all and it is not an official release, even if the username makes it look like this and the Github link links to the official repository. I asked the original developer if he could provide a official Meteor package and he accepted. Is there some way to contact the (wrong) exacttarget user (who uploaded the broken package) to ask him if he would leave is username to the official author of FuelUX? If not, then is the only way to choose another username?

See also https://github.com/ExactTarget/fuelux/issues/1521#event-416143368

medihack commented 8 years ago

Bump. Any help here? Is there really no way to contact that user. Is it somehow possible to flag that package so that it can be deleted an the official package can be uploaded?

splendido commented 8 years ago

hello @medihack, 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

domyen commented 8 years ago

Copy and pasting from my #415 comment

It appears that this package was published by an organization under your name. There's currently no way to transfer packages to other users so the two approaches are:

Get added to that organization by the original owner so you can have access priveleges. (not lost on me that org members are currently hidden, this choice was originally intended for Meteor Developer Account privacy and it's biting us) Re-upload the package under your own Meteor Developer Account (requires signing up here) and republishing this package. MOD's can then flag the package so that it no longer appears in search results.

I understand that both of these choices are less than ideal. I'll circle back with the others and see what we can do.