Move plugins to Seneca organization

nfantone commented 8 years ago

@mcdonnelldean @rjrodger and cia.

Given that,

A fair number of plugins are already available to users.
The Seneca ecosystem is growing.
Not all of them are being maintained on a regular basis.
Many plugins duplicate functionality (last time I checked, there were three packages that enables support for AMQP).
Our communication skills, specially towards the community, are far from top notch (just this repository alone has over 50 issues, some dating from 2014).

I propose to join efforts and move "official" plugins under the Seneca organization wing. This is an approach similar to what the good people at Koa have done.

The idea here is to have a single place for users to find "quality" plugins. What defines "quality" is the main issue here, of course. I'd like to propose some minimum requirements:

At least one active lead maintainer.
Committed to actively answering PRs and Issues.
Aligned with Seneca coding conventions and good practices.
Pre-defined repository setup (use of labels, CI build, code coverage, semver releases, eslint rules, etc.)

This is, of course, just to kick off the discussion. But I think I'd help a lot towards cleaning up and trimming some of the wilderness in the ecosystem.

mcdonnelldean commented 8 years ago

This is pretty much our thoughts too @nfantone. @naomifeehanmoran and @AdrianRossouw can give you more info. They have been doing a lot of background work to make this a reality and are nearly ready to share our thoughts. Do note, they are pretty much exactly what you've mentioned above 💃

nfantone commented 8 years ago

@mcdonnelldean Fantastic news! So random people around the globe had the same idea roughly at the same time. This needs to be a good thing.

mcdonnelldean commented 8 years ago

@nfantone It was actually the whole mess with the repos above that broke the camel's back. Something had to change.

naomifeehan commented 8 years ago

hey @nfantone as @mcdonnelldean said we are currently in the process of content curation for the growing Seneca ecosystem and based on your comments we are all on the same wavelength. It will take some time to get everything tidied up but we will get there :)

nfantone commented 8 years ago

@naomifeehanmoran Anything I can do in the meantime? Writing docs? Closing PRs? Reviewing stuff?

naomifeehan commented 8 years ago

@nfantone we welcome any ideas or opinions on what is lacking in docs, you can log issues and PRs against https://github.com/senecajs/senecajs.org/issues.

mihaidma commented 8 years ago

hey @nfantone I coordintate the very small team that currently automates the tests, standardizes plugins after moving and fixes test failures. We need help from code/tests fixing, PR review and readme review. Please ping me if you want specific tasks.

mcdonnelldean commented 8 years ago

@nfantone Hey, I just wanted to update you. We are now at the deprecation stage of this task. We are removing a load of obviously outdated stuff just so we can deal with what actually matters. Once this phase is complete we will start chatting to yourselves and others. We will have a much leaner, higher quality org by the end of this all :D

nfantone commented 8 years ago

Hey, @mcdonnelldean! Great news! I'll be away this whole week, but will catch up with you when I return (I still have some bugs assigned to me that'd like to push forward).

mcdonnelldean commented 8 years ago

@nfantone Hey, massive apologies for the delay on this. I will have documentation around this either later today or tomorrow. We finally got consensus on realistically enabling the community to own major plugins that live in the official org. As soon as the document is ready I will share it here.

nfantone commented 8 years ago

@mcdonnelldean Good to hear! Though "Massive" sounds like a number a tad above what's necessary. No need for apologies.

Just let me know if I can be of help.

mcdonnelldean commented 8 years ago

@nfantone Super sorry about the delay on this. We have been moving mountains :D

Anyway, long story short. In the next few days I'll formally invite your module into the org. There aren't many stipulations, pretty much just standardising on linting and testing.

The general plan is to invite any high quality community modules into the org directly, standarise on some bits for parity and then let you run it freely as normal.

I've some documentation to add around it to the repo, once done I will open a formal invite with instructions 🎉

nfantone commented 8 years ago

This is welcoming news! Keep me posted, then.

senecajs / seneca

Move plugins to Seneca organization #406