Hey,
Thanks, I appreciate the response. It sounds like your main concern is the
overhead of maintaining the .gitignore file, is that right? Could that
potentially be mitigated by a clear writeup of what's included, why, and
then an easy way to close all other tickets? E.g. we could easily just
Is there a more nuanced discussion of this issue anywhere? The reasons
stated in the linked PR that it's "not for the project template to provide
configuration for source code management tools" feels more like an opinion
than a fact.
I know one of the goals that emerged from recent discussions
Hey Andrew,
Thanks for drafting this language and I think it looks great. As someone
who only recently applied after hearing it discussed on an episode of
Django Chat[1], I'm all for the goals of making it more encouraging and
accessible and think this is a great step in that direction.
Here are
