Fine with me.
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."
- Original Message -
From: "Austin Macdonald"
To: pulp-dev@redhat.com
Sent: Wednesday, Sep
+1 to option 3
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."
- Original Message -
From: "Michael Hrivnak"
To: "Brian Bouterse"
Cc: pu
I tend to agree with Brian.
I agree that with creation of another project will confuse more the users.
I also like the idea of creation new tags, or renaming existing ones more than
creation of new project.
Regards,
Ina Panova
Software Engineer| Pulp| Red Hat Inc.
"Do not go
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
?f_devices=woman
Let me know your thoughts and ideas.
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 lis
ad where we were discussing possible statements [0].
[0] http://pulp.etherpad.corp.redhat.com/290
--------
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."
__
Do i understand correctly that blocker bugs will not be verified by
default, unless we would set "require QE signoff" to True?
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
make the issue as blocker and fix it in tight deadlines.
I think all blocker bugs should be verified by default, and other bugs just
when there's flag set by devs.
18 янв. 2017 г. 19:23 пользователь "Brian Bouterse"
написал:
Yes, that is my understanding.
On Wed, Jan 18, 2017 at
gards,
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 wrote:
> David, does my response answer your question?
>
> Ina, same to you: does
this strategy from the beginning but now i
could do that even with closed eyes.
+1 of writing down the benefits of cherry-picking and clear our
expectations.
Regards,
Ina Panova
Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where there
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 wrote:
> One of the thi
community 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,
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
refoxproj".
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.
ons, I will be happy to answer those.
----
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 4, 2017 at 11:58 PM, Partha Aji wrote:
>
> I was trying to figure out pu
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
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
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
+1 for add/remove. An aside note, i want to make sure we stick to 'remove'
specifically' and not 'delete'.
I wanted to bring this up, since these 2 terms are quite similar but still
feels different.
Regards,
Ina Panova
Software Engineer| Pulp| Red Hat Inc.
re, yes
it is unstable and most likely has issues and bugs.
But people usually expect more or less this ^ when it comes to a completely
new and drastically big change.
Regards,
Ina Panova
Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where t
ps 1-6 mentioned for cherry-picking then steps 1-2
mentioned for merging forward.
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 25, 2017 at 6:49 PM, Sean Mye
ng the git history
cleaner and other things mentioned previously in my email
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, May 26, 2017 at 5:46 PM, David Davis w
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 Dav
Mihai,
both of the Tasks are added to the sprint, so they will be worked on asap.
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 8, 2017 at 3:53 PM, Miha
] 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
oming
changes, otherwise 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, Ju
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
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 whe
o is always and easy path :)
----
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 15, 2017 at 10:42 PM, Daniel Alley wrote:
> I _strongly_ disagree with the idea o
Another model to consider is to look how downstream kernel guys accept
patches - it should have at least 3 acks and none nack.
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.&quo
+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 wrote:
> +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."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev
+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, Oct 2, 2017 at 2:45 PM, Daniel Alley wrote:
> +1
>
> On Mon, Oct 2, 2017 at 7:37 AM, Michael Hrivna
a starting point we should define as a team what we expect to have
in those 2 sections, since it might turn out everyone would have its
different expectations.
Regards,
Ina Panova
Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where there
@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 Macdon
-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 and
and further discussed with the team in the written manner.
This approach will minimize the probability of implementing something which
may not work later.
Thank you.
Regards,
Ina Panova
Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where
+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
wrote:
> Sounds good. Our policy has been to stop building for and
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
+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, Dec 12, 2017 at 8:32 PM, Austin Macdonald
wrote:
> +1
>
> On Tue, Dec 12, 2017 at 2:01 PM, Bihan Zh
in case there are not opened
yet.
Thank you!
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 31, 2018 at 9:11 PM, Tom McKay wrote:
> A couple foreman RFEs co
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
tions.
[0]
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.&
We had an irc chat and a call, the questions where addressed with a
possible solution.
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, Mar 8, 2018 at 4:35 AM,
e can 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 wrote:
> I didn't get a chan
and evaluating 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 wr
ng 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 an
The answer to your question you can find here:
https://github.com/Katello/katello/pull/7262#issuecomment-376094549
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 S
line of code to cover which is not really
realistic to happen, +1 complex to mock.
+1 to own policy of plugins.
[0] https://media.giphy.com/media/g8GfH3i5F0hby/giphy.gif
Regards,
Ina Panova
Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where
e text on the monitor.
then...I will take the action item and schedule the meeting.
Meanwhile we'll have time to chew on Easter eggs and give to the proposal a
deeper, unbiased, full of protein (that helps brain thinking) thought.
Regards,
Ina Panova
Software Engineer| Pulp| R
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 trail.
couple of email addresses for
different purposes ;)
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 4, 2018 at 6:57 PM, Brian Bouterse wrote:
> OK I'm convi
ption request? Under project CLI with
tag RPM?
Or under rpm_plugin project with tag CLI?
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 5, 2018 at 1:21 AM, Austin M
drops 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
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
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
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 W
/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."
[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 wrote:
>
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
/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
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
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
*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 wrote:
> To make a concrete example to prove my understati
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
me more for now.
----
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 wrote:
> Let's brainstorm on something.
>
> Pulp
ing willbe 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 le
+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
e 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 t
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
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
+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, Jun 14, 2018 at 10:19 PM, Bihan Zhang wrote:
> +1
> I think the plugin_template is very valuable for boot
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
?
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
/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.
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
+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
+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:
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
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
guy Y.
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:
>
&
/github.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
+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
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
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
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,
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,
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
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] https://github.com/
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
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
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 trail.
+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 Bouters
ser's 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
+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
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
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 trail.&
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."
+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 le
+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
1 - 100 of 265 matches
Mail list logo
