-
Notifications
You must be signed in to change notification settings - Fork 144
BSD community pinboard #430
Comments
We are forming an BSD Working Group with the active BSD contributors. This relates to ansible/community#430
We are forming an BSD Working Group with the active BSD contributors. This relates to ansible/community#430
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
If you want to actively lead or are interested to be part of this Working Group, add your name to the Wiki page ! If we have a large enough group, we can start our own BSD Working Group. I started labeling all the BSD related issues and PRs so we can more easily track them:
PS If you no longer want to receive any messages from this pinboard, feel free to unsubscribe from this issue ticket. |
Should we present ourselves in the wiki under "Community" for specific BSD flavours? |
@tuxillo That is a good idea! I added a "Flavours" column. |
I have added myself to the list, thanks for setting this up! |
So, my interest is mostly making sure stuff still work for FreeBSD (for my work). I use to be also interested into NetBSD, but we stopped using it in the gluster buildsystem, so I kinda stopped finding issues and testing there. |
We are forming an BSD Working Group with the active BSD contributors. This relates to ansible/community#430
So we got a good response for AIX, BSD and Solaris, HP-UX (unsurprisingly) is a bit silent. How do we proceed ? Having a meeting would probably be best. See my thoughts on this at: #421 (comment) In any case, please review open issues and PRs to help close issues. Also help in writing integration tests would be very welcome (and is not hard at all). Since we have FreeBSD in Shippable CI these would be run continuously and find issues with FreeBSD updates as well as changes to the modules. |
I added myself. Thank you very much! |
I added myself. Thank you very much! |
We could collectively benefit from forming a Working Group related to BSD integration. We have quite some contributors on Github and users on IRC that are interested in improving this integration.
So this issue is a wake-up call to potential interested parties (earlier and existing contributors to Ansible). The benefits of having a Working Group is that members of the Working Group can:
Since we have quite some open PRs, reviewing and testing modules and contributions are important for the quality of the modules and helps getting things moving.
The text was updated successfully, but these errors were encountered: