gonum / old-website Goto Github PK

Code for the Gonum website

HTML 22.10% CSS 70.96% Go 6.94%

old-website's Introduction

Gonum

Installation

The core packages of the Gonum suite are written in pure Go with some assembly. Installation is done using go get.

go get -u gonum.org/v1/gonum/...

Supported Go versions

Gonum supports and tests using the gc compiler on the two most recent Go releases on Linux (386, amd64 and arm64), macOS and Windows (both on amd64).

Note that floating point behavior may differ between compiler versions and between architectures due to differences in floating point operation implementations.

Release schedule

The Gonum modules are released on a six-month release schedule, aligned with the Go releases. i.e.: when Go-1.x is released, Gonum-v0.n.0 is released around the same time. Six months after, Go-1.x+1 is released, and Gonum-v0.n+1.0 as well.

The release schedule, based on the current Go release schedule is thus:

Gonum-v0.n.0: February
Gonum-v0.n+1.0: August

Build tags

The Gonum packages use a variety of build tags to set non-standard build conditions. Building Gonum applications will work without knowing how to use these tags, but they can be used during testing and to control the use of assembly and CGO code.

The current list of non-internal tags is as follows:

safe — do not use assembly or unsafe
bounds — use bounds checks even in internal calls
noasm — do not use assembly implementations
tomita — use Tomita, Tanaka, Takahashi pivot choice for maximimal clique calculation, otherwise use random pivot (only in topo package)

Issues

If you find any bugs, feel free to file an issue on the github issue tracker. Discussions on API changes, added features, code review, or similar requests are preferred on the gonum-dev Google Group.

https://groups.google.com/forum/#!forum/gonum-dev

License

Original code is licensed under the Gonum License found in the LICENSE file. Portions of the code are subject to the additional licenses found in THIRD_PARTY_LICENSES. All third party code is licensed either under a BSD or MIT license.

Code in graph/formats/dot is dual licensed Public Domain Dedication and Gonum License, and users are free to choose the license which suits their needs for this code.

The W3C test suites in graph/formats/rdf are distributed under both the W3C Test Suite License and the W3C 3-clause BSD License.

old-website's People

Contributors

Stargazers

Watchers

Forkers

sbinet-gonum mewbak mewpull benluteijn

old-website's Issues

redirect: add redirect for gonum.org/v1/exp/...

sporadic travis test failures due to TLC cert domain mismatch

What are you trying to do?

Test PRs.

What did you do?

Send a PR to gonum/gonum.

What did you expect to happen?

Consistent test results.

What actually happened?

Sporadic failures due to TLS cert domain mismatch.

For example, this tail of the travis log:

$ go get gonum.org/v1/tools/cmd/check-imports
go get: warning: modules disabled by GO111MODULE=auto in GOPATH/src;
ignoring go.mod;
see 'go help modules'
package gonum.org/v1/tools/cmd/check-imports: unrecognized import path "gonum.org/v1/tools/cmd/check-imports" (https fetch: Get https://www.gonum.org/v1/tools/cmd/check-imports?go-get=1: x509: certificate is valid for *.netlify.com, netlify.com, not www.gonum.org)

travis_time:end:024399ea:start=1540833706042593151,finish=1540833706180869248,duration=138276097
 
 The command "go get gonum.org/v1/tools/cmd/check-imports" failed and exited with 1 during . 

Your build has been stopped.

What version of Go and Gonum are you using?

N/A

Does this issue reproduce with the current master?

N/A

Force TLS connections?

Netlify has a "Force TLS connections" , "Forcing TLS will redirect all traffic to HTTPS and set Strict Transport Security Headers for 1 year."

Is this something we want? We somewhat force this anyway because the hugo generation (at least at the moment) hard paths https links.

Avatar doesn't show up on the website

When I use hugo server --watch the avatar shows up fine, but it isn't showing up for me on chrome or firefox. I don't see any build errors on netlify either. Looking in to it.

Link to mailing list uses `mailto:` scheme in contact section, should only use https:

From https://www.gonum.org/#contact:

       <li>
         <i class="fa-li fa fa-envelope fa-2x" aria-hidden="true"></i>
-       <span id="person-email" itemprop="email"><a href="mailto:https://groups.google.com/forum/#!forum/gonum-dev">https://groups.google.com/forum/#!forum/gonum-dev</a></span>
+       <span id="person-email" itemprop="email"><a href="https://groups.google.com/forum/#!forum/gonum-dev">https://groups.google.com/forum/#!forum/gonum-dev</a></span>
       </li>

https isn't loading properly

A lot of the icons don't load properly from https://www.gonum.org/, and navigating switches from https to http. See https://www.reddit.com/r/golang/comments/70mnfi/new_hugobased_website_for_gonum/dn4cc6b/

I think this is an academic theme issue. Going to https://kortschak.io/ or https://gopherdata.io/ gives me "connection not private" errors on both firefox and chrome (os x). I have no idea why gonum.org is fine for the connection not private errors, though we have other issues.

Misconfigured mailto link

On the first page the link to the google group is
"mailto:https://groups.google.com/forum/#!forum/gonum-dev"
causing it to open my email client instead of linking to the page.

This is probably caused by the email being configured to be that link and the page being set up to auto generate link.

gonum.org: add a link to godoc.org

it seems we don't have a prominent link to Gonum's godoc documentation from gonum.org.
(there are links to various godoc packages on the main page, but nothing that says "here is the documentation page")

we probably should add something that can be easily discovered on the main landing page.