How to contribute to tiedot about tiedot

[HouzuoGuo]

Hello & thank you!

You have done the right thing - after cloning the repository, there is a local copy of tiedot source code and you can freely make code changes, test, and compile.

Do not worry about the package namespace (github.com/.../tiedot) mentioned in main.go, Go will only use the local source code during compilation, formatting and testing.

Remember that Go relies on GOPATH environment variable to discover source code "packages", therefore make sure that the local source code copy lives under the GOPATH.

Here's an example setup:

Prepare environment

export GOPATH=/tmp/mytiedot
mkdir -p /tmp/mytiedot/src/github.com/HouzuoGuo/
cd /tmp/mytiedot/src/github.com/HouzuoGuo

Clone and compile

git clone https://github.com/HouzuoGuo/tiedot.git
cd tiedot
go build

However, in order to push your commits to Github, the usual approach is to "fork" (to make tiedot "your own"), push some commits, and submit a "pull request" to the original project in order to merge your commits. I usually like to avoid the hassle and just enable your commit access to this repository.

What do you have in mind in terms of new features/improvements for tiedot?

[Sekhmet]

Thanks!
When I've cloned my fork i created it in src/github.com/Sekhmet/tiedot.
I should anyways clone this to folder called src/github.com/HouzuoGuo/tiedot (even if it doesn't match my real forked repository) to force Go import good files?

[HouzuoGuo]

Assuming that you intend to merge changes back to the original project some point in the future, the fork should not change the package namespace, and Go is not going to fetch source code from remote locations during compilation and testing.

If you wish others to try out your fork, then you need to change the namespace to match your username, so that others may download/compile your source code via go get mechanism.

[Sekhmet]

Thanks!