Isn't its license - AGPL v3.0 - a problem? My understanding of the AGPL in this case is that if you publish a blog with Pelican, you have to also publish any t

Isn't its license - AGPL v3.0 - a problem? My understanding of the AGPL in this case is that if you publish a blog with Pelican, you have to also publish any trivial fork of Pelican that you create, even if only by a single trivial patch. Seems rather onerous given how likely us devs are to tweak something here or there. I'd gravitate towards any of the many MIT-licensed generators instead.