Difference between revisions of "Category:Contribute"

From EPrints Documentation
Jump to: navigation, search
m (update references)
 
Line 2: Line 2:
 
* [[How to write plugins| Write a plugin]]
 
* [[How to write plugins| Write a plugin]]
 
* [[Languages| Translate EPrints into another language]]
 
* [[Languages| Translate EPrints into another language]]
* [http://trac.eprints.org Submit a bug, and or a bugfix]
+
* [https://github.com/eprints/eprints Submit a bug, and or a bugfix]
 
* Make a theme
 
* Make a theme
 +
* Add some [[Unit tests]]
  
With the exception of bugs (which should be submitted to [http://trac.eprints.org trac.eprints.org]) your contributions should be uploaded to [files.eprints.org] where other people can download them and make use of them. If you make something you think other people will find useful it's worth shouting about it on EP-Tech. {{EPrintsTech}}
+
With the exception of bugs (which should be submitted to https://github.com/eprints/eprints) your contributions should be uploaded to https://files.eprints.org or https://bazaar.eprints.org where other people can download them and make use of them. If you make something you think other people will find useful it's worth shouting about it on EP-Tech. {{EPrintsTech}}
  
 
Before you write any code it's worth taking a look at the [[StyleGuide]] that way other EPrints developers and contributors will be able to read and understand your code more easily.
 
Before you write any code it's worth taking a look at the [[StyleGuide]] that way other EPrints developers and contributors will be able to read and understand your code more easily.

Latest revision as of 06:46, 30 August 2018

A lot of people want to know how they can contribute to EPrints. There are a number of easy ways:

With the exception of bugs (which should be submitted to https://github.com/eprints/eprints) your contributions should be uploaded to https://files.eprints.org or https://bazaar.eprints.org where other people can download them and make use of them. If you make something you think other people will find useful it's worth shouting about it on EP-Tech. For free support and discussion about EPrints you can sign up to the EP-Tech here: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech.

Before you write any code it's worth taking a look at the StyleGuide that way other EPrints developers and contributors will be able to read and understand your code more easily.