Skip to content

Add a code of conduct #26

@labra

Description

@labra

After reading some discussions I would like to point several things:

  • The viadeSpec is a living document as you can see in the title, so you must look at it as a working draft or proposal rather than as a real specification. The goal is to have a channel to discuss about a common data model for routes representation that can help interoperability.
  • The proposal is not mandatory and the different teams can decide if they accept or not parts or the whole data model. My suggestion is that you take a look at Postel's law when you implement your systems.
  • The spec should not be affected by time considerations of the different teams, i.e. is a change is good to improve the specification, then it could be accepted even if that change can affect the implementations. The goal is to provide a good-enough spec for a route management system
  • Please, try to be polite when you propose or discuss the issues and respect other people's opinions. My advice is that you focus your comments only on the technical aspects of your proposal leaving out any comment about your laboratory assignment, your team work, personal preferences, etc.

The previous notes could be part of a code of conduct file that we can add to the repository.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions