Adding Items to the Marketplace

I'm working on a few modules and wondered how to add them to the marketplace here? Also, if I do add some items, how do I get a forum in my profile to support the modules.

Thanks!
updated by @jimmy: 10/14/15 06:25:32AM

That all gets done in a single go. We just need to change your quota to a 3rd party developers quota and you get a bunch of extra stuff:

* documentation section to document how your module works
* blog for blogging about whats going on
* forum to answer user questions
* issue tracker to keep track of bugs 'n stuff.
* payments to track sales (if your modules are not free)

Mind if we check out your modules before release?

Thanks for the info. I have no problem with the JR team or anyone checking over the code for any modules I post. I'm assuming that would be done via a beta channel? I want to also make sure that only the modules I want in the marketplace appear in the marketplace. There are a few modules which are complex and I don't want to be listed at all.

Oh, let me know what I would have to do on my end. Is the marketplace linked to one JR local install? If you want to send me an email to discuss, that's fine.

Also, on a different topic (while I remember) - the Issue Tracker in this site (JR) never shows the current / open issues. I remember with the old JR4 site I could see the current issues / bugs that the JR team was working on. On the new site, the Open Issues tab is blank, the Closed Issues tab last issue was on May 1st - I'm assuming an issue was closed after May 1st. The only tab that seems to be updated is the Feature Requests tab content. Is the Issue Tracker only for accounts above the basic account?

If you have something ready that you want us to check out, send us a note to support at jamroom dot net.

Really just want to check it out to see what its doing and to see that the code doesn't introduce vulnerabilities to the system. Also offer some suggestions on how to handle stuff if we see them.

So far I've seen some alterations that should have been done a different way and the developer just needed to be shown that way existed.

For stuff that you dont want to appear in the marketplace, first thought is dont upload it to the marketplace. You can make it private or just in a beta or private channel if that suits though.

The way the system works is you use the developer module wherever your module is installed at to package it as a .zip file. that part adds all the licenses in to the package. Then you upload it to your profile on jamroom.net. If its marked as stable and is active, people can then see it in their marketplace on their installs.

As for the issue tracker, we tend to do most of the issues as private issues. Its real busy in the issue tracker, but mostly just Brian, Doug, Paul and myself chatting about stuff.

Do you activate the other options on this site once the first module is approved? Does every module have to be approved?

Obviously, you can do what you guys want, but I loved following the bugs on the old site. It's a shame that you guys are keeping that private... especially since it's "open source". If it's "real busy"... developers who want to work with your script should be able to see the issues vs. having to post them in the forum IMO. I can understand not posting critical zero-day bugs, but everything else should be posted so that if a developer runs into something he isn't beating his head trying to figure out what is going wrong IMO

Yes, we ought to use the public issue tracker more, I think we have just got out of the habit!! We'll rectify that


--
Paul Asher - JR Developer and System Import Specialist

Thanks Paul.

I did post a bug there this morning, but them went and fixed it so the issue is now in the closed section - https://www.jamroom.net/the-jamroom-network/tracker/1667/jrlike-not-showing-item-url-in-notification-email


--
Paul Asher - JR Developer and System Import Specialist

Excellent! Now we have to get the other developers working on JR to stop thinking they're working for the NSA.

- we don't think that at all. In fact, we all agreed that we needed to use the public issue tracker more a few months ago. We'll try harder in future


--
Paul Asher - JR Developer and System Import Specialist

I know, just having some fun!


updated by @jimmy: 09/13/15 02:33:45PM