|
Generic Question:
When should a plugin be in https://github.com/grails-plugins vs an individual's account on GitHub? Is the grails-plugins only for SpringSource supported plugins? What about SpringSource projects that don't currently have a Grails plugin? Specific Question: I've thought about creating a spring-social plugin a couple times and when I talked to Burt at Gr8Conf, he mentioned he'd thought about creating one too! I've also seen one currently under active development (https://github.com/pgherveou/spring-social). There hasn't been anything officially "released" yet though (grails.org/plugin/spring-social). Should we try and consolidate efforts and create a new repo on the grails-plugins organization on GitHub (https://github.com/grails-plugins/grails-spring-social) for an official spring-social plugin and release it? I'm happy to contribute and work with some others, but certainly not an expert when it comes to creating plugins, ha! Or is it better to just let an individual (i.e. pgherveou in this case) own a plugin and encourage them to officially release it whenever they think it's ready? Please let me know! Thanks, Bobby |
|
+1 on a spring-social plugin, especially with easy integration of spring-security-core.
A while back someone started a port of the spring-social-showcase to grails that you can find here: https://github.com/fsamir/grails-social-showcase Unfortunately, it's only about half way there in terms of functionality and has a number of issues. I've been going through fixing things in it, and I was planning on publishing that back to Github once completed. Al On Tue, Aug 2, 2011 at 1:39 PM, bobbywarner <[hidden email]> wrote: *Generic Question:* |
|
In reply to this post by bobbywarner
Right, grails-plugins is for SpringSource plugins. But hosting the code under your own account is quite common, you just need to release the plugin as zip-only so the release script (or release plugin) doesn't check the code into svn.
I won't have time to work on a spring-social plugin, but can help out with questions, and certainly with integration with the security plugins. If it makes sense to make it an official plugin we can easily move it under grails-plugins. Burt > *Generic Question:* > When should a plugin be in https://github.com/grails-plugins vs an > individual's account on GitHub? Is the grails-plugins only for SpringSource > supported plugins? What about SpringSource projects that don't currently > have a Grails plugin? > > *Specific Question:* > I've thought about creating a spring-social plugin a couple times and when I > talked to Burt at Gr8Conf, he mentioned he'd thought about creating one too! > I've also seen one currently under active development > (https://github.com/pgherveou/spring-social). There hasn't been anything > officially "released" yet though (grails.org/plugin/spring-social). > > Should we try and consolidate efforts and create a new repo on the > grails-plugins organization on GitHub > (https://github.com/grails-plugins/grails-spring-social) for an official > spring-social plugin and release it? I'm happy to contribute and work with > some others, but certainly not an expert when it comes to creating plugins, > ha! > > Or is it better to just let an individual (i.e. pgherveou in this case) own > a plugin and encourage them to officially release it whenever they think > it's ready? Please let me know! > > > Thanks, > Bobby > > -- > View this message in context: http://grails.1312388.n4.nabble.com/Spring-Social-Plugin-tp3713142p3713142.html > Sent from the Grails - dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
Hello guys! We have a first approach to this plugin, maybe is useful for you... Regards 2011/8/2 Burt Beckwith <[hidden email]> Right, grails-plugins is for SpringSource plugins. But hosting the code under your own account is quite common, you just need to release the plugin as zip-only so the release script (or release plugin) doesn't check the code into svn. -- (¯`·._.·[Jµðn]·._.·´¯) |
|
In reply to this post by bobbywarner
> Or is it better to just let an individual (i.e. pgherveou in this case) own
> a plugin and encourage them to officially release it whenever they think > it's ready? Please let me know! It doesn't matter too much where a plugin is located as other GitHub users can be provided with commit access. What we don't want is multiple Spring Social plugins. How many are there currently, and how many are active? One final thing: if people gather around one implementation we can then put you in touch with the Spring Social team. I'm sure they'd be happy to help where they can. Peter -- Peter Ledbrook Grails Advocate SpringSource - A Division of VMware --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
This post has NOT been accepted by the mailing list yet.
Hi guys
I am actively working on this plugin on my repository for a project of mine I would be happy to get some advice from the spring team and work with other contributors I already made some changes to integrate with the last 1.0.RC2 release, I will release that asap on github Ideally, I think the plugin should have a script equivalent to the s2-quick-start of spring-security-core to copy controllers (providerSignin and connect), domain (userconnections) and api keys to config |
|
Hi Peter,
Looks like there are two currently that I know of: https://github.com/synergyj/grails-spring-social (Jose Juan Reyes) https://github.com/pgherveou/spring-social Pgherveou and Jose, Looks like you both have great starts on a spring-social plugin! No reason for me to create another one. So, would you be interested in consolidating into one going forward and working together? If so, who would like to work on consolidating the best ideas from both into one? Anything I can do to help out? I could maybe work on some documentation using the standard Grails Docs once the two plugins are consolidated! Please let me know. Thanks, Bobby |
|
Hi everyone,
I am currently developing the Spring Social Grails plugin (https://github.com/synergyj/grails-spring-social )
You are welcome to participate in the development, i want to release the first version this weekend. Cheers, -- Domingo
On Wed, Aug 3, 2011 at 9:50 AM, bobbywarner <[hidden email]> wrote: Hi Peter, |
|
This post has NOT been accepted by the mailing list yet.
Hi guys I released a new version that run with the last spring social RC
I also uploaded a live grails app running on cloud foundry http://spring-social-demo.cloudfoundry.com/ as I did a lot of changes i just activated facebook and twitter, (the checkbox to automatically publish status after connect is also for the moment disabled) If you want to collaborate on this plugin let me know |
|
In reply to this post by Domingo Suárez Torres
Hi humans,
I just released the Spring Social Core and Spring Social Twitter plugins, check it out the showcase:
The documentation is on the way, stay tuned, the next step is create the Facebook plugin. Cheers -- Domingo
2011/8/3 Domingo Suárez Torres <[hidden email]> Hi everyone, |
|
Nice work Domingo!!! Thanks, Bobby!
|
|
This post has NOT been accepted by the mailing list yet.
This post was updated on .
Hello domingo
good job, working on the social plugin. I checked out your plugin, to see how I could swap my implementation with yours in my application. I have few questions After few iterations I realized it was easier to bind the backend using gorms and grails services rather than using the default jdbc factory provided by the project It allows me to have as hasMany in the spring user Domain class static hasMany = [userConnections: UserConnection] I also removed all dependencies to the spring-social-web my sources are here if you want to see more (https://github.com/pgherveou/spring-social-demo) This approach would require to write the plugin as a template updating the main user class, though or doing some meta programming magic perhaps What do you think ? |
| Powered by Nabble | Edit this page |
