Change name of app from v1

[kurtrwall]

V1 is inherently a temporary name. The name of our app shouldn't be temporary. The project's name is cfgov and we'll be using the core app to store our "toolset". Any ideas?

[jimmynotjim]

How about just main-site or parent-site?

[kurtrwall]

Hyphens kind of make python barf...however, let's say our atomic work is "finished". We might want to make that it's own project by itself, and our v1 or main-site app will be in it's own isolated project. Take a look at cfgov-django's app structure. Our team's work could be encapsulated in that project and then installed as an app into cfgov-django. @rosskarchner I'd like to know your thoughts on this.

[rosskarchner]

I've been thinking the other way around: we move our legacy Django apps into cfgov-refresh (open sourcing a bunch of them in the process).

My votes would be:

• "core"
• merging cfgov/v1 into cfgov/cfgov

[jimmynotjim]

I'm going to vote to not repeat names anywhere in the dir structure, that just makes describing locations to others difficult.

[kurtrwall]

I was thinking "core" would house our atomic elements, whereas "v1" would use them. Is it okay to merge app code into the project's folder for settings, urls.py, etc?

[kurtrwall]

Does anyone see anything wrong with naming it flapjack?

[Scotchester]

Does anyone see anything wrong with naming it flapjack?

❤️ 💓 😻

[rosskarchner]

Yeah-- they're just python packages.

other ideas:

cmscore
cmstypes
cms

wagtail calls their own primary package 'wagtailsite' https://github.com/torchbox/wagtail-wagtailsite

[anselmbradford]

@cfpb/cfgov-backends Is this something we still want open?

[Scotchester]

Is this something we still want open?

YES

[willbarton]

@Scotchester speaks for me in these matters.

[cwdavies]

@willbarton I vote for changing the name of app from v1 to cms which is an abbreviation for Content Management System