Skip to content
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

[New Resource] NIC Teaming (NetLBFO) #80

Closed
tysonjhayes opened this issue Jan 4, 2016 · 8 comments
Closed

[New Resource] NIC Teaming (NetLBFO) #80

tysonjhayes opened this issue Jan 4, 2016 · 8 comments
Labels
enhancement The issue is an enhancement request.

Comments

@tysonjhayes
Copy link
Collaborator

Add Nic Teaming (NetLBFO) to the list of resources.

@tysonjhayes tysonjhayes added enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community. labels Jan 4, 2016
@tysonjhayes tysonjhayes changed the title [New Resource] NIC Teaming (NetLBFO [New Resource] NIC Teaming (NetLBFO) Jan 4, 2016
@rchaganti
Copy link
Contributor

Here it is: https://github.com/rchaganti/DSCResources/tree/master/cWindowsOS/DSCResources/cNetworkTeam

I just need to update it as per contribution guidelines here and add tests! :D

@rchaganti
Copy link
Contributor

When I copy this new resource to my fork, what should I name it? Leave it as cNetworkTeam or name it MSFT_xNetworkTeam?

@tysonjhayes
Copy link
Collaborator Author

If the intention is to submit a PR to us then it should be renamed MSFT_xNetworkTeam. Though you bring up a good question that I've proposed elsewhere that we should drop the x/c nomenclature. So it would just be MSFT_NetworkTeam instead. What are your thoughts?

@rchaganti
Copy link
Contributor

Yes, I will submit a PR here. Given an option, I will remove x or c from it completely.

@PlagueHO
Copy link
Member

PlagueHO commented Jan 5, 2016

The x/c isn't really that useful TBH - I thought x was for experimental and c was for community - but it seems like useless information to me. But to remove it now from all resources would mean all configs using them would need to be updated - which might not be ideal.

All my resources use c, but as I'm transferring them across to MSFT I'm changing them to x.

As long as the naming is consistent I'm happy :)

@rchaganti
Copy link
Contributor

I didn't mean that we change existing resources. We can just drop the x/c prefix for all new resources.

@PlagueHO
Copy link
Member

PlagueHO commented Jan 7, 2016

I just noticed that there has been some discussion already around dropping the x/c nomenclature in this issue:
PowerShell/DscResources#27

It looks like the policy was to drop the x/c off the resources once ALL 'c' resources are integrated and all 'x' resources are adhering to the best practices policy.

I'm not certain of what the final plan is currently though as this discussion was during June last year.

I'd suggest we stick with the 'x' for now and when a final instruction is issued we could submit a PR to change all resources. This actually shouldn't be difficult as I've changed some of my resources from 'c' to 'x' without too much difficulty.

@tysonjhayes ?

@rchaganti
Copy link
Contributor

just a progress update on MSFT_NetworkTeam. I completed the style and code guideline updates to the resource module and added examples. I am adding unit / integration tests and should be able to push the PR early next week.

@vors vors removed the help wanted The issue is up for grabs for anyone in the community. label Feb 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue is an enhancement request.
Projects
None yet
Development

No branches or pull requests

4 participants