<div dir="ltr">I also imagine us getting to that point where the CLI does not require any code specific to a particular plugin, but I'm not sure we'll get there in 3.0.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 15, 2017 at 10:25 AM, Brian Bouterse <span dir="ltr"><<a href="mailto:bbouters@redhat.com" target="_blank">bbouters@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>+1 to all of the core stuff. Thank you for writing it up.<br><br></div>For
 the pulp_rpm case +0 to what you had written. I had imagined it with a 
slightly different example, but I think in practice it's almost the 
same.<br><br></div>pip install pulp_rpm<br></div>from pulp_rpm import anything<br><br></div><div>As
 an aside, I'm hoping that plugins only have to provide a server package
 and that by installing it on the server the CLI will know about the 
additional command set somehow. If so this would avoid plugin writers 
having to make additional pulp_rpm_common and pulp_rpm_cli pip packages.
 If we can't do that then I would think the pip and import for a plugin 
like RPM would be:<br><br></div><div>pip install pulp_rpm<br></div><div>pip install pulp_rpm_common<br></div><div>pip install pulp_rpm_cli<br><br></div><div>from pulp_rpm import anything<br></div><div>from pulp_rpm import cli<br></div><div>from pulp_rpm import common<br><br></div>Does
 ^ make sense? Is that similar or different to how others imagined it? 
It's slightly different than the example given by @mrhivnak, but in 
practice I don't think it is different.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 12, 2017 at 12:52 PM, Daniel Alley <span dir="ltr"><<a href="mailto:dalley@redhat.com" target="_blank">dalley@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1<br></div><div class="m_-4655170493482439970HOEnZb"><div class="m_-4655170493482439970h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 12, 2017 at 12:13 PM, Jeff Ortel <span dir="ltr"><<a href="mailto:jortel@redhat.com" target="_blank">jortel@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1, This sounds good to me.<br>
<div><div class="m_-4655170493482439970m_-492742366280464707h5"><br>
On 05/11/2017 10:59 AM, Michael Hrivnak wrote:<br>
> We had a brainstorm session today to re-evaluate the previously-identified options, and try to come up with<br>
> some new ones. None of the previously-identified options had enough support to be chosen. See the thread "PyPI<br>
> names for Pulp3" for background.<br>
><br>
> To re-cap, we are focused on two related questions:<br>
><br>
> 1. What python namespace should Pulp use, since we cannot continue to use "pulp"?<br>
><br>
> 2. What PyPI package names should we use?<br>
><br>
> I pitched an idea for 1 that everyone on the call liked, which is "pulpcore". It could alternatively be<br>
> "pulp_core", although my pinky finger prefers the former. The group of roughly 10 people who participated in<br>
> the discussion are recommending "pulpcore" for consideration as the python namespace to replace "pulp". Please<br>
> add your feedback to this thread.<br>
><br>
> "core" is likable because it implies a plugin architecture. It's similar to the word "platform" that we've<br>
> used extensively, but shorter (which people liked), and perhaps slightly more descriptive (which people also<br>
> liked). Example:<br>
><br>
> from pulpcore import streamer<br>
><br>
> We discussed renaming what is currently "pulp.platform" to something more descriptive. "platform" is a word<br>
> that's been with us a long time, but it's worth re-considering, especially if we shift to a similar word such<br>
> as "core". "pulpcore.platform" seems awkward.<br>
><br>
> A proposal is "pulpcore.apps", since that code is all directly related to the celery app and django app.<br>
><br>
> Python namespaces would include:<br>
><br>
> pulpcore.apps<br>
> pulpcore.cli<br>
> pulpcore.common<br>
> pulpcore.plugin<br>
> pulpcore.streamer<br>
><br>
> For python package names, they would look something like this:<br>
><br>
> pip install pulpcore<br>
> pip install pulpcore_cli<br>
> pip install pulpcore_streamer<br>
> pip install pulpcore_common<br>
><br>
> Plugins would continue to use their existing namespace and package names, with whatever variations are<br>
> appropriate in Pulp 3. For example:<br>
><br>
> import pulp_rpm.plugins<br>
> pip install pulp_rpm_plugins<br>
><br>
> Thoughts? Those of you who were part of the discussion, please chime in with any additional points you'd like<br>
> to highlight.<br>
><br>
> --<br>
><br>
> Michael Hrivnak<br>
><br>
> Principal Software Engineer, RHCE<br>
><br>
> Red Hat<br>
><br>
><br>
><br>
</div></div>> ______________________________<wbr>_________________<br>
> Pulp-dev mailing list<br>
> <a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
> <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><br>
><br>
<br>
<br>______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><p style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important"><span style="margin:0px!important;padding:0px!important">Michael</span> <span style="margin:0px!important;padding:0px!important">Hrivnak</span></p><p style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important"></p><span style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important"><span style="margin:0px!important;padding:0px!important">Principal Software Engineer</span><span style="margin:0px!important;padding:0px!important">, <span style="margin:0px!important;padding:0px!important">RHCE</span></span> </span><span style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px"></span><br style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important"><p style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important">Red Hat</p></div></div>
</div>