-
-
Notifications
You must be signed in to change notification settings - Fork 423
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
Readme update #866
Readme update #866
Conversation
- Add 'Getting Started' section with suggested links and short instructions. - Remove Usage Notes, will be moved into the book. - Transform list of library-creates into table. - Combine features and status into one single feature-list - Add Authors and License section
I kind of like the logo, though I'd want to look into copyright/trademarks a bit more. Please don't remove any content from the README until it's added back somewhere else, though (as I mentioned already in the tracking issue). We should probably update the statement about it being ready "for experimental use". Also, we're at draft 29 now. The Merging status and features somehow probably also makes sense. Agree that we shouldn't spend much space/time on my talk and or the history of the merge anymore. |
Thanks for the review. I will remove the cargo toml, and add those two sections back. So that's an important point that you mentioned: "for experimental use", what would you like to see in this place? In what stage is Quinn? Like QUIC is already used by more than half of all connections from the Chrome web browser to Google's servers. Microsoft Edge and Firefox support it. And I heard it is possible to use it for youtube as well. |
The logo is used over here: https://quicwg.org/, I can find it on many other blog posts or quic related websites. Over here are the original resources: https://github.com/quicwg/wg-materials/tree/master/badge There is a commit from 8 days ago with the message 'Delted LICENSE' So it seems like there is no license on it, hence we can use it until they have. I asked a question over there to the person whom removed the license: |
…n, up-date current draft.
Unfortunately, copyright law dictates that if there is no license specified, you do not have permission to do anything with it. It's also common for standards bodies to want careful control over their branding so it doesn't get associated with work they don't intend to endorse. |
Maybe it's time to get rid of, or at least boil down, the fine-grained feature list, also? That dates from when most QUIC implementations were significantly incomplete; these days if you just say "quinn is a QUIC implementation" then the rest is implied. |
You mean the what's currently the Status list? Yeah, I think getting rid of that makes sense. But let's keep what we currently have as Features, though we should add a note that our HTTP/3 support is still experimental. |
Good point @Ralith, I will fiddle around with some other logo-ideas such that we will not have to deal with those copyright issues. If there are more points to be added or removed from the features list, please let me know. Perhaps it can be nice to add a statement that it is fully async compatible. |
I think we should remove the checkboxes in this case, since they're all checked anyway. |
So reviewing the new version you have so far:
|
…started; Add Jean as colaborater/author; Change to new logo, and reduce vertical height; Add capital letter and period to overview
Thanks for the review, I updated all your feedback points. As for the overview table. I also added a new logo. Please let me know what you think of it. I'm not a very good designer but given some feedback and some time I will be able to get something nice for QUINN. Since the org requires the logo for a profile picture, this has become a necessity. I played along with some variations, I like this one more. The lines in the logo circle represent connections, it seems technical, and it symbolizes streams and endpoints. The strike through line represents time, progress, fast, speed. |
Is this good to go now, any opinions on the logo, and or extra comments on the content? |
I have some nits about the logo. Mainly the spacing seems pretty uneven, in particular the distance between Q and u is much larger than between the other letters. I also wonder how the space between the Q and the circle relates to other spacing (maybe should be a bit more), and I feel that the whitespace on the inside of the circle (between the circle and the other thing) should increase a little bit. It also looks like the horizontal white line throughout the letters is thicker than the spacing between the letters, which feels wrong. Also, please add the logo as an SVG. I don't have Photoshop and am unlikely to have access. (Honestly, the logo doesn't seem all that important to me, so focusing on the content first and leaving the logo for later also seems like a fine option to me.) I think you didn't really respond to my previous remark about table vs bullet list for the overview. Let's not have periods after the Links items, and only have a single capital per bullet there. Also, lower-case Owner in the Authors section. |
Thanks for the second review!
Yes to a certain degree the logo is a secondary item. Tough I would really recommend it, in my view it makes the library look way more professional even if it is a simple logo with just the name 'Quinn' in some special font. And after all the logo is already worked on, so unless you totally don't like it, it's a small effort to make the changes as described. If you really don't want or like it we can remove it and focus on it more at a later stage. All perfect for me 👍 .
I use https://www.photopea.com/ which is free and almost identical to photoshop
Imo the table version looks cleaner but it isn't that big of a deal to change it to a bullet list. I will go for the bullet list and change it back as it was.
For the lower-case 'Owner' I think we should maintain the English grammar rules and maintain the rules for capitalized titles. Thus instead capitalizing |
…dd more space in the circle; Ensure strike trough line is evenenly sized as space between letters; Change Q spacing;
It looks like that can also export to SVG, so let's use that and store it as SVG. SVG is scalable and can be used on the web as-is, whereas PSD is a proprietary file format that cannot be used on the web.
I don't see how it makes sense to use title capitalization for the project roles. |
Cool, I will export it to SVG 👍
It makes sense as in that it is according to the English grammar rules which state that (job) titles that should begin capitalized every other word. You can check sites like https://titlecaseconverter.com/, https://capitalizemytitle.com/, out to validate this grammar. |
@Ralith you maybe reluctant to weigh in on this particular bikeshedding argument, do you have an opinion as the only native speaker on our team? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @djc that the terms in question do not constitute formal job titles; rather, they're plain adjectives, which should not be capitalized.
README.md
Outdated
- All feedback welcome. Feel free to file bugs, requests for documentation and | ||
any other feedback to the [issue tracker][issues]. | ||
- The quinn-proto test suite uses simulated IO for reproducibility and to avoid |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd drop the bullet points here in favor of a paragraph break.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TimonPost if you process this I think this is ready to merge!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On https://github.com/TimonPost/quinn/tree/timon/read-me-update I still see the bullet points in the Contribution section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
o whoops my bad. I changed the wrong bullet points I see
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yeah, please change those back. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed it 👍
Thanks for sticking with it, this is a good change! |
Live version
https://github.com/TimonPost/quinn/tree/timon/read-me-update
Changes
- Grammer fixes
- Remove Usage Notes, will be moved into the book.
- Add project logo
- Add 'Getting Started' section with suggested links and short instructions.
- Update draft version
- Transform a list of library-creates into the table.
- Combine features and status into one single feature-list
- Add Authors and License section
You can open the logo file with https://www.photopea.com/ which is free without accounts and or licenses.
Discussion
I removed the cryptography and buffer section since it will be added to the book.The features list and the status list seemed very similar to me, I think they can be combined into one single list, perhaps there are reasons to keep it as the old way?