Add guidance to help folks with Hacktoberfest 2020 here

[a-roberts]

Hey everyone, I've been doing things with the cd.foundation's outreach commitee and we've been discussing Hacktoberfest and how Jenkins did it in the past, see https://www.jenkins.io/events/hacktoberfest/

I think it'd be a good opportunity to encourage folks to contribute to Tekton as part of Hacktoberfest and so I've been thinking of putting together some documentation - we could tell people which labels to use, who are handy contacts if they get stuck, and who are the awesome mentors/contacts to have.

As a start it could be something like added here into the readme at the top (so under, say, hacktoberfest-2020.md which we link to)...

@eddycharly on our recent Dashboard Working Group call suggested we do things a little more personable too as opposed to just some text - so a link to a short introductory video may be of use, as well as a mention of the project ideas we have for each area.

For project areas I'm thinking...

• Dashboard
• Pipeline
• CLI
• Catalog
• Website
• Experimental

Operator and Chains? Not sure about the learning curve here, unfamiliar with contributing to either, so could do with some experts.

Tagging @abayer @vdemeester @bobcatfish @eddycharly @dibyom @afrittoli @AlanGreene for input especially, should anyone want to share ideas on how to best go about it.

Please share this as well with anyone else you think can pitch in, thanks!

P.S, for the Dashboard we've got this so far, and this is from our most recent working group call.

Hacktoberfest

• Docs / website / katacoda enhancements
• Import
  • from catalog by version?
  • kubectl apply doesn’t work with generateName (needs to be a create) which is used in a lot of examples in the pipeline repo, so should the action be customisable or use a different method to import the resources Update Import Resources to support use of generateName dashboard#1552
  • Support git revision Add support for specifying git revision on Import Resources form dashboard#1550
• Workspaces not supported for TaskRuns and PIpelineRuns Ability to bind Workspaces dashboard#1283
• Anything for chains? Looks like no CRDs
• Single namespace install revisit (docs) Limit dashboard visibility to a subset of namespaces dashboard#1018 and Document single namespace visibility installs for release (experimental first) dashboard#1507
• Security revisit (anything preventing adoption)
• Platform support (e.g. clouds) - try and doc
• Any links/common themes to the other Tekton project areas?
• Update roadmap with progress to date / changes in approach etc.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[AlanGreene]

I think it's safe to close this one now 😸

/close

[tekton-robot]

@AlanGreene: Closing this issue.

In response to this:

I think it's safe to close this one now 😸

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.