-
Notifications
You must be signed in to change notification settings - Fork 16
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.
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
First updates #2
Conversation
foreman_theme_satellite.gemspec
Outdated
s.metadata = { "is_foreman_plugin" => "true" } | ||
s.license = 'GPL-3.0' | ||
s.authors = ['Alon Goldboim, Shimon Stein'] | ||
s.email = ['[email protected]'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have a better email address?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It comes down to the definition of "we".
In Foreman, we can (and do in some cases) use dev@community
.
But we are not in Foreman here, so maybe not?
We could ask @ShimShtein nicely if he wants to be listed here for now
they are required |
Came here to link theforeman/foreman-documentation#2542 (comment) which concluded they were needed. |
No description provided.