Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Using a mature name for the repo aligned with our non formalized sexy naming schema #1

Closed
gwarf opened this issue Jun 1, 2018 · 6 comments
Closed

Using a mature name for the repo aligned with our non formalized sexy naming schema #1

gwarf opened this issue Jun 1, 2018 · 6 comments
Assignees
@brucellino
Labels
enhancement New feature or request
Milestone
Release v0.1.0

Comments

@gwarf
Copy link
Member

gwarf commented Jun 1, 2018

OCD striking...

It may be appropriate to rename the project to ansible-* something to remain aligned with the usual naming scheme we are using and that was used for all the other ansible-related components.
We may or may not also want to use some specific casing.
@brucellino brucellino self-assigned this Jun 1, 2018
@brucellino brucellino added the enhancement New feature or request label Jun 1, 2018
@brucellino
Copy link
Member

Totally down with this. Will take a look at it soon.

@brucellino
Copy link
Member

I've changed the name of the repo to ansible-VOMS-client-role - still haven't added this to the style guide, but closing this issue in the meantime. You cool with this @gwarf ?

brucellino added a commit that referenced this issue Jun 17, 2018
@brucellino
Change playbook to use new role name
6e95227 
Closed #1 by changing the url of the remote.
Changed the name of the role used in the default testing
scenario
@gwarf
Copy link
Member Author

gwarf commented Jun 18, 2018

Sounds perfect.
Still, I think that an issue name containing the words mature and sexy may not be that much appropriate ;)

@enolfc
Copy link
Contributor

enolfc commented Jun 19, 2018

Can we agree on the naming schema? I was using ansible-role-* instead of ansible-*-role as here. Don't mind going either way, but we should converge

@gwarf
Copy link
Member Author

gwarf commented Jun 19, 2018

Even if I've been using the ansible--role model I think that ansible-role- is more sensible. It's also what is used in some of the examples on Ansible galaxy: https://galaxy.ansible.com/intro

@gwarf gwarf reopened this Jun 19, 2018
@brucellino
Copy link
Member

OK ! repo name is now /(ansible-role)([a-z]+)/

brucellino added a commit that referenced this issue Jun 28, 2018
@brucellino
Update the travis badge for changes in #1
d3a68a7
brucellino added a commit that referenced this issue Jun 28, 2018
@brucellino
Update default scenario playbook for #1
c90390a
@brucellino brucellino added this to the Release v0.1.0 milestone Jul 4, 2018
brucellino added a commit to EGI-Federation/Ansible-Fashion-Police that referenced this issue Jul 21, 2018
@brucellino
Update the GitHub control to reflect the proper naming scheme
558708c 
Discussed in EGI-Federation/ansible-role-VOMS-client#1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brucellino brucellino

Labels
enhancement New feature or request
Projects
None yet
Milestone
Release v0.1.0
Development

No branches or pull requests
3 participants
@gwarf @enolfc @brucellino