[QUOTE=HeyBanditoz;50348451]where are you hosting your code at?[/QUOTE]
Private Git server
[QUOTE=Strideynet;50363564]Private Git server[/QUOTE]
Why not just make the code public? The original project was public, and everyone would benefit.
[QUOTE=HeyBanditoz;50365582]Why not just make the code public? The original project was public, and everyone would benefit.[/QUOTE]
There is a good chance that when I am finished and happy with everything I will release the source on github. Personally I'm not a fan of github and my dedicated box runs a mighty fine git server that works very well for me. I don't want to seem like a twat but I like working in small teams and during development I like to keep a careful eye over everything. Based on the nonactivity on all of the forks except for mine over the past few months it is clear nobody else really wants/has the time to contribute so there is nothing for me to gain by using github. If somebody here can prove they adhere to good standards and are willing to use my task tracker etc I may consider allowing them to develop with me during the alpha stages. When it is done I will happily maintain it but then I will let the open source spirit continue to add features but unfortunately, because I like my code neat and I like to know was going on, during my alpha and beta sprint I will not be allowing random people to send pull requests.
Feel free to dumb me if you disagree with my opinion
[QUOTE=Strideynet;50443097]There is a good chance that when I am finished and happy with everything I will release the source on github. Personally I'm not a fan of github and my dedicated box runs a mighty fine git server that works very well for me. I don't want to seem like a twat but I like working in small teams and during development I like to keep a careful eye over everything. Based on the nonactivity on all of the forks except for mine over the past few months it is clear nobody else really wants/has the time to contribute so there is nothing for me to gain by using github. If somebody here can prove they adhere to good standards and are willing to use my task tracker etc I may consider allowing them to develop with me during the alpha stages. When it is done I will happily maintain it but then I will let the open source spirit continue to add features but unfortunately, because I like my code neat and I like to know was going on, during my alpha and beta sprint I will not be allowing random people to send pull requests.
Feel free to dumb me if you disagree with my opinion[/QUOTE]
I don't program much myself, but won't pushing the code to GitHub speed up development? It will allow you to reach a greater number of users, and some could help bug test.
[QUOTE=HeyBanditoz;50446994]I don't program much myself, but won't pushing the code to GitHub speed up development? It will allow you to reach a greater number of users, and some could help bug test.[/QUOTE]
it'll also most likely bring in more devs to look over the code and fix simple shit that you might over-look. it's pretty silly to not just have the branch open for everyone, even more so when you're gonna release it publicly
[QUOTE=Soren;50447102]it'll also most likely bring in more devs to look over the code and fix simple shit that you might over-look. it's pretty silly to not just have the branch open for everyone, even more so when you're gonna release it publicly[/QUOTE]
I'm quite a silly guy but you have made some good arguments for me to consider. For some reason I get stuck with my existing development patterns which for a long time have just avoided github because it was just so easy to use my own git server and not get stuck with limitations.
There's a pay-it-forward aspect to this as well. You lose absolutely nothing by putting it on Github, and the community gains. Of course, if your intent is to take it closed-source, that's you're right, but it's a completely different discussion that I suspect folks would have some strong opinions on. I'm hopeful you'll move it over to Github. I'd love to see this gamemode regain some vibrancy.
[QUOTE=Buzzkill_HABB;50452971]There's a pay-it-forward aspect to this as well. You lose absolutely nothing by putting it on Github, and the community gains. Of course, if your intent is to take it closed-source, that's you're right, but it's a completely different discussion that I suspect folks would have some strong opinions on. I'm hopeful you'll move it over to Github. I'd love to see this gamemode regain some vibrancy.[/QUOTE]
It may work its way onto github once I get the chance in the next few weeks. You guys have made convincing arguments for it.
In terms of closed source I don't think I would actually be allowed by the license terms. To me it all seems legalese and legaltldr was unclear. Why don't license creators write non buklshit explanations of what it entails haha.
The stablish branch is now found at:
185.38.149.101:27015
It lacks alot of the features I currently have running on the unstable but I wouldnt really like to push the unstable branch at this time as sometimes it just crashes out.
[QUOTE=Strideynet;50453293]It may work its way onto github once I get the chance in the next few weeks. You guys have made convincing arguments for it.
In terms of closed source I don't think I would actually be allowed by the license terms. To me it all seems legalese and legaltldr was unclear. Why don't license creators write non buklshit explanations of what it entails haha.[/QUOTE]
Yea, I mean like it's totally not LGPLV3 or something.... I dunno.
[IMG]http://image.prntscr.com/image/057d3cf22fb3416088db642a3961994c.png[/IMG]
[QUOTE=riekelt;50458439]Yea, I mean like it's totally not LGPLV3 or something.... I dunno.
[IMG]http://image.prntscr.com/image/057d3cf22fb3416088db642a3961994c.png[/IMG][/QUOTE]
I know its LGBP v3 I just have no idea what that entails. Half the licensing discusses libraries because it was designed as a license for open source libraries. I tried the site you linked but I still didn't quite grasp what it means I must do. I.e do I have to give my source whilst I am developing?
[QUOTE=Strideynet;50458549]I know its LGBP v3 I just have no idea what that entails. Half the licensing discusses libraries because it was designed as a license for open source libraries. I tried the site you linked but I still didn't quite grasp what it means I must do. I.e do I have to give my source whilst I am developing?[/QUOTE]
The picture I posted with that message is the LGPLV3 license in TL;DR. So yes, you must disclose the source code.
[QUOTE=Strideynet;50458549]I know its LGBP v3 I just have no idea what that entails.[/QUOTE]
The LGBT v3 license basically gives you the freedom to share with anyone, regardless of which way they want to go - whether that's commercial or open source - but it is semi-viral however, and the rule is that you generally have to share what you've got with everyone - although there is protection available for doing stuff in regard to libraries, for example.
Server needs player but its nice to see it working again
Sorry, you need to Log In to post a reply to this thread.
