generated from noisedestroyers/claude
tryagain
This commit is contained in:
4
.obsidian/workspace.json
vendored
4
.obsidian/workspace.json
vendored
@@ -41,12 +41,12 @@
|
||||
"state": {
|
||||
"type": "markdown",
|
||||
"state": {
|
||||
"file": "README.og.md",
|
||||
"file": "claude.md",
|
||||
"mode": "source",
|
||||
"source": false
|
||||
},
|
||||
"icon": "lucide-file",
|
||||
"title": "README.og"
|
||||
"title": "claude"
|
||||
}
|
||||
},
|
||||
{
|
||||
|
||||
134
README.og.md
Normal file
134
README.og.md
Normal file
@@ -0,0 +1,134 @@
|
||||
# Development Insights & Release Management System
|
||||
|
||||
## Project Overview
|
||||
|
||||
A comprehensive software development project management and release automation system that provides insights into software development projects, build history, ticket management, and streamlined release processes. The system integrates multiple development tools to create a unified dashboard for project oversight and automated release management.
|
||||
|
||||
## Scope of Work
|
||||
|
||||
### Primary Objectives
|
||||
1. **Development Insights Dashboard**: Centralized view of software projects, commit history, build status, and development tickets
|
||||
2. **Release Management Automation**: Streamlined package creation, release note generation, and distribution
|
||||
3. **Multi-Platform Integration**: Unified interface connecting CruiseControl.NET, Manuscript (FogBugz), cloud storage, and help center systems
|
||||
4. **Document Generation**: Automated creation of release notes and documentation from project data
|
||||
|
||||
### Core System Components
|
||||
|
||||
#### Backend Services
|
||||
- **Database Layer**: PostgreSQL database with caching layer for external system data
|
||||
- **CruiseControl.NET Integration**: Real-time monitoring and data extraction from CC.NET build servers
|
||||
- **Manuscript Integration**: Ticket and development comment synchronization from FogBugz/Manuscript
|
||||
- **Document Generation Service**: PDF creation for release notes using project and ticket data
|
||||
- **Cloud Upload Service**: Automated file distribution to configured cloud storage locations
|
||||
- **Help Center Integration**: Automated article creation and updates in support portals
|
||||
- **Web API Server**: RESTful API serving frontend and external integrations
|
||||
- **Database Interface**: Data access layer (potentially using Supabase)
|
||||
|
||||
#### Frontend Application
|
||||
- **Project Management Interface**: Multi-view web application for project oversight and release management
|
||||
- **Real-time Dashboard**: Live project status and build monitoring
|
||||
- **Package Configuration**: Tools for defining and managing software packages
|
||||
- **Release Workflow**: Guided interface for package publishing and distribution
|
||||
|
||||
### Feature Requirements
|
||||
|
||||
#### Project Management Views
|
||||
1. **Project List View**
|
||||
- Display all tracked CruiseControl.NET projects
|
||||
- Project selection and navigation interface
|
||||
- Project status indicators and summary metrics
|
||||
|
||||
2. **Project Details View**
|
||||
- Current build status and detailed information
|
||||
- Historical build and commit data visualization
|
||||
- CruiseControl.NET action logs and developer notes
|
||||
|
||||
3. **Release Notes View**
|
||||
- Integration with Manuscript ticket data
|
||||
- Formatted display of project-related development notes
|
||||
- Release note preview and editing capabilities
|
||||
|
||||
4. **Package Management View**
|
||||
- Software package configuration interface
|
||||
- Association with CruiseControl.NET projects
|
||||
- Cloud storage destination configuration
|
||||
- Help center article mapping and templates
|
||||
|
||||
5. **Publishing Interface**
|
||||
- Package selection for release
|
||||
- Pre-publish validation and preview
|
||||
- Execution of automated publishing workflow
|
||||
- Status tracking and confirmation of completed actions
|
||||
|
||||
### Technical Integration Requirements
|
||||
|
||||
#### External System Connections
|
||||
- **CruiseControl.NET**: Log parsing, build status monitoring, project data extraction
|
||||
- **Manuscript (FogBugz)**: Ticket data synchronization, developer comment extraction
|
||||
- **Cloud Storage Services**: Automated file uploads to configured destinations
|
||||
- **Help Center APIs**: Article creation and modification automation
|
||||
|
||||
#### Data Management
|
||||
- **Real-time Synchronization**: Continuous data updates from external systems
|
||||
- **Historical Data Preservation**: Complete audit trail of builds, commits, and releases
|
||||
- **Configuration Management**: User-defined package settings and publishing workflows
|
||||
|
||||
### Deliverables
|
||||
|
||||
1. **Backend System**
|
||||
- PostgreSQL database schema and configuration
|
||||
- Integration services for all external systems
|
||||
- Web API with comprehensive endpoint coverage
|
||||
- Document generation and file management services
|
||||
|
||||
2. **Frontend Application**
|
||||
- Responsive web interface with all specified views
|
||||
- User authentication and authorization system
|
||||
- Real-time data visualization and interaction
|
||||
- Package configuration and publishing workflows
|
||||
|
||||
3. **Documentation**
|
||||
- System architecture documentation
|
||||
- API documentation and integration guides
|
||||
- User manuals and administration guides
|
||||
- Deployment and maintenance procedures
|
||||
|
||||
4. **Testing & Quality Assurance**
|
||||
- Comprehensive test suite for all components
|
||||
- Integration testing with external systems
|
||||
- Performance and scalability validation
|
||||
- Security assessment and compliance verification
|
||||
|
||||
## Definition of Terms
|
||||
|
||||
### Core Concepts
|
||||
- **Software Package**: A configured, releasable version of software that includes build artifacts, release notes, and distribution settings
|
||||
- **Project**: A software development initiative tracked by CruiseControl.NET with associated builds and commits
|
||||
- **Build History**: Complete record of compilation attempts, test results, and deployment actions from CruiseControl.NET
|
||||
- **Release Notes**: Generated documentation combining Manuscript ticket information and build details for a software package
|
||||
|
||||
### External Systems
|
||||
- **CruiseControl.NET (CC.NET)**: Continuous integration server providing build automation and project tracking
|
||||
- **Manuscript (FogBugz)**: Issue tracking and project management system containing developer tickets and comments
|
||||
- **Help Center**: Customer support portal or knowledge base requiring automated article updates
|
||||
|
||||
### Technical Components
|
||||
- **Cache Layer**: Local database storage of external system data to improve performance and provide offline capability
|
||||
- **Upload Tool**: Service responsible for transferring files to designated cloud storage locations
|
||||
- **Document Creation Service**: Automated system for generating PDF release notes and documentation
|
||||
- **Web Server**: HTTP server component providing API endpoints and serving the frontend application
|
||||
- **Database Interface**: Data access abstraction layer, potentially implemented using Supabase
|
||||
|
||||
### Workflow Terms
|
||||
- **Publishing**: Complete process of selecting a package, generating release materials, uploading files, and updating documentation
|
||||
- **Package Configuration**: Process of defining software package properties, including associated projects, upload destinations, and help center articles
|
||||
- **Integration Synchronization**: Automated data collection and caching from external systems (CC.NET, Manuscript)
|
||||
|
||||
## Success Criteria
|
||||
|
||||
- Unified dashboard providing comprehensive project insights
|
||||
- Automated release workflow reducing manual effort by 80%+
|
||||
- Real-time synchronization with all external systems
|
||||
- Scalable architecture supporting multiple concurrent projects
|
||||
- Intuitive user interface requiring minimal training
|
||||
- Comprehensive audit trail for all release activities
|
||||
22
prompt.md
Normal file
22
prompt.md
Normal file
@@ -0,0 +1,22 @@
|
||||
Please help me create a scope of work for a software project.
|
||||
|
||||
The purpose of the software is to allow many groups to gain insight into software development project, the history of commits & builds, and the tickets used to define the features and bugs. It will also allow the user to view and edit published software packages, select new builds for a package, create release notes, upload the new build's installer to a cloud storage service, and update links on a help center with templated text.
|
||||
|
||||
The software will be be modular. The two main portions will be a backend and frontend.
|
||||
|
||||
The backend will host a postgresql database, and interface with:
|
||||
- CruiseControl.NET, reading the logs and caching them in the database. This data will include software projects, branches, commit and build history, and notes.
|
||||
- Manuscript (fogbugz), reading notes and caching them in the database. This data will include developer comments and timing history.
|
||||
- Document creation, to make release note PDFs from a software package's manuscript and ccnet notes.
|
||||
- Upload tool, to upload software packages and release note documents to defined locations in cloud storage.
|
||||
- HelpCenter Article Updater, to create or modify support portal / help center articles when software packages are published.
|
||||
- Web server, to serve the web ui
|
||||
- Database interface, sitting atop postgresql. Perhaps supabase?
|
||||
The frontend will be a web interface interacting with the Web server component of the backend. The web interface should have several views:
|
||||
- List projects, to show the details of projects tracked by cruisecontrol.net, and letting the user select a project to work within.
|
||||
- Project details, showing current build status and details, history of cc.net actions and notes
|
||||
- Project release notes view, including notes from Manuscript for the selected project
|
||||
- Package list and editor view, showing configurable packages. A software package is a released version of software. The user should be able to give the software package a name, define which cc.net project is associated with it, choose cloud locations to upload to, and define the help center articles to be updated.
|
||||
- Publish view, to allow the user to select a package for publishing, show the publish details (name, upload location, release notes, help center article, etc...), and execute these actions on the package.
|
||||
-
|
||||
Could you start by creating a scope of work to summarize this in README.md? Could you also include a definition of terms?
|
||||
Reference in New Issue
Block a user