+1
________________________________
From: Beckerle, Mike <mbecke...@owlcyberdefense.com>
Sent: Monday, October 5, 2020 10:23 AM
To: dev@daffodil.apache.org <dev@daffodil.apache.org>
Subject: Re: Subproject names proposed for discussion
+1 from me.
________________________________
From: Interrante, John A (GE Research, US) <inter...@research.ge.com>
Sent: Monday, October 5, 2020 9:28 AM
To: dev@daffodil.apache.org <dev@daffodil.apache.org>
Subject: Subproject names proposed for discussion
Steve Lawrence and I would like to bring a topic to the dev list for discussion
since not everyone is paying attention to the review of my runtime2 push
request. Steve suggested, and I agree, that renaming some of the Daffodil
subprojects might make their meanings more obvious to newcomer devs. If we do
rename some subprojects after discussing it on this list, we will do it
immediately in its own pull request since mixing changes with renames makes it
difficult to see which changes are just renames instead of actual changes.
What do devs think about us renaming some subprojects like this?
rename daffodil-core to daffodil-schema-compiler
leave daffodil-lib alone
rename daffodil-runtime1 to daffodil-backend-parser-scala
rename daffodil-runtime1-unparser to daffodil-backend-unparser-scala
rename daffodil-runtime2 to daffodil-backend-generator-c
