New package for inclusion - meteor-useraccounts suite

[vparpoil]

meteor-useraccounts

User Accounts is a suite of packages for the Meteor.js platform. It provides highly customizable user accounts UI templates for many different front-end frameworks. At the moment it includes forms for sign in, sign up, forgot password, reset password, change password, enroll account, and link or remove of many 3rd party services.

Links

• Atmosphere
• Github repository

Current status of the project

• Active
• Maintained
• Abandoned

Reasoning

This project is referenced by the meteor guide as best practice to handle UI, but abandoned
Having a well-working user accounts suite was one of the great things about meteor at some point. Today, these packages are no longer maintained and people need to maintain forks of such projects to keep in line with dependencies updates. New comers won't benefit of these forks and I guess the guide walkthrough is difficult to follow for them.

I am willing to contribute to maintenance.

[StorytellerCZ]

Given the diversification of the front-end this is primarily something for Blaze users. If we could establish a group around Blaze then this would be great for it.

[vparpoil]

I think that a good part of atmosphere packages are Blaze centric and since Blaze is still referenced in the Guide as "the easiest to learn and has the most full-stack Meteor packages", I believe that Blaze packages should be included here and maintained by those in the community still using it.

In my mind, there are enough Blaze users that raised their hands in the kick off discussion to consider bringing in Blaze centric packages.
The case of the meteor-useraccounts suite was already proposed in this dicusssion though

[vparpoil]

I bumped into a react version of the accounts UI : https://github.com/royGil/accounts-react which has been forked and is maintained here : https://github.com/day/accounts-react/
I though it was worth mentioning here if it moves forward

[StorytellerCZ]

Interesting. I'm thinking maybe creating a Blaze team here for interested people.

[StorytellerCZ]

OK, Blaze team created. Any volunteers who want to take on maintaining this package?

[vparpoil]

Hi @StorytellerCZ, I am willing be a maintainer for this package. We use it in production in many apps

[StorytellerCZ]

This is pretty big project. Should probably be its own sub-team under Blaze team if we could get enough members.
Would be nice if we could create directories for repositories at least for presentation purposes.

But with @mitar here (who is member of that GitHub org) the question is if at this point it wouldn't be more feasible to get new maintainers into the project rather than fork/copy it over here. We can keep it under the same organizational structure if needed.

[mitar]

Sadly I do not have any real permissions there. Has anyone contacted @splendido?

[splendido]

Hi guys!
...shame on me about the way I've abandoned the project, I know!
I'm not really happy about it too :-(

This said, I'd be really happy to give required permissions to people willing to maintain all those packages!
Just tell me one to get superpowers and you'll be all set...

Thanks for the poke, really appreciated!

[coagmano]

There's no shame in changing priorities. It's FOSS after all

I'd be happy to help maintain as well, I've requested to join the blaze team

[mitar]

@splendido Awesome! Let us organize things on our side here (this is a new community project to maintain Meteor packages) and will get back to you.

For others: do you think we should move packages here to this repository? Or manage them in their original organization? The advantage of the former is that there will be always somebody with permissions around.

[vparpoil]

I think having a single org will also create a stronger image for the community

[copleykj]

I'm personally in favor of keeping things simple and not having multiple orgs for us to try to manage. That being said, this adds quite a lot of potential work, and I'd like to get a showing of who's willing to commit time to these packages before we move forward.

[copleykj]

After looking into this a little more, I'm not sure this is a great idea. The scope of work here is pretty large and the original org already lists of 9 members, yet maintenance is non-existent.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[StorytellerCZ]

@splendido If you want you can give access to community packages and I can jump in once in a while to merge and publish the most pressing things, but right now I don't think we have enough people willing to effectively maintain such a huge project.

[splendido]

@splendido If you want you can give access to community packages and I can jump in once in a while to merge and publish the most pressing things, but right now I don't think we have enough people willing to effectively maintain such a huge project.

@StorytellerCZ sure, sounds good! I've just invited both you and @filipenevola!

[StorytellerCZ]

@splendido great! Thanks! Can you also add me to the Atmosphere org so that I can publish new versions?

[filipenevola]

@StorytellerCZ you already have permissions to publish it.

But if the community doesn't want to really maintain it's probably better to keep it under compat org.

[vparpoil]

Hi @StorytellerCZ,
Can you confirm you have access to the whole useraccounts project ?
If so, I think it would be great to have a new version of useraccounts:unstyled compatible with last Meteor version. Here is the pull request
Edit - and also, useraccounts:core still needs updates in its original or compat version : meteor/meteor#11743

[StorytellerCZ]

Sorry, but I don't have access to any make any merges or anything of that sort on GitHub, I'm just a member of the org. As for Atmosphere I don't see myself having access to the whole.

[vparpoil]

@splendido can you double check? It looks like something didn't worked as expected... Thanks a lot !

[filipenevola]

Hi, at least on the Meteor Software side we are going to keep putting these changes under meteor-compat org. It is easier for us to track all the issues in a single organization for compat packages.

[vparpoil]

Closing this issue now because meteor team decided to maintain the meteor-compat versions of the principal packages and we can contribute there if modifications are needed. Thanks !

[harryadel]

What's the status of this? Is useraccounts still being maintained at meteor-compat? I noticed the latest commit was 6 months ago by @denihs who no longer works at Meteor AFAIK. Maybe we're ought to revive this and merge the latest changes done under meteor-compat into the original package then move it under MCP. What do you guys think?

I'd be willing to chip and help carry this over if all parties are agreed!

For now, I'm using useraccounts at a local project, so I'm going to pull meteor-compat version and continue my work over there until hopefully this is resolved so it can be all brought back to the original package under MCP.

cc @splendido @StorytellerCZ @denihs @filipenevola @vparpoil