Skip to content
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

Wiki #17

Open
graforlock opened this issue Nov 10, 2016 · 2 comments
Open

Wiki #17

graforlock opened this issue Nov 10, 2016 · 2 comments
Assignees
Labels

Comments

@graforlock
Copy link

graforlock commented Nov 10, 2016

I was wondering how do we proceed on with wiki:

Since you cannot fork it and pull request it we can create a develop branch on wiki locally and public repo sodium-typescript-wiki in SodiumFRP with default branch as develop. We can then add another origin as develop to point at sodium-typescript-wiki, work there, and once its ready, just merge and push to original origin.

Any thoughts?

@graforlock
Copy link
Author

@the-real-blackh @rixrix I will be having my go at the gitbook , it would be full of errors of sorts, but anyone would be able to contribute.

@dakom
Copy link
Contributor

dakom commented Jan 4, 2018

@graforlock - did you make progress with the gitbook? Or should we continue with the wiki?

@the-real-blackh - I'm considering picking away at some docs and things here and there, maybe on the Wiki for starters but the gitbook sounds cool too. Either way, I'm concerned about stepping on the toes of your published book. I'd imagine there's significant overlap and I wouldn't want to prevent sales, and there's even room for outright plagiarizing since you've already documented lots of the API there... can you please share your official stance on this or maybe some guidelines on what should/shouldn't be copied from the book and published publicly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants