Fix default branch on Github

[abias]

Hi,

looking at https://github.com/lsuits/lsu-block_quickmail/branches, I see that the branch LSU_37_GRADEBOOK is set as default branch and not the master branch. I assume that this is a mistake and master should be the default branch.

I would appreciate if you could fix this so that especially everyone coming to https://github.com/lsuits/lsu-block_quickmail will get the right branch instantly.

Cheers,
Alex

[rrusso]

I don't think LSU ITS is supporting this any more, so I've moved it to https://github.com/lsuonline/lsuce-block_quickmail and updated the default branch there.

[abias]

Hi Robert,

thank you for your quick reply!

So you made a copy of this repository and pushed it to another institution on Github? Please let me state that nobody from the outside will understand this duplication of repos. It's already hard enough for us to follow the code on Github here as you do not update https://moodle.org/plugins/block_quickmail anymore as official release channel. We are currently trying to make the transition from Quickmail v1 to v2, but the way how you manage and maintain this plugin gets more and more opaque to us.

May I propose that you transfer ownership of this Github repo to the other institution if the maintenance has been handed over?

Thank you in advance,
Alex

[rrusso]

I no longer work for them and they blocked me from being able to update the repo, so there's not a whole lot I can do in here except comment. I can't even close out tickets.

[abias]

Thanks, Robert, for your frankly reply.

May I ask you, is there anybody left who is maintaining this plugin then anymore in this repo here? Or will you continue to maintain it on the other repo which you just created?

I mean, we have been watching the very long development of Quickmail v2 from the sideline and were wondering where and when this will end. Now that v2 is not officially released but appears to be usable - and especially based on the fact that Quickmail v1 is fundamentally broken on Moodle 3.7 as reported in #280 and #288 - we wanted to make the switch.

However, upgrading a plugin to a version which is not officially released as stable and just downloaded from a Github repo which is not maintained anymore sounds like a suicide mission....

Thanks for your insights,
Alex