[Pulp-dev] Removing PublishedArtifact?

2018-09-17 Thread Brian Bouterse 
A plugin writer (@oleksander) pointed out to me that PublishedArtifact
seems a bit out of place for his usage. I can see why he thinks that, and
after thinking about it, Pulp does seem a bit over-complicated in this
area. I've written [0] to describe the problem, promote discussion of this
issue, and hopefully decide on a resolution.

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

Discussion and collaboration is welcome!

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

[Pulp-dev] Stages API Performance Data Collection

2018-09-17 Thread Brian Bouterse 
I'm interested in implementing a data collection feature for Pulp3. This
will allow us to easily and accurately benchmark pipeline performance to
clearly show improvement as we make changes. Borrowing from my old queueing
theory days... here is a data collection feature proposal:

https://pulp.plan.io/issues/4021

Any comment/ideas are welcome. Thank you!

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

Re: [Pulp-dev] Call for Presenters: Community Demo, Wednesday September 17th

2018-09-17 Thread Brian Bouterse 
The demo is coming up this Wednesday. There's still time to signup here
[2]. Also here [1] are some notes on how to be a presenter.

[1]: https://pulp.plan.io/projects/pulp/wiki/Demo_Presenter_Notes
[2]: https://etherpad.net/p/Pulp_Community_Demo_Agenda

On Tue, Sep 11, 2018 at 7:11 PM Brian Bouterse  wrote:

> We're moving this back 1 week to September 18th. I'm hoping this will
> allow for a full upload/sync/publish demo of pulp_rpm for Pulp3.
>
> Feel free to sign up for next week's demo!
>
>
> On Fri, Sep 7, 2018 at 2:15 PM, Brian Bouterse 
> wrote:
>
>> Have you contributed to Pulp or the Pulp community in some way since the
>> last community demo? Show the community what you've done!
>>
>> The next community demo is scheduled for Wednesday, September 12 at
>> 14:00 UTC [0].
>>
>> All demos should be pre-recorded; here are some docs on how to do that
>> [1]. Once you have your topic selected, put yourself on the agenda here [2].
>>
>> [0]: https://bit.ly/2oOVlE5
>> [1]: https://pulp.plan.io/projects/pulp/wiki/Demo_Presenter_Notes
>> [2]: https://etherpad.net/p/Pulp_Community_Demo_Agenda
>>
>> Thanks,
>> Brian
>>
>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Stages API Performance Data Collection

2018-09-17 Thread Dana Walker 
I love this idea!  Running benchmarks as we go will allow us to react
quickly if there are unforeseen performance pain points.

Have you run anything similar to this proposal back in Pulp2 or elsewhere?
I'm a little concerned about the storage capacity needed for the sheer
number of sqlite3 databases generated.  Maybe a script could periodically
empty /var/lib/pulp/debug/ as it reaches certain configured size/age limits?

--Dana

Dana Walker

Associate Software Engineer

Red Hat




On Mon, Sep 17, 2018 at 2:36 PM, Brian Bouterse  wrote:

> I'm interested in implementing a data collection feature for Pulp3. This
> will allow us to easily and accurately benchmark pipeline performance to
> clearly show improvement as we make changes. Borrowing from my old queueing
> theory days... here is a data collection feature proposal:
>
> https://pulp.plan.io/issues/4021
>
> Any comment/ideas are welcome. Thank you!
>
> -Brian
>
> ___
> 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

[Pulp-dev] URL Word Separators

2018-09-17 Thread Jeff Ortel 

What is the project policy on word separators in URLs?

My take on 3 most common options:

1. The words run together - is hard to read. Example: /contentguard/
2. Hyphens in URLs are easy to type and read.  Most common and 
recommended based on my limited search.  Example: /content-guard/
3. Underscores strike me as odd outside of programming languages. Harder 
to type.  Example: /content_guard/


Does django have a recommendation/limitation?

Thoughts?



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

Re: [Pulp-dev] URL Word Separators

2018-09-17 Thread Bruno Rocha 
IMO option 2 "slug" is the most common for urls.

Em seg, 17 de set de 2018 19:12, Jeff Ortel  escreveu:

> What is the project policy on word separators in URLs?
>
> My take on 3 most common options:
>
> 1. The words run together - is hard to read. Example: /contentguard/
> 2. Hyphens in URLs are easy to type and read.  Most common and
> recommended based on my limited search.  Example: /content-guard/
> 3. Underscores strike me as odd outside of programming languages. Harder
> to type.  Example: /content_guard/
>
> Does django have a recommendation/limitation?
>
> Thoughts?
>
>
>
> ___
> 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

Re: [Pulp-dev] URL Word Separators

2018-09-17 Thread Dana Walker 
SEO groups universally answer hyphens (option 2) over underscores as Google
evidently parses the former as word separators and the latter as word
joiners.  While we don't care about search rank for our purposes, it seems
good to remain consistent with the preferred route nowadays (even though I
personally like underscores as I find them easier to read even though
hyphens are faster to type).  Here's just one example [0], but I skimmed
many and they're consistent.

[0]
https://www.woorank.com/en/blog/underscores-in-urls-why-are-they-not-recommended

Dana Walker

Associate Software Engineer

Red Hat




On Mon, Sep 17, 2018 at 6:22 PM, Bruno Rocha  wrote:

> IMO option 2 "slug" is the most common for urls.
>
> Em seg, 17 de set de 2018 19:12, Jeff Ortel  escreveu:
>
>> What is the project policy on word separators in URLs?
>>
>> My take on 3 most common options:
>>
>> 1. The words run together - is hard to read. Example: /contentguard/
>> 2. Hyphens in URLs are easy to type and read.  Most common and
>> recommended based on my limited search.  Example: /content-guard/
>> 3. Underscores strike me as odd outside of programming languages. Harder
>> to type.  Example: /content_guard/
>>
>> Does django have a recommendation/limitation?
>>
>> Thoughts?
>>
>>
>>
>> ___
>> 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
>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] URL Word Separators

2018-09-17 Thread David Davis 
It looks like Google recommends the use of hyphens in URLs to separate
words[0]. It looks like Django also favors this approach[1].

[0] https://support.google.com/webmasters/answer/76329?hl=en
[1] https://code.djangoproject.com/ticket/25473

David


On Mon, Sep 17, 2018 at 6:12 PM Jeff Ortel  wrote:

> What is the project policy on word separators in URLs?
>
> My take on 3 most common options:
>
> 1. The words run together - is hard to read. Example: /contentguard/
> 2. Hyphens in URLs are easy to type and read.  Most common and
> recommended based on my limited search.  Example: /content-guard/
> 3. Underscores strike me as odd outside of programming languages. Harder
> to type.  Example: /content_guard/
>
> Does django have a recommendation/limitation?
>
> Thoughts?
>
>
>
> ___
> 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