Skip to content

Missing contribution guidelines for alpha stage APIs #1267

Open

Description

@artur-ciocanu

Expected Behavior

The CONTRIBUTING.md file should contain enough details about how should we contribute implementations for alpha stage APIs like:

  • where should we add the APIs to which interface
  • how should we prefix the alpha API methods, like Alpha1
  • which version should we use like 1.x.x vs 0.x.x for alpha stage modules

Actual Behavior

Currently there are no instructions in the CONTRIBUTING.md file.

Steps to Reproduce the Problem

Please check the current CONTRIBUTING.md file.

Release Note

RELEASE NOTE:

Activity

  1. artur-ciocanu commented on Mar 18, 2025

    @artur-ciocanu
    ContributorAuthor

    @cicoyle and @salaboy could you please let me know your thoughts.

  2. siri-varma commented on Mar 19, 2025

    @siri-varma
    Contributor

    I think this is a great idea. But do you think we could further offload it to contributors by adding some automation, like Checkstyle? For example, alpha APIs usually have 'alpha' in their method names. We could create a rule to check if a method name from the Dapr import contains 'alpha' and ensure the calling method also has 'alpha' in its name.

    I understand it is easier said than done. But wanted to know everyone thoughts as well.

  3. cicoyle commented on Mar 19, 2025

    @cicoyle
    Contributor

    Our Contributing.md file mostly aligns with dapr/dapr's. I would be happy to see it expanded on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions