Project Ideas

Project Idea Wiki

Click Edit to share your 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.

---

Your Project Ideas Below

Title: Pulumi Plugin

• Channel Name: #gardening-idea-pulumi
• Description: Spinnaker is a great tool, but it could be even better with the addition of a Pulumi plugin! This would allow users to author resources using infrastructure as code in modern programming languages like javascript, Typescript, python, C# and Go.
• Team Lead (interim): @danfhernandez

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.

Title: Document Halyard Config Fields

• Channel Name: #gardening-idea-hal-config
• Description: Create documentation on halyard config fields and add to Spinnaker.io. The Kleat project needs this, as well as the Kubernetes Operator.

Title: UX Improvements

• Channel Name: #gardening-idea-ux-improvements

• Description: Let's make Spinnaker easier to use, as well as more helpful!

  • Landing page
    • better call to action for creating new/first applications and projects
    • improved layout and information display for applications and projects lists
    • minor UI cleanup and tweaks
  • Applications page
    • new & improved application information summary page
    • minor UI cleanup and tweaks

• Team Lead: TBD, with help UX help from @noahi

Title: Sorting all the things! And by things, we mean docs

• Channel Name: sig-documentation
• Description: Make the Spinnaker documentation easier to use. Participate in our card sorting exercise asynchronously. Start here, and stop by the Slack channel if you have questions or want to chat!
• Team Lead: Documentation SIG

Title: Simplifying and categorizing the CodeLabs section. Docs improvement.

• Channel Name: sig-documentation #gardening-idea-improvecodelabspage
• Description: Organize the table of contents based on Kubernetes provider. Categorize the left column based on cloud provider. For example Tutorials: Azure AKS, AWS EKS, Google GKE, Oracle OKS. Run through one of the tutorials after being categorized to make sure they work in april 2020.

https://www.spinnaker.io/guides/tutorials/codelabs/

Title: Update Project Dependency/Library Versions

• Channel Name: #gardening-idea-dependency-version-updates
• Description: Is there low-hanging fruit around updating versions of open source libraries and other dependencies that Spinnaker relies on? Updating these could have a big security benefit.

Title: Live Contributions Dashboard to Gamify OSS Contributions

• Channel Name: #gardening-idea-contrib-dashboard
• Description: Devstats is great, but it lacks some functionality around real-time data and is not optimized for individual gamification. Can we build a dashboard that we can use to gamify and recognize Spinnaker contributions, that could be shared with other CDF or CNCF projects? GraphQL API queries to GitHub should provide the data we need. Would be good to recognize small contributions like comments and PR reviews as well as PRs etc.