> Finally, we have to consider the effort required to rename the plugin (Bruno,
> WDYT? )
There will be some effort, and we can miss updating some Javadocs or Strings
here or there. Some users already familiar with the Uno Choice name would have
to be notified on the new name.
But if we agree on a new name, I'd gladly fire Eclipse, rename the artifact ID
and update the Javadocs and any other reference to the old name that I can find
:^)
Bruno
From: Ioannis Moutsatsos <imoutsat...@gmail.com>
To: jenkinsci-dev@googlegroups.com
Sent: Thursday, February 19, 2015 12:36 AM
Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters
All,
I do have to take responsibility for naming this plugin. So here goes the
thinking behind it.
This is a plugin for making one or more choices among options for a parameter.
Some of the functionality was previously distributed among different plugins
(dynamic parameter plugin, extensible choice parameter plugin, extended choice
plugin), but none of these was able to deliver cleanly and consistently the
four main things I wanted:
- Dynamic generation of the parameter options,
- multi-select using a variety of formats (check-boxes, radio buttons,
lists),
- filtering, and
- dynamically refreshed options based on other parameter choices that users
make.
Thus I thought that naming the plugin Uno-Choice was appropriate for two
reasons:
- One (Uno) control that could do it all and
- Uno for the project behind it (BioUno.org)
In retrospect, perhaps I could have chosen a better name but having Bruno like
it, sealed the deal! The rest is history as they say...Bruno developed it, and
here we are finally contributing it to empower all Jenkins users.
So, if the name could confuse new users how could we improve it?
Let me try to offer a few alternatives.
- BioUno Dynamic Choices
- BioUno Scripted Choices
- Dynamic Options Parameter
- Scripted Options Parameter
Finally, we have to consider the effort required to rename the plugin (Bruno,
WDYT? )
Thanks all for the feedbackBest regardsIoannis
On Wednesday, February 18, 2015 at 7:31:29 PM UTC-5, Richard Bywater wrote:
Personally I'd avoid the word Uno in the plugin name completely as, according
to the README, you can have one *or more* parameters and Uno Choice Dynamic
Parmeter says to me that the plugin only supports one choice.
Richard.
On Thu, Feb 19, 2015 at 1:22 PM, 'Bruno P. Kinoshita' via Jenkins Developers
<jenkin...@googlegroups. com> wrote:
> A suggestion: give the plugin a more descriptive name. Random Jenkinsusers
>are not going to have any idea what “Uno” is. Crediting theinstitution that
>did the work is fine, but if I were looking to makemy parameters dynamic, I
>would pick a plugin named “Dynamic Parameter”and skip right over “Uno Choice”.
Good point. I didn't choose the name, but I like it. Maybe Uno Choice Dynamic
Parameter? Other suggestions? > BTW if this is to be usable in a secured
installation you need tointegrate with the script-security plugin.
True! My bad for forgetting about this. I will try to integrate it in my next
development cycle for the plug-in. I will try to check if the Dynamic Parameter
plug-in is already integrated with the script-security plug-in. If not, I'll
try to submit a pull request (otherwise I'll use it as reference :)
CheersBruno
From: Jesse Glick <jgl...@cloudbees.com>
To: Jenkins Dev <jenkin...@googlegroups. com>
Sent: Wednesday, February 18, 2015 7:01 PM
Subject: Re: New plug-in: Uno Choice Plug-in for dynamic parameters
On Tue, Feb 17, 2015 at 8:30 AM, 'Bruno P. Kinoshita' via Jenkins
Developers <jenkin...@googlegroups. com> wrote:
> We developed a plug-in in the BioUno project
A suggestion: give the plugin a more descriptive name. Random Jenkins
users are not going to have any idea what “Uno” is. Crediting the
institution that did the work is fine, but if I were looking to make
my parameters dynamic, I would pick a plugin named “Dynamic Parameter”
and skip right over “Uno Choice”.
BTW if this is to be usable in a secured installation you need to
integrate with the script-security plugin.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsub...@ googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/jenkinsci-dev/ CANfRfr0gip- ui8oZggT277keKGzYDJoH_
WKsEHPFSWjcbw3%2BAQ%40mail. gmail.com.
For more options, visit https://groups.google.com/d/ optout.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-de...@ googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/jenkinsci-dev/ 1979203684.442515. 1424305331365.JavaMail.yahoo%
40mail.yahoo.com.
For more options, visit https://groups.google.com/d/ optout.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/d6cecb3b-faaa-43c4-993f-a38c7ba6ede1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/1083540686.2576291.1424359023253.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.
