-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


On 06/29/2016 09:47 AM, Brian Bouterse wrote:
> +1 to using contrib in favor of pulp_contrib, and similar for other new repos.

+1

> 
> My reasoning is based on optimizing the common case. It's very common for 
> people to work with Pulp repos 
> everyday so having a cleaner name is nice. The uncommon case is when it's 
> forked AND a user doesn't know
> where it came from AND they don't look at the README which came with their 
> fork. In that situation they
> could also rename it.
> 
> Whatever the decision we should reach one soon.
> 
> -Brian
> 
> 
> On 06/27/2016 09:01 AM, Jeremy Cline wrote:
>> On 06/24/2016 03:07 PM, Michael Hrivnak wrote:
>>> On naming, I have a slight preference toward keeping the pulp_ prefix 
>>> convention, but that might just
>>> be rooted in habit. My general feeling is that the name of a git repo 
>>> should stand on its own, and
>>> the fact that it may be present on github within a particular user or 
>>> organization's namespace does
>>> not displace the value of the name itself being fully descriptive.
>>> 
>>> If I fork pulp/contrib, I end up with mhrivnak/contrib. Yes, the list of my 
>>> repos will show that is
>>> was forked from pulp/contrib, but it still seems weird. I have to go to 
>>> github to see that. If
>>> someone forked it from me, now the original name's context is hard to find.
>> 
>> You can always rename your fork pulp_contrib if you really want to.
>> 
>>> Even when I merely clone it, I'd get a local directory named "contrib". 
>>> Perhaps others already
>>> organize their local git clones by organization, but I've always just had a 
>>> flat directory of stuff
>>> that's been cloned from all over, because the repo names are usually fully 
>>> descriptive.
>> 
>> I use directories to sort all the projects I contribute to and I guess I 
>> assumed everyone else did as
>> well, but renaming your fork on GitHub also solves this problem for you, as 
>> does `git clone <url> 
>> <dir_name_of_your_choice>`.
>> 
>> 
>> 
>> 
>> _______________________________________________ Pulp-list mailing list 
>> Pulp-list@redhat.com 
>> https://www.redhat.com/mailman/listinfo/pulp-list
>> 
> 
> _______________________________________________ Pulp-list mailing list 
> Pulp-list@redhat.com 
> https://www.redhat.com/mailman/listinfo/pulp-list
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXc/s3AAoJEM9lW7UwFwZXG4kP/35UlbOcTGVStnTplFyLN7ew
k2oyWESC73zZwqoD4+zRQ7MSpy3ut8wgzWZm9S9WDo0ylJEu3F2DcDmjrd/CqISp
UOJfmNwL5oRjSJhfvnqfj88R2txyPiNgjk5uW+Z3jfIl1MQq33bSuIVniP4xi9i7
MvV4UuiaxxSKq6p+Ro70leDM+OhmlcYxqreKuJYVb2nnO6aIU2sVy/CQpc+cUt6x
go+xsu7Nf5y1YD4EiYYYU+yegj7HaJ63E2s0/m5NeYxtU8oFtyRELpSXpYjolOIq
VT3lYyw9MYlLReMs23M+ranqUKqKFtt9ipJwgcgFBaYTaWKNCm9BkBFLo/MKyQN7
m8IjtvdeltjCJ/Ep0ZFR8otfYBC4AhEn/BAjydiE7Bm22dE4DQCXmCQdnfx+wTSz
C/MyVNdoWH0hfmS1GQNwEjMKHIRDu3vQt8PrDf0SuZswzyU8J0kd48w+bqa/kMHq
lqg23OeFrQOyqE8pGLw7qub6CYiygx3oDgT/lsCoUM0032pxX8updQiltQWc7qib
VS24aVz47/3RdBhT3GDAS3e435t81jGRhPt+UDU6yTOBury3zYWxcZ7SXYSHIFoj
D7svLWB5mkeCymrglhcnIatJnGBa9RoPSHfn0trVo3zW4XQleuuqfw58H9WRbXJu
tA8fmx3u9v4BiagVgmHl
=q4ZX
-----END PGP SIGNATURE-----

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

Reply via email to