[Pulp-dev] Plugin teams problem statement

[David Davis]

Last week we talked about forming teams for each Pulp plugin and I wanted
to open up a community discussion around that idea. @bmbouter and I have
come up with a proposed problem statement [0] to kick off this discussion.

We’re looking for feedback from everyone so please feel free to check the
statement out and make edits. Or respond to this email with any thoughts
about it.

After about a week or so, I’ll try to create a PUP based on any feedback we
get.

[0] http://pad-theforeman.rhcloud.com/p/pulp-plugin-pup

David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] [pulp 3] proposed change to publishing REST api

[Dennis Kliban]

@jortel and I have been discussing[0] how a user should find out what
publication was created after a request is made to
http://localhost:8000/api/v3/repositories/foo/publishers/example/bar/publish/

I propose that we get rid of the above URL from our REST API and add
ability to POST to
http://localhost:8000/api/v3/repositories/foo/publishers/example/bar/publications/
instead. The response would be a 201. Each publication would have a task
associated with it.

This work would probably be done by whoever picks up issue 3033[1].

[0] https://pulp.plan.io/issues/3035
[1] https://pulp.plan.io/issues/3033
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Pulp 3 app location

[Brian Bouterse]

Recently many of these setup.py files were deleted so now there is only:

common/setup.py  <--   going away anyway with
https://pulp.plan.io/issues/3066
platform/setup.py
plugins/setup.py

I think it's good to have the folder use the python namespace names. If we
did that it would be renaming 'platform' to 'pulpcore' with `git mv
platform pulpcore`. I made an issue for this here [0] if that is what we
want to do.

[0]: https://pulp.plan.io/issues/3089


On Mon, Jun 19, 2017 at 2:54 PM, Austin Macdonald  wrote:

> We recently made the decision to namespace Pulp as "pulpcore" [0], but
> this has made our app location a little awkward:
> `pulp/platform/pulpcore/app`
>
> To kick off the conversation, I think the best place to start is a map of
> all of the setup.py files:
>
> bindings/setup.py
> client_admin/setup.py
> client_consumer/setup.py
> client_lib/setup.py
> common/setup.py
> devel/setup.py
> oid_validation/setup.py
> platform/setup.py
> plugins/setup.py
> repoauth/setup.py
> server/setup.py
> streamer/setup.py
>
>
> To me, it makes sense that pulpcore should move up a level, so the app
> would live in `pulp/pulpcore/app` and the setup py would live in
> `pulp/pulpcore/setup.py`
>
>
> [0]: https://www.redhat.com/archives/pulp-dev/2017-May/msg00030.html
>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev