Skip to content

Add contribution 101 #266

Description

@mbohlool

Add a contribution document explain the structure of the repo and best practices to start developing. Topics includes (but not limited to):

  • What is generated, semi-generated, and manual
  • What is base repo and how it is related to this repo
  • How to update generated client
  • What should be fixed in preprocessing script and what should be an upstream fix
  • What should be commit and how many commits my PR should have

Activity

  1. ebbeelsborg commented on Jun 22, 2017

    @ebbeelsborg

    Perhaps also some guidelines on how and when one should write different types of tests (unit, integration, e2e...)?

  2. mbohlool commented on Jun 22, 2017

    @mbohlool
    ContributorAuthor

    That is a good idea. I can start something and then we can all contribute to it.

  3. self-assigned this
    on Jun 22, 2017
  4. removed their assignment
    on Apr 15, 2019
  5. fejta-bot commented on Jul 14, 2019

    @fejta-bot

    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.

    Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
    /lifecycle stale

  6. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jul 14, 2019
  7. micw523 commented on Jul 26, 2019

    @micw523
    Contributor

    /remove-lifecycle stale

  8. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jul 26, 2019
  9. roycaihw commented on Aug 20, 2019

    @roycaihw
    Member

    /assign

  10. added
    kind/documentationCategorizes issue or PR as related to documentation.
    priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.
    on Sep 11, 2019
  11. roycaihw commented on Oct 1, 2019

    @roycaihw
    Member

    What is generated, semi-generated, and manual
    What is base repo and how it is related to this repo

    The original design was https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/csi-new-client-library-procedure.md

    Also it would be great if we have document around how to run tests in this repo. Ref: kubernetes-client/python-base#126 (comment)

  12. micw523 commented on Oct 22, 2019

    @micw523
    Contributor

    /assign

  13. scottilee commented on Nov 30, 2019

    @scottilee
    Contributor

    @micw523 any update on this and #910?

  14. removed their assignment
    on Dec 2, 2019
  15. micw523 commented on Dec 3, 2019

    @micw523
    Contributor

    Thanks for the ping - it will be done - I just returned from a conference and regained my desktop.

  16. added a commit that references this issue on Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

kind/documentationCategorizes issue or PR as related to documentation.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions