Renaming of the master branch

[alaunay]

Hello,

Renaming the master branch had the consequence of closing a lot of unanswered and unverified PR, which were still waiting for some sign from the #Wazuh team.

Should we just definitely understand that you are NOT team players, and don't want ANY external contribution ?

Thanks for the clarification.

[c-bordon]

Hello, we are currently in the process of standardizing our repositories, which is why we changed the name of the master branch to main.

As for external contributions, they are always welcome. We have several changes that we are working on in our roadmap, so as soon as we can, we will share said roadmap so that you can continue making contributions according to said roadmap.

[alaunay]

If contribs are welcome, why simple corrections like this one:

#904
#909

Or more complex adds:
#908

Never got any answer in a year ?

When looking at issues or PR, it seems like all non-wazuh-people just get completely ignored.

[Dwordcito]

Hello @alaunay , there have been many changes to Wazuh recently. We're organizing ourselves to receive these types of requests, prioritize them accordingly, and review them appropriately.

Leave the PRs open/reopen to main, and we'll look into them when we can.

[alaunay]

Unfortunately, they have been closed by your branch renaming, without any possibility to reopen them.

[teddytpc1]

Hi, @alaunay.
Some comments on the mentioned PRs:

• Add ip_update_interval parameter support #904: for 5.0.0 all the customizations to the components will be removed from the repositories of the deployment alternatives. So, the change does not align with the Wazuh plan. If you consider that the default value for a parameter is not appropriate, please open an issue in the corresponding component repository, https://github.com/wazuh/wazuh, in this case.
• Add repo paths for snapshot management #909: while it can be useful, the wazuh-puppet repository is not the appropriate place to include it. Please open an issue for the Wazuh indexer team in the corresponding component repository, https://github.com/wazuh/wazuh-indexer, so they can evaluate the proposal.
• correct dashboard version for Debian #908: let me know if you can open an issue reporting this, please. If not, I will. We will include the new issue for the 4.13.0 release.