David Pordomingo

@carlosms @vcoisne Do you think we should document something like: >_How to use source{d} offline?_ Explaining what you wrote here. I think it could be a recurrent problem in some...

About the error getting `run.sh`, which caused this issue, I think it could be more user friendly, and point to proper docs about what was needed, why, and how to...

Would satisfy your suggestions about the error messages, the ones described by #247 ? Should we iterate on this?

>_[...] this case (I think) was that he tried to start up CE and it attempted to fetch the `run.sh` file from our GitHub repo._ >_Based on the discussion above,...

I don't like the idea of adding extra details in markdown docs because then you're exposing internals, tieing to them, and being forced to update the docs if the implementation...

>_@dpordomingo described [here](https://github.com/src-d/sourced-ce/issues/241#issuecomment-537543975) what are the requirements. Once you have the requirements it can be used offline for local repos._ The problem I see is that it's not explained how...

I think it can be useful for debugging and more expert usage, the same way than for other apps. But we can discuss the output, maybe the standard formats would...

I can fix what you suggested: - links (only the already spotted bugs, not checking all other links), - move `CONTRIBUTING.md` to its standard location, - code syntax. But I...

Per [later investigation](https://github.com/dpordomingo/sourced-ce/commit/06f6370040e3af1e8de38117335e527e738e6fd2#diff-dff6e33f1efa0da0de404f69a5b91165R1), I confirmed that each edition made from GitBook UI ([no matter what is edited](https://github.com/dpordomingo/sourced-ce/commit/06f6370040e3af1e8de38117335e527e738e6fd2#r35019658)) forces GitBook to parse the whole docs, and format them according to their...

Don't worry @vcoisne, we didn't know about this issue before you tried. We discussed it in slack many months ago, but at that moment all of us did prefer regular...