I'm not an expert in packaging, I've released a few apps, but my novice
eyes caught some things:
* Bullet 6 under "Packaging your app" mentions the manifest file, without
specifying anything useful about it to someone (eg: me) who doesn't know
what it's for. Maybe add a descriptional oneliner, or a link to more
details as a bare minimum.
The same goes for other steps here too; they merely instruct what to do
without any background or analysis of the code, like the first tutorials do.
* Creating a release requires you to think about naming, and there's a
couple of names to be defined:
  - package name as found on pypi / installable with pip   (django-polls)
  - module name as it's imported in python   (polls)
  - name of the template dir   (polls, = module name)
Maybe clarify the distinction and definition, and provide some guidelines.
Eg: prepend 'django-' to django apps, and remove it from the module name,
except when it might collide with another module, and use the same name for
the template dir.
* The guide could include a link to documentation on how to setup and
manage a VCS repo for collaboration (even just by pointing to how it's done
for django itself). Also mentionable are other tools like (to name a few)
readthedocs, django-apps.com, and, if CI was given a short introduction,
travis-ci (since many django apps seem to use this) could be mentioned.

Just my thoughts to make this tutorial as good as the others!

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to