search

lukeed / taskr

A fast, concurrency-focused task automation tool.
MIT License
2.53k stars 74 forks source link

Community Plugins needing TLC #261

Closed Swizz closed 7 years ago

Swizz commented 7 years ago

As proposed by @jbucaran.

Follows the #260 discussion, but proclaims the real subject.

lukeed commented 7 years ago

Scoped packages are now enabled & parsed by Fly.

This issue should be a list of community packages that need updating.

If you find a Fly plugin that is outdated or seems to be neglected:

1) Post a link to the repository here 2) Open an issue in the plugin's repository in attempt to contact the author 3) Fork & submit a PR if you can 😄

Forked repositories can (and sometimes should) be published as a scoped package.

Note: Don't forget the --access public flag!

Swizz commented 7 years ago

Will not use @fly scope only on officially maintained packages ? (I mean part of the fly org or by a fly core contributor)

lukeed commented 7 years ago

No, scopes should only be used if there are name conflicts.

hzlmn commented 7 years ago

@lukeed Are there any reasons for not using @Swizz 's style for official packages, i mean making them scoped?

lukeed commented 7 years ago

I believe that all affected packages will break when existing users go to download them. This sorta thing should have been done before/with 2.0 launch.

Swizz commented 7 years ago

Publish under both name and scoped. Use npm-deprecate to claim the new scoped format ?

lukeed commented 7 years ago

Sure. I don't mind doing that. However, I'm still waiting on @jbucaran to grant me NPM access for nearly all the org repos. 🙏 One can only ping so many times.

jorgebucaran commented 7 years ago

@lukeed I'll get around that this week. 🙇 👋

lukeed commented 7 years ago

lol 🤐 What about fly-coffee very quickly so that @hzlmn can use it?

hzlmn commented 7 years ago

@lukeed Man, I don't use coffeescript, it was just for example :laughing:

lukeed commented 7 years ago

Oh, haha. Well, now it's 1.0 anyway...

pine commented 7 years ago

Hi. Should I move some my fly-* repositories to the organization what I am managing ? And, do you think other people's repositories should do so 🤔

I think that it is best to be properly maintained ☺️

jorgebucaran commented 7 years ago

I think that'd be the way to go.

@lukeed Waiting for npm to reply on a thing, then I'll add you all to the repos, soon! 🙏

Swizz commented 7 years ago

Finished some days ago the fly-serve plugin, can I ask for some code reviews ?

lukeed commented 7 years ago

Hi @Swizz I've left a "code review" for you in https://github.com/Swizz/fly-serve/pull/2 👍

lukeed commented 7 years ago

Closing as Taskr now offers official packages via the scoped @taskr namespace! 🎉 Thanks @Swizz and @hzlmn for the idea -- moving to "Taskr" was the perfect time to introduce this.

We will also be maintaining a list of community plugins on the root README 👍

Thanks all 🙌