Transfer of Ownership

[jdhitsolutions]

Microsoft has transferred ownership of this module to PowerShell.org. It is our hope to bring this module back up to speed and maintain it for as long as the PowerShell community sees value in it. It will take us a little time to get things organized. It is very possible that many of the pull requests will be rejected so that we can start with a clean slate.

We are hoping to rely on the past expertise of the previous primary contributors:

• @davegreen
• @devblackops
• @rkeithhill
• @TylerLeonhardt

If your status with this project needs to change, send DM on Twitter (@jeffhicks)

[devblackops]

This is awesome to see! My Stucco project relies on Plaster, so I'm happy to see PowerShell.org taking over the project and ensuring it continues on.

[LaurentDardenne]

Does the project stay coupling to Visual Studio Code ?

[jdhitsolutions]

That's one of the things I have to look into. I'll need to check with @TylerLeonhardt to see what is happening now.

[TylerLeonhardt]

Yes I have no plans to remove the existing integration in the PowerShell extension and I personally am hoping that with Plaster getting some love, the integration can also get some love as well.

Id be happy to chat about how the integration works. It all should 'just work' still as long as the cmdlets don't change too much.

My ask is that new Plaster maintainers do test new versions of Plaster with the extension 🙂 so I don't get caught too off guard. 😅

[jeffpatton1971]

Have the schemas been moved from http://www.microsoft.com/schemas/PowerShell/Plaster/v1 ? Looking to leverage Plaster to enforce standards on my own modules as well as things I'm working on for my job. So am interested in that schema validation, and the idea that was presented a while back about customizing, or proposing metadata items.

[jdhitsolutions]

I honestly am not sure. That page at Microsoft doesn't exist. I'll have to check into what should happen now.

[jeffpatton1971]

Yea, I noticed that as well, which is why I asked. My understanding is that the XML was validated against that schema, if nobody knows it may be worth sorting out perhaps something based on JSON vs XML...just my two cents though ;-)

[jdhitsolutions]

I'm checking with Microsoft.

[rkeithhill]

Manifests are validated against the schema but if you have access to the schema file (it is in the repo Release\Plaster\Schema\PlasterManifest-v1.xsd) you don't need it to be served up over HTTP. Also, http://www.microsoft.com/schemas/PowerShell/Plaster/v1 is the schema's namespace so again, it doesn't have to exist at that URL. It just ensures that the elements in a Plaster manifest have fully qualified names that include that namespace.

[jeffpatton1971]

@rkeithhill thanks for that clarification, would it make sense to transition that schema from XML to JSON?

[rkeithhill]

IMO no, not worth it. Whatever settings format you pick, someone is not going to like it. This is from the release notes on Windows Terminal:

• Terminal will no longer complain if you leave trailing commas in your "JSON" settings (#6312)
  - What even is JSON anymore?
  - Yes, we perhaps chose a poor configuration format given that we expected users to have to hand-edit it.

[jeffpatton1971]

LOL fair...i guess XML being icky is not enough ;-) Most likely would be the same reasoning for making the schema a little more extensible

[sheppyh]

Is there anything I can do (as a random member of the public) to help get things re-organised? Triage of open issues?