Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a code of conduct #26

Open
labra opened this issue Mar 24, 2020 · 0 comments
Open

Add a code of conduct #26

labra opened this issue Mar 24, 2020 · 0 comments

Comments

@labra
Copy link
Contributor

labra commented Mar 24, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant