We have the DALnet organization set up in GitHub and moved over the existing issues and pull requests. To continue the existing process, we will have the following steps for submitting changes:

Developer/contributor will submit a pull request
Our integration with travis CI will test/build the changes to ensure things compile properly (Might set it to error on warnings to guarantee code quality)
After two thumbs up are provided, changes will be merged to master.

Please let me know your thoughts on this. We appreciate the voluntary changes made to bahamut but having a clear list of steps ensures everyone is on the same page and expectations are laid out properly.

Another note, I’m going to be adding the ability to write libcheck test cases to the code for those who’d like to ensure backwards compatibility with changes is maintained. I’ll comb through the code and try to pick out any methods that should have initial test cases but if you guys have any in mind, feel free to let me know.

On Mar 20, 2018, at 6:12 AM, Mattias Ahnberg <ahnberg@DAL.NET> wrote:

Hi everyone,
epiphani has served DALnet and the bahamut community for many many years as lead
for the DALnet coding team. We're now changing around the team a bit and skill is
stepping up and taking over the flag as lead going forward.

Epiphani will stick around as a contributing member going forward so he will not
disappear!

We've also moved the main repository for bahamut into the DALnet organisation on
github; you can now find it on https://github.com/DALnet/bahamut

Thank you for all your contribution epiphani, both in the past and what is to come!

Congratulations skill!
--
/ahnberg
_______________________________________________
admin mailing list
admin@lists.dal.net
https://lists.dal.net/mailman/listinfo/admin