Created the docs layout

2026-06-08 12:12:50 +00:00 · 2016-06-24 19:11:56 -07:00
parent 14ccf37210
commit 39b3bfcd43
14 changed files with 52 additions and 0 deletions
@@ -0,0 +1,9 @@
+author:  Jason
+
+>	file encodings!
+>	performance standards
+>	platform support
+>	how to write portable code, tests, UI across platforms
+>	#ifdef
+>	note about internal APIs?
+>	avoid take dependency on code via reflection
@@ -0,0 +1,4 @@
+author:  Joey
+> PowerShell community, twitter, facebook, linkedIn...)
+> Community ground rules, appeals process (if they disagree with our decision)
+> SME
@@ -0,0 +1 @@
+author:  Joey
@@ -0,0 +1,3 @@
+author:  Bruce
+
+>Bruce: breaking changes contract (.NET Core has a great one)
@@ -0,0 +1,2 @@
+author:  Bruce
+>	Bruce: code reviews (style, ScriptAnalyzer rules to cover this)
@@ -0,0 +1,6 @@
+author:  Andy
+
+
+> meaning of label, assignees, etc.
+> triage process
+> requirements for resolving (timing), closing... 
@@ -0,0 +1,8 @@
+author:  Hemant
+>	Hemant: "SLAs" for pull requests
+  > ALWAYS point to documents when critiquing PRs
+  >	this should also include the blackbox of Windows/STEX testing
+  >	time can totally be wishy-washy here
+  > "some tests we can only run internally"
+  >	exact timeline not need for Aug17
+  >	Windows quality gates
@@ -0,0 +1 @@
+author:  Sergei and Andy
@@ -0,0 +1,2 @@
+author:  Sergei and Andy
+> steps for Trying out with the binaries a developer just built
@@ -0,0 +1,9 @@
+author:  Sergei and Andy
+
+
+
+>getting started working with PowerShell github
+>branch structure intro
+  >	branching (and folder) structure (where do I submit PRs? where's the release branch? dev branch? working branch?)
+>PR process and requirements
+> more
@@ -0,0 +1,7 @@
+author:  Jim
+
+
+>	Jason/Jim: Testing requirements (code coverage, required for incoming features/enhancements)
+  >	local build/test execution instructions
+  >	tools needed for build/test execution
+  >	our CI explained