Re: [Pulp-list] [devel] Create a `devel` repository for Pulp

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/29/2016 09:47 AM, Brian Bouterse wrote: > +1 to using contrib in favor of pulp_contrib, and similar for other new repos. +1 > > My reasoning is based on optimizing the common case. It's very common for > people to work with Pulp repos >

Re: [Pulp-list] [devel] Create a `devel` repository for Pulp

+1 to using contrib in favor of pulp_contrib, and similar for other new repos. My reasoning is based on optimizing the common case. It's very common for people to work with Pulp repos everyday so having a cleaner name is nice. The uncommon case is when it's forked AND a user doesn't know

Re: [Pulp-list] [devel] Create a `devel` repository for Pulp

On 06/24/2016 03:07 PM, Michael Hrivnak wrote: > On naming, I have a slight preference toward keeping the pulp_ prefix > convention, but that might just be rooted in habit. My general feeling is > that the name of a git repo should stand on its own, and the fact that it > may be present on github

Re: [Pulp-list] [devel] Create a `devel` repository for Pulp

On naming, I have a slight preference toward keeping the pulp_ prefix convention, but that might just be rooted in habit. My general feeling is that the name of a git repo should stand on its own, and the fact that it may be present on github within a particular user or organization's namespace

Re: [Pulp-list] [devel] Create a `devel` repository for Pulp

On 06/21/2016 11:58 AM, Brian Bouterse wrote: > +1 to this idea. > > Also, there is an task to create a "contrib" area for Pulp [0]. It would > be great to see some of these things (especially scripts) move into an > install-able package. I would be fine with a `devel` and a separate `contrib`

Re: [Pulp-list] [devel] Create a `devel` repository for Pulp

+1 to the installable package. We call ours pulp-utils at my site. - Kodiak On Tue, Jun 21, 2016 at 11:58 AM, Brian Bouterse wrote: > +1 to this idea. > > Also, there is an task to create a "contrib" area for Pulp [0]. It would > be great to see some of these things

Re: [Pulp-list] [devel] Create a `devel` repository for Pulp

+1 to this idea. Also, there is an task to create a "contrib" area for Pulp [0]. It would be great to see some of these things (especially scripts) move into an install-able package. @jcline, would you be able to comment on [0] with a recommendation for which repo it should be kept in and

Re: [Pulp-list] [devel] Create a `devel` repository for Pulp

If you want to make the Ansible role reusable, I recommend to put it into a separate Git repository and make it available via Ansible Galaxy. I also recommend do make it more atomic (one role for Pulp, one role for MongoDB and one role for Qpid). The role should also take advantage of existing

Re: [Pulp-list] [devel] Create a `devel` repository for Pulp

On 06/20/2016 02:40 PM, Sean Myers wrote: > Yes. I'm also happy to see the ansible books live in devel since they're > primarly > used by vagrant and CI, which would both live in devel, and you can't do > either > without one or the ansible playbooks. I was thinking that maybe we should

Re: [Pulp-list] [devel] Create a `devel` repository for Pulp

On 06/20/2016 01:49 PM, Jeremy Cline wrote: > Hi all, > > Currently, we have development-related files and packages spread out > across our Git repositories on GitHub. It would be nice if it was all > part of one repository for developers. This would include things like: > > * The Vagrantfile

[Pulp-list] [devel] Create a `devel` repository for Pulp

Hi all, Currently, we have development-related files and packages spread out across our Git repositories on GitHub. It would be nice if it was all part of one repository for developers. This would include things like: * The Vagrantfile currently in pulp/pulp * The devel Python packages