[foreman-dev] [Event] Foreman Community Demo Items - Thu 04 Jan 3pm [BST]

[Ori Rabin]

First demo of 2018!
I'm sending an early reminder before the holidays so everyone has time to
plan ahead and add to the agenda.

As always, have a think for items which have been completed since
the last demo on 2017-12-07. There is a query that will show you items
completed (i.e. marked as closed) since the last demo [2].  Please add demo
items following the instructions on the agenda page [3].

If you can't be present but have something to show, add it to the
agenda and let me know - I'll be happy to talk about the feature in your
absence. Please do leave me enough time to familiarize myself with the
content
though :)

[1] https://www.youtube.com/watch?v=BVTiwSEMcyw
[2] http://tinyurl.com/ycpqnew3
[3]
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

--
Ori
IRC: orabin

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[foreman-dev] [Event] Foreman Community Demo Items - Thu 07 Dec 3pm [BST]

[Ori Rabin]

Hi all,

Demo time! As always, have a think for items which have been completed since
the last demo on 2017-11-16. There is a query that will show you items
completed (i.e. marked as closed) since the last demo [2].  Please add demo
items following the instructions on the agenda page [3].

If you can't be present but have something to show, add it to the
agenda and let me know - I'll be happy to talk about the feature in your
absence. Please do leave me enough time to familiarize myself with the
content
though :)

[1] https://www.youtube.com/watch?v=g8XnAKfG9xY
[2] http://tinyurl.com/ycf7wqcv
[3]
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

--
Ori
IRC: orabin

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[foreman-dev] [Event] Foreman Community Demo Items - Thu 16 Nov 3pm [BST]

[Ori Rabin]

Hi all,

Demo time! As always, have a think for items which have been completed since
the last demo on 2017-10-26. There is a query that will show you items
completed (i.e. marked as closed) since the last demo [2].  Please add demo
items following the instructions on the agenda page [3].

If you can't be present but have something to show, add it to the
agenda and let me know - I'll be happy to talk about the feature in your
absence. Please do leave me enough time to familiarize myself with the
content
though :)

[1] https://www.youtube.com/watch?v=QHzNIFjMpTM
[2] http://tinyurl.com/ydbo6a43
[3]
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

--
Ori
IRC: orabin

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[foreman-dev] Foreman Vertical Navigation Survey

[Ori Rabin]

Hello all,

The Foreman development team is considering switching to a new,
vertical-oriented navigation. As this is a big change to the look-n-feel of
the application, we wanted to consult the community on it.

You can learn more about the reasoning and development of the UI in this
video (https://www.youtube.com/watch?v=hQwJ11GYfjY) and see it in action in
this video (https://youtu.be/nZBnQo57Xdc?t=14m33s).

We'd like to invite you to play with the new UI on out demo box (
https://vertnav.demo.theforeman.org - login "admin" / "vertnav" - apologies
for the self-signed cert).

Please share your thoughts in the survey:
https://goo.gl/forms/ERJhphis7Gd85EwJ3

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] [Hammer CLI] Hidden flag for all parameters

[Ori Rabin]

There is no reason that option shouldn't be available in hammer.
I opened up a bug for it: http://projects.theforeman.org/issues/18878
Please update the issue if there is any other relevant information to add.

On Fri, Jan 20, 2017 at 7:21 PM,  wrote:

> Hey all,
>
> I saw that it is possible to hide values in the host parameters, host
> group parameters and global parameters. However, there is no flag provided
> in the Hammer CLI to create parameters as hidden values for these
> instances. Do I miss something or is there any reason why this is not
> possible?
>
> Thanks for reading and kind regards
>
> --Gerrit
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] Draft community survey questions

[Ori Rabin]

I think plugins should be on a separate page or it should be an open
question because even a list on 20 is too long.
CRs can appear in the question itself, it's pushing it but the list is
still reasonable.

Maybe the question: How would you rate our user support? can have links
instead of bringing back the do you know our IRC question?

+1 for the contributor survey.

On Wed, Dec 21, 2016 at 10:04 PM, Greg Sutcliffe 
wrote:

> Hi all,
>
> Last year I rushed the community survey, and forgot to get feedback on the
> questions it contained - I'm not making that mistake again :)
>
> Below is the draft question set - fair warning, its a big email :P. My aim
> is to either make it shorter, or at least break it up into a couple of
> logical pages. I've tried to indicate where the departures from last year
> are (especially the dropped/potentially-dropped ones). Feedback on what to
> change or things to add is very welcome - if you have a burning question to
> ask, lets hear it!
>
> Additionally, I may be able to fund some small incentive strategy to get a
> larger sample size. I can see two ways to do that:
>
> * Some small reward for the first X people to fill out the survey (eg $5
> gift card or something)
> * All response go into a raffle for some nice (more expensive) things
>
> Clearly this would require the user to identify themselves (an email is
> probably all I'd need) - that would be optional, of course. Do people
> support this? What would be your preferred option?
>
> The plan is to gather feedback on this in the New Year, publish the survey
> by mid January with a big push for early responders (hence the swag
> incentive above) and then re-push in person at the conferences. We then
> close it after about a month (mid Feb) and do the analysis.
>
> Anyway, the questions:
>
> ### To keep from last year - self-explanatory
>
> How long have you been using Foreman?
> [3m, 6m, 1yr, 2y, 3+yr]
>
> How many people use Foreman in your organization
> [1, 5, 10, 50+]
>
> What Foreman version are you using?
> [nightly, stable, old-stable, older]
>
> How many nodes do you manage with Foreman?
> [0, 10, 50, 200, 500, 1000, 1, 2+]
>
> What operating system do most of your Foreman servers use?
> [RHEL/CentOS/Fedora, Debian, Ubuntu, SUSE, Other]
>   (do we need to split this more, eg Fedora vs RHEL?)
>
> Which Compute Resources do you use with Foreman?
> Which Foreman plugins do you use?
>   these two need better structuring, the lists are long & stats were skewed
>   last year due to missing options. See end of post for the actual lists.
>
> How would you rate our user support?
> [mailing list, IRC, website, docs], 1-5 score
>
> How well do major releases (e.g. 1.9, 1.10) meet your needs?
> [frequency, features, bugs, stability], 1-5 score
>
> Any other feedback about our support and documentation? [text]
>
> Overall, how well does Foreman meets your requirements? [text]
>
> What's the most important thing you'd like to see done next in Foreman?
> [text]
>
> Do you have any additional comments or special requests? [text]
>
> ### New additions
>
> Would you accept Foreman gathering anonymous usage stats to help improve
> the
> project? This would have an opt-out and a way to see the data before
> sending
> (see https://github.com/theforeman/rfcs/pull/31 for a proposed design -
> comments
>  welcome!)
>   I really want to hear user feedback on this to avoid backlash later. Not
>   sure if it should be a simple yes/no or text-field for comments.
>
> What geographical area are you in?
> [Europe, N America, S America, Africa, Asia, Oceania]
>   We don't really know where our userbase is, although we have a hunch.
> I've
>   tried to keep it coarse, and it'll obviously be optional.
>
> ### Dropped from last year
>
> What do you use Foreman for at your organization?
>   I think our problem domain is fairly well specified, and knowledge of
>   specific plugins/CRs is more specific & valuable. Anything really ugent
> will
>   end up in the "most important thing" or "additional comments" boxes
>
> What are your top 3 from the following potential future features?
>   Basically the same thing as "what's most important to add", just ask it
> once
>
> Why did you choose it instead of alternatives?
>   I think I'd rather focus on Foreman than go off on a tangent. People who
>   are switching away won't fill in the survey anyway.
>
> Do you Use Locations / Organization features?
> Could you tell us more about your usage of Locations/Organizations?
> Any other feedback on your Locations/Organizations usage that you'd share?
>   I think we've gathered all the feedback we can on this last year.
>
> Would you be interested participating in a foreman community event?
> Would you be willing to help organise Foreman events in your area?
>   We saw good responses to the birthday events, but these questions don't
> work
>   on an *anonymous* survey. Potential to add back in if we ask for email
> addrs
>
> 

[foreman-dev] Hash rocket syntax

[Ori Rabin]

Hello,

The hash rocket syntax is still in use throughout the project.
New prs are sometimes submitted with the x: y syntax instead and then asked
to change.

As discussed on IRC yesterday there should be consistency and there is an
option to autofix with rubocop if the style is changed to change existing
code with less effort.

Since right now the lowest ruby version supported in core is 2.0 and there
are even discussions about dropping that, should this syntax change?

Ori

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.