Skip to content
monsieurh edited this page Mar 21, 2017 · 3 revisions

Adding a plugin

Before adding a plugin, ask yourself the following questions.

Does the plugin benefit to end users ?

eOS is famous for being accessible to non-tech savvy users out of the box. Let's keep it that way and not bloat ePIT with cryptic stuff. Any techie like you is not afraid of typing apt install <package-name> if needed.

Is the plugin installing a software from the AppCenter ?

Yes...

If it is, we should discuss the following point : why should the user install through ePIT rather than the AppCenter ? Remember : the goal is not to replace the AppCenter. However, exceptions exist.

...and I think elementary should ship it out of the box

Let's discuss it, if we agree on this as a community, great, let's use this !

No

Great. Either through adding the right PPA, downloading a .deb file or compiling from source, that'll be a nice addition to ePIT !

I'm done coding !

Create a submit a pull request. If you're unfamiliar with it, read the useful github documentation on pull requests

Contact

You can hangout out, ask questions and else on irc, Gitter and Reddit/r/elementaryos