{"id":990,"date":"2016-02-08T00:00:00","date_gmt":"2016-02-08T00:00:00","guid":{"rendered":"http:\/\/officedevblogs.wpengine.com\/?p=990"},"modified":"2021-11-16T11:38:30","modified_gmt":"2021-11-16T19:38:30","slug":"pnp-feb-2016-release","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/pnp-feb-2016-release\/","title":{"rendered":"Office 365 Developer Patterns and Practices \u2013 February 2016 release"},"content":{"rendered":"
\n

Office 365 Developer Patterns and Practices<\/a>\u00a0(PnP) February\u00a02016 release is out with new contributions from community for the community. This post contains all the details related on what was included with the release and what else has been happening in the PnP world during the past month.<\/p>\n

What is Office 365 Developer Patterns and Practices (PnP)? \"Office<\/h3>\n

PnP is community driven open source initiative\u00a0where Microsoft and external community members are sharing their learning’s around implementation<\/em> practices for Office 365 in general and also SharePoint on-premises (add-in model). Active development and contributions happen our GitHub project<\/a> under ‘dev’ branch and each month there will be a master merge (monthly release) with more comprehensive testing and communications.<\/p>\n

This is work done by the community for the community without any actual full time people. It\u2019s been great to find both internal and external people who are willing to assist and share their learning’s for the benefit of others. This way we can build on the common knowledge of us all. Currently program is facilitated by Microsoft, but already at this point we have multiple community members as part of the PnP Core team and we are looking to extend the Core team with more community members.<\/p>\n

Notice that since this is open source community program, there\u2019s no SLAs for the support what we provide from program. There is however highly active PnP Yammer group<\/a>, where you can get fast support on any questions around the existing materials. If you are interested on getting more closely involved, please check the following guidance from our GitHub wiki.<\/p>\n