I have created a SoapBox Core add-in that I think would be generally useful to the SoapBox Core community and I would like to share it. Is what's the best way for me to put my add-in out there so that other people will find it and use it?
To my knowledge, there is no established repository for add-ins. Though you could always create a codeprojects article on whatever add-in you’ve created and share your work with the broader community that way. You might even drum up some good PR for the project while you’re at it.
What I think would be really cool is if there were a proverbial ‘SoapBox Add-in App Store’ type of things where people could write add-ins and share them with the SoapBox Core community. Of course all add-ins posted there would be under the same general license as SoapBox Core itself and so they would all be free, unlike the app stores.
This type of communal resource is important because there are a lot of ideas out there, like undo/redo functionality, user configuration setup and management, that may not truly belong in SoapBox CORE, but are still generally useful and could benefit other developers. By not adding these types of things to the core, we would be depriving each other of mutual benefits. However, by adding too much stuff to the core we will increase the complexity of the core and hence the overhead associated with learning and using it.
What do you guys think of this idea? I really like it, but I have no idea how to create, manage or host such a beast. If you like the idea and think you know how to actually create such a thing, please leave a comment. I would love you talk to you and try to implement your good idea with you.
answered 19 Oct '10, 22:36
Karl directed me to this question because he thought the NuGet idea might fit in well with the "marketplace" idea. Once you accept that NuGet is an acceptable package format, then you can leverage all of the infrastructure around NuGet. At the base of nuget.org they use Orchard CMS, and as you can see on nuget.org, each package has its own little home page. If you dont want to stand up your own service, I think myget.org provides third party hosting for nuget feeds. As for source code, nuget.exe supports a "-Symbols" parameter that includes much more than just the debugging symbols, it also includes a complete copy of the source. By default this code is sent to symbolsource.org, but the maintainers of that site recently introduced a method for you to host your own symbol server if you like.
I think this is a nicer fit than maintaining your own svn repository for add-ins. Contributors can make their own decision about where/how to host their source control system. You wont have to. If they want to contribute the code to the plug-in store they can do so by using the Symbols option. If they only want to contribute the binaries, they can do that too.
Anyway, I'm not really part of the Soapbox community, so you'll have to evaluate this idea against your own goals and needs. But I promised Karl I'd let you guys know about that blog entry and how it might be useful to your community, and I wanted to make good on that promise (better late than never).
If you like the idea, I'd be happy to help get it off the ground. Karl knows where to find me :)
answered 10 May '12, 22:50