I think we should start off with an outline and then assign each section to whom ever wants to write it. We can then post the content here and have everyone review it. Finally we can work on the format.

Sounds good. That reminds me of a fortune cookie I had the other day which said, "Begin ... The rest is easy". I love that.

Sounds like a plan

Not having worked on anything like this before - not sure how we edit the guide. Do I have the right permissions?

I can provide that. We can work on the outline/format/content... when we get the alpha release I can put it on my site and I will give you and Marco full access to the page.

After each section/sub-section, let put a 'examples' item. If PSH includes something with 'get-help whatever_cmdlet -examples', then we simply refer that as an exercise, otherwise, we put in an example.

As for assigning, at the header of each section/sub-section, put some "()", "[]", or "{}" identifiers maybe along with "insert name here" for whomever will take on that section/sub-section.

"rsiddaw wrote Today at 3:03 AM delete this comment
Not having worked on anything like this before - not sure how we edit the guide. Do I have the right permissions?"

You would need Dev permissions on this project. Are you interested? Do you have VSTS?

Very much interested. I was involved in the discussion on the microsoft powershell newsgroup (RichS) on this and would like to contribute

Done. rsiddaw - you are now a Developer on the project and should be able to see the "edit" link in upper left of wiki pages, etc.

"After each section/sub-section, let put a 'examples' item. If PSH includes something with 'get-help whatever_cmdlet -examples', then we simply refer that as an exercise, otherwise, we put in an example. As for assigning, at the header of each section/sub-section, put some "()", "[]", or "{}" identifiers maybe along with "insert name here" for whomever will take on that section/sub-section."

Good idea. Cool thing is, you can "link" to a real *.ps1 script in the tree (just browse to it in the src tree to get the URL). Naturally, the code needs to exist first. We can also go the other way and take the samples and add them to the tree latter. Either way. Look forward to seeing the doc grow.

Thank you - that seems to be working

I think that is a good idea William...
So... Marco/Rich put your initials next to what ever sections you want to write.

I've picked up the Install\Config section as I added it. I'll pick up some more when you guys have had a chance to select

I would suggest that wherever possible we make the examples administrative tasks that will (a) aid the admin by supplying remade scripts and (b) shoe the admins how to approach scripting tasks.

I selected some.. I will pick up what ever is left

Refactored TOC today. Just click on the link to take you to the empty Wiki page and click Edit to start adding content for your page.

I like that.. very nice

I added a the functions section... Let me know if you guys think the format is ok. I would like everyone to comment that is envolved.

I like this - I'll start adding content. I tend to write as it comes and then go back and edit so first draft will probably be quite rough. I presume we will use US spellings e.g. color as opposed to British colour. Coming from England I have an opinion as to which is right but I'll fit in with the majority view :-)

I dont think it matters... but they... then I can blame all my spelling mistakes on the british :)

I started Objects... Please comment

If we had any gunboats left ..... I'd send one over :-)

I've commented on Objects & Executionpolicy is ready for commenting

Just a thought, but maybe we should come up with three or four status values to be consistent:
NS = Not Started
SC = Started Content
UR = Under Review (will proceed to Done when everyone approves.)
Done = Review Finished and Section Considered complete
Ref = Under Revised Review. For when a section is revised.

If this is cool then we can label all the sections.

Example:
CMDLets (UA-NS)
Function (BS-UR)
Objects (BS-Done)
Install (RS-NS)
Profiles (RS-NS)
Execution Policy (RS-UR)
Extending with PSSnapins & Providers (RS-NS)

Works for me

Changed Profiles to Configuration as we are really talking about config which goes beyond profiles
This is looking good guys

Variables is now Under Review... Please comment

CMDLets is in SC, but stop by and comment please

Configuration is now Under Review - - all comments welcome

Ok... lets get some stuff finalized... Please take a moment to approve/disapprove on everything marked UR. If all approve (William, Rich, and myself) we will mark as done.

Install is ready to review

William... can you review all the stuff marked UR and approve/disapprove. We can mark a big chunk as done.

Chapter 1 finished and all available for review

we are still waiting on William... did he bow out? I guess we can mark them done since we both checked off.

I'm OK with that. Its over a month since we asked for review\sign off. Should we start to open this up for wider comment eg via PowerShell newsgroup?

fine with me

Sorry guys. Been on vacation and other things. They look good. The thing with wiki, they are never done, nor should they be. It is a "green" document that can change as we learn more or find something that just does not sound right or could be said clearer. It can and should grow and change over time.

:)

OK ADSI and AD next. Need to think about this one a bit so it doesn't end up as book :-)

Looks like I just have types and pipes left. Hope to get it soon

If we dont like the "done" any other suggestions? I agree with william that its probaby never quite done.

How about just not having anything against the sections that we are happy with at the moment. In otherwords the default state is done. Any section that has a label is being worked on

sounds good.

removed the "done"

Finally found time to get back to this. I've done a first pass on the ADSI and AD section. All comments gratefully received

IMO we should move this guide to the community site.

I presume you mean powershellcommunity.org Works for me. Actually moving it may encourage me to finish off a few more sections as I visit the community site more than here