You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
@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?
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 reposodium-typescript-wiki
inSodiumFRP
with default branch asdevelop
. We can then add another origin asdevelop
to point atsodium-typescript-wiki
, work there, and once its ready, just merge and push to originalorigin
.Any thoughts?
The text was updated successfully, but these errors were encountered: