-
Notifications
You must be signed in to change notification settings - Fork 2
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
Blitz more Libz! #11
Comments
Yes. Please note there was the wish for a better name last year. |
Ah I wasn't aware of that, and can see why some folks might prefer a different name. What if we just call them 'evaluations'? |
Let's bikeshed a little on that, catchy would be desirable. |
How about making https://github.com/Gilnaa/globwalk the next https://github.com/rust-lang-nursery/glob ? |
As I brought up in the CLI WG, what about helping to organize libz blitz centered around each of the other WGs. For example, the CLI WG could identify features we need, crates that fulfill those features, and then work on a libz blitz to help get them fleshed out. |
I would like to bring |
@Enet4 @epage Using the domain working groups as a source for libraries to focus on sounds good to me! Particularly libraries that are common between use-cases in multiple domains. Maybe we should start a thread on one of the forums to collect a set? @Keats Should we suggest @skade I've opened #15 to work on a new name, so we can keep the threads a bit separate. |
Yes, I've been thinking about improving chrono's API for a long time. I've been intending to write up my plans, as well, perhaps blitzing would give me the kick I need to actually do it? It'd be welcome, anyway. |
@KodrAus the |
Also (@KodrAus @Enet4) related to the state of chrono: one of the big issues that I had in the past was that the primary maintainer was essentially out of the picture and, although they owned the repo and crates.io, they weren't responsive or making releases. They've since transferred ownership to me, which gives me a lot more emotional wherewithal in terms of actually doing work for the project. It also means that my old philosophy of not seeking out contributions because it could be so disheartening to do work and have it not released for a year goes away. Hopefully by this time next year we'll have a much larger group of people maintaining chrono, with at least one other releaser, and ideally a 1.0 release. There are big challenges to overcome to get there, but (other than multiple calendar systems, which I think might block 1.0 and which I don't know what they should look like) I think we can get pretty far. |
@quodlibetor let me know if you need help with |
Until we get an official I've spent a bit of time switching some types around and redesigning some traits and I think we can get to a much simpler API while still maintaining all of chrono's current power. |
@quodlibetor @Dylan-DPC @Enet4 I thought we could move the discussion about @Keats Thanks for clarifying! I think I understand the background around |
The libz blitz offers a great framework for exploring, evaluating and polishing libraries. Should we do more evaluations for stabilising libraries this year? If so, what libraries do folks think could benefit from a blitz?
The text was updated successfully, but these errors were encountered: