Sonic 1 Telephone Hack #1.

Markey is currently working on it. So it's only Markey who can work on it. I should have been more specific in the rules.

 

BAMM

Revision 002's done. Who's next for revision 003?

EDIT: Made some adjustments to the text and pylon.

 

Yep! I'll continue it.
Music is my strong point so expect some good music next revision!

 

AverageSonicHacker, wait. A lot of people have already expressed and interest in working on the next revision (In here and on IRC) and I think we also need CaveQuest to confirm who is next to work on it.

 

There is a lot of people who want to work on this and 1st person to grab it was AverageSonicHacker when Markey Finished. Therefor It's his turn.

Anyway the reason of not going out with it was because I didn't get the chance to alert Markey to wait until daytime/morning. So blame it all on me.

EDIT: OK So I noticed that he said that Music was his strongpoint. If he works just on that he could technicly work with someone who codes. Just asking if that's the case tho.

 

If that is the case, I think a public repository is a necessity.

I done it here: https://github.com/CaveQuest/Telephone1
It starts straight from REV002-02, because I do not think the first is necessary at this point.
Apparently it is properly setup to be my first time on Github. I am not sure how different is it to SVN, but if anyone needs to commit/push (or whatever term is the correct) their changes to this, and authorization to the system is indeed necessary, let me know.

EDIT: New link.

 

Thank you for that.

 

While I understand that iApple has tried make things more accessible with GitHub, surely this should have been up to CaveQuest to sort out. I dunno, it seems like someone taking the initiative, but in the wrong way. Another problem is that general access is restricted to that repository. It's supposed to be an open, collaborative project. Also, not everyone knows how to use GitHub, which may restrict some from collaborating.

While having this project on GitHub makes some sense, I thought the point of this project wasn't multiple people having access at the same time, but rather the project be a continuous pass-along, so someone adds a part to it and passes it on until somehow a completed project is made. It just seems like the wrong decision for this sort of project.

 

I think a list of all the members who wish to work on this project should be created. Markey did the first half, and AverageSonicHacker is currently going to work on the project now. I think whoever wishes to work on it next should chime in, then CaveQuest should make a list to keep track of who should go next. From there ASH, should send a copy of the disassembly via PM to the next person on the list so no one else has access to it. And the process should keep repeating until whenever the project is finished. But in the end CaveQuest it's completely up to you on how the project is set up.

 

The problem with making a list, is that it can end up huge, this would only discourage others from wanting to help later on. Additionally, some may take forever to get what they need to get done, done. Some may slack and laze about doing nothing, "holding up the queue" as it were.

I would settle for a "who posts next, gets it" job. It may seem unfair from the standpoint that the person would have to be in the right place at the right time. But on the other hand, no-one is to know when the person will post their finishing part.

The main point? I'm seeing less cons with this method, than with the former.

 

Meanwhile this is discussed...

REV03: New demos for the new level layouts. Fixing the playback system was necessary, so I re-recorded SYZ (because were originally made/tested with the broken system).

DOWNLOAD

Demos for the credits need to be recorded again (unless a new system is made, or other people do it for me).

EDIT: Fixed erroneous rev number =U

 

Uh, you're not supposed to just edit things like that, regardless of your intentions. See, this is why having it on GitHub in this way is a bad idea. No-one but you can edit it, and you're free to make edits to something whenever you wish regardless of the fact that it's A) Not your turn, but AverageSonicHacker's and B) It's pointless fixing demos when those layouts could be edited again in the future. Please, iApple, stop making edits until CaveQuest confirms this is the way he wants the project to go.

 

Seeing as we're going by who's posting things, I'd like to reserve a place. :V

 

I do not see what is wrong. Sure, I forgotten to advise here though, but I went with CaveQuest's statement... and done something simple... as GHZ1 and MZ1's actual layouts are.

 

If you want to use GitHub for a project like this, it has to be in a repository owned by the project leader (CaveQuest), which the person who wants to do something will fork, and then submit a pull request to the main repository, which the project leader will have to approve, so that nobody is pushing commits directly to the main repository.

Pull requests could also be used if an emergency fix needs to be made after someone's turn is over.

 

For this to not screw up lets wait until AverageSonicHacker is done. A list is not a bad idea in the short run but not the long. I suggest we wait until ASH is done.

 

Ok. I am now home. Meaning I will clearify. I am going to wait until ASH is done. Then before he post his revision he will post that he's done and ask for the next person to step forward. (First to get it) instead of posting the Disasm here. After that for example JoenickROS wanna work on it he reply and gives him an email. So he can send the Disasm through Dropbox that way. Let me know what you think of this idea or if we should go the Github way? I will get the ownership of the Github posted earlier if that's the case.

 

I personally think this is a good idea. It stops anyone other than the person editing it from changing anything. I'll work on stuff today so we can get the show on the road quicker. I'll post gain as soon as I finish...

 

It that's a question aimed at everyone, I vote for GitHub. Maybe open an actual poll, so the thread isn't cluttered with vote posts like this.

 

I'll reserve a place here. Remind me when it will be my turn, it won't come soon probably...