A couple of years ago the original OpenSprites project began. It was written in PHP off the back of a discontinued forum package, so about a year later it too was dropped in favour of a new site, built from the ground up in node.js. This new site was titled OpenSprites (Next). It was kept pretty low profile unless you were watching GitHub.

Development of the new site was pretty hot up until September when the weather is sometimes too good to miss (UK here), and then it dropped of completely. The project has always been run by a team, but it is difficult to organise one efficiently online when everyone has other commitments, so it ended up with a few committed members carrying the project.

I'm here to see if I can drum up any interest in completing the project, old team members or new. The site runs just fine on a server, but that costs me money, so I want to hear some positive noises before I start it again. The original site always drew some positive noises from the community, so it'd be great to actually get it out there.

Obviously a newcomer would need to revise the repository and issues to understand what's going on. Unfortunately, I've not done much coding in a long while, but I can point to things that might help. I'm thinking that having members needn't be the case anymore, instead with anyone chipping and coordinating their efforts on Gitter.

Again, this is only to see if there is interest, so just take a glance over the repository and comment if you'd like to help. Thanks.

Awesome! Can't wait until this takes off! (Sadly I dont have windows or Mac or Linux to try this)

DeleteThisAcount wrote:

Awesome! Can't wait until this takes off! (Sadly I dont have windows or Mac or Linux to try this)

What OS *do* you have?

novice27b wrote:

DeleteThisAcount wrote:

Awesome! Can't wait until this takes off! (Sadly I dont have windows or Mac or Linux to try this)

What OS *do* you have?

DOS!!!



or maybe a chromebook which he does not count as Linux as it is locked down

I might be ale to help. Later

herohamp wrote:

novice27b wrote:

DeleteThisAcount wrote:

Awesome! Can't wait until this takes off! (Sadly I dont have windows or Mac or Linux to try this)

What OS *do* you have?

DOS!!!



or maybe a chromebook which he does not count as Linux as it is locked down

Guess what.. YOUR RIGHT!!!!

I'm poor I can't afford a window! I'm getting a switch first

herohamp wrote:

novice27b wrote:

DeleteThisAcount wrote:

Awesome! Can't wait until this takes off! (Sadly I dont have windows or Mac or Linux to try this)

What OS *do* you have?

DOS!!!



or maybe a chromebook which he does not count as Linux as it is locked down

How about crosh?

Blaze349 wrote:

herohamp wrote:

novice27b wrote:

DeleteThisAcount wrote:

Awesome! Can't wait until this takes off! (Sadly I dont have windows or Mac or Linux to try this)

What OS *do* you have?

DOS!!!



or maybe a chromebook which he does not count as Linux as it is locked down

How about crosh?

im not ready to go into dev mode yet

cheeseeater wrote:

I'm here to see if I can drum up any interest in completing the project, old team members or new.

Well yeah, I'm (still) interested! I just don't know how to properly do it and not have it die in a month/5 months/etc

Any ideas on why OS-Origin and OS-Next just died? OS-Origin went pretty far from scratch, and OS-Next at least got somewhat close to catching up, IIRC. Just disinterest, boredom with the project?

(edit: formatting)

_nix wrote:

cheeseeater wrote:

I'm here to see if I can drum up any interest in completing the project, old team members or new.

Well yeah, I'm (still) interested! I just don't know how to properly do it and not have it die in a month/5 months/etc

Any ideas on why OS-Origin and OS-Next just died? OS-Origin went pretty far from scratch, and OS-Next at least got somewhat close to catching up, IIRC. Just disinterest, boredom with the project?

(edit: formatting)

It think it was down to my bad organisation. Because I wanted to hold some parts off until a later stage it left some hands idle. Additionally, when you're communicating through GH Issues and Gitter it's difficult to know when to contribute with interfering. I think that lead to the two factors you mention.

_nix wrote:

cheeseeater wrote:

I'm here to see if I can drum up any interest in completing the project, old team members or new.

Well yeah, I'm (still) interested! I just don't know how to properly do it and not have it die in a month/5 months/etc

+1
although please please please try not to allow people without any experience with the technologies we use to just be able to commit to master, because we've seen that happen with many projects on the ATs

nanalan wrote:

_nix wrote:

cheeseeater wrote:

I'm here to see if I can drum up any interest in completing the project, old team members or new.

Well yeah, I'm (still) interested! I just don't know how to properly do it and not have it die in a month/5 months/etc

+1
although please please please try not to allow people without any experience with the technologies we use to just be able to commit to master, because we've seen that happen with many projects on the ATs

Before allowing anyone to commit I think I'll ask to see a working example of previous work.

cheeseeater wrote:

nanalan wrote:

_nix wrote:

cheeseeater wrote:

I'm here to see if I can drum up any interest in completing the project, old team members or new.

Well yeah, I'm (still) interested! I just don't know how to properly do it and not have it die in a month/5 months/etc

+1
although please please please try not to allow people without any experience with the technologies we use to just be able to commit to master, because we've seen that happen with many projects on the ATs

Before allowing anyone to commit I think I'll ask to see a working example of previous work.

Why not only allow PR like on scratch 3.0 where it is required for 2 people to review it

herohamp wrote:

cheeseeater wrote:

nanalan wrote:

_nix wrote:

cheeseeater wrote:

I'm here to see if I can drum up any interest in completing the project, old team members or new.

Well yeah, I'm (still) interested! I just don't know how to properly do it and not have it die in a month/5 months/etc

+1
although please please please try not to allow people without any experience with the technologies we use to just be able to commit to master, because we've seen that happen with many projects on the ATs

Before allowing anyone to commit I think I'll ask to see a working example of previous work.

Why not only allow PR like on scratch 3.0 where it is required for 2 people to review it

That could also be a possible option.

cheeseeater wrote:

herohamp wrote:

cheeseeater wrote:

nanalan wrote:

_nix wrote:

cheeseeater wrote:

I'm here to see if I can drum up any interest in completing the project, old team members or new.

Well yeah, I'm (still) interested! I just don't know how to properly do it and not have it die in a month/5 months/etc

+1
although please please please try not to allow people without any experience with the technologies we use to just be able to commit to master, because we've seen that happen with many projects on the ATs

Before allowing anyone to commit I think I'll ask to see a working example of previous work.

Why not only allow PR like on scratch 3.0 where it is required for 2 people to review it

That could also be a possible option.

I'd be fine with having PRs assigned to me for review

Firedrake969 wrote:

cheeseeater wrote:

herohamp wrote:

cheeseeater wrote:

nanalan wrote:

_nix wrote:

cheeseeater wrote:

I'm here to see if I can drum up any interest in completing the project, old team members or new.

Well yeah, I'm (still) interested! I just don't know how to properly do it and not have it die in a month/5 months/etc

+1
although please please please try not to allow people without any experience with the technologies we use to just be able to commit to master, because we've seen that happen with many projects on the ATs

Before allowing anyone to commit I think I'll ask to see a working example of previous work.

Why not only allow PR like on scratch 3.0 where it is required for 2 people to review it

That could also be a possible option.

I'd be fine with having PRs assigned to me for review

I second this. It's how Liam and I work on Scrap - everything lives in a branch/PR and is reviewed.

Sounds like PRs are the way to go then. If further interest comes around I'll create the PR branch.

herohamp wrote:

novice27b wrote:

DeleteThisAcount wrote:

Awesome! Can't wait until this takes off! (Sadly I dont have windows or Mac or Linux to try this)

What OS *do* you have?

DOS!!!



or maybe a chromebook which he does not count as Linux as it is locked down

I hacked mine with dev mode so i have crosh.
(ctrl + alt + t)

Bump

The domain is set to auto-renew on Apr 16, 2017 and expire on May 16, 2017. Unfortunately I may end up having to let it expire.