+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 <bbout...@redhat.com> 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. > > @jcline, would you be able to comment on [0] with a recommendation for > which repo it should be kept in and built from? > > [0]: https://pulp.plan.io/issues/1998 > > -Brian > > 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 currently in pulp/pulp >> * The devel Python packages currently in each repo >> * Release engineering tooling currently in pulp/pulp >> * Jenkins jobs definitions currently in pulp/pulp_packaging >> * Ansible playbooks currently in pulp/pulp and pulp/pulp_packaging >> * Various tools and scripts living in "playpens" >> >> It might also be worth breaking out our Ansible roles into their own >> `ansible` repository. Right now we have _two_ sets of Ansible roles >> (one in pulp/pulp and on in pulp/pulp_packaging). >> >> What do you all think? >> >> >> >> _______________________________________________ >> Pulp-list mailing list >> Pulp-list@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-list >> >> > _______________________________________________ > Pulp-list mailing list > Pulp-list@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-list >
_______________________________________________ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list