home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
URGENT - GOOGLE CODE Project repo : will be closed
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="yoavain" data-source="post: 1129172" data-attributes="member: 92067"><p>As a plugin developer and mainly a plugin maintainer I think the best option is a central location for all plugins. </p><p>I picked up a few abandoned plugin projects. In some of them it was very hard to locate latest code. Developer could not reached, or did not commit latest changes, etc. In most cases I had to create my own repository by taking the latest available code, just to get full access to maintain these projects.</p><p></p><p>However, I do understand these are open-source projects, that are developed by programmers on their free time. Each has his preferences of an SCM. I don't think that we should force anyone to learn and use a specific system or use a specific repository.</p><p></p><p>I do think we should encourage developers to write an informative plugin/skin first post that include:</p><p>1. A link to their repository. (no matter where it is)</p><p>2. An explanation of how to build the project, (including creating the installer). This can either be a "For build instruction, check the README.txt in the trunk", a page in the MP wiki, a link to a thread in the forum, etc.</p><p>3. Contact information. You should be able to contact the developer. I used to give a link to the issue tracker in Google code. This should be enough as long as you're actually developing on maintaining. </p><p></p><p>We should also encourage developers to commit all their changes, i.e. if someone releases a new version of a plugin, it should reflect latest code (or a tag) in their repository, otherwise, this is not an open-source project.</p><p>We should also encourage developers to be responsible and when they leave a project, try to find someone who is willing to continue the project. (This is a tough one, I know...)</p></blockquote><p></p>
[QUOTE="yoavain, post: 1129172, member: 92067"] As a plugin developer and mainly a plugin maintainer I think the best option is a central location for all plugins. I picked up a few abandoned plugin projects. In some of them it was very hard to locate latest code. Developer could not reached, or did not commit latest changes, etc. In most cases I had to create my own repository by taking the latest available code, just to get full access to maintain these projects. However, I do understand these are open-source projects, that are developed by programmers on their free time. Each has his preferences of an SCM. I don't think that we should force anyone to learn and use a specific system or use a specific repository. I do think we should encourage developers to write an informative plugin/skin first post that include: 1. A link to their repository. (no matter where it is) 2. An explanation of how to build the project, (including creating the installer). This can either be a "For build instruction, check the README.txt in the trunk", a page in the MP wiki, a link to a thread in the forum, etc. 3. Contact information. You should be able to contact the developer. I used to give a link to the issue tracker in Google code. This should be enough as long as you're actually developing on maintaining. We should also encourage developers to commit all their changes, i.e. if someone releases a new version of a plugin, it should reflect latest code (or a tag) in their repository, otherwise, this is not an open-source project. We should also encourage developers to be responsible and when they leave a project, try to find someone who is willing to continue the project. (This is a tough one, I know...) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
URGENT - GOOGLE CODE Project repo : will be closed
Contact us
RSS
Top
Bottom