but like @RiccardoBlb said, some parts might be under different licenses.
it might be solved with additional descriptive text as additional licenses, right. if provided.
TLDR legal is an excellent template if youāre willing to put in that extra effort.
Caution using an open text field for license. If the site grows large and some day you want to be able to filter or sort by license (āshow me everything I can use and leave the other stuff outā), the last thing you want to deal with is 1,000 free-text entered licenses which may be misspelled, non-existent, or super-rare. Youāll never be able to filter by that field.
If it turns out to be a big issue and contributors want more licenses on the siteās list (assuming there isnāt just a single license), they can always be added based on popular demand.
If different parts of an asset are under a different license, it would need to be explained clearly, or otherwise break the asset up into two listings. I suppose this opens up the need for multiple-license selection, which is a bit of a pain, but it guarantees youāll be able to filter/categorize later on.
To cover the āI wanna special licenseā open-text case, optionally there could be a ācustomā license type. But thatās a mess and possibly a maintenance/review headache Iād not encourage.
So my advice is, start out with draconian rules/policy (within reason), and only loosen up from there if you see a need. If you start out wild-west, itās hard going back.
5 Likes
I think Iāve found a good middle-ground. You choose what you want and it gives you a list of licenses that are compatible with them. Itās not legal advice (and will be stated as such) but I think itās better to have one than not. It still needs a little bit of work (assets vs code as @sgold pointed out) but I think itās about as much as I can do for the topic.
10 Likes
I think most artwork assets like models, images, sound clips, etc. are usually licensed under some of Creative Commons licenses.
2 Likes
I didnāt want to get into it after writing a few walls of text myself, but yes CCās a more typical starting point than source code project licenses like BSD-3.
@jayfella A license selector like posted above would be very cool, but honestly Iād suggest keeping this as simple as you can. We donāt want you getting burned out working on tangential stuff before anythingās operational. Can always be upgraded later. Personally Iād be fine with a simple dropdown list of licenses you (or everyone here) hand-picked, maybe with a description shown for convenience.
I know you can say itās not legal advice and so on, but it might be a bit too much hand holding in the short term. Longer term itās a fine visionāitāll make the site look more mature. For now itād be fine if you linked to an appropriate license selector, if thereās even a need for that.
Iāve already done the licensing stuff. I wonāt keep posting screenshots but you select a source code license and an asset license. In the description under the license title it has a link to a license chooser in a separate page.
Everything is going pretty well. My primary concern is ORM. There are three types of asset (free/paid/contribute) with three separate states (potential/unapproved, live assets, amendments) and I have to do the groundwork now or Iāll lose the database structure and data if I do it later. Itās nothing I canāt deal with but yeahā¦ brain teaser. All the rest is just leg-work; conforming to standards, URL hierarchyās, etc. boring, tedious but nice when itās done.
1 Like
Cool, sounds perfect. 
Yeah, good luck with the old ORM junk. I usually āoutsourceā that stuff these daysā¦ databases = boring!
Just an update as to whatās happening over the next few days:
I havent used Patreon/Payoneer before, so Iām unclear as to how long it takes for the funds to reach me. As far as Iām aware Patreon releases funds on the 5th of every month. I believe itās 3-5 working days for Payoneer to transfer it to my bank. Once the funds are available Iāll purchase the hosting and a SSL certificate. It may take a day or two to get things up and running properly on the server. So at a guess, assuming these time-scales are valid it will be around the 12th July that the website will be online.
For the first month registration will be disabled. Patreon sponsors will recieve login details via email. All public pages will be visible to the public, they just wonāt be able to register and login.
Iām hoping that it will be available to everybody the following month, I do believe personally that it will be ready by then.
Everything is going as planned so far. Itās been tough, but itās coming along very nicely
12 Likes
So is the long term idea to build this into the SDK to allow for adding plugins and things to projects?
1 Like
It seems like that would be the natural flow of its future. There are so many hurdles to jump before we get there, though. I would very much like to see the day it does.
1 Like
The payment process takes a few hours but is same-day. The server has been purchased and is being configured. As Iām sure you understand it takes a little while to get everything together, but Iāve got it up and running with a SSL certificate. Just need to go over everything twice to make sure I havenāt missed anything. Details to patreons will be sent in the next few days. Thank you again for your sponsorship 
6 Likes
The website is now live and available to view. Registration is currently disabled. Patreon sponsors will recieve details later today or tomorrow.
This is a preliminary stage. Hopefully over the next few weeks any issues will be ironed out and the public will be allowed to register.
If you experience a āmaintenanceā page, itās just me updating the codebase. Itās usually back up within a minute or three.
12 Likes
It is looking good @jayfella!
2 Likes
Looks pretty cool! The only feedback I have was that I was a little confused at first that clicking on the images wouldnāt open the store page. It took me a minute to realize it was trying to drag through the assets.
Ah. I can fix that I think. Iāll make the whole box clickable instead of just the title. 
Thanks for the feedback
also i think there should be some field to mark if it will be JME 3 or JME 4 (when jme4 will be already in development). it might be added as some required TAG too.
This might just be a WIP detail yet to be finished, but I feel like it would look nicer if the background and theme were more like the forum colors. Maybe using the darker and lighter shades of grey here. For some reason the plain black/white gradient reminds me of āstock photoā or āexampleā websites.
Iām not sure about the background gradient itself, although it might work better if it used the forumās light/dark grey colors. The light-blue accent color used here is also nice (the whole theme is really), and that would be cool to see used too.
(Referring to #383838, #222222, and #6A86BB. Maybe the yellow #E6BE02 also.)
I am very much a functional programmer. I am definitely not an artist or designer. I know my strengths and they do not lie in art. I would really appreciate some help from someone in that field. Maybe a mock-up in photoshop or something - thatās how I usually get them - and I can work from that.
1 Like
Looks pretty cool!
Regarding reviews and ratings: 10 max stars seem a bit excessive. 5 max stars would probably easier to tell apart at a glance, since right now I have to manually go and count them. Seems like this is what Iām thinking about: The Magical Number Seven, Plus or Minus Two - Wikipedia
1 Like
Also, in mobile view, the arrows for scrolling the showcased items seem to prefer the left side:
