Ways To Contribute and Participate

You do not have to just contribute code! There are other ways you can contribute:

  • Communicate - Use the General Slack Channel and this Wiki to communicate with the community
  • Congregate - Attend user groups, conferences, library events, developer meetings - and any other venue where SimplyE libraries and users meet to share information and ideas. If you are a developer (or just interested in developer discussions), join the weekly Library Simplified Developer Meetings. If you are a library manager, you may wish to volunteer for the Library Simplified Monthly call or attend their meetings / online discussions.
  • Test - Download and try out SimplyE; provide bug reports, experiences, feedback. 
  • Develop - Contribute bug fixes, new features, developer cycles. Contributing code is far easier than you might think! See the Code Contribution Guidelines for more details.
  • Translate - Translate the SimplyE user interface into your language.
  • Prototype - The best way to gain support for an idea is to build and share prototype code. If you'd like to share existing prototypes, see the Code Contribution Guidelines for more details.
  • Deploy - Share your experiences in deploying SipmlyE in different organizations and situations, at large and small scales
  • Support - Become active members on the Slack Channel, answer others' queries and help solve their technical problems
  • Experiment - Take the system for a spin, try it out with different types of content and scenarios; tell everyone what you find.
  • Donate content and metadata - To test and experiment withSimplYE, free test collections unencumbered by restrictive usage rights are needed. Contact us via Slack if you have content to donate for testing.
  • Request new features / Share ideas - Is there something that you really need out of SimplyE or isn't working right? Request new features/improvements or report bugs via our Issue Tracker (your Wiki Account also works in the Issue Tracker). You can also vote on existing features, or add your own comments/suggestions. Both of these can help developers decide which issues are the most important to the community. See the below section on How To Contribute Ideas or Suggest New Features for more details.
  • Help Improve Documentation - Our Documentation is now managed directly via a new section of our Wiki: Documentation. Although normal Wiki users cannot edit that area of the Wiki, you can always add comments for additions/changes/suggestions. If you are interested in contributing more formally, volunteer to help via one of the mailing lists, and we can add you to our Documentation Team and provide you with access rights to edit/improve the Documentation directly.
  • Let us know if there's a way we can ease the process of contributing to SimplyE
  • Don't be shy! Contributions don't have to be 100% polished or perfect; no one will think any the less of you. "Share early, share often" is a well-known open source mantra. The sooner you contribute something, the sooner others can help with the polishing, and you no longer have to maintain the customization against the evolving core SimplyE platform, since it will be part of the platform!


Platforms for Contribution and Participation

  • This Wiki - Help making this Wiki a useful, concise and up-to-date information source by
    • supplying content
    • correcting content
    • deleting obsolete content
    • restructuring or otherwise improving content
  • The Slack Channel - Take an active part in the discussion on #General.
    • share your thoughts aboutSimplyE
    • ask questions
    • provide feedback
  • Documentation
    • add comments to existing docs, to help enhance the existing content
    • volunteer to help improve content or otherwise enhance it
  • Library Simplified GitHub - GitHub allows for collaborative & social code development! You can create your own GitHub account (it's free) to get started, and then "fork" our repository to start creating your own modifications (which can be submitted back to us via a GitHub "Pull Request"). For much more information see Development with Git.
  • The Feature/Issue Tracking System (JIRA) (uses same login as Wiki)
    • bug reports
    • feature requests
    • patches
    • add your vote to existing issues, or add your own comments
    • "watch" existing issues (you will receive an email any time a new comment is added or the issue status is updated)
    • volunteer to work on a feature/issue (just add a comment to that issue)


  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.