Play 1.x Roadmap?

[jaliss]

Play 1.x Roadmap?

[magro]

+1 for a 0.2.5 release.

[gobijan]

+1...
anyone alive here? jorge?

[jaliss]

@Akumadevil main development is going to be focused on Play 2 at least until I can make it more complete. Bug fixes and minor improvements can go into the Play 1 version. If you want to add things that's great. You're most welcome to contribute.

Let me comment on your list:

1. Out of the box use of database tables rather than hashmap (done)
   I did not want to impose a model or storage requirement to people using the module. That's why I provide the SocialUser class that you can map and save it to whatever you want (eg: database, mongo, etc) by implementing your own UserService. As I commented on the code, the hashmap implementation is not suitable for production environments.

2. Support for multiple identity providers, which would be consolidated against a single user record
   This is something I'm planning for version 2. But we could add it to version 1 as well. We should agree on the design if you want to work on this.

3. Email as the username (no need to have both)
   Good point. I was thinking of removing the username in the version for Play 2. We could do it in this version too.

4. Overwrite any view or email template
   This can already be done, you need to add the templates in your app views directory following the same directory structure and Play should automatically pick up your files instead of the module's.

5. Reset password
   This already implemented

6. Resend activation link (i.e. don't lock the username)
   This is already implemented

7. Remember me
   I think my concern with the "remember me" functionality is that you would not get a new oauth tokens from the social networks which could be different from your last visit. If you already signed in using any of the networks you'll just jump into the app. One click. Remember me could be helpful for username/password logins ... Not so sure about this one.

8. Enforced HTTPS
   This would be good to have, but again would just be useful in the username/password case.

Thanks,
Jorge

[gobijan]

Hi Jorge,
thx for your explanation. How about bugfix releases? Facebook for example is currently broken and you need to do is accept the attached code here: #69
Would be really cool if we could speed up this branch here for all the play1 lovers with a bit of Release Early Release Often(TM) mentality :)
Cheers

[jaliss]

@tschundeee you are right :-) Things have been crazy on my end and haven't been able to follow this properly. Hope to be back on track soon.

[jaliss]

I'm afraid I can't continue working on the 1.x branch. All the development effort is going into the main branch that works with Play 2+