Scratch

jvvg wrote:

SJRCS_011 wrote:

jvvg wrote:

Scratch validation thing: on the new user system, all registrations must be Scratch validated so we don't have any way to store whether old accounts are validated.
Backup code: We can try that. However, I still think that manual backups every few days works. Also, I'm not sure if x10 supports cron jobs, and as the database gets bigger, that would probably have a significant impact on server performance.

yeah, you can do cron jobs every 5 mins (i would think, though, that'd you do every week probably)
and the max execution time is 30 seconds

The other part is that we want to make all of the code work anywhere, in case we have to switch servers.

true, true
When are you guys planning on releasing Mod Share IV?

Well, I'm going to show everybody some pictures before we release it:

User page


Upload page


Project page


Messages

Oh, and, my favorite one  ...

Another announcement: Mod Share IV will be entirely open-source. We will release the code a little after the site is open.

jvvg wrote:

Another announcement: Mod Share IV will be entirely open-source. We will release the code a little after the site is open.

Is it going to have a Git repo?  Cause I'd be interested in playing around with it and modifying things, and if it has a repository, it's a lot easier to import it into Eclipse (yes, I know, it's weird for someone to use Eclipse for php developing, but I like my IDE's to support several things)

Oh, and what license will it be under? (CC, MIT, Apahe, GPL, LGPL, etc)

Last edited by SJRCS_011 (2012-09-18 19:47:43)

SJRCS_011 wrote:

jvvg wrote:

Another announcement: Mod Share IV will be entirely open-source. We will release the code a little after the site is open.

Is it going to have a Git repo?  Cause I'd be interested in playing around with it and modifying things, and if it has a repository, it's a lot easier to import it into Eclipse (yes, I know, it's weird for someone to use Eclipse for php developing, but I like my IDE's to support several things)

Oh, and what license will it be under? (CC, MIT, Apahe, GPL, LGPL, etc)

Yeah, we will probably use Git (hosted on Assembla), and we will probably use the Creative Commons license (I forget which one).

I personally use Notepad++ for PHP developing, because it has an FTP client built in and pretty good syntax highlighting.

I sooo can't wait!  I especially cant wait to see the source!!  You guys should make like you're own license for it like you did for futuresight universal software license

jvvg wrote:

XenoK wrote:

I sooo can't wait!  I especially cant wait to see the source!!  You guys should make like you're own license for it like you did for futuresight universal software license

We're just going to use creative commons (plus a bit of our own).

Here're two CC licenses I'd suggest:

CC-BY-SA What Scratch uses

CC-BY-SA-NC same as scratch, but means you can't use it for commercial purposes without your explicit consent

jvvg wrote:

XenoK wrote:

I sooo can't wait!  I especially cant wait to see the source!!  You guys should make like you're own license for it like you did for futuresight universal software license

We're just going to use creative commons (plus a bit of our own).

Creative commons licenses are not for software.

nXIII wrote:

jvvg wrote:

XenoK wrote:

I sooo can't wait!  I especially cant wait to see the source!!  You guys should make like you're own license for it like you did for futuresight universal software license

We're just going to use creative commons (plus a bit of our own).

Creative commons licenses are not recommended for software.

Fixed

Also, I'd suggest the MIT license, EPL, or maybe the GPL

jvvg wrote:

SJRCS_011 wrote:

nXIII wrote:

Creative commons licenses are not recommended for software.

Fixed

Also, I'd suggest the MIT license, EPL, or maybe the GPL

I'm writing our own. None of the other ones quite seem to fit. Also, I don't like all of the jargon in the other ones. This one will be rather short.

btw, check your email, i sent a contact us request thingy

EDIT: The MIT license is pretty short.
Here:

Copyright (c) <year> <copyright holders>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Personally, I use that for all of my software in terms of licensing.

Last edited by SJRCS_011 (2012-09-20 19:45:44)

jvvg wrote:

Our license.txt file now looks something like this:

*Snip*

Nice wording 

funelephant wrote:

Idea!

Maybe if one of you know how to create apps, you could make a Mobile Mod Share!

there's really no need for it, but I may be willing to work on an Android app for browsing Mod Share projects, much like Bingo's browser.  What do you think, jvvg?
(Also, I'd need some documentation on the API)