time icon indicating copy to clipboard operation
time copied to clipboard

The Book is hardly readable

Open JakkuSakura opened this issue 4 years ago • 13 comments

This book https://time-rs.github.io/book has almost nothing in it. Is it complete?

JakkuSakura avatar May 26 '21 12:05 JakkuSakura

No, it's not.

jhpratt avatar May 26 '21 15:05 jhpratt

It would be helpful if the book made it clear that it is incomplete - right now the missing text seems like a bug :)

SorteKanin avatar Oct 31 '21 19:10 SorteKanin

This deterred me from using this crate for several days trying to find the actual contents of the book. It was a lower priority so I just kept doing other things and I've only just now started to look into this in particular. I'd be happy to help document if there's a good place to start?

briankung avatar Dec 30 '21 23:12 briankung

Incidentally I was just thinking about this last night. I think it may be preferable to inline this into crate documentation, using empty modules for hierarchy. This would make it more discoverable and more likely to be maintained once it's actually written.

If you're looking for somewhere to start, though, documenting formatting and parsing is probably the best place initially. Other than that I don't think there's a particular order that anything should be completed in.

This is, quite obviously, a low priority for me. There's development of the time crate itself, a number of RFCs that I am working on for Rust itself, and other improvements in Rust that are where I've been putting my focus. I certainly appreciate the offer to help! I assure you I will review any pull requests that are sent my way, even if they may be delayed (like the couple open now).

jhpratt avatar Dec 30 '21 23:12 jhpratt

i also think there should at least be an incomplete warning in the main page of the book and in the website https://time-rs.github.io

laralove143 avatar May 10 '22 18:05 laralove143

There's a reason the US Army puts "This page intentionally left blank." in their various manuals. The book almost scared me away from this crate as well.

egrieco avatar May 12 '22 10:05 egrieco

Everyone: I'm super busy. The website is open source. Feel free to create a pull request with the notice. Or better yet, help write some documentation :wink: Repeated comments here don't do anything.

jhpratt avatar May 12 '22 18:05 jhpratt

Fully understand @jhpratt. Been working on other code but I'll try to get to this in the not too distant future.

I would feel a little bit bad just adding a whole bunch of "Intentionally left blank." comments. However, now that I'm actually using the library, there are a few other code changes that might up the priority of creating a pull request.

egrieco avatar May 12 '22 22:05 egrieco

Am championning this. @jhpratt anything to keep in mind?

xy2i avatar Jul 30 '22 15:07 xy2i

Not really.

jhpratt avatar Jul 30 '22 16:07 jhpratt

(Let me first say I absolutely understand this is maintained on a volunteer basis and this comment is posted with an intention to be useful rather than to complain.)

I also just looked at https://docs.rs/time/0.3.12/time/index.html which has no introduction to the crate but rather just begins with a list of feature flags. It makes the crate look less mature than it apparently is.

I agree that moving it into rustdoc would make it more discoverable and make the rustdoc look better, and that is probably the first thing people will find. This also does not seem like it will be such an enormous crate that it needs a separate book. Since @jhpratt says this would be acceptable in principle I might send some PRs.

sourcefrog avatar Aug 05 '22 14:08 sourcefrog

No worries about tone, I fully agree!

In terms of migration to within the crate, I would prefer the book be developed in its current location first. Once it's sufficient, I can move it into this repository (possibly as a subtree, not sure).

jhpratt avatar Aug 05 '22 15:08 jhpratt