Topic: Changes to development

[Niko]

SMF Arcade development will be soon moved to Github (my other mods will follow).

This is simply because I'm trying to get others more involved in this project. (I haven't had much time/interest to work on arcade lately).

This applies only to 2.5 and 2.6. 2.0 won't be moved.

[Skhilled]

Is this site moving there or just coding development?

[Niko]

Just coding.

[Skhilled]

Ah! Thanks for the heads up.

[mcsignanddesign]

Ok  ..... In english please ....

"GitHub is the best way to collaborate with others. Fork, send pull requests and manage all your public and private git repositories."

It sounds like to me that Niko is just giving them the code, so they can do the coding their way, to keep it an ongoing open source code ? But yet, there is a price !!

I have no idea what GitHub is or does ... but that may be the biggest Question of it all, How is Github better that people coding from this site?

[Skhilled]

I think he needs other people to do it for him and/or help him cause he does not have the time to devote to it nor has much interest in it any more.

(I haven't had much time/interest to work on arcade lately).

First, he has to find others willing to help at GitHub. There have been coders here asking to help over the years but he has refused their help. I'm not sure how GitHub is going to be any better but I guess we'll have to wait and see.

[Niko]

I think he needs other people to do it for him and/or help him cause he does not have the time to devote to it nor has much interest in it any more.

(I haven't had much time/interest to work on arcade lately).

First, he has to find others willing to help at GitHub. There have been coders here asking to help over the years but he has refused their help. I'm not sure how GitHub is going to be any better but I guess we'll have to wait and see.

Github makes it easier for others to take part since code is available to everyone and is up to date. Ofcourse this would be possible with self hosted solutions too, but it would be same issue as with current SVN, my upload bw is too slow for multiple users.

[Niko]

Github project can be found at: https://github.com/nikop/SMF-Arcade/

[fwitt]

registered an account, followed Niko and the arcade project.

will try and remember to wander around when I'm more awake.

[fwitt]

Made my first attempt at a bug fix https://github.com/nikop/SMF-Arcade/pull/1

fixes the bug on issue tracker http://smfarcade.info/forum/index.php?issue=479.0

simple small change to see if I have worked out how to use github correctly

[Skhilled]

Now to see if it get implemented and how long before another upgrade.

[fwitt]

I think it will take more than just the one minor bug fix to trigger the next upgrade.

I picked something simple to do as I was running through githubs tutorial.

[Skhilled]

Yeah, I know.

Hopefully, it will get things rolling.

[fwitt]

Made my first attempt at a bug fix https://github.com/nikop/SMF-Arcade/pull/1

fixes the bug on issue tracker http://smfarcade.info/forum/index.php?issue=479.0

simple small change to see if I have worked out how to use github correctly

Niko pulled it into the main repository the day after i posted it, i didn't pick up on the change till today. I also changed the wrong branch meant to fix it in 2.5 but fixed it in the development (2.6) branch and cant currently spot how to push it to the 2.5 branch or indeed make changes to the 2.5 branch. So obviously missed something somewhere.

[fwitt]

finally found time to work out what I did wrong last time and have pushed to correct branch this time.

think I now have the (basic) idea of how github works.

If Underdog doesn't object I'm going to test this new found knowledge by trying to create a branch to match his unofficial version and see if I can push the bug fixes from that into the main branches.

Once I have the bug fixes into 2.5 I'll put it out to the beta team. New features are better going into the development (2.6) branch of code.

If anyone can think of any other bugfixes that need to go into the 2.5 code point me to either the post or the issue tracker for the relevant item in the issue tracker. Bugs that someone has a solution for first as that should make the merges easier to do that way round.