Move the windows_package and windows_feature LWRPs into core Chef
fix formatting
add examples
use the package resource by default

The default provider can be accessed with just package instead of windows_package, which is cruft from the documentation from the existing LWRP.
windows package, before removing feature
focus on windows package
Add attributes to the resource
Merge pull request #2 from opscode/btm/windows-package

RFC: Windows Package Core Resource/Provider
notes on knife-openstack changes
separated current and future proposals
Ohai 7 cloud network enhancements
add internal discussion link
ohai changes will be a separate PR
Add --no-network to the RFC

The comments in https://github.com/opscode/knife-openstack/pull/30 make the case
for not knowing the names of your networks in advance.
Added --bootstrap-network

This was in the original internal RFC, I overlooked it thinking --networks
covered the use case. Clearly it is necessary.
Removed --network option because OpenStack API does not appear to support it

Dug through the API code and server_create code in Fog and found that the
networks get attached to the node after server_create is called, which means
there's currently no abilility to limit which networks attached by new servers.
This could be a limitation of my test environment (nova-network), but the API
docs and Fog code appear to support this conclusion.
link up KNIFE-423 for knife openstack network list
Merge pull request #7 from mattray/openstack-network

OpenStack named network enhancements to server create and delete.