blob: 76d5f97150562b823cd142f0bcd06a6997497367 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
Ideas
=====
* Bazaar:
* README with basic info and HOWTO
* Rename de project to "boilerplater" or "skeletor"?
* Licenses:
* Public domain
* Creative Commons
* Perl
* Metafiles:
* Changelog formats
* Semver
* [Developer Certificate of Origin](https://developercertificate.org/)
([1](https://elinux.org/Developer_Certificate_Of_Origin),
[2](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst).
* Standards:
* Robotstxt
* Securitytxt
* Modules:
* Python
* Flask
* Debian package
* Website checklist
* Manpage
* Multilicense
* Bugs-everywhere
* Code:
* Per-module push-to-deploy scripts (`bin/deploy.d`)
* Makefiles: non-conflicting target names with aliases/shorthands in the main Makefile
* Check/detect/verify mode, telling which modules are installed and checking for missing things (like LICENSE)
* Update mode to update configs between a project and templater's defaults
* If git is in use, commit all changes, but check first it there are non-commited changes in the repo
* Hugo: tell the user about adding a theme: http://gohugo.io/getting-started/quick-start/
* Be verbose about the need to review and edit files, adding LICENSE headers into source files, etc
* Try an alternative command-line format, like "module:option1=value,option2=value with spaces"
* Git: optionally configure user.signingkey, commit.gpgsign, etc
* Debian package module
|
