Re: [Pulp-dev] Nomenclature Clarification

2019-03-13 Thread Austin Macdonald
We don't have an official process, but bringing it up here is a good place to start. Depending on the changes, it would be best to update the docs: https://docs.pulpproject.org/en/3.0/nightly/concepts.html https://docs.pulpproject.org/en/3.0/nightly/glossary.html

Re: [Pulp-dev] Nomenclature Clarification

2019-03-13 Thread Dennis Kliban
Discuss it here. Get support for the change. Open ticket on pulp.plan.io. Submit a PR. On Wed, Mar 13, 2019 at 10:52 AM Eric Helms wrote: > Thanks for the feedback. I should know this, but if I wanted to propose an > official change to the nomenclature what is the correct process? > > On Wed,

Re: [Pulp-dev] Nomenclature Clarification

2019-03-13 Thread Eric Helms
Thanks for the feedback. I should know this, but if I wanted to propose an official change to the nomenclature what is the correct process? On Wed, Mar 13, 2019 at 10:47 AM Dennis Kliban wrote: > On Fri, Mar 8, 2019 at 10:34 AM Eric Helms wrote: > >> Howdy, >> >> Within Pulp 3, I've found

Re: [Pulp-dev] Nomenclature Clarification

2019-03-13 Thread David Davis
+1 to pulp-api. Perhaps one day in the far, far future our descendants will find some better API format than REST and we can spare them the pain from having to rename the ‘pulp-rest-api’ service. David On Wed, Mar 13, 2019 at 10:48 AM Dennis Kliban wrote: > On Fri, Mar 8, 2019 at 10:34 AM

Re: [Pulp-dev] Nomenclature Clarification

2019-03-13 Thread Dennis Kliban
On Fri, Mar 8, 2019 at 10:34 AM Eric Helms wrote: > Howdy, > > Within Pulp 3, I've found myself struggling to refer to the pieces of the > runtime deployment and wanted to raise a few questions I keep coming back > to. > > 1) Per [1], pulpcore seems to reference the entirety of the server, >