It’s been suggested to me that base64, data_encoding, tar, and backtrace are all appropriate here. Sounds right to me. Any other opinions?
This graph shows the great effect the libz blitz has been having for the log
crate. We still need lots more help! Please check the tracking issue for opportunities to contribute.
I updated the crate list per the last few suggestions, and attempted to generalize the categorizations there a bit.
The walkdir review is scheduled for 6/13, and the intent is to start evaluations one month ahead of time, so it’s behind schedule. It still doesn’t have a lead assigned. Is anybody interested in leading the walkdir evaluation, starting this week? It doesn’t require a great deal of experience, since the entire process is outlined in the checklist, and there are previous examples to crib off of.
If not, I will begin the walkdir evaluation on Friday.
The error-chain review is scheduled for 6/27, which means @aturon needs to get that evaluation rolling soon as well.
Ok I’m happy to pick up the walkdir
lead. I think it’s a fairly safe crate to get my feet wet, there’s plenty of prior work to look at and @burntsushi is already on board. Should be a walk in the park
But if you’re looking at the Libs Team peeps to take on these roles that’s no problem
Thanks a bunch @KodrAus. You are assigned! Please open the thread at your earliest convenience.
I added num_cpus to the crate list.
It came to my attention that Packt has a forthcoming book called “Rust Cookbook”. I filed an issue about it.
Done Doesn’t look like I’ve got permission to make the post a wiki though, could one of the admins please convert it?
Done. The way I did it was to click the "..." at the bottom of the post, then the wrench icon, then "make wiki".
Status update 2017-05-27
Here’s what is going on in libz blitz news this week. Contribution opportunities are in bold.
reqwest
- The evaluation is wrapping up
- We could use more eyes on the guidelines checklist
- The libs team discussion will be on Tuesday
- Expect lots of issues to be filed soon! We will need help
walkdir
- The evaluation has started!
- The libs team discussion will be two weeks from Tuesday
log
- Still closing out those issues from the evaluation
- @omh1280 fixed some missing derives
- @omh1280 added documentation for the log! macro
- @omh1280 clarified some documentation
- @nivkner ensured that public types have Debug impls
- @omh1280 added examples for all the macros
- @nivkner improved the error type for FromStr
- @omh1280 improved documentation of log levels
- @omh1280 linkified all the documentation
- @opilar provided CI badges in Cargo.toml
- @opilar set the documentation link to docs.rs
- @omh1280 eliminated stuttering type names
- @budziq added keywords to Cargo.toml
- @AndyGauge extended example code for log_enabled
- @AndyGauge documented how to set max log level
- @morrme corrected the html_root_url
- @budziq linkified some documentation
- @nivkner resolved some inconsistent error messages
- @morrme corrected the html_root_url for env_logger
- @budziq eliminated stuttering in env_logger
- @morrme set the documentation link for env_logger
- @MarkMcCaskey documented the Metadata struct
- @jehiggs documented the Record struct
- @jehiggs documented the Location struct
memmap
flate2
Cookbook
- We made great progress this week and last, but plenty of issues left! Check out CONTRIBUTING.md
- We need feedback on how to make the cookbook better navigable!
- @brson filled out the “about” page, including how to read this book and a note about crate representation
- We may need to re-brand the cookbook
- @budziq fixed an mdBook formatting issue
- @luisbg fixed a typo
- @luisbg added an example of recursively finding all files by predicate
- @budziq added an example of showing timestamps on log messages
- @cetra3 added an example of iterating through a paginated web API
- @bjnyfv fixed up the hex encoding / decoding example
- @AndyGauge added an example of posting a file to paste.rs
- @pepyakin added a crossbeam example
- @baishuai fixed a mistake in the lines of a file example
- @budziq provided clearer explanations of many examples
- @budziq added an example of headers and URL parameters
API guidelines
Thanks everyone!
-
I added a link the recording of today’s libs team meeting about
reqwest
. -
I wrote a summary of the meeting.
Can I suggest glob/globset? I believe globset
is the way forward but it would make sense to transition the glob
crate to be globset
Thanks for the suggestion @Keats! Seems like the right kind of crate, though I’m not familiar myself.
So far our crate tracking issues have not had a “Release 1.0” issue actually filed, but I kind of think they should. I might go back and do that and link up the tracking issues. Any opinions?
There’s some question about whether it makes sense to include mio in the cookbook as it is a low level systems-integration piece.
Rust Libz Blitz status update 2017-06-02
Here’s what is going on in libz blitz news this week. Spoiler alert: it was another great week! Thanks everybody.
Upcoming we’ll expect @aturon to open the error-chain evaluation soon. It also looks like we need to get someone on the hook to lead the mio evaluation to get that evaluation started by 6/11.
I’m also interested in getting some of the “out-of-band” evaluations going, crates like idna, net2, unicode-segmentation, env_logger. We can run these exactly as we do the others, but we just won’t schedule a libs team meeting to finalize them. Anybody interested in leading them just speak up. I may pick up one myself next week.
log
- @budziq updated docs to link to loggers
- @rap2hpoutre improved the max_level docs
- @jehiggs improved Location docs
- @MarkMcCasky improved Metadata docs
- @jehiggs improved Record docs
- @budziq improved added “Errors” to set_logger docs
- @nivkner improved set_logger_raw docs
- @rap2hpoutre added an example to set_logger
- @aergonaut added serde impls for LogLevel and LogLevelFilter
- @meven also added serde impls for LegLevel and LogLevelFilter!
- @alisha17 began changing set_logger to panic on error
- @nivkner updated ParseLevelError docs
- @nivkner renamed the error type
reqwest
- libs team reviewed on 5/30, with the help of @seanmonstar, @KodrAus, and stephanbuys. video
- @dtolnay filed the tracking issue
- @tomprince hid internal conversions to reqwest::Error
- @tomprince made Error::get_ref return a Send + Sync error
- @seanmonstar converted RequestBuilder to an &mut self builder
- @theduke began moving the try_ macro
- @alisha17 converted examples to use ?
- @little-dude handled json serialization errors
- @budziq added html_root_url
flate2
Looks like the only remaining blocker is to rename internal types to match public types.
url
No activity this week but there are still issues open.
memmap
Looks like remaining work is blocked on questions about the API.
cookbook
- @budziq added a note about OAuth to network examples
- @derekdreery added a memmap example
- @budziq added a thread pool example
- @jaemk put sheilds behind a cache
- @budziq added an example of custom headers and URL parameters
- @budziq added an example of consuming a paginated REST API
API guidelines
Tasks needing contributors
- log: Support construction of
LogRecord
s andLogMetadata
- log: Expand log! docs for
max_level_*
- log: Maintaner wanted for env_logger
- reqwest: Expose RedirectAttempt and RedirectAction types
- reqwest: Add realistic examples for Response
- reqwest: Document Body constructors
- reqwest: Document Error
- reqwest: Add examples for
body
- url: Document percent_encoding module
- url: Implement Debug for many types
- url: Put error conditions in “Errors” sections
- url: Explain the term “fragment”