sublimator wrote:I'm not really following you here Artee. You think it's too hard for a non programmer?
Do you think that "svn update http://sublime...
. is a natural way to determine what was changed in plugins/configuration since last time?
Most software I've ever seen use simpler pattern: revision and release notes.
sublimator wrote:__author__ and __version__ I can do if it will make you happy (though version control has that inbuilt ) but I don't particularly like massive docstrings. __author__ and __version__ won't solve any problems in and of themselves though.
Yes I agree with you but since Sublime use Python, some features can be done using pythonic way
According to docstrings - it was only a proposal due to the fact that a lot of plugins will be provided as a single file.
sublimator wrote:You want a package index like PyPi?
Yes and no
Compare the following screens:http://pypi.python.org/pypi/Pylons/0.9.7
The first contains a lot of usefull information about plugin - the second is completely useless (I apologize for a choice
sublimator wrote:PyPi is built upon a lot of setuptools/distutils infrastructure that simply isn't applicable unfortunately.
PyPi was an idea how it can be accomplished.
I think that we need simpler system because community is respectively smaller.
sublimator wrote:Who is going to do that job?
It depends on who have access to edit such information
I think that simple wiki page or phpBB forum is too static to do that (and doesn't have an integration with SVN or Git).
Maybe CMS like Plone or other simple solution? Hosting is cheap, e.g. Webfaction account - 10$ per year
If it will be based on the Python I'm ready to help.
I know, that above information maybe is related to systems with big community and lot of plugins but AFAIK Sublime claims to be a piece of software entirely based on plugins so IMHO should provide proper platform for this.