Plugin Repository

[JWH_Matthew]

1.Does such repository need to have a stand alone domain ?
Wouldn't it be better to use a subdomain, for example plugins.get-simple.info, to have everything under one flag ?

I would say yea it needs its own domain, but I will talk to Chris about doing something with a sub domain to forward to the actual domain.

2. Downloading a plugin shouldn't force visitor to log in. Unless it's a simple method of preventing from download bots (transfer leechers) or other crap.

I think we need to require a login, this will just give us a little more control over things.

3. You came up with couple nice thoughts, like notifying users about new version of a plugin.
I'd go with advanced version. If somebody wants to get info about new version of certain plugin, he would just have to check "I want to get info about future updates of this plugin" and then download.
If user is logged, his mail would be automatically added to plugin's mailing list.
If not logged in, he would be asked to enter his e-mail address.

I love the idea about the check box.

Plugins have to be approved by admins/mods who are webdevelopers. Other way plugins would contain dangerous code, and who knows what else.

I agree, we wouldn't necessary have to be very strict about approval; but this would allow us to create guidelines for plugins
to ensure they are not screwing up the core.

4. Things which have definitely to be added:
- download counter - this would definitely tickle every developer's ego Yes!
- comments , but this feature should lead to dedicated thread on forum. Not really sure how I like this,
maybe we could do a FAQ where users could submit questions, and the dev could choose to publish them. We
could also do a ranking system like rate with up to 5 starts type dill
- plugin changelog This would be nice.
- possibility to download older version of plugin, if it doesn't contain any vulnerabilities (or were fixed) I am not sure this is a great idea due to the amount of storage it may require. But we could always look into it!
- additional translations of plugins to other languages. If plugin doesn't use a language file, then there should be a possibility to download a translated plugin (should be up to community to translate most popular plugins)This again could become an issue with storage. I am not sure the best way to do this as it is needed.
- good installation guide, not only as a .txt file inside plugin archive I think we could implement javascript tabs that would allow for one tab to be screenshots one tab to be installation and so on.
- screenshots We may have to limit this to like 4 or 5 due to storage.
- nightly builds - if those lazy devs won't drop the development ;This could be a storage issue to.)

This is all great, I am going to get a list of things that will be included. No one has contacted me yet willing to help out!

Another thing we need to add is as developers you could choose to set up a individual account or a company account that
would allow you to place company links and logos.