Protege4Contributing - Revision history

TaniaTudorache at 06:10, May 24, 2016

2016-05-24T06:10:14Z

TaniaTudorache at 04:52, May 24, 2016

2016-05-24T04:52:52Z

TaniaTudorache at 04:51, May 24, 2016

2016-05-24T04:51:54Z

TaniaTudorache at 04:51, May 24, 2016

2016-05-24T04:51:19Z

JenniferVendetti: /* Advertising your plugin on this wiki */

2012-11-16T20:50:21Z

‎Advertising your plugin on this wiki

JenniferVendetti: /* Advertising your plugin on this wiki */ Fixed link for creation of new plug-ins. Format for doing this with semantic forms has changed.

2012-11-16T20:48:50Z

‎Advertising your plugin on this wiki: Fixed link for creation of new plug-ins. Format for doing this with semantic forms has changed.

JenniferVendetti at 23:39, January 25, 2011

2011-01-25T23:39:10Z

RichMorin: /* Creating a plugin */

2009-04-01T19:29:14Z

‎Creating a plugin

Nickdrummond: /* Plugins */ auto-update link

2008-11-07T13:28:56Z

‎Plugins: auto-update link

Nickdrummond at 15:36, August 14, 2008

2008-08-14T15:36:40Z

@@ Line 10: / Line 10: @@
 '''Back to [[Protege4UserDocs|Protege User Documentation]]'''
-'''Back to [[Protege4DevDocs|Protege Developer Documentation]]'''
+'''Back to [[Main_Page#Developer_Documentation|Protege Developer Documentation]]'''
 __TOC__
@@ Line 89: / Line 89: @@
 '''Back to [[Protege4UserDocs|Protege User Documentation]]'''
-'''Back to [[Protege4DevDocs|Protege Developer Documentation]]'''
+'''Back to [[Main_Page#Developer_Documentation|Protege Developer Documentation]]'''

@@ Line 41: / Line 41: @@
 using a simple view plugin as the example.
-See also: [[Protege4DevDocs#Working_with_the_Protege_source_code|Documentation for Protege 4.x developers]]
+See also: [[Protege4DevDocs#Working_with_the_Protege_source_code|Documentation for Protege developers]]
 === Allow Protege to download your plugin directly ===
@@ Line 78: / Line 78: @@
 https://github.com/protegeproject/protege
-Also see: [[Protege4DevDocs#Working_with_the_Protege_source_code|Documentation for Protege 4.x developers]]
+Also see: [[Protege4DevDocs#Working_with_the_Protege_source_code|Documentation for Protege developers]]
 === Bug reports ===

@@ Line 9: / Line 9: @@
 '''Back to [[Protege4UserDocs|Protege User Documentation]]'''
 '''Back to [[Protege4DevDocs|Protege Developer Documentation]]'''
@@ Line 84: / Line 85: @@
 Please follow our [[Protege4UserDocs#Bugs_and_feature_requests|guidelines]] if you have found a bug.
 The better a bug is described, the more likely it is to be fixed quickly.

@@ Line 1: / Line 1: @@
 <div class="orangeBox">
-<span class="orangeBoxTitle">Contributing to Protege 4.x</span><br /><br />
+<span class="orangeBoxTitle">Contributing to Protege</span><br /><br />
 Protege is an open source project, with a large community, many of whose members help to add to its success through varied means.
-This page explains the routes through which you can contribute to Protege 4.x and its community.
+This page explains the routes through which you can contribute to Protege and its community.
-If you are interested in other ways of helping please contact us through http://mailman.stanford.edu/mailman/listinfo/p4-feedback.
+If you are interested in other ways of helping, please contact us through the [https://mailman.stanford.edu/mailman/listinfo/protege-user protege-user mailing list].
 </div><br />
-Back to [[Protege4UserDocs]]
+'''Back to [[Protege4UserDocs|Protege User Documentation]]'''
+'''Back to [[Protege4DevDocs|Protege Developer Documentation]]'''
 __TOC__
@@ Line 20: / Line 18: @@
 === Mailing lists ===
-Plenty of people ask questions on the various mailing lists available for Protege support and it would be impossible to deal with this big an inbox
+Plenty of people ask questions on the various mailing lists available for Protege support, and it would be impossible to deal with this big an inbox,
 if it were not for the fellow community members that frequently offer answers, advice and pointers. We welcome contributions from everyone.
 === Documentation ===
-Tools such as Protege 4.x are continually growing and it is hard to spend huge amounts of time changing screenshots, wording and formatting
+Tools such as Protege are continually growing and it is hard to spend huge amounts of time changing screenshots, wording and formatting
 in the documentation (such that it is).
@@ Line 34: / Line 32: @@
 == Plugins ==
-The most obvious way to contribute to the tools is to produce a plugin. Protege 4.x is built on top of an OSGi compliant plugin mechanism, so it
+The most obvious way to contribute to the tools is to produce a plugin. Protege is built on top of an OSGi compliant plugin mechanism, so it
 is easy to implement new menu items, views and other plugins and it is even possible to extend the types of plugin that can be created.
 === Creating a plugin ===
-A [http://www.co-ode.org/downloads/protege-x/plugin-code-example.php step by step guide] is available,
+A [https://github.com/protegeproject/protege-plugin-examples step-by-step guide] is available,
 using a simple view plugin as the example.
 See also: [[Protege4DevDocs#Working_with_the_Protege_source_code|Documentation for Protege 4.x developers]]
-=== Allow Protege 4.x to download your plugin directly ===
+=== Allow Protege to download your plugin directly ===
-From build 104 (pending Nov 2008) users will be able to check for plugins that are registered with us and download/install them directly into Protege.
+Users are able to check for plugins that are registered with us and download/install them directly into Protege.
 Enabling this for your plugin is very simple and should massively increase your number of users.
@@ Line 54: / Line 52: @@
 === Advertising your plugin on this wiki ===
-If you have developed a plug-in for Protege-OWL 4.0 and you would like to contribute it to the community, follow the following steps:
+If you have developed a plug-in for Protege, and you would like to contribute it to the community, follow the following steps:
 * Click the [[Special:FormStart/Plugin|New Plugin Link]].  You may want to right click and choose a new window.
 * Choose a name for the page  that  discusses the new plugin (e.g. "Sub Ontology Tab").
@@ Line 61: / Line 59: @@
 * Fill in the other fields and save.
 * Click the create new version and use the naming convention described.  Without this step the plugin will not show up in the plugin list below.
-* Make the plugin compatible with "Protege-OWL 4.0".
+* Make the plugin compatible with "Protege-OWL 4.0" or the version it is compatible with.
 * When you are done save the page and make sure that your plugin shows up on the [[Protege-OWL_4.2 |4.x version of the Protege-OWL editor]] page.  It seems for some reason this page often does not update for a while so you may need to come back later.
 Some useful links when adding a plugin page to the wiki are the following:
@@ Line 68: / Line 66: @@
 * [http://protegewiki.stanford.edu/index.php/Category:Person Person Category] lists the people who are known to this ontology.
-== Core Protege 4.x ==
+== Core Protege ==
-Many code contributions can be factored into plugins and this is our preferred route as it keeps the core light and minimises risk. However, sometimes changes have to be made to the core.
+Many code contributions can be factored into plugins and this is our preferred route as it keeps the core light and minimizes risk. However, sometimes changes have to be made to the core.
 === Code submissions ===
-We have a number of people that contribute to the general codebase of Protege 4.x. The overall responsibility of the core application has been split over several groups in several locations for quite some time (so it is sometimes difficult to even define the current P4 team).
+If you would like to submit a contribution to the protege core codebase, please fork the code on [https://github.com/protegeproject/protege github], and submit a pull request.
-It is essential that the codebase remains as stable as possible, and we currently have no official code review or otherwise official scheme for dealing with contributions to the core - everything is assessed case-by-case. However, we will always consider ideas, so please contact us if you have a particular proposal.
+You can find the codebase for the core of Protege, and many of the plugins that we maintain on github:
-also see: [[Protege4DevDocs#Working_with_the_Protege_source_code|Documentation for Protege 4.x developers]]
+Also see: [[Protege4DevDocs#Working_with_the_Protege_source_code|Documentation for Protege 4.x developers]]
 === Bug reports ===

@@ Line 62: / Line 62: @@
 * Click the create new version and use the naming convention described.  Without this step the plugin will not show up in the plugin list below.
 * Make the plugin compatible with "Protege-OWL 4.0".
-* When you are done save the page and make sure that your plugin shows up on the [[Protege-OWL_4.0 |4.x version of the Protege-OWL editor]] page.  It seems for some reason this page often does not update for a while so you may need to come back later.
+* When you are done save the page and make sure that your plugin shows up on the [[Protege-OWL_4.2 |4.x version of the Protege-OWL editor]] page.  It seems for some reason this page often does not update for a while so you may need to come back later.
 Some useful links when adding a plugin page to the wiki are the following:
 * [http://protegewiki.stanford.edu/index.php/Category:Organization Organization Category] shows all the types of organizations that are currently known.  There are some duplicates already.