Raised This Month: $165 Target: $400
 41% 

View Poll Results: Should we move away from PHP stack?
No. Continue using the PHP stack. 17 65.38%
Yes. Move away from the PHP stack. 9 34.62%
Voters: 26. You may not vote on this poll

[Meta 2019] Current Direction, Future Goals, and Feedback


Post New Thread Reply   
 
Thread Tools Display Modes
Author Message
RumbleFrog
Great Tester of Whatever
Join Date: Dec 2016
Location: US
Old 10-17-2019 , 13:11   [Meta 2019] Current Direction, Future Goals, and Feedback
Reply With Quote #1

Next Release

Our current direction for SourceBans++ is the release of 1.7.0, which is long due since the last version was well over a year ago.

Since the previous release, there have been hundreds of commits to the repository. Thanks to the numerous contributors to the repository.


The primary objective of 1.7.0 release is to rewrite, stabilize, and fix various backend bugs that crippled the full-extent of usage.

It also means that the frontend template rewrite is pushed back to potentially the next minor semver.

Rewrite

Of course, being there's only so much you can do building on the existing old codebase, a rewrite is almost imminent.

This is where we need your feedback and ideas.

Moving away from PHP

We are looking to move away from the PHP stack to potentially Rust/Golang/Nodejs. However, due to a good majority of the population base using shared hosting, which is limited to PHP, we are not confident that this is a feasible transition for many.

Core Features

One of the many entropies of the original codebase is the utterly bloated core codebase. Hence, it includes features that weren't necessary for the average user but built-into the core.

Our goal for the rewrite is to minimize the amount of code and features within the code. Provide only the essentials but expose a powerful interface for building upon the core.

Related issue: https://github.com/sbpp/sourcebans-p...s-faq/issues/6

Translation and Templating

One of the most significant issues that still reside within v1 is the templating system.

The unnecessary abstraction created by xajax made it quite difficult and tedious to create custom templates/themes; this also hinders the ability to translate the system into another language.

This is on top of the awkward chaining of templates, which made styling difficult.

Plugin-Side of Things

Similar things could be said about the plugin side of things.

While efforts were made during the syntax transition, there are still broken features and entropies.

With that said, we are prepared to rewrite the plugin along with the web panel for SP 1.10+
__________________


Fingerprint: 91CC4E84AE4BFA89F2E431DD462F405E7D61ED35

Reach me @ https://keybase.io/rumblefrog

Github: https://github.com/rumblefrog

RumbleFrog is offline
Exp93
Junior Member
Join Date: Apr 2019
Old 10-17-2019 , 15:51   Re: [Meta 2019] Current Direction, Future Goals, and Feedback
Reply With Quote #2

The contributions have been from many and I think it goes to show how substantial the developer base is for PHP. I am really not convinced it's a good idea and I wholly object to even considering a move to another language. Statistically speaking PHP is the go to language, just take a look at W3 Techs:
https://w3techs.com/technologies/details/pl-php/all/all & https://w3techs.com/technologies/ove...g_language/all

For the reasons you're highlighting also, with regards to host restrictions, it just further reinforces that this is the wrong thing to do.

The core features I think have become far too stretched, the only 2 important things to me about SB++ is:
- Synchronising Bans
- Managing Admin Access

At a push I'd say it's also important to:
- Report Users
- Appeal Bans

I don't really think SB++ best serves as a public-facing panel (with regards to like server stats or public banlists) and this could easily be re-implemented as plugin/extension functionality, with this being said however, are you now possibly considering taking away what has become core to the project, for a long time by a lot of users?

Translation and Templating I don't really have any comments, but either way anything to make it easier to do either of the above activities is surely a good thing... what I'd say would be nice is some sort of embeddable functionality, so you can implement it into existing templates or webpages.

Plugins, I've covered that above already in some respects, otherwise the ability to build on SB++ is surely also a good thing.
Exp93 is offline
RumbleFrog
Great Tester of Whatever
Join Date: Dec 2016
Location: US
Old 10-17-2019 , 16:03   Re: [Meta 2019] Current Direction, Future Goals, and Feedback
Reply With Quote #3

We are also considering a potential rename of the project after the rewrite.

The name "SourceBans" sounds inclusive to only the core ban features, yet we consider admin management and reports as essentials as well.

So a rename is also another thing to consider. But, I'm not certain how the SEO would work out.

.
__________________


Fingerprint: 91CC4E84AE4BFA89F2E431DD462F405E7D61ED35

Reach me @ https://keybase.io/rumblefrog

Github: https://github.com/rumblefrog


Last edited by RumbleFrog; 10-17-2019 at 16:05.
RumbleFrog is offline
Exp93
Junior Member
Join Date: Apr 2019
Old 10-17-2019 , 16:16   Re: [Meta 2019] Current Direction, Future Goals, and Feedback
Reply With Quote #4

Quote:
Originally Posted by RumbleFrog View Post
We are also considering a potential rename of the project after the rewrite.

The name "SourceBans" sounds inclusive to only the core ban features, yet we consider admin management and reports as essentials as well.
I feel that the ++ can have a lot of different meanings, and the extensive - but still core - feature set could be represented in this.

Quote:
Originally Posted by RumbleFrog View Post
So a rename is also another thing to consider. But, I'm not certain how the SEO would work out.
I can definitely say from experience that organic traffic is king, if we can get the word out there, and make people aware, then that will fix itself. To be honest though, I feel like the name won't matter to most, so long as they know how/where to find us. Of course in all of this, you can redirect the domain name(s)?
Exp93 is offline
RumbleFrog
Great Tester of Whatever
Join Date: Dec 2016
Location: US
Old 10-27-2019 , 21:59   Re: [Meta 2019] Current Direction, Future Goals, and Feedback
Reply With Quote #5

Those who voted Yes for moving away, if possible, leave your reasoning as a reply.
__________________


Fingerprint: 91CC4E84AE4BFA89F2E431DD462F405E7D61ED35

Reach me @ https://keybase.io/rumblefrog

Github: https://github.com/rumblefrog

RumbleFrog is offline
anonym93
Junior Member
Join Date: Dec 2013
Location: Romania
Old 11-05-2019 , 07:06   Re: [Meta 2019] Current Direction, Future Goals, and Feedback
Reply With Quote #6

Maybe i'm exaggerating now but I think on Laravel will be more easy to develop and customization and anyway, I hope here is a lot of people who know to work on Laravel
__________________
anonym93 is offline
DigidyDOG
Junior Member
Join Date: Sep 2015
Location: I live in the USA
Old 11-10-2019 , 06:02   Re: [Meta 2019] Current Direction, Future Goals, and Feedback
Reply With Quote #7

All I can think of is moving away from php and something that a lot of shared hosts don't offer will be very detrimental to the project.

Also some feedback, larger communities need the ability to assign the same admin different roles in different servers. So for instance an admin can have mod in one server and admin in another. This was a feature in the original sourcebans and I would like to see it come back.

Anyways I am liking the direction SourceBans is going (however slow) I can't see what this team can bring. Keep up the great work.
DigidyDOG is offline
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 10:15.


Powered by vBulletin®
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Theme made by Freecode