Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

branding: UAVCAN -> OpenCyphal #194

Merged
merged 2 commits into from
Apr 12, 2022
Merged

branding: UAVCAN -> OpenCyphal #194

merged 2 commits into from
Apr 12, 2022

Conversation

pavel-kirienko
Copy link
Member

Supersedes #193

@pavel-kirienko pavel-kirienko self-assigned this Apr 11, 2022
@pavel-kirienko pavel-kirienko mentioned this pull request Apr 11, 2022
Closed
@pavel-kirienko pavel-kirienko marked this pull request as ready for review April 11, 2022 20:20
@pavel-kirienko pavel-kirienko enabled auto-merge (squash) April 11, 2022 20:20
@pavel-kirienko
Copy link
Member Author

There is a critical difference between Cyphal and OpenCyphal: Cyphal is the technology, whereas OpenCyphal is an implementation (there may be several; e.g., there is Canadensis, Arduino-UAVCAN, libuavesp, whatever). Therefore, when referring to the team behind this project, one should say OpenCyphal; when referring to the Specification, one should say Cyphal.

Also at the moment, there is no such thing as Cyphal Consortium.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@coderkalyan
Copy link
Contributor

coderkalyan commented Apr 12, 2022 •
edited
Loading

Also at the moment, there is no such thing as Cyphal Consortium.

😆 I thought I had avoided this but I guess I didn't.

coderkalyan
coderkalyan approved these changes Apr 12, 2022
View reviewed changes
Copy link
Contributor

@coderkalyan coderkalyan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your enhancements on my original PR look good 👍

Are we cutting the 3.0 release with this, or waiting on anything else?

@pavel-kirienko pavel-kirienko merged commit 75bb34c into master Apr 12, 2022
@pavel-kirienko pavel-kirienko deleted the rebranding branch April 12, 2022 15:39
@pavel-kirienko
Copy link
Member Author

I don't think there's anything to wait for, so yes, v3.0 is officially out. This is necessary because we did rename at least one definition in the API.

# for free to join this conversation on GitHub. Already have an account? # to comment
Reviewers

@coderkalyan coderkalyan coderkalyan approved these changes

Assignees

@pavel-kirienko pavel-kirienko

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@pavel-kirienko @coderkalyan