-
Notifications
You must be signed in to change notification settings - Fork 144
macOS community pinboard #432
Comments
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 macOS Working Group. I started labeling all the macOS 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. |
I'm interested in reviewing/watching the outputs of this group should I add myself to this page or just remain part of this ticket? |
@jcftang If you subscribe to this ticket, you only get the updates to this ticket. If you add yourself to the list on the wiki, you will get included in new issues/PRs and can follow the discussion in those tickets. But it's a good question, we should probably make a distinction between people interested to be notified (notified), and people interested to review (maintainers). So I am going to add a Roles column. |
Hey there, I've been checking some issues on the list and I've noticed that most seem already resolved. Got a few hours here and there, so maybe I can assist? |
hi @dagwieers :) i'm really flattered to receive this notification but sadly i moved on platform automation. if there's anything i can do in the frontend part of things, let me know. |
We could collectively benefit from forming a Working Group related to macOS 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: