Page 1 of 1

Community repo for themes and plugins

Posted: 10 Nov 2013, 21:01
by lightonflux
Hi there,

it would be great if ttrss had an community repo where people can upload their plugins/themes.

Here my idea of an implemantation:

Users can go to option and click a checkbox (button) that says "activate community repo" then they see a disclaimer (data loss etc) and then the plugin sections has a new category called "community plugins".

Then it works as expected:

1. The user clicks on a plugin
2. clicks activate
3. then ttrss pulls it from the repo and activates it
4. it can be used


On the repo site:

The community repo is a git repo on github or similar. People can send a pull request to add their plugin / theme to ttrss.

To get a plugin accepted there will be some rules:

* plugin / theme has to be open source (OSI/FSF complaint licenses and CC)
* needs a LICENSE file or license as comment if only one script
* has to be stable
* needs description and image (themes), name of author and version

Then when a pull request is send people from the community look over it. If everything is okay someone with the rights will accept the pull rewuest. It will be in the repo and people can access the plugins/themes if they want.

What are your opinions on my idea?

Re: Community repo for themes and plugins

Posted: 10 Nov 2013, 21:05
by fox
No shit. Ever heard about github?

>What are your opinions on my idea?

I for one can't wait to deal with this wall of text of yours because making a topic on the subforum linking to the github repo is somehow not enough.

Re: Community repo for themes and plugins

Posted: 10 Nov 2013, 21:24
by lightonflux
My point is that users will not have to go to forum and search through other walls of text just to get the information that the plugin is incompatible with the newest api.

It would improve usability if users could

* activate the repo
* and active a plugin

instead of the effortful task of

* going to the website/wiki (first time user)
* into the forum, then the riight sub forum
* then search for plugins, reading walls of text to see if something is(in) compatibily with X
* download an archive
* decomppress the archive
* upload it (if they don't work via ssh on the server)
* then activate it in ttrss GUI or config file

And don't forget that they have to look for updates every few month.

[I know you can do cron + git pull, but not all hosters provide cron or git and not every plugin dev provides a git repo.]

Re: Community repo for themes and plugins

Posted: 10 Nov 2013, 22:06
by fox
oh no the effort of forum posting

it's a shame some manage to overcome this monumental obstacle, not pointing fingers or anything ofc

Re: Community repo for themes and plugins

Posted: 10 Nov 2013, 23:35
by LifeWOutMilk
lightonflux wrote:not all hosters provide cron or git

This kind of kills your entire idea doesn't it?

Re: Community repo for themes and plugins

Posted: 11 Nov 2013, 13:22
by fox
OP, tbf, it's not like anyone is exactly stopping you from making such a site. Unless you are purely an idea man, of course.

Re: Community repo for themes and plugins

Posted: 11 Nov 2013, 13:45
by lightonflux
LifeWOutMilk wrote:This kind of kills your entire idea doesn't it?


No, cron is not needed, since the user will trigger action (initial install) if he activates the plugin. And updates can initiated like feed updates (several methods).

Git is not needed for download by the user, but nice for managing the repo.

ttrss would download the files via a GET HTTP-request (low level) (curl/wget if activated or similar) like you do now when you download a plugin from the forum or a github page or when ttrss gets a feed.