Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sourcebans Integration #3

Open
miketorman opened this issue Dec 4, 2015 · 5 comments
Open

Sourcebans Integration #3

miketorman opened this issue Dec 4, 2015 · 5 comments
Assignees

Comments

@miketorman
Copy link

Why hasn't this been officially integrated yet? There is a huge demand for this and as far as I can tell lex's module is outdated. If someone could add completely integrated functionality for sourcebans it would help large community owners who host servers outside of gmod, instead I'm going to have to go hire a coder to figure something out so we can integrate. you guys should seriously consider adding in the functionality.

thanks,
mike

@Nayruden Nayruden changed the title Sourcebans Sourcebans Integration Dec 12, 2015
@Nayruden Nayruden self-assigned this Jan 26, 2016
@60percentCaffeine
Copy link

That's an assigned enhancement. That means that it is in progress, right? Then, when this will be ready?

@bigdogmat
Copy link

"enhancement" is just a tag used on github issues, doesn't mean it's being worked, could just mean it's an idea to look upon. As far as I know I haven't seen any Sourcebans related commits, nor is the main development focused on this verison of ULX currently

@60percentCaffeine
Copy link

@bigdogmat I know that enhancement is a tag, but this is ASSIGNED issue. That's key word there. Thanks for the information!

@bigdogmat
Copy link

bigdogmat commented May 3, 2016

From how I see it Nayruden always gets assigned to framework stuff, while SticklyMan always gets assigned to gui related stuff. Not so much as a "I'm assigning myself because I'm gonna work on it" system, more of a sorting system for saying which code base it'd happen in

@Nayruden
Copy link
Member

Nayruden commented May 3, 2016

@bigdogmat is exactly correct. Task assignment is not an indication of anything other than who "owns" the task, it does not mean it's being worked on. I'm pretty sure you can't see it from the public/normal side of GitHub, but Stickly Man and I stuck this in the "low priority" pipeline on ZenHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants