Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package still maintained? #1

Closed
dandv opened this issue Nov 13, 2014 · 10 comments
Closed

Package still maintained? #1

dandv opened this issue Nov 13, 2014 · 10 comments

Comments

@dandv
Copy link
Contributor

dandv commented Nov 13, 2014

Looks like there are actively maintained wraps of the d3 library, like https://atmospherejs.com/garrilla/d3

If you'd like to hide this package from Atmosphere, while still letting apps install it, you can run

meteor admin set-unmigrated sergeyt:d3

Thanks! This will help users who search Atmosphere easily find the most current packages.

@mizzao
Copy link

mizzao commented Nov 24, 2014

Damn, it is very hard to figure out which community is an updated version of d3 now that they stopped updating it in core.

@sergeyt
Copy link
Owner

sergeyt commented Nov 24, 2014

unmigrated this package!

@sergeyt sergeyt closed this as completed Nov 24, 2014
@mizzao
Copy link

mizzao commented Nov 24, 2014

@dandv garilla:d3 looks like it just appeared recently too, and might not be that stable. What are you suggesting as the most actively maintained d3 to use? Otherwise I'm considering starting my own...

For example, he did this instead of using api.export.

@dandv
Copy link
Contributor Author

dandv commented Nov 24, 2014

@mizzao: I've started working with authors of popular libraries to integrate Meteor support directly. So far, we have:

Work is tracked at MeteorCommunity/discussions#14

It'd be great of we got @mbostock to accept a PR like that, and have only one integration on which Meteor devs can work.

@mizzao
Copy link

mizzao commented Nov 24, 2014

What does that mean? You just get the package developer to push to Atmosphere every time they release a new version?

I dunno, this seems like a lot of hoops to jump through just to get a working, updated d3 library. You are good at that, but for now I am probably going to just publish my own d3 wrapper package, in the absence of any well-established alternatives. Happy to deprecate this once you get to that point.

@dandv
Copy link
Contributor Author

dandv commented Nov 24, 2014

Right now, it just means running meteor/publish.sh, which takes care of versioning and publishes the package on Atmosphere. Pretty painless.

Because most libraries use build scripts of some sort (e.g. Grunt files) to publish updates, pushing to Atmosphere can easily become a zero-effort operation if we update the Gruntfile as part of the PR.

@dandv
Copy link
Contributor Author

dandv commented Nov 24, 2014

Ouch re. garilla's hack... deserves a flag - please flag https://atmospherejs.com/garrilla/d3. I'll take a stab at an official d3 integration PR tonight.

@mizzao
Copy link

mizzao commented Nov 25, 2014

How do you flag something? Don't see it anywhere on the page.

@dandv
Copy link
Contributor Author

dandv commented Nov 25, 2014

There should be the word "Flag" right there.

image

@mizzao
Copy link

mizzao commented Nov 25, 2014

I see, had to be logged in. Never mind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants