-
Notifications
You must be signed in to change notification settings - Fork 17
Project Ideas
All hackathon participants will check this document to find out what project ideas are on the table. Present yours here, even if it isn't fully formed.
If you see an idea here that interests you, visit its Slack channel to engage.
Each project idea must have a title, channel name, and description.
Your channel name should be #gardening-idea-<nameStringThatWorksAsARepositoryNameToo>
When you have volunteered yourself or identified a team lead, add the team lead's github handle.
For example:
Title: Barbot
- Channel Name: #gardening-idea-barbot
- Description: Build a bot that reminds you at opportune times to consider drinking a mocktail or adult beverage.
- Team Lead: @dnilasor
Title: Foobot
- Channel Name: #gardening-idea-foobot
- Description: Build a bot that blasts Oscar the Grouch GIFs to multiple Slack channels each time a pipeline stage completes (please don't build this)
No numbering necessary! To add yours below, just start a new line for the title and use * for the Channel Name and Description.
Title: Spinnaker Istio Integration
- Channel Name: #gardening-idea-istio
- Description: Wondering how many folks out there use Istio and how we are all managing delivery of various configurations (especially in large orgs). Wondering if we can come together to somehow visualize (or lean into existing tools) Istio infrastructure in Spinnaker. There has been some talk of this in the past, but curious how others are managing this!
Title: Spinnaker App/Project Cost Analysis
- Channel Name: #gardening-idea-costanalysis
- Description: Today, there are many free (and paid) offerings to generate cost analysis of various cloud providers. An idea would be somehow aggregating cost metrics, data, etc per application. Some ideas would be common tags, or somehow a way to estimate the price. AWS has AWS Cost Explorer and GCP has a Cost Explorer of its own. Challenges are how to integrate tags and such to query effectively! Open to ideas around this too.
Title: Spinnaker CX Pages on Spinnaker.io
- Channel Name: #gardening-idea-cx
- Description: Spinnaker.io needs a clearer path for new developers to follow when contributing to Spinnaker services. Existing resources for development environment setup and contribution guidelines should be reviewed and updated. We should create new content providing clear paths for dev using local environments and Kubernetes or VMs to test and validate. A detailed proposal for CX content organization is needed for the upcoming Spinnaker.io site refresh.
Title: Spinnaker Monitoring Doc
- Channel Name: #gardening-idea-monitoring-doc
- Description: Many orgs have monitoring set up for their Spinnaker instance(s) and may have dashboards that they use to monitor health and performance. Documenting these implementations would be very helpful.
Title: RDS Snapshotter Plugin
- Channel Name: #gardening-idea-rds-snapshotter
- Description: Build a plugin to kick off and optionally wait for an RDS snapshot to occur in a native pipeline stage.