Simple Plugin Theme Store

[Lewis England]

Hi everybody, 

I'm a guy who loves customisation, and the Jenkins Simple Theme Plugin was a wonderful thing for me. 
I have been using it for a while and found out many wonderful things that I can tweak and theme.

However, it has come to my attention that there is no central theme repository or theme catalogue for this plugin. 
This is where I feel I can step in, but I'd like to get an idea on interest.

MY PLAN:
 - Create a database and interface for completed / WIP Jenkins Themes (names, descriptions, screenshots)
 - Allow users to upload to it (ZIP file with CSS, JS and other theme files)
 - Allow links back to the original source, guessing GitHub, for community contribution (and other classic GitHub uses)

 - Ratings, comments, tags and all the other standard stuff.

REASON:
Jenkins is a highly versatile system and I'm sure that those who are installing the Simple Theme plugin are the kind of people who are not a fan of the default UI.
Also, I personally am not too keen on searching around the internet for theme ideas / source to get started with. 

Please let me know who is interested in this idea / who would like to help out.

[Baptiste Mathus]

Hi, great idea. BUT I think you should really have a look at the work being done mostly by Gus Reiber. I suppose that might impact that kind of plugins, so I think it's better to sync with him.

If you want to have a glimpse into what it could look like, look for the Jenkins office hours recording of yesterday.

Cheers

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e814b4e7-845c-4706-9d72-0f24a51a1f43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Victor Martinez]

Hi,

 Actually I like that idea! I believe you could something similar to the scriptler approach (https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin) which is based on a particular central catalog:

  - http://scriptlerweb.appspot.com/ (actually is not accessible anymore for some reason)

  - https://github.com/jenkinsci/jenkins-scripts/

 But that's also true, as Baptiste mentioned, Jenkins community is thinking to move forward to another 2.X version which might also affect the UI. 

Anyway, I like your idea so let's see what' the community think and probably it's worth to ask in the Jenkins Development group too.

Cheers

[Oleg Nenashev]

+1 for the idea.

I would vote to use a GitHub organization as a repo. Related thread: https://mail.google.com/mail/u/0/#inbox/15040c942f2816bf

In such case I see the following advantages:

• You get a "repository" out of the box including project README pages, etc. => Minimal efforts
  
• Each theme can be stored as a separate repository and maintained individually.
• Existing theme repositories may be easily forked
• Snippets from GitHub may be used directly
• You can present a list of Snippets in Simple Theme Plugin
  
• You can use GitHub stars as a community rating for sorting
• You can version themes using GitHub releases or Git tags tags
  

We could use the existing Jenkins CI org, but probably a new organization is better due to the indexing advantages.

Best regards,
Oleg

воскресенье, 27 сентября 2015 г., 14:55:42 UTC+3 пользователь Victor Martinez написал:

[Oleg Nenashev]

Added jenkinsci-dev to Cc

среда, 7 октября 2015 г., 12:11:32 UTC+3 пользователь Oleg Nenashev написал:

[Kayn Ty]

i approve that idea.

it could be great to have a link to that central place on the Simple Theme Plugin readme, https://github.com/mallowlabs/simple-theme-plugin and in the official jenkins website.