April 27, 20178 yr I've gathered you all here today, because I want to talk about our lord and saviour; the SDN. The SDN is in a pretty horrible place at the moment and I've already seen Alek trying to take on some of the challenges (read; outdated scripts, official OSBot script) which is awesome! The SDN is still flawed though, and here I am directly referincing to the SDN Requests. I know people who have waited weeks upon weeks getting their SDN requests even looked at and I've got to say; it's honestly really demotivating to have to wait so long to get a script on the SDN - and it's demotivating for all ranks of scripters aswell as new upcoming ones. I will here propose an idea to the SDN management. This is to be discussed, hated or graced upon. Proposed idea (and food for thought) | There will need to be hired new SDN Managers that can manage the SDN requests and update the SDN. Scripter rank 2 or higher can apply. A hired SDN manager will only be able to manage and review scripts for scripters that have the same rank or below. (Ex. Scriper Rank 2 can manage scripts from other Scripter 2's, Scripter 1's and upcoming scripters). Pros: SDN requests will be handled a lot faster It will be more motivating to request SDN uploads Cons: The quality of scripts may decrease if not reviewed by top-tier scripters/developers. Inconsistency in scripts if reviewed by more people I would like to know, what people think of the situation and the proposed idea. This post was mainly written because I see a problem that should be discussed; not so much because I think my idea is the solution. Other solutions and proposals are welcome. Discuss. Edited April 27, 20178 yr by Container
April 27, 20178 yr this went baaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaad last time and that's why alek removed it(them) im pretty sure.
April 27, 20178 yr i think the plebs would get everything wrong. you would need trusted people to manage. and then you would have to manage the managers. i think its a good idea, but i think you would have a damn hard time implementing it
April 27, 20178 yr I suggest @Token to be SDN manager. He is online a lot and wants to do more stuff. Also he barely has any scripts so he its not like hes gonna deny new scripts because they would be a competetion to his
April 27, 20178 yr 3 minutes ago, paper said: i think the plebs would get everything wrong. you would need trusted people to manage. and then you would have to manage the managers. i think its a good idea, but i think you would have a damn hard time implementing it i will manage the managers who manage the sdn who manage the scripters who manage niki manage
April 27, 20178 yr 4 minutes ago, Imateamcape said: last SDN manager @Extreme Scripts ripped khal's code He wasn't the last but yes thats true, the last was @Ericthecmh i think if i remember. Extreme was before him with the name "Divinity" i think.
April 27, 20178 yr This is why we have Scripter Three ranks but the developers decided to stop the line of SDN Managers. Probably for the best, no one scripter should possess such a power. Only one can control the ring.
April 27, 20178 yr Scripters could steal eachothers code, won't recommend using other scripters to check the SDN. I agree that there should be more SDN managers.
April 27, 20178 yr I haven't been much active on osbot before lately, but have you tried an automatic system? That would be much better tbh
April 27, 20178 yr 4 minutes ago, jens4626 said: I haven't been much active on osbot before lately, but have you tried an automatic system? That would be much better tbh Manual code review is definitely for the best, ensures safety in the scripts uploaded.
April 27, 20178 yr This would only work I reckon if the person who did this had no active SDN scripts hence couldn't benefit that much from stealing code. A way to go about this would be to hire someone for the job. But then you may as well just hire another Dev. To be honest I think alek is doing a really good job with what is in place at the moment, and it is clear he is investing lots of time into the client and SDN. It's a difficult topic without a clear solution, and unfortunately I don't think this solves it (or atleast it didn't last time!) -Apa
April 27, 20178 yr looooooooooooooooooooooooooooooooool theres a scripter section for a reason u MUPPET
April 27, 20178 yr Author 1 minute ago, Tom said: looooooooooooooooooooooooooooooooool theres a scripter section for a reason u MUPPET This concerns people that doesn't have access to that section aswell.
Create an account or sign in to comment