Concrete questions after the question feedback at Stack Exchange: Specific features used as user-facing conveniences are:
- Provided the license in a standard location - Most useful API functions highlighted in the front-page README - All Exported functions documented via GoDoc, made sure it correctly published to Go's GoDoc <https://godoc.org/go.didenko.com/fst> website - Integrated *Travis CI* continuous build - Followed semantic versioning guidelines Controversially: - Marked the `dev` branch as default instead of `master` - Used the `0.1.0` tag instead of beta designation, like `1.0.0-beta.1` - Tagged minor patch as `0.1.1` after the original `0.1.0` release - Even though non-master default branch triggers a bug in the Go Report Card <https://goreportcard.com/report/go.didenko.com/fst>, still included the badge, albeit it reviews a previous version of the code. Should any of that be done differently, or is something missing? On Monday, November 13, 2017 at 12:41:13 PM UTC-6, Vlad Didenko wrote: > *fst* is the package I posted to practice community-related workflows, > including writing documentation, using *travis-ci*, setting up vanity URL > redirection. The *fst* package adds convenience routines for testing > filesystem-related logic, helps to create, clone, cleanup, and compare > directory trees. > > > It would be great to have some feedback about how approachable the package > is - both from the user-facing information and from API perspective. > > > The package repository is at: github.com/didenko/fst > <https://github.com/didenko/fst/tree/master> > > If more convenient, I have also opened the question on StackExchange > <https://codereview.stackexchange.com/questions/180333> > > Thank you! > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
