Merge branch 'develop'

erniep888 · Feb 2, 2016 · 853bdb9 · 853bdb9
2 parents 46b1dd7 + d64b582
commit 853bdb9
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 1 deletion.
diff --git a/README.md b/README.md
@@ -6,6 +6,16 @@ There have been several different implementations of this web application but no
 
 **The most important goal of Scrumtime 1.0 is to provide a complete separation between the REST API and the Single Page Application UI.**
 
+### Todo ###
+- Get the ScrumTime.Foundation working before renaming to ScrumTime.Core
+    - Migrate to ASP.NET 6
+    - Ensure that the db can be switched to SQLServer (do not force MongoDB to be used)
+- Consult OWASP to determine the best secure JSON approach
+- Create a new UI that is a Single Page Application
+- Evaluate GitHub and BitBucket user authentication mechanisms to determine if both can be supported
+- Remove the concept of ScrumTasks (allow tasks to be updated on end-user's schedule...not just during Scrum meetings)
+- Standup public service in cloud hosted environment (depending on cost)
+
 ### 1.0 Minimum Features
 _**API supporting:**_
 - **User** - A user is the ScrumTime secured user that belongs to the default organization. This provides the CRUD operations for the user.
@@ -22,7 +32,7 @@ _**API supporting:**_
 - **Bug** - A bug belongs to a product, story, or bug and may have tasks and artifacts.
 
 _**Single-Page-Application:**_
-    - Separate the UI project completely from the rest-api
+- Separate the UI project completely from the REST API
 
 ### Post 1.0 Features
 _**API supporting:**_ 

diff --git a/source/ScrumTime.Foundation/ReadMe.txt b/source/ScrumTime.Foundation/ReadMe.txt
@@ -25,3 +25,4 @@ Product
 // Future
 Team
 
+-(ep) Instead of having the scrum tasks being identified with each meeting, I would prefer to promote an end user's ability to update the tasks on their own time.  The current model forces a scribe to be involved during the Scrums.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -25,3 +25,4 @@ Product
		// Future
		Team

		-(ep) Instead of having the scrum tasks being identified with each meeting, I would prefer to promote an end user's ability to update the tasks on their own time. The current model forces a scribe to be involved during the Scrums.