> south...
South was long time integrated in half way. Since Satchmo 0.9.2 final
South will be enabled in the quick installation by default and
necessary to be installed before Satchmo update/upgrade or if a future
upgrade is expected. I am trying to support upgrades backwards from
between versions 0.9.0 final and 0.9.2 final easy even without
previously installed South.
Documentation should be balanced. Some people say that Satchmo is an
unusual Django application which duplicates parts of Django
documentation. Not all is to be duplicated.
> And what about the 'default' password, why it was not indicated on the
> quickstart documentation?
I do not know what you mean by 'default' password. (which password and
where?) In general: If you customize anything related to a password, a
default password should be an empty string in all cases for security
reasons in order to every input is rejected by default if a password
is not configured intentionally and no password should be stored in
the souce code except of local_settings otherwise it can be easy
revealed by repository. (no defaults like "1234"!) This is not
anything unexpected what should be explained.
> issue 1317
Nobody wrote anything to my objections to the issue
https://bitbucket.org/chris1610/satchmo/issue/1317/add-requirements-to-setuppy
. Therefore the ticket stay not only "open" but "new".
> What is the best way to submit modifications to the web page/
> tutorials?
The source is the /docs directory of Satchmo. Create a fork of
Satchmo, edit what you want, commit and ask for beedback or send a
pull request if you are just sure with yourself.