Looking at the update center issue, I can figure out there is a lot of work 
to do. In nutshell, below tasks need to get done-

1-Switch from update fetching (from update-centre.json) technique to a 
technique which supports portability so that user can install other plugins 
that may not follow update-center.json format.

2-Associated infrastructure changes and UX improvements of 4 tab plugin 
manager and reputation system for plugins(some rating system e.g., firefox 
extension center) 

3-Some way to add other update center for plugins.

To accomplish first task, I think i have to completely understand the 
infrastructure of the jenkins that is quite a big task.I will try to do it 
as soon as possible.
If you have some way around and if I am missing something then please tell 
me.Till now I was looking at jenkins outer working  
and now I am quite familiar with it.

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9ac1e131-70c2-4253-b52f-539527bf6444%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to