-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grafana Pinboard #139
Comments
@seuf @rrey Feel free to use this issue for communication and https://github.com/ansible/community/wiki/Grafana for documentation. Please give me a shout if there is anything else. I wonder if reviewing the existing PRs would be a good place to start |
Thank you @gundalow ! I'll start by reviewing the PRs ! |
Bot meta update ansible/ansible#63859 |
Hi, I didn't want to do by myself now as there seem to be a number of open Grafana PRs https://ansible.sivel.net/pr/byfile.html (ctrl+f Thanks |
@gundalow I made the PR here : ansible/ansible#64657 I think it can be merged after ansible/ansible#50816. |
@gundalow have no answer from author on ansible/ansible#50816 so I think we the ansible/ansible#64657 can be merged whenever you want. I have just rebased it, do you need any thing else on this PR ? What are the next steps for working groups about the move to collections ? |
@rrey Looks like the above got merged, which is great. For the Grafana Working group the question is:
Being in your own repo gives you some more control, and freedom to do a release of the Grafana collection independently of the main Community Collection. I am looking for some willing Working Groups to test this out. Basically we'd freeze ansible/ansible and just do the work in the new collection repo. I'm happy to jump on a call and discuss any of this if that may be easier. |
Hi ! I think it makes more sense to have a lifecycle for each working group. |
@rrey @seuf Hi, I've created https://github.com/gundalow-collections/grafana which is a copy of what's currently in ansible/ansible:devel. It has basic CI (Python 3.6 on Ubuntu 1804). I've invited you both to the org, you should receive an email from GitHub to accept joining the team. |
I wonder if one of the PRs from https://github.com/ansible/ansible/labels/grafana could be reworked for the new repo, perhaps ansible/ansible#62930 or ansible/ansible#64097 ? |
Thanks ! |
@seuf if you want to jump on a call so we can discuss this, let me know. |
@gundalow what should we do for our modules maintenance ? Should we use the |
@rrey @seuf I think we can ignore Grafana files in ansible/ansible for the moment. I've just your closed the two PRs (one from each of you) that have been replicated in
|
|
|
I'm going to try to migrate this pinboard to https://github.com/ansible-collections/community.grafana but there may be a slight disruption as it requires multiple moves. I will follow up when the migration has been completed. |
migrated and pinned! |
I'm happy to announce that the registration (free) for the Ansible Contributor Summit is open. Which day should you attend?
Refer to the registration page for details. See you at the summit! |
Reminder - AnsibleFest and Ansible Contributor Summit are 1 week away! In case you missed it, we will also be having a Hackathon throughout the entire Ansible Contributor Summit and AnsibleFest. This is a great opportunity to collaborate in real time with other members of the Ansible Community! For more info and the latest updates, please see the Ansible Contributor Summit 2021.09 HackMD. |
Reminder - Day 1 of the Ansible Contributor Summit and the Hackathon start tomorrow (Tuesday, 28 September 2021)! For more info and the latest updates, please see the Ansible Contributor Summit 2021.09 HackMD. |
We could collectively benefit from forming a Working Group related to Grafana integration. We have quite some contributors on GitHub and users on IRC that are interested in improving this integration.
So this issue is a call for potential interested parties (earlier and existing contributors to Ansible). The benefits of having a Working Group is that members of the Working Group can:
The text was updated successfully, but these errors were encountered: