Anyone want to take over maintenance of RubyCAS-Server?

[Matt Zukowski]

I've been increasingly busy over the last few months, with less and less time for dealing with a growing RubyCAS community. Meanwhile, the number of interesting pull requests seems to be going up. I'm starting to realize that my continued control over the master RubyCAS-Server repo is starting to hinder the project. It's time for me to let go.

Last year I handed off RubyCAS-Client duties to Matt Campbell, and this has worked out great. Matt has stepped up and moved the project forward much better than I could have. I would love to see something similar happen to the RubyCAS-Server side of things. A number of you have contributed some great patches over the last year, and you are being Cc'ed on this directly (I'd like to get https://github.com/lifton on this as well, but can't figure out his/her email addy).

Let me know if you're interested. You would be given full admin access to the rubycas org, and would be free to make decisions about the future of RubyCAS. My hope is that you could also take care of at least some of the pull requests trickling in over GitHub. You wouldn't be on your own -- as with the handoff of RubyCAS-Client, I would continue to be involved, would participate in admin work, coding, and discussion of future directions as much as possible.

I think this is a pretty good opportunity to jump in to a  active project with a lot of potential. Judging from the increasing frequency of posts on the google group, stack overflow, and the number of pull requests, pickup of RubyCAS is continuing to rise. The sever code is much better now than it was a few years ago, so you'd be taking over a fairly clean proejct. There's also some interesting stuff going on in the wider CAS community right now, with talk of standardizing around a REST API.

Please reply here if you're interested. 

Thanks,

Matt

[Marvin Addison]

Please bear with a roundabout offer to help. I would like to invite RubyCAS to join the Jasig community. Some benefits:

 - Access to a large CAS ecosystem consisting of developers, deployers, and technologists

 - Collaboration opportunities with other CAS projects (Jasig CAS Server, mod_auth_cas)

 - Access to additional project resources (aka smart folks and good tools)

If you were willing to join Jasig via the well-defined Incubation process [1], it would connect you with a large new community of developers. I'm hopeful that with a broader audience of talented and like-minded developers you could more easily recruit a new project lead. Please let me know if you're interested in this approach.

Even if you decide that Jasig is not a good fit for your project, I'd still be interested in tapping the Jasig CAS community on your behalf for volunteers. Even if we don't fill the position from someone in the Jasig community, I do hope our two communities can work more closely in the future.

Best,

Marvin Addison

Middleware Services/Virginia Tech

CAS Committer/Jasig

[1] https://wiki.jasig.org/display/INCU/Incubation+Process

[de Herdt Arne]

Actually I am interested, since we are using the RubyCAS on a large scale here at work.

However, we have actually rewriten huge sections of the source code to make it deployable over capistrano and run as a stand-alone application under passenger suited to our needs, so pushing these changes back is not a option.

We're also gonne refactor our side to use the Sequel gem instead of ActiveRecord as we discovered a problem with the current code base that prevents  an authenticator from being used more than once with different database connections. This results in the authenticators using the last defined DB connection. Seems to be an AR problem, so we're gonne refactor this out.

Still, I would like to help out on Rubycas whenever I can in my free time.

Arne De Herdt               

--
You received this message because you are subscribed to the Google Groups "RubyCAS" group.
To view this discussion on the web visit https://groups.google.com/d/msg/rubycas-server/-/7rc-6lA6UroJ.
To post to this group, send email to rubycas...@googlegroups.com.
To unsubscribe from this group, send email to rubycas-serve...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubycas-server?hl=en.

[Tyler Pickett]

Matt,

I would be willing to take over, I think there is definitely some interest in moving the project forward from several members of our small community. As for Marvin's invitation to join the Jasig community is worth serious consideration because of the potential benefits to both organizations. 

Arne,

I've been tinkering with some pretty radical refactorings of the current software to break the core application logic away from both the web and persistance layers. The ultimate goal in my mind of these refactorings is to be able to use different storage technologies for different types of tickets to fit their life cycle better (automatic removal of short lived tickets from redis anyone?) and be able to build a Rails engine so I don't have to manage as many servers. This may not be a great idea but it is one worth investigating in my mind.

--
Tyler Pickett

Research to Practice LLC

E-Mail: ty...@therapylog.com

Skype: t.pickett66

Mobile: +1-417-827-6416

[Matt Zukowski]

Okay great. Tyler, you now have Owner access to rubycas on GitHub. Arne, I think everyone would be interested to see the work you guys have done. At the very least maybe you could publish it as a branch in the official RubyCAS repo? Let me know your GitHub username and I'll grant you access.

Marvin, I think getting RubyCAS to participate in Jasig makes a lot of sense. Incidentally I actually work for a group with similar goals to Jasig's -- Educoder, a loose consortium concerned with fostering open source tools for use in education and the learning sciences (https://github.com/educoder). That said, realistically I'm not the right person to spearhead putting RubyCAS in Jasig's incubation process. At least not in the next few months. It sounds like this would be worthwhile, but would require some commitment of time and effort, which is exactly what I'm trying to avoid right now by handing off RubyCAS to the community.

Maybe the way to get started with Jasig for now would be to loop us (RubyCAS devs) in the discussions around the future of the CAS protocol?

To post to this group, send email to rubyca...@googlegroups.com.
To unsubscribe from this group, send email to rubycas-serv...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/rubycas-server?hl=en.

[de Herdt Arne]

My Github name is NekoNova.

I need to check at work here if we can do this. They're finicky when it comes to these things….

At the moment we have rewritten a lot of things to actually map the entire RubyCAS to Redis instead of ActiveRecord mapping. 

Will discuss this today with my chef and see how I can do this.

Arne De Herdt               

Software Engineer

 

 

ProSiebenSat.1 Games GmbH

A company of ProSiebenSat.1 Media AG

 

Medienallee 19

D-85774 Unterföhring

Tel. +49 (89) 9507-8808

Fax +49 (89)9507-98934

Arne.D...@ProSiebenSat1Games.com

Executive Board: Markus Büchtmann, 
Andreas Heyden, Achim Kaspers

Company Residence: Unterföhring

HRB 119657 AG Munich

VAT number DE 182196509
TAX no. 9143/122/60981