New Maintainer

[geoffgarside]

@bbiao has volunteered to take over maintainership. Member access to the go-cas organisation has been granted.

[finalthink]

@bbiao Hi.

Why don't you merge the pull request from other developers?

If you wanna this cas lib keep alive, but you don't have time, you can give the maintainership to another one. @geoffgarside @bbiao

[bbiao]

@bbiao Hi.

Why don't you merge the pull request from other developers?

If you wanna this cas lib keep alive, but you don't have time, you can give the maintainership to another one. @geoffgarside @bbiao

I'm very sorry for that. It's been very busy in 2020. I will make sure the pr will be reviewed and merged in the following days.

[xczh]

Is this project still under active maintenance? It seems that a lot of the code was modified five or six years ago.

I think the following improvements should be done at least:

• Remove glog external log library dependency
• The client has not fully implemented the description of CAS protocol version 2.0 and 3.0. I suggest that according to the protocol text, refer to the Java version of the client implementation, re comb and improve the implementation details
• Rearrange the code and file structure if necessary. This may seem like a disruptive change, so you can consider developing it on v3.0

@bbiao Do you have time for these jobs? I noticed that the go-cas organization does not have any public members. The number of users is continuously losing. Maybe we can consider absorbing some public members to jointly maintain the project, so as to maintain the activity of the project development.

[bbiao]

@xczh thanks for your suggestion and I appreciate anyone who want to contribute to this project.

Since I am not very familiar the github organization system, I need sometime to learn how to add public members.

As mentioned in issue #26, I think the work will be done in the following week.

And after that, we can discuss how to start a new v3 version.