Well, on our plans, first and foremost is to foster sharing. That must include not only software developers that love SCM, but also the hobbyist that managed to get something cool and say “Gee, this is cool, why not share it?” without having to ask himself "Now, where should i put it? how to let others know about it? should i make some package? installation instructions?.. "
To reach there, I’m tinkering with the Mios Marketplace, ideally making it bidirectional. Once you have something on your Vera, you should be able to publish it right from there, without bothering with packaging and install procedure. After all, you already have done it!
Now, if a plugin is popular, it will grow and evolve, likely forked too. For this a SCM is a lot of help, especially a distributed one (like Git). But it also needs some web pages (like a wiki), a ticket system… etc.
My first thougt (already mentioned it) was using Trac ([url=http://trac.edgewall.org/]http://trac.edgewall.org/[/url]) but it seems inadecuate for a multi-project environment. Almost the only alternative is Redmine ([url=http://www.redmine.org/]http://www.redmine.org/[/url]), but still no consensus on it.
A different possibility is Fossil ([url=http://www.fossil-scm.org/]http://www.fossil-scm.org/[/url]), it applies the ‘Distributed SCM’ concept not only to the code management; but also to the wiki, documentation and bug tracking… seems pretty amazing. Unfortunately, it replaces your SCM, so you have to install it to use it… a no-no these days. Unless it were preinstalled in the Vera box, and you interact with it locally, and the Vera box synchronizes with everybody else that also have your plugin… a weird and powerful concept, but somewhat further into the future.
current plan:
-
first, just some wiki pages and a forum channel. Things move from there to the MIOS marketplace manually on request from the contributors. If you need real SCM, please use GitHub, GoogleCode, BitBucket, or something like that. On each ‘releasable’ version, just put a note in the forum and/or email us to update the marketplace.
-
in a month or two, a web application (RedMine or similar), with integrated SCM (likely SVN and Git). At this step, we plan to make the Marketplace auto-update from the SCM, probably from a ‘release’ branch, or by a predefined tag
If we decide to go with the ‘publish from your Vera’ idea, it would be integrated with Redmine, or whatever we’re using.
About the “make it or we’re moving” thing… well, I don’t think it’s a totally bad thing. at least for a while. we don’t have a publicly writable SCM, so If you want one, you have to use some other service. Once we have our own, you’re free to choose if you want to migrate to ours, or stay there. It’s even possible (but i can’t promise it yet) that we could make the marketplace ‘follow’ some branch on external SCMs. I don’t see this a ‘desertion’.
I’ll put some extra steam on the Redmine evaluation. If anybody here has any comments on this, please share.