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

Add an update to the Q&A #371

Merged
merged 1 commit into from
Jun 21, 2018
Merged

Add an update to the Q&A #371

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/qna.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,8 @@ There are several reasons:
1. According to SmartBear, [Swagger Codegen 2.x and 3.x should be supported in parallel for a while](https://github.com/swagger-api/swagger-codegen/issues/7754#issuecomment-375039048) without the possibility to work with git branches to merge the fixes from one branch to the next. Having to implement everything twice is not a good idea and the best use of the Swagger Codegen community resources.
1. Having a community-driven version can bring the project to the next level.

UPDATE: After the public launch of OpenAPI Generator, some of the core team members were contacted by Ron (SmartBear) and we explained to him the reasons of the fork as explained above. We also asked him to contact team@openapitools.org if he wants to discuss further but so far we don't see any email from him to team@openapitools.org.
Copy link
Member

Choose a reason for hiding this comment

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

I would remove "we":

and explained to him the reasons of the fork as explained above.

And later:

He was asked to contact team@openapitools.org for further discussion, but so far there was no email from him to team@openapitools.org

Copy link
Member

Choose a reason for hiding this comment

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

"we" is appropriate here, as William and I both had separate interactions with him. In British English, there's also a "Royal We" which is used by single people of office or status; it can be used more generally to distance a single person or entity from a damaging situation. In both cases, "we" would be used correctly in this document.

Copy link
Member

Choose a reason for hiding this comment

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

I had contact with Ron too... I can provide Gitter logs...

It is just the rest of the page written in third person and for this section there is switch to "we". I style problem in my opinion...

But it is a detail.


#### Has anything been done in attempt to address the issues before deciding to fork Swagger Codegen and maintain a community-driven version?

There were several conversations with SmartBear (Ron, Hugo) via emails, gitter, Skype call and GitHub issues.
Expand Down