Skip to content

review member.interface field for full corpus #1083

@1ucian0

Description

@1ucian0

With the introduction of member.interface as a mandatory field. Most of the members fail because they did not declared their API language or interface (as it was not a thing when they were submitted as candidates).

Important

Definition of done
This issue can be closed once all members have an interface field declared. All changes can be done in the same PR.

Tip

Check out the possible interfaces in https://qiskit.github.io/ecosystem/interfaces/ . The field is not about the language is which the software is written, but the language from which the software can be called.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions