using submodules

[axd1967]

Is there a need to use submodules? The submodule concept is quite tricky, and this repo uses one submodule only. The contribution guide silently assumes a contributor masters the submodule concept.

E.g. when I want to contribute, I'll store my contributions on a branch that will be pushed and used for a pull request. But manipulating branches in the presence of submodules needs some experience (that I'm trying to acquire right now).

(see also e.g. https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/, but there are more examples out there)

[nesquena]

You are right, the submodule approach is not ideal. Need to come up with an easier way to allow people to send pull requests for the wiki.

[axd1967]

Why not move the current pages right into this repository, and ditch the submodule?

I guess the issue is clouded by the fact that the submodule is actually the GitHub wiki content (or that's probably the reason why a submodule is being used).

A possible, but less attractive alternative could be to ditch the wiki, and use the web publishing feature ("pages) of GitHub instead. (I'm not experienced in that for the moment, so I'm not sure how well that would work)

[yvolk]

+1 for moving content to a single repository.
I just wanted to contribute my corrections to the guide directly from my device, but I can't - I don't have a User friendly tool for this on Android :-(

[axd1967]

hello??

this is a confusing situation.

here is an example of a problem: https://github.com/codepath/android_guides/wiki/Listening-to-Sensors-using-SensorManager is not the same as 04b67ba (use this SHA-1 in the "other" wiki, and if this confuses you, you found the problem that this issues tries to uncover!)