Re: [Pulp-dev] RFC process

ber it, so i will need to dig into my mails to find it out. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Mon, Feb 6, 2017 at 4:59 PM, David Davis <davidda...@redhat.co

Re: [Pulp-dev] release process updates

, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Mon, Jan 23, 2017 at 8:51 PM, Jeremy Audet <jau...@redhat.com> wrote: > David, does my response answer your question? > >

Re: [Pulp-dev] Upcoming epel6 Dependency Issues

I like this approach. w/r to the blog post, would be good to explicitly point the users to give feedback on pulp-list (who knows, maybe not every user is aware of this list), since the comments are disabled. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go

Re: [Pulp-dev] PyPI names for Pulp3

and ask what do they think? maybe they will come up with new ideas. Not sure if it is a good idea, though. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Wed, Apr 19, 20

Re: [Pulp-dev] PyPI names for Pulp3

we have not considered yet 'pulpapp' pip install pulpapp pip install pulpapp_cli pip install pulpapp_streamer Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Ap

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

+1. Thanks Brian for all your effort and commitment. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Aug 10, 2017 at 9:58 PM, Daniel Alley <dal...@redhat.com&

Re: [Pulp-dev] PyPI names for Pulp3

I am going to schedule a meeting so we can have a live vital beneficial discussion. Thank you all for participation and feedback, we will try to find a consensus during ^^, or at least next steps. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the

Re: [Pulp-dev] PyPI names for Pulp3

The meeting is scheduled for Tomorrow. Find the details below, everyone is welcome to join. When: Thursday May 11 at 2.30pm UTC Where: https://bluejeans.com/436590399 Interact: https://etherpad.net/p/pypi_naming Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do n

Re: [Pulp-dev] PyPI names for Pulp3

ory-or-not If you deathly disagree please speak out now, otherwise these would be the final decision taken in order to complete https://pulp.plan.io/issues/2444 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is

[Pulp-dev] Docker Manifest list support in Pulp

] https://pulp.plan.io/issues/2384 [1] https://pulp.plan.io/issues/2385 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." ___ Pulp-dev ma

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

wise i don't see sense in pushing forward is there is no boost from the very beginning. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Mon, Jun 12, 2017 at 4:13 PM, Davi

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

Having at least one +1 is not impartial approach just because the developer who , as you said, found the time for the research and writing down the proposal obviously will vote as +1 :) Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead

Re: [Pulp-dev] PUP-3: Proposal to change our git workflow

That's correct, we need not to forget to set the new branch as protected. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Fri, Jun 2, 2017 at 3:52 PM, David Davi

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

And if we would remove all 'shades of grey' and go back just to +1 and -1 where people would need to make their mind up *clearly* which would lead stronger arguments of doing or not doing this. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the pat

Re: [Pulp-dev] PyPI names for Pulp3

proj". Plus pulpproject is already taken. 2) pulp3 - is ambiguous regardless of if the 3 is for Pulp3 or Python3. 3) plp - looks like pip 4) pulpapp vs pulp_app 5) pulp_platform 6) spot for new ideas I encourage you all to *speak your piece *before I would create the Doodle. ----

Re: [Pulp-dev] REST API Milestone/alpha?

@Austin, do we want to update the etherpad since jwt work was merged? Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Mon, Oct 9, 2017 at 2:34 PM, Austin Macd

Re: [Pulp-dev] New Docs for Demo Presenters

That all looks good, i would just suggest not to limit the presentation by 4 minutes. Maybe omitting this would be better, you never know what kind of feature will be demoed. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go in

Re: [Pulp-dev] Proposing dropping old fedora releases for 2.15

+1 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Nov 14, 2017 at 4:18 PM, Michael Hrivnak <mhriv...@redhat.com> wrote: > Sounds good. Our policy has be

Re: [Pulp-dev] Task tagging in Pulp 3

-end situation. > Do we really need to allow users to search tasks by a resource/repo at all? I think this is useful and we should keep this. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path a

Re: [Pulp-dev] 2.17.0 Release request

Based on some more discussion it has been decided that we're not ready yet for another Y release. The request for Y release has been withdrawn. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and

[Pulp-dev] 3.2.0 Crane release schedule

/wiki/320_Crane_Release_Status Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." ___ Pulp-dev mailing list Pulp-dev@redhat

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

To make a concrete example to prove my understating: Since pulp_rpm is maintained by core team we could adopt this change, meanwhile pulp_deb is beyond our control and we( core team) cannot enforce or influence this change. Yes? Regards, Ina Panova Software Engineer| Pulp| Red Hat

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

*understanding Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Mon, May 14, 2018 at 12:27 PM, Ina Panova <ipan...@redhat.com> wrote: > To make a concrete

[Pulp-dev] Crane 3.2.0 dev freeze

The code for Crane 3.2.0 is now frozen. There are a total of 3 issues prepared for the release. The current beta date is May 16. https://pulp.plan.io/issues?query_id=108 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead

Re: [Pulp-dev] Composed Repositories

. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Mon, May 14, 2018 at 9:44 PM, Jeff Ortel <jor...@redhat.com> wrote: > Let's brainstorm on something. >

Re: [Pulp-dev] MODIFIED redmine issues for 3.0 beta

in case we set the target release specifically Beta, otherwise it sounds like it brings some confusion. There is a big period between Beta and GA and you never know what can happen to those set issues especially if they are targeted as GA. Regards, Ina Panova Software Engineer| Pulp| Red Hat

Re: [Pulp-dev] Core Commit Bit Process

open and public via email, with majority of core-devs voted and no -1. Some time limit on voting would be set as well. * chance of re-applying for commit bit with some cooldown Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go in

Re: [Pulp-dev] 'id' versus 'pulp_id' on Content

uuid sounds like good compromise. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Jun 14, 2018 at 9:38 PM, Jeff Ortel wrote: > > > On 06/14/2018 12:19 P

Re: [Pulp-dev] Lazy for Pulp3

the steps in the diagram except step 14. If squid pushes the bits out of the cache, it will be re-downloaded again to serve to other clients requesting the same bits. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where th

Re: [Pulp-dev] Foreman / Katello / Pulp at FrOSCon2018

Awesome news! Whoever is around - do not miss the chance to stop by, share ideas, experience and grab swag! Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Jun 5, 20

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

+1 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Fri, Jun 1, 2018 at 6:11 PM, Austin Macdonald wrote: > +1 > > On Fri, Jun 1, 2018 at 8:54 AM, Dana Wal

Re: [Pulp-dev] Pulp 2 plugin release plan

of collaboration with the build team? Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Mon, Jun 18, 2018 at 8:20 PM, Dennis Kliban wrote: > Earlier today a few of us m

Re: [Pulp-dev] Branching Pulp 2 for plugins

Please keep in mind that for docker plugin it's 4.0dev and not 3.0dev. пн, 2 июл. 2018 г., 16:49 David Davis : > In order to conform to the pulp/pulp repository, I propose we update our > branches for our plugins. This would include: > > 1. Moving master to 2-master > 2. Moving 3.0-dev to master

[Pulp-dev] 2.17.0 Release request

/wiki/2170_Release_Status <https://pulp.plan.io/projects/pulp/wiki/2160_Release_Status> --- Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail."

Re: [Pulp-dev] 2.17.0 Release request

[0] https://pulp.plan.io/projects/pulp/wiki/2170_Release_Status Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, May 3, 2018 at 4:05 PM, Ina Panova <ipan...@redh

Re: [Pulp-dev] Pulp2 Release Engineer Needs Volunteer

Brian, i'd like to take care of the upcoming pulp2 Y release. I'll ping you on irc to sync up on details. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Wed, May 2,

Re: [Pulp-dev] Pulp 2 plugin release plan

? Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Jun 19, 2018 at 11:53 PM, Tom McKay wrote: > Just curious, but I assume that for an async plugin release that

[Pulp-dev] 2.17.0 Release request

/wiki/2170_Release_Schedule Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.

Re: [Pulp-dev] 2.17.0 Dev Freeze - Tuesday, July 31

2.17.0 Release is delayed due to unforeseen discovered issues. For the new tentative dates please check the release schedule [0] Thank you. [0] https://pulp.plan.io/projects/pulp/wiki/2170_Release_Schedule Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go

[Pulp-dev] Commit bit PUP-6

ub.com/pulp/pups/blob/master/pup-0001.md Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev

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

+1 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Aug 16, 2018 at 3:08 PM, Dennis Kliban wrote: > +1 > > On Wed, Aug 15, 2018 at 4:06 PM, Brian Bouters

Re: [Pulp-dev] Commit bit PUP-6

PR updated, ready for re-review. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Aug 16, 2018 at 1:00 PM, Ina Panova wrote: > I have opened a PR for PUP

[Pulp-dev] 2.17.0 Dev Freeze - Tuesday, August 7 at 16:00 UTC

All outstanding issues and regressions were resolved. The code for 2.17.0 is now frozen. Check the list of work completed and prepared for the release: https://tinyurl.com/y96j92hl Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead

Re: [Pulp-dev] Pulp Code Owners

. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Aug 14, 2018 at 3:56 PM, Milan Kovacik wrote: > > > On Tue, Aug 14, 2018 at 3:47 PM, David Davis > wrote: > >&g

Re: [Pulp-dev] Commit bit PUP-6

I tried to address all the comments and updates the PR. Please give another look and vote once you're ready! Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Au

Re: [Pulp-dev] Commit bit PUP-6

I tried to address all the comments and updates the PR. Please give another look and vote once you're ready! Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Au

[Pulp-dev] 2.17.0 RC delay.

Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Commit bit PUP-6

Voting on PUP-6 ended on August 28. The PUP passed with five +1 and no -1. Tomorrow I will send out an announcement with the link to the adopted and documented process of Commit bit assignment. Thanks all for participating! Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc

Re: [Pulp-dev] commit-bit nomination

for the other topics. +1 on the voting. I also solicit the team to be pro-active, so we can fail fast things which do not work out for us. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a

Re: [Pulp-dev] Voluntary Resignation of the Commit Bit

Bihan, as per your request, the commit bit was removed from the following repositories: pulp/pulp pulp/pulp_docker Thanks a lot for all your contributions and project involvement! Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead

[Pulp-dev] Commit bit assignment.

Hello Pulpers, We have just adopted an officially documented process of commit bit assignment. We believe the community will embrace this change which we hope will in turn encourage even more contributions. For more information check out this PUP [0]. With <3, Pulp Team. [0]

Re: [Pulp-dev] Revising PUPs

+1 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Mon, Jul 9, 2018 at 3:22 PM, Dana Walker wrote: > +1 > > Dana Walker > > Associate Software Engine

Re: [Pulp-dev] Branch protection

+1 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Jul 10, 2018 at 11:31 PM, Jeff Ortel wrote: > +1 > > > On 07/10/2018 02:30 PM, David Davis wrote:

Re: [Pulp-dev] possible to upload container image blobs?

] https://github.com/pulp/pulp_docker/blob/master/docs/user-guide/recipes.rst#upload-v2-schema-2-and-schema-1-images-to-pulp Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On

Re: [Pulp-dev] Removing a few sprint items?

drop this issue from the sprint. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Wed, Mar 14, 2018 at 5:03 PM, Brian Bouterse <bbout...@redhat.com> wrote: > I

Re: [Pulp-dev] Plugin triage

It makes sense to let to mini-teams to triage the issues, but the decision whether to put or not on the sprint still should be addressed by whole team, or at least acknowledged. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go in

Re: [Pulp-dev] Demos switching to pre-recorded videos

drastically or maybe no need to host live demo at all? Why don't we just post the list of recorded videos on the pulp lists then, suggest to watch them later? :) Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no

Re: [Pulp-dev] Roadmap Challenges

as a team, we make sure that it gets picked up and worked on, and we do not leave/pospone it be there for X amount of time because maybe it does not really not look appealing. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead

Re: [Pulp-dev] Demos switching to pre-recorded videos

I would keep this as a suggestion but not a hard requirement. Some people would still like to train their live demoing skills :) Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a

Re: [Pulp-dev] Improving technical decision making

, but with these rotation we can: 1) do knowledge transfer, this way less experienced person will learn from a more experienced. 2) the ecosystem of our team will be healthy, and we will not panic when that single person that knows X is not PTO and he have sev1 issue or similar. Regards, Ina Panova

Re: [Pulp-dev] let's rename RepositoryVersion to Snapshot

and not snapshots. Back to aptly, they use the term shapshot, which you need to manually create https://www.aptly.info/doc/aptly/snapshot/create/ Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a

Re: [Pulp-dev] Port Pulp3 to use RQ

alternatives. [0] https://www.youtube.com/watch?v=Qmhc7tZ6ElQ Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Mar 20, 2018 at 9:52 PM, Daniel Alley <dal...@redhat.com> w

Re: [Pulp-dev] Pulp 3.0 RC roadmap and check-ins

Did we identify and confirm that the mentioned deadline is feasible? Or in order to complete this on time installer team members need to share the workload and commitment? Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead

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

perspective ;) Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Wed, Jan 2, 2019 at 8:55 PM Austin Macdonald wrote: > +1 automatic namespacing for master/detail. I realize th

Re: [Pulp-dev] QE commit bit

+1 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Jan 17, 2019 at 10:18 AM Tatiana Tereshchenko wrote: > +1 > > On Wed, Jan 16, 2019 at 8:32 PM Bria

Re: [Pulp-dev] pin pulpcore?

if we won't pin pulpcore we'll keep receiving such reports as #4317. +1 to option1 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Jan 17, 2019 at 2:06 PM Tatiana Te

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

+1 to namespace master/detail as well. +1 to Brian's suggestion to try. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Dec 18, 2018 at 12:15 AM Brian Bouterse wr

Re: [Pulp-dev] [Pulp-list] Pulp 3.0 RC release

The beta 2 release of pulp_docker for Pulp 3 is now available. It includes support for pulpcore 3.0.0rc1. https://pypi.org/project/pulp-docker/4.0.0b2/ Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no

Re: [Pulp-dev] Skipping plugin issues during triage

+1 to the proposal Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Wed, Feb 27, 2019 at 9:05 PM Daniel Alley wrote: > +1 > > On Wed, Feb 27, 2019 at 2:0

Re: [Pulp-dev] Changes in the Pulp 3 Upload story

+1 to facilitate the upload process. At the conferences, there have been many users pointing out how inconvenient current upload process is . Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and

Re: [Pulp-dev] Pulp 2 and 3 Service Name Clashes

to make only the hyphens change. @asmacdo https://pulp.plan.io/issues/4497 i think this is a dupe of https://pulp.plan.io/issues/4429 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a

Re: [Pulp-dev] pulp_file ownership

+1 for the core team ср, 20 мар. 2019 г., 9:06 Tatiana Tereshchenko : > +1 move the pulp_file repo under the core team > > On Tue, Mar 19, 2019 at 10:10 PM Austin Macdonald > wrote: > >> +1 for the latter. >> >> Since some changes to pulpcore or pulpcore-plugin also require changes to >>

Re: [Pulp-dev] Skipping plugin issues during triage

Kersom, for the plugin issues that have a BZ associated we can agree to reach QE whenever plugin mini-team does the triage separately. This way main triage will shorter and QE will be aware of other plugin related issues as well. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc

Re: [Pulp-dev] Pulp 2 and 3 Service Name Clashes

ric Helms wrote: >>>>> >>>>>> My key with proposal with Option 2 is to set Pulp 3+ up to be the >>>>>> future without carrying any baggage. Let's put the baggage on the older >>>>>> bits and keep it there and leave the future

Re: [Pulp-dev] Pulplift responsibilities

I have created a team in our github organization and have added current volunteers. https://github.com/orgs/pulp/teams/pulplift/ Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a

Re: [Pulp-dev] Pulplift responsibilities

I had some irc convo with Austin and as a result i removed pulplift team and updated ansible installer team with new members :) Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail."

Re: [Pulp-dev] Pulp2 Bug Backlog Closing?

Brian, i think the query should have Sprint and Sprint/Milestone because plugins have the Sprint filter only. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Ap

Re: [Pulp-dev] YouTube Custom URL

+1 PulpProject Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Mar 26, 2019 at 6:50 PM Brian Bouterse wrote: > +1 to PulpProject (like the site) > > O

Re: [Pulp-dev] Pulp2 Bug Backlog Closing?

+1 i like the comment +1 sending an email, so people can look and re-open if needed. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Wed, Apr 10, 2019 at 6:37 PM D

Re: [Pulp-dev] Pulp2 Bug Backlog Closing?

i also suggest to add to the query 'sprint candidate yes' so we don't close the ones we plan to solve in the upcoming sprint/s. wdyt? Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a

Re: [Pulp-dev] Pulp 3 tag

+1 to handle tag during the triage process Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Apr 2, 2019 at 3:53 PM Brian Bouterse wrote: > +1 to Tanya's suggest

Re: [Pulp-dev] YouTube Custom URL

turns out this is occupied as well https://www.youtube.com/user/PulpProject so +1 to the one as our twitter handle Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On T

Re: [Pulp-dev] Pulp 3 tag

+1 to create a pulp2 tag after mass-close Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Apr 11, 2019 at 3:48 PM Brian Bouterse wrote: > Great idea David! &g

Re: [Pulp-dev] YouTube Custom URL

yes! +1 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Apr 11, 2019 at 3:16 PM Daniel Alley wrote: > "Only way to be sure is to try it, but if no

Re: [Pulp-dev] Content Copy (between repos)

one-shot approach sounds good to me. +1 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Apr 11, 2019 at 6:05 PM Daniel Alley wrote: > The one-shot approach ba

Re: [Pulp-dev] State of the docs & Docs drive kickoff

Thank you for writing up this email. I reviewed high priority tickets and left some comments. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Apr 4, 2019 at 10:54

Re: [Pulp-dev] problems with publishers in Pulp 3

I updated the description of the story and removed the "Publishers Removal" part. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Fri, Apr 12, 2019 at 10:

[Pulp-dev] a release of pulp_docker 4.0.0b3 is available

a docker image that has manifest schema v2s1 - Enable docker distribution to serve directly latest repository version Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a

Re: [Pulp-dev] Pulp2 Bug Backlog Closing?

agreed, le'ts not include sprint_candidate, instead we can re-open issues that need attention. for example, rpm and docker plugins created a list with issues we plan to re-open. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go in

Re: [Pulp-dev] Release Note Process Improvements

Thank you Brian for moving this forward. That's a good improvement! Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Jun 4, 2019 at 4:39 PM Brian Boute

Re: [Pulp-dev] Release Note Process Improvements

+1 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Sat, May 25, 2019 at 10:18 PM Tatiana Tereshchenko wrote: > +1 to improve release notes process > >

Re: [Pulp-dev] black

-0. Fully agree with Tanya's 3rd point of observation. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Wed, Jun 19, 2019 at 5:22 PM Austin Macdonald wrote: &g

Re: [Pulp-dev] breaking change: accept Null instead of empty string

+1 to the suggestion. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, May 21, 2019 at 9:10 PM David Davis wrote: > This makes sense to me. +1. > >

Re: [Pulp-dev] Pulpcore RC3 Updates and Planning

+1 to option C Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Jul 2, 2019 at 4:42 PM Tatiana Tereshchenko wrote: > I agree, it's fine to do nothing un

Re: [Pulp-dev] black

Seems like there are usecases where flake8 might be handy. Let's keep it for now. We can always drop it later, after people get more used to black. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no

Re: [Pulp-dev] Pulp 3 tag

Curiosity question - what we will benefit from removing tags Pulp 3, Pulp 3 MVP, and Pulp 3 RC Blocker? Except of tons notifications received? I would keep them on the issues as they are, for historical reasons of pulp3 development. Regards, Ina Panova Software Engineer| Pulp| Red Hat

Re: [Pulp-dev] Master-detail inheritance in Pulp 3

I would avoid making changes in class naming. So +1 for the OneToOneField definition. Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Apr 23, 2019 at 6:45 PM D

Re: [Pulp-dev] Database support in Pulp 3

+1 to drop MariaDB support. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Sun, Jul 14, 2019 at 10:10 PM Brian Bouterse wrote: > I believe we have reached

Re: [Pulp-dev] Namespacing one shot upload and copy endpoints

There have been ongoing couple of more discussions offline regarding copy/remove and it kinda boiled down to: v3///action/ which will allow filtering v3/// will not allow filtering Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may

Re: [Pulp-dev] Pulpcore RC5 Release Planning

another beta but it is waiting on [0] being included and released in core. Thoughts? [0] https://pulp.plan.io/issues/4681 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail."

  1   2   3   >