I think it may be a good idea for someone from plex to set up a collective repo on git hub to allow plugin code, etc to live within the collective.
This would allow authorized developers easier access to code to be able to commit bug-fixes changes, etc without needing to get pull requests authorized or added to individual projects.
I personally would not mind taking time to fix plugins, skins etc if it were easy to commit the changes,etc and this model would promote more development. Users who are not authorized can still make pull requests. I don’t want to waste my time fixing a plugin just to wait for an absent author to accept it and this solves that issue as well.
I am a professional python developer (yes, thats how I make my living) and I think you will find more people with experience willing to help out if we make it easy. There are many plug-ins that could benefit from being modified by someone with alot of experience. Again I don’t want to have to contact 9-10 authors separately just to get added to their personal github repo if their is another alternative. If the original coder does not like a modification, there is always revert 
One other python project that I am a core developer that uses this model very successfully with large collectives is plone (see https://github.com/collective/).
Any comments? Anyone knowledgeable enough to set something up with github?
Hi Jason!
All Plex plug-ins are available here: Plex Plug-ins · GitHub
This organisation is managed by the Plex team, not the original plug-in authors (although several of the authors have permission to manage the repos themselves). While we do still require pull requests before updating these repos, since there are many people actively managing them, requests should be accepted in a short amount of time. This requirement is in place because our store server (the one that media servers connect to when installing/updating plug-ins) pulls new versions from these repos directly. Requiring that code is reviewed before being added to the master repositories helps ensure that bad code isn’t inadvertently pushed out to all our users.
I hope that clears a few things up!
-james
There is also an Unsupported Appstore (see my sig for the link) intended for plugins which for numerous reasons may not be appropriate for the official Plexinc repository. At present the number of plugins in it is limited because it is based on an opt-in system. Any plugin developers who want their work to appear in the Unsupported Appstore have to be willing to post their code on github, after that adding the plugin is a snap.
Awesome!, off to work I go
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
