Carrying on from this repo.

[ghost]

Hay ya. I have been working a lot with b3 and echelon and because of this I have manually been going though and fixing bugs I find and other things like that. I mostly do webdesign but if you are up for it I will fork this repository and I will add all of the bug fixes and a new skin I made.

Just asking seeing as the last update was over 3 years ago I think. :)

[WickedShell]

Yeah I got roped into working on Echelon2 originally, all I wanted to do was make it succeed in installing and got convinced to do more work on it. But I basically ran out of steam on it, and as you've noted haven't worked on it in awhile. (In part since I no longer admin any game servers).

You are definitely welcome to fork and fix the theme and bugs! There were/are a lot of layout bugs, which is something I'm not very familiar with working on, and found extremely frustrating. I'm sure someone working on echelon v2 would be appreciated within the B3 community as Echelon v2 offers a number of features that V1 doesn't but is also very broken in some ways.

[ghost]

Awesome. Okay. Well that's great. I have already got alot of bugs sorted out with things and a new ish design planned.

I have seen a lot of different people have the echelon respiratory what one would you suggest I fork or is your the most up to date?

[WickedShell]

I haven't tested any of the other ones. It looks like a couple people have made changes specific to their website/usage. I really haven't tested them, or talked to the people who created them for the most part so I can't really steer you for that.

[ghost]

Once I have forked and commit a list of changes would I need to go over the forums for b3 and request they update the download?

[WickedShell]

Not at all, if you're improving it and fixing bugs then that should definitely be what people are pointed at. (As I'm sure you're aware I'm not the original author by any means, and I'm only linked as I was fixing things, and the project had been dead and abandoned at the time. (Much as it is now).

[ghost]

Okay cool. Well I have forked it and I am going to be pushing changes to my version all the time. When I think my version is stable enough I will create a pull request over to you. A lot of things will change so yeah :P Unless you want me to just to keep pushing changes to my version and running it like that and then directing the guys over at b3 to my github repository.

[WickedShell]

I'd probably say that it makes more sense for you to keep it going on your repository, and have the B3 side of things point at your github. If you're the one making changes and developing it makes more sense, as it will let the issue tracker be correct/current there. I can't see me find timing to resume working on this any time soon.

[ghost]

Okay sounds good :) thanks for all the help.

[wassie]

hey AokMikey, did you manage any progress yet with bug fixing? If you need someone to test things with you, I'll be happy to support. Not as a programming guy, just a guy that likes to help!

[ghost]

wassie commented 4 hours ago hey AokMikey, did you manage any progress yet with bug fixing? If you need someone to test things with you, I'll be happy to support. Not as a programming guy, just a guy that likes to help!

I have ditched this project a little. I have reviewed the base code and it is hmm. Bad. Not be offend anyone here. I am working on a new system at the moment for my community but its being built with a lot of different systems within that. When I am done with it I will branch the "Echelon" part of it out and remove the other systems from it. Then push it open sourced and allow others to help with the work on it.

[WickedShell]

No offense taken here. This is a significant part of why I stopped working on it as there where large structural problems, and it was outside my primary interests and skills, I originally picked up working on it just because I wanted to get the installer to work to try it out :)

On Mon, Feb 22, 2016 at 12:17 PM, Michael notifications@github.com wrote:

wassie commented 4 hours ago hey AokMikey, did you manage any progress yet with bug fixing? If you need someone to test things with you, I'll be happy to support. Not as a programming guy, just a guy that likes to help!

I have ditched this project a little. I have reviewed the base code and it is hmm. Bad. Not be offend anyone here. I am working on a new system at the moment for my community but its being built with a lot of different systems within that. When I am done with it I will branch the "Echelon" part of it out and remove the other systems from it. Then push it open sourced and allow others to help with the work on it.

— Reply to this email directly or view it on GitHub https://github.com/WickedShell/echelon/issues/49#issuecomment-187328257.

[wassie]

ok, I do understand that other things matter more. But is there any chance to get some issues fixed for the people that are still using Echelon? I really would appreciate that. I think that guys like you with big programming experiance good get those issues fixed. but of course it take some time. one of you interested in fix some things for me? if it would help, I'm willing to pay a small amount for it.

[WickedShell]

At this point I just don't have time to take it on unfortunately.

[ghost]

@wassie You are welcome to start tickets over on my repo if you want and I will address them but its not my top priority at the moment.

@WickedShell I've not forked this repo but instead i've cloned it. with reference back to this one for a more stable version. I can add you to the contributors if you ever come back to this project :) Hope it is all okay with you. ( My repo ). If you are happy with it then I would appreciate a link to the new repo on your readme if at all possible? :)

[WickedShell]

@AoKMiKeY I'd say that forking has more sense/working off the existing commit tree, as that preserves the commiter/author history. Most of the code here came before I started working on it for example, and there are one off contributions from others, the nice thing about the git history is that it preserves all the contributions that have happened.

[wassie]

@AoKMiKeY ok, I will do that. Did your repo allready had any improvement or is it still the same version (v2.0b2)?

[ghost]

@wassie its currently the same but I would not suggest using it. I will be pushing an update some time today to make it work again but keep the the releases for a working

@WickedShell I know of a little git hack / work around and I will do that to put all the old git history back into my repo. I just needed to clear some specific bits but. But I do agree with you. The main reason that I did what I did was being I do not intend to be working on this for a huge amount of time before I Ctr+A > Del the whole system and start from scratch with a little bit of a rebrand too. Mainly because I already have some of the base work for this ready.

update: I have added an archive branch that is a merge from the version 2. I have also added a contributor list to the readme for version two and the master branch. Like I said. I plan on scrapping a lot of the work so the contributors will need to be changed for the new version anyway.

[MichaelHillcox]

@WickedShell do you see emails to this account? Wicked.Shell.Scripts@gmail.com Oh, yeah, this is AoKMiKeY but I'm moving away from that name.