Re: Plugin site prototype

Just to bump this thread to the top. I have not voted for this site yet, but I definitely support the change. There are much features which could be added, but it would be great to kick-off the site and the underlying infrastructure to the beta-* version on jenkins.io. It would allow making

Re: Plugin site prototype

Wondering if that should be somehow expressed in the hpi itself, or if it's fine/a feature to have it outside. I guess having it in the project itself would have an advantage: if a plugin goes from user-facing to only library-plugin (or the contrary), that could be expressed per version. Great

Re: Plugin site prototype

On Tue, Sep 6, 2016 at 2:21 AM, Daniel Beck wrote: > > > On 01.09.2016, at 21:43, Gus Reiber wrote: > > > > At the moment, we lack any sort of metadata to make that distinction, > but I think that would help the site greatly. > > > We could introduce

Re: Plugin site prototype

> On 01.09.2016, at 21:43, Gus Reiber wrote: > > At the moment, we lack any sort of metadata to make that distinction, but I > think that would help the site greatly. We could introduce the 'library' category of plugins and add a special meaning to that. However I

Re: Plugin site prototype

+1 to that. I would love to filter out plugins that aren't directly feature enabling. At the moment, we lack any sort of metadata to make that distinction, but I think that would help the site greatly. I think it would also be good to mark those OSS Jenkins is recommends during the install

Re: Plugin site prototype

(replies inline) On Thu, 01 Sep 2016, Gus Reiber wrote: > Tyler, I am confused by your post. > 256 is A LOT less than 50k. A LOT, A LOT less. 20x less. > 10K is a lot less than 50k, so if anything, Open-Stack Cloud's 256 installs > is being exaggerated. It is being graded on an easier scale

Re: Plugin site prototype

Your example highlights an issue: there is no reason to show `structs` to a user at all, since it offers no user-level features. It is just an API. No one chose to install it, they just got it as a dependency from some update of another plugin. When I worked on NetBeans we could mark modules as

Re: Plugin site prototype

Tyler, I am confused by your post. 256 is A LOT less than 50k. A LOT, A LOT less. 20x less. 10K is a lot less than 50k, so if anything, Open-Stack Cloud's 256 installs is being exaggerated. It is being graded on an easier scale than Structs, which is also being graded on an easier scale than

Re: Plugin site prototype

> On 31.08.2016, at 19:33, R. Tyler Croy wrote: > > This doesn't quite make sense to me. The home page already lists 'Recently > Updated' and also 'Most Installed' as a separate column, so I'm confused as to > why the math would include things from there. > > Asked

Re: Plugin site prototype

(replies inline) On Wed, 31 Aug 2016, Daniel Beck wrote: > > Also, all install graphs seem to have a hardcoded minimum Y value of 1 > > installs ??? way above that of most plugins. > > That's an interesting observation. Anyone else has comments on this? This was > a contested issue

Re: Plugin site prototype

(replies inline) On Wed, 31 Aug 2016, Daniel Beck wrote: > > > What does the "Recently installed" list on the home page mean? > > It's what I was referring to as "trending" plugins in my initial post: The > math is still work in progress, but the idea is to show these three lists: > > 1. The

Re: Plugin site prototype

> On 31.08.2016, at 16:34, Jesse Glick wrote: > > Is the POM `` even at all reliable? Could we > additionally/instead check for the GitHub user(s) to perform recent > releases and/or merge recent pull requests? This site uses (latest) update-center.json + the per-plugin

Re: Plugin site prototype

Very nice. On Wed, Aug 31, 2016 at 7:07 AM, Daniel Beck wrote: > Filter by maintainer (which as metadata is a bit of a mess due to > inconsistencies in POMs, but we try) Is the POM `` even at all reliable? Could we additionally/instead check for the GitHub user(s) to perform

Re: Plugin site prototype

> On 31.08.2016, at 15:50, Christopher Orr wrote: > > Yeah, it’s weird that the POM value rather than > value is used — searching ?maintainers= works fine. e.g. "orrc" gives > the expected results, but "Christopher Orr" returns multiple Christophers. Both work. Sometimes

Re: Plugin site prototype

Looks pretty cool! > On 31 Aug 2016, at 13:31, Daniel Beck wrote: >> * the search for maintainers should be improved. I only maintain the Job DSL >> plugin, but the page shows 7 plugins and the most relevant (Job DSL) is >> shown last. >>

Re: Plugin site prototype

> On 31.08.2016, at 13:24, Robert Sandell wrote: > > The index links goes to the wiki instead of the anchor point on the same page. True, that's weird. I'll make sure to put it on the to-do list if it isn't yet. -- You received this message because you are subscribed

Re: Plugin site prototype

And it doesn't seem to behave well on firefox; the browse/filter bar disappears and resets for every click I make. On Wed, Aug 31, 2016 at 1:22 PM, Daniel Spilker wrote: > Hi, > > I like it a lot! Thanks to everyone for the great work! > > my 2 cents: > * optional

Re: Plugin site prototype

> On 31.08.2016, at 13:22, Daniel Spilker wrote: > > * optional dependencies are not labeled as such, but should be. It's an > important info that shows which additional plugins will be installed or not Good point. Also, we currently don't cover implied dependencies

Re: Plugin site prototype

Looks good! How do I get the logo/icon to display instead of the default text? Some "issues" I've found: The Dependencies section shows all dependencies as "required" (as I interpret the missing info) even though some of them are optional. The index links goes to the wiki instead of the anchor

Re: Plugin site prototype

Hi, I like it a lot! Thanks to everyone for the great work! my 2 cents: * optional dependencies are not labeled as such, but should be. It's an important info that shows which additional plugins will be installed or not * the search for maintainers should be improved. I only maintain the Job DSL