aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLeandre17 <leandre.godet@epitech.eu>2025-02-17 20:06:22 +0100
committerLeandre17 <leandre.godet@epitech.eu>2025-02-17 20:07:07 +0100
commit8e307f611a62e54018660ddcd13d52f516516dad (patch)
treec4c404f599c148d31290f2c0e59da47cff637d4b
parentc5c8ee8aa105b5a7653264a5279211b9500a40b3 (diff)
[ADD] new plan
-rw-r--r--_plan.qmd100
1 files changed, 79 insertions, 21 deletions
diff --git a/_plan.qmd b/_plan.qmd
index 2fef622..f3b35d2 100644
--- a/_plan.qmd
+++ b/_plan.qmd
@@ -11,7 +11,7 @@ The basic plan 3 month plan is this:
The weekly tasks could be follows:
-Month 1: Research, Planning, and Initial Prototypes
+# Month 1: Research, Planning, and Initial Prototypes
* defining the problem starts 2025-02-05 todo by sabin
* setup the project collab-tools starts 2025-02-05
@@ -43,9 +43,23 @@ Month 1: Research, Planning, and Initial Prototypes
* [research different ways to extend Quarto] - todo by sabin
* [define the project scope] - todo
* [reflect on report structure]
+ * Parts of the report advice:
+ * Front page.
+ * Abstract.
+ * Table of Contents.
+ * Introduction.
+ * Project Planning.
+ * Analysis and Design.
+ * Description of the Program.
+ * User Guide.
+ * Testing.
+ * Discussion and Conclusion.
+ * Bibliography.
+ * Appendices
+ * Are all these parts usefull ? Do we need more or less?
* [advisor meeting agenda]
- * [time]
- * [surprise]
+ * [time] how should we spend our time / balance (meeting, personal work)
+ * [surprise] how to handle / forsee anexpected event
* [write an UML diagram of quarto]
## From 02-22
@@ -53,32 +67,76 @@ Month 1: Research, Planning, and Initial Prototypes
* [write Lua parser]
* [write Lua validator]
* [write Lua serializer]
-* Document the development process
+* [document the development process]
+* [write report Description of the program]
## From 03-01
-* Refine the prototype
-* test edge cases
-* gather community feedback
+* [refine the prototype]
+* [test edge cases]
+* [gather feedback]
+* [write report introduction]
+* [write report abstract]
-Month 2: Full Development & Testing
+# Month 2: Full Development & Testing
-## From 03-14
+## From 03-08
+* [improve prototype]
+* [test basic functionalities]
+ * parser
+ * validator
+ * serializer
* [midterm report]
+ * ready to be send
+ * understandable by the other
-* Week 5: Improve prototype as required
- * Test basic functionalities
-* Week 6: Optimize performance, improve error handling, and add customization options
- * Create test cases for different scenarios
- * Validate error handling and robustness
-* Week 7: Test across real-world use cases and ensure compatibility with different Quarto formats
-* Week 8: Gather user feedback, make necessary improvements, and finalize core functionality
+## From 03-15
-Month 3: Finalize Documentation, Deployment
+* [midterm report]
+ * March 19th 1215-16 (ca.) in Room 44.3-40
+* [optimize performance]
+* [improve error handling]
+* [add customization options]
+* [create test cases] for different scenarios
+* Validate error handling and robustness
+
+## From 03-22
+
+* Test across real-world use cases and
+* [ensure compatibility] with different Quarto formats
+
+## From 03-29
+
+* [gather user feedback]
+* [make necessary improvements]
+* [finalize core functionality]
+
+# Month 3: Finalize Documentation, Deployment
+
+## From 04-05
+
+* [write more documentation]
+* [tutorials]
+* [create a demo]
+* [write report User Guide]
+
+## From 04-12
+
+* [conduct final testing]
+* [fix any remaining bugs]
+* [write report testing]
+
+## From 04-19
+
+* [release the extension]
+* [promote it] within the Quarto community
+* [write report discusion and conclusion]
+* [write report appendices]
+* [write report bibliography]
+
+## From 04-26
-* Week 9: Write documentation, tutorials, and create a demo project
-* Week 10: Conduct final testing and fix any remaining bugs
-* Week 11: Release the extension and promote it within the Quarto community (if possible)
-* Week 12: Gather post-release feedback and plan for future improvements
+* [gather post-release feedback]
+* [plan for future improvements]