coulomb/markitect-main
2
0
Fork 0
Code Issues 60 Pull Requests Actions 1 Projects 12 Releases 1 Wiki Activity

Let's have diary entries as seperate files in a subdir #48

New Issue
Closed
opened 2025-09-30 22:07:39 +00:00 by tegwick · 0 comments
tegwick commented 2025-09-30 22:07:39 +00:00
Owner
Copy Link

The idea of keeping a project diary is to provide a big picture view for what has been going on.
Diary entries should not be as detailed as git commit messages obviously and there should be one a day (hence the name) when a project is worked on intensly and once after major milestones at the least for low activity projects.

The goal is to pick up work again where we left easily. Life is full of distractions you know.

Maybe we should have a project historian agent to help keep the diary.

Let's start easy by cleaning up and then creating an issue for the creation of a betteragent to support us accross future projects.

The idea of keeping a project diary is to provide a big picture view for what has been going on. Diary entries should not be as detailed as git commit messages obviously and there should be one a day (hence the name) when a project is worked on intensly and once after major milestones at the least for low activity projects. The goal is to pick up work again where we left easily. Life is full of distractions you know. Maybe we should have a project historian agent to help keep the diary. Let's start easy by cleaning up and then creating an issue for the creation of a betteragent to support us accross future projects.
tegwick added this to the Clean Repository Standard project 2025-09-30 22:07:39 +00:00
tegwick changed title from Let's have diary entrie as seperate files in a subdir to Let's have diary entries as seperate files in a subdir 2025-10-01 00:27:41 +00:00
tegwick moved this to Done in Clean Repository Standard on 2025-10-04 22:59:04 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
priority:critical
Critical priority issue
 priority:high
High priority issue
 priority:low
Low priority issue
 priority:medium
Medium priority issue
 status:active
Issues currently being worked on
 status:blocked
Issues blocked by dependencies
 status:done
Completed issues
 status:review
Issues under review
 status:todo
Issues ready to be worked on
 type:bug
Bug report
 type:documentation
Documentation update
 type:enhancement
Enhancement to existing feature
 type:feature
New feature request
 wish
Feature wishlist item - idea to be discussed and refined
 wish/archived
Archived or rejected wishlist item
 wish/discussion
Wishlist item currently being discussed and refined
 wish/draft
Wishlist item with initial draft specification
 wish/ready
Wishlist item ready to become a regular issue
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project Clean Repository Standard
Assignees
Clear assignees
bubble-reader tegwick
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coulomb/markitect-main#48
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?