Re: [Pulp-dev] Namespacing plugins, looking for feedback

On Fri, Jan 11, 2019 at 5:01 PM Jeff Ortel wrote: > > > On 1/9/19 11:30 AM, Tatiana Tereshchenko wrote: > > To summarize where we are so far: > *All* master/detail related endpoints will be automatically prepended > with Django app *label* [0] > - concer

[Pulp-dev] RPM plugin meeting notes

Pulp 2: - modularity issues are on the sprint [0], dalley is working on them. - module dep solving story [1], dalley or jortel will take a look at the corresponding PR to see if it requires any adjustments Pulp 3: - Agreement reached with the stakeholders that it's ok to publish

Re: [Pulp-dev] Namespacing plugins, looking for feedback

To summarize where we are so far: *All* master/detail related endpoints will be automatically prepended with Django app *label* [0] - concerns: 'pulp_' in the label - options to address concerns: * introduce a new attribute to the AppConfig class to use in the endpoints

Re: [Pulp-dev] Namespacing plugins, looking for feedback

late/app/__init__.py#L8 >> >> `endpoint_namespace = rpm` or `short_label = rpm` >> >> Result: /api/v3/content/rpm/packages/ >> >> The downside is that every plugin would need 1 more line of code. The >> upside is that we could implement it exactly sam

Re: [Pulp-dev] Namespacing plugins, looking for feedback

ncouraged to do? > > David > > > On Wed, Jan 2, 2019 at 12:58 PM Tatiana Tereshchenko > wrote: > >> Thank you all for the discussion so far. >> The question - the type field and namespacing in content summary - is >> solved with https://pulp.plan.io/issues/41

Re: [Pulp-dev] Namespacing plugins, looking for feedback

the next couple of days. Thank you, Tanya On Thu, Dec 20, 2018 at 9:41 AM Tatiana Tereshchenko wrote: > Since we are leaning towards prepending types for _all_ master/detail > models and not only for the content model, that Django fix is no longer > important for us. > > Tanya

Re: [Pulp-dev] Namespacing plugins, looking for feedback

ases plugin writers might want to >>>> change the name (eg cases where you can't use type as the class name like >>>> File). >>>> >>>> David >>>> >>>> >>>> On Tue, Dec 18, 2018 at 9:23 AM Brian Bouterse >>>> wrote:

Re: [Pulp-dev] Namespacing plugins, looking for feedback

be possible to default to class name but let plugin writers >>> override this? I would imagine in some cases plugin writers might want to >>> change the name (eg cases where you can't use type as the class name like >>> File). >>> >>> David >>&g

Re: [Pulp-dev] Namespacing plugins, looking for feedback

com/pulp/pulp_ansible/pull/38/files#diff-debb42c875c19140793de39be3696ee3 > > David > > > On Sun, Dec 16, 2018 at 4:41 PM Tatiana Tereshchenko > wrote: > >> There is an issue [0] of colliding type names in the content summary >> which evolved into more general namespacing problem for

[Pulp-dev] Namespacing plugins, looking for feedback

There is an issue [0] of colliding type names in the content summary which evolved into more general namespacing problem for plugins. The suggested changes [1] are: 1. include plugin name into the content summary "content_summary": { "pulp_rpm.package": 50, "pulp_rpm.errata": 2,

Re: [Pulp-dev] Proposal: merge the content-app & streamer

+1 to merge +1 to have clear docs for plugin writers how to create their own content app On Mon, Dec 3, 2018 at 11:25 PM Dennis Kliban wrote: > It was pointed out on IRC that plugins that have to supply their own > content app (such as docker) currently need to supply 2 implementations of > it

Re: [Pulp-dev] Proposal to remove 'notes' fields from the Pulp 3 RC

+1 On Tue, Dec 4, 2018 at 4:49 PM Brian Bouterse wrote: > +1. Ty for bringing this up @dalley > > On Tue, Dec 4, 2018 at 10:47 AM Jeff Ortel wrote: > >> no objection >> >> On 12/3/18 10:32 PM, Daniel Alley wrote: >> >> *Background:* >> >> "Notes" are a generic key value store where data can be

Re: [Pulp-dev] Distributing Pulp3 Plans

+1 On Mon, Dec 3, 2018 at 5:54 PM Daniel Alley wrote: > No objection > > On Mon, Dec 3, 2018 at 11:52 AM Jeff Ortel wrote: > >> +1 >> >> On 12/1/18 6:01 AM, David Davis wrote: >> >> +1 from me. >> >> David >> >> >> On Fri, Nov 30, 2018 at 10:26 AM Dennis Kliban >> wrote: >> >>> No objections

[Pulp-dev] pulpcore-3.0.0b15 and pulpcore-plugin-0.1.0b13 available

The following packages are now available on PyPI: - pulpcore 3.0.0b15 [0] with its release notes here [1] - pulpcore-plugin 0.1.0b13 [2] with its release notes here [3] The beta documentation is available here [4]. [0]: https://pypi.org/project/pulpcore/3.0.0b15/ [1]:

Re: [Pulp-dev] 2.18.0 Dev Freeze, last chance to merge

If you have any feature or bugfix for 2.18.0 which are not merged yet, please merge it today. 2.18.0 Dev Freeze is today at 22:59:59 UTC. Tanya On Thu, Nov 8, 2018 at 8:35 PM Tatiana Tereshchenko wrote: > 2.18.0 Dev Freeze is postponed until next week. > > The updated schedule can be

Re: [Pulp-dev] 2.18.0 Dev Freeze - postponed

2.18.0 Dev Freeze is postponed until next week. The updated schedule can be seen here: https://pulp.plan.io/projects/pulp/wiki/2180_Release_Schedule Tanya On Tue, Nov 6, 2018 at 2:54 PM Tatiana Tereshchenko wrote: > Due to the applicability feature being critcal but not being complete

Re: [Pulp-dev] 2.18.0 Dev Freeze - postponed, Thursday, November 8 at 20:00 UTC

: https://pulp.plan.io/projects/pulp/wiki/2180_Release_Schedule Tanya On Fri, Nov 2, 2018 at 9:37 AM Tatiana Tereshchenko wrote: > This is a reminder that the dev freeze for 2.18.0 will be on Tuesday if > everything goes as planned. This release is going to contain the features > list

[Pulp-dev] 2.18.0 Dev Freeze - Tuesday, November 6 at 20:00 UTC

This is a reminder that the dev freeze for 2.18.0 will be on Tuesday if everything goes as planned. This release is going to contain the features listed here[0]. [0] https://pulp.plan.io/versions/64 ___ Pulp-dev mailing list Pulp-dev@redhat.com

Re: [Pulp-dev] 2.18.0 Dev Freeze - Tuesday, September 18 at 16:00 UTC

The 2.18.0 beta release of Pulp is delayed by one more day. If no issues come up, it should be available on Wednesday, October 3rd. On Tue, Sep 25, 2018 at 4:11 PM Dennis Kliban wrote: > The 2.18.0 beta release of Pulp is delayed by one week. It should be > available on Tuesday, October 2nd. >

Re: [Pulp-dev] Proposal to drop support of Python 3.5 for Pulp 3

Big +1 Tanya On Wed, Sep 12, 2018 at 4:50 PM, David Davis wrote: > +1 > > David > > > On Tue, Sep 11, 2018 at 10:35 AM Jeff Ortel wrote: > >> +1 >> >> On 09/07/2018 01:09 AM, Simon Baatz wrote: >> > I had a discussion on IRC with Brian yesterday which led to the >> > question whether we can

Re: [Pulp-dev] Requiring 2FA in Github

+1, enabled. On Fri, Jul 27, 2018 at 12:02 AM, Dennis Kliban wrote: > +1, but I already have it enabled. > > On Thu, Jul 26, 2018 at 3:53 PM, David Davis > wrote: > >> I got a notification from another organization I am a member of on >> Github[0] that they are going to require Two Factor

Re: [Pulp-dev] Proposed Update to PUP-4

+1 On Tue, Jul 24, 2018 at 8:10 PM, Brian Bouterse wrote: > +1 Thank you! > > On Tue, Jul 24, 2018 at 11:37 AM, Dana Walker wrote: > >> A PR [0] is up with a proposed update to PUP-4: Code of Conduct [1]. >> >> The proposal changes the details of where the Code of Conduct is to be >>

Re: [Pulp-dev] Volunteer is needed to work on Pulp 2 issue #3687

Daniel, thanks for working on that! Tanya On Fri, May 25, 2018 at 2:28 PM, Tatiana Tereshchenko <ttere...@redhat.com> wrote: > Hi all, > > A gentle reminder that we need someone to work on the mongoengine 0.14+ > issue #3687 as soon as possible. > > Thank yo

[Pulp-dev] Volunteer is needed to work on Pulp 2 issue #3687

Hi all, A gentle reminder that we need someone to work on the mongoengine 0.14+ issue #3687 as soon as possible. Thank you, Tanya [0] https://pulp.plan.io/issues/3687 ___ Pulp-dev mailing list Pulp-dev@redhat.com

Re: [Pulp-dev] Lazy for Pulp3

Thanks Justin! +1 to consider this use case, I can confirm that many users asked for that. Tanya On Wed, May 16, 2018 at 8:52 PM, Justin Sherrill wrote: > > > On 05/16/2018 01:02 PM, Brian Bouterse wrote: > > A mini-team of @jortel, @ttereshc, @ipanova, @dkliban, and

Re: [Pulp-dev] 2.16.0 dev freeze -- 22:00 UTC Tuesday, March 13th

The code for 2.16.0 is now frozen. There are a total of 9 stories/tasks/refactors prepared for the release: https://pulp.plan.io/issues?query_id=61 Tanya On Tue, Mar 13, 2018 at 11:05 AM, Tatiana Tereshchenko <ttere...@redhat.com> wrote: > Any Pulp2 core or plugin code that you want

[Pulp-dev] 2.16.0 dev freeze -- 22:00 UTC Tuesday, March 13th

Any Pulp2 core or plugin code that you want included in the 2.16.0 release must be: a) merged to master by 22:00 UTC, March 13th b) associated with a story, refactor, task or a bugfix issue. If you want/need to adjust this date, please reply on list. Thanks, Tanya

Re: [Pulp-dev] Migrating Sprint to Custom Field [happening tomorrow]

Thank you! My late but big +1. Tanya On Tue, Mar 6, 2018 at 11:04 PM, Brian Bouterse wrote: > Thanks for all the feedback! With many +1s and no -1s, I'm going to make > this change tomorrow. I'll send out links to the result when it is done. > > -Brian > > > On Mon, Mar 5,

Re: [Pulp-dev] Stories to groom

Solved. Thanks On Tue, Feb 13, 2018 at 7:55 PM, Tatiana Tereshchenko <ttere...@redhat.com> wrote: > Hi all, > > Can someone review and groom the following stories for the upcoming sprint > planning? > > https://pulp.plan.io/issues/3339 > https://pulp.plan.io/issu

[Pulp-dev] Stories to groom

Hi all, Can someone review and groom the following stories for the upcoming sprint planning? https://pulp.plan.io/issues/3339 https://pulp.plan.io/issues/3353 Thanks, Tanya ___ Pulp-dev mailing list Pulp-dev@redhat.com

Re: [Pulp-dev] Voting for PUP 4: Code of Conduct

+1 On Wed, Dec 13, 2017 at 5:43 PM, Brian Bouterse wrote: > +1 > > On Wed, Dec 13, 2017 at 11:24 AM, Ina Panova wrote: > >> +1 >> >> >> >> >> Regards, >> >> Ina Panova >> Software Engineer| Pulp| Red Hat Inc. >> >> "Do not go where the path may

[Pulp-dev] Triage lead role is open

Hi everyone, I'm rotating off of the triage lead, and I'm looking for someone else to rotate on and run triage. The triage process happens on IRC every Tuesday and Friday at 10:30 ET. Read more about the process here [0]. Please reply-all if interested. [0]:

[Pulp-dev] FilterSets in plugin API

There are FilterSets [0][1] defined for master models, so they can be used as-is or extended by plugin for detail models. Currently they don't seem to be available via plugin API and plugin defines its own FilterSet [2]. Is it intentional? I suggest to add them to pulpcore.plugin. Thanks, Tanya

Re: [Pulp-dev] PUP Process: "obvious consensus"

+1 Thanks, Brian! Tanya On Thu, Aug 10, 2017 at 3:21 PM, David Davis wrote: > +1. I think this is worth trying out. > > > David > > On Thu, Aug 10, 2017 at 8:54 AM, Austin Macdonald > wrote: > >> +1 >> >> Thank you Brian! >> >> On Thu, Aug 10, 2017

Re: [Pulp-dev] Developing Pulp 2 and 3 in parallel

JFYI, there is a Vagrant deep dive on Pulp channel and in case you'd like to take a quick look there was a section [0] about multiple boxes in this video. [0] https://youtu.be/0LDoNPIZyzk?t=37m44s On Wed, May 10, 2017 at 2:54 PM, David Davis wrote: > I wanted to run Pulp

Re: [Pulp-dev] Proposal to use google style docstrings (PUP-2)

+0 Tanya On Mon, Apr 17, 2017 at 11:43 PM, David Davis wrote: > +0 > > > David > > On Mon, Apr 17, 2017 at 4:32 PM, Bihan Zhang wrote: > >> +1 >> >> On Mon, Apr 17, 2017 at 4:24 PM, Michael Hrivnak >> wrote: >> >>> +0 >>> >>> On

[Pulp-dev] Next IRC bug triage, Tuesday April 18

Due to upcoming holidays bug triage meeting is canceled this Friday. Do not forget to join next triage session on #pulp-dev on freenode. It is scheduled for Tuesday April 18 at 14:30 UTC. See you there, Tanya ___ Pulp-dev mailing list

Re: [Pulp-dev] pull request test results are now publicly available

+1 So great! Thanks, Dennis! On Wed, Apr 12, 2017 at 3:04 PM, Michael Hrivnak wrote: > That is great! Thanks for making this happen. > > On Tue, Apr 11, 2017 at 10:08 PM, Dennis Kliban > wrote: > >> The Jenkins pull request test jobs are now configured

<    1   2   3