Stop Post on Elgg 'Alternative Plugin Repo' thread

19 views
Skip to first unread message

Shouvik

unread,
May 5, 2011, 11:58:37 AM5/5/11
to Elgg Plugin Repository
I think it is pretty much clear that Elgg will never have any
provision to host non-GPL plugins on its plugin repository. So, I
think rather than making effort to make them understand the fact,
let's concentrate on the development on this united venture of the
Elgg developers.

Ismayil Khayredinov

unread,
May 5, 2011, 12:06:53 PM5/5/11
to elgg-plugin...@googlegroups.com
Any idea on how big we are thinking? It would be good to have an estimate on the number of non-GPL plugins out there...

Do we also know how many Elgg developers are there?
--
Ismayil Khayredinov
freelance professional
events • web services • translations

ismayil.k...@gmail.com
ismayil.khayredinov
00 420 724 384 468

ismayil_khayredinov.vcf

Team Webgalli

unread,
May 5, 2011, 1:27:24 PM5/5/11
to Elgg Plugin Repository
As far as we know, there are only a few commercial developers for
elgg. At a maximum it will be 15 including us. Of these only 4 or 5
have got a plugin repo of their own. So it will be better to bring
them all together, than to get scattered.
We thought of this Idea of having a common commercial plugin repo for
elgg last December. And as we talked by our skype conversation, we
have got the resource too for it. But there happened some Government
restrictions in Paypal payments to India @https://www.paypal-apac.com/
india/ and thats why we keep the project pending. Now, recently this
discussion started. We can launch the common repo if needed. The repo
will be similar to http://webgalli.com/pg/groups/ . We are planning of
modifying the groups plugin than to develop a new plugin. Let us know
if you have any questions or suggestions.

On May 5, 9:06 pm, Ismayil Khayredinov <ismayil.khayredi...@gmail.com>
wrote:
> Any idea on how big we are thinking? It would be good to have an
> estimate on the number of non-GPL plugins out there...
>
> Do we also know how many Elgg developers are there?
>
> On 05.05.2011 17:58, Shouvik wrote:
>
> > I think it is pretty much clear that Elgg will never have any
> > provision to host non-GPL plugins on its plugin repository. So, I
> > think rather than making effort to make them understand the fact,
> > let's concentrate on the development on this united venture of the
> > Elgg developers.
>
> --
> Ismayil Khayredinov
> freelance professional
> events . web services . translations
>
> <mailto:ismayil.khayredi...@gmail.com> ismayil.khayredi...@gmail.com
> <skype:ismayil.khayredinov?chat> ismayil.khayredinov
> <skype:+420774693672begin_of_the_skype_highlighting            +420774693672      end_of_the_skype_highlighting?call>00 420 724 384 468begin_of_the_skype_highlighting            00 420 724 384 468      end_of_the_skype_highlighting
> <http://cz.linkedin.com/in/ismayilkhayredinov>
> <http://twitter.com/ihayredinov>
> <http://www.blogger.com/profile/16533597828768665576>
> <http://www.last.fm/user/ihayredinov>
> <http://www.facebook.com/ismayil.khayredinov>
>
>  ismayil_khayredinov.vcf
> < 1KViewDownload
Message has been deleted

Shouvik

unread,
May 5, 2011, 2:21:43 PM5/5/11
to Elgg Plugin Repository
I think 15 developers are enough for a good base of sophisticated
plugins.

Being in India, I have the very same problem too, Paypal restriction.
Wordpress has an e-commerce possibility but it is not meant for multi-
user interface.

Maybe, it could be as simple as using the groups plugin and adding a
form field to put the button code generated from Paypal, Dhrup and I
had been discussing.

Team Webgalli

unread,
May 5, 2011, 2:23:49 PM5/5/11
to Elgg Plugin Repository
@social Web : Thanks for the comments.

We think the design wont matter. See our elgg communites GPL repo. Who
cares of the design? We think it will be better if we use the default
elgg layout as because people are more familar with that. Anybody can
develop a new design to convert an elgg install similar to
themeforest. Butthe functionality is more important. So we should give
the importance to functionality first.

On May 5, 10:46 pm, SocialWeb Team <milocke...@gmail.com> wrote:
> Exactly, we are few. Even though we got the people selling plugins/
> themes we need a good PR so people can find us and new developers can
> join us.
>
> We have our own shop, pretty basic but we have it and had sales. The
> main problem is the payment gateway. We have like tons of commercial
> themes just sitting there on our desktop because of payment
> limitations.
>
> I like webgalli's repo, don't get me wrong, but I was thinking a
> design/layout something like... themeforest

Team Webgalli

unread,
May 5, 2011, 2:28:36 PM5/5/11
to Elgg Plugin Repository
The first problem in front of us is single site licence. We and Vasco
are sellings plugins with a single licence option. Would like to know
your ideas on how to manage this situation, when we are going to be
global. In our case we are using our own algorithm for locking the
plugins. So We need to develop a common algorithm for this, when we go
global. Any thoughts?
Message has been deleted

Mike (vazco)

unread,
May 6, 2011, 2:46:43 AM5/6/11
to Elgg Plugin Repository
Webgalli, I don't think websit needs a global security mechanism. Each
developer can take care of locking their own plugins. I think we
should rather keep things simple now, locking mechanism is a feature I
would see a few iterations ahead, if idea becomes successfull.

On 6 Maj, 01:49, SocialWeb Team <milocke...@gmail.com> wrote:
> Interesting. How do you lock plugins? We never done that, but yes we
> could have a common license (locked) and full license (higher price
> but with full access to source code)
>
> I think we have something here =)

Team Webgalli

unread,
May 6, 2011, 7:31:13 AM5/6/11
to Elgg Plugin Repository
Vasco, the problem is that many of our plugins are single licence
pack. After the user purchase the plugin, he can generate the key for
one time with n the site itself. So no need for the developer to keep
tracking of the payment. User buys the plugin > joins the group >
generate a key themselves.

So we cant host these plugins outside somewhere making it availalbe
with for multiple sites with a single purchase. This will be cheating
to all others who allready purchased single licence.

So lets add a way in the repository, such that the developer can
select whether the plugin should be restricted or not.
Reply all
Reply to author
Forward
0 new messages