Sir R. M8gic1an
2010-08-02 12:05:54
'ello there.
Developers and Staff have access to these forums, as you have definitely noticed by now.
The reasoning behind it is very simple:
- The more of them get involved, the more likely the success of MSI is
- Developers have obviously a lot of developing experience and knowledge, and therefore can give a hand & interesting hints, driving MSI to places we hadn't considered. (Pointers, bitwise consts?)
- Staff can always give a hand leading with (basically everything) and can consider ways of helping MSI & using MSI (Boreas - Barebones, etc)
And I'm sure we could think of a few more benefits that go both ways.
Now, my question is: Do we want to give access to Senior Members?
Originally I didn't, so that MSI would build its own identity, rules and people, rather than just being a bunch of SSRLers.
Now, that we already have all this, I see some benefits:
- SSRLs are capable scripters
- SSRLs are capable thinkers
- SSRLs are community driven
And this could come to benefit MSI tremendously. It would also give SSRLs an interesting thing to get involved in.
It is true that they don't NEED access to the private forums to get involved, but the involvement that I would expect coming from SSRLers is more on the high level end, rather than filling in a few script records every now and then.
It would also give the opportunity to other community projects to mix in with MSI.
^ About this, you guys will always have the ultimate say. But there is a lot of potential to try out new technologies" and so on by plucking it into MSI. I've post before a way to allow testing of features without stopping MSI from running properly, by using defines.
After all, it's this sort of development that makes us (SRL) stronger, and this as a community project is seeming to reach a level where it can bring sub-projects in.
We'd need to be very careful about that, so we don't drift off course, but it is definitely a possibility.
So the question is: Allow SSRLers to view these forums - or not?
~RM
Developers and Staff have access to these forums, as you have definitely noticed by now.
The reasoning behind it is very simple:
- The more of them get involved, the more likely the success of MSI is
- Developers have obviously a lot of developing experience and knowledge, and therefore can give a hand & interesting hints, driving MSI to places we hadn't considered. (Pointers, bitwise consts?)
- Staff can always give a hand leading with (basically everything) and can consider ways of helping MSI & using MSI (Boreas - Barebones, etc)
And I'm sure we could think of a few more benefits that go both ways.
Now, my question is: Do we want to give access to Senior Members?
Originally I didn't, so that MSI would build its own identity, rules and people, rather than just being a bunch of SSRLers.
Now, that we already have all this, I see some benefits:
- SSRLs are capable scripters
- SSRLs are capable thinkers
- SSRLs are community driven
And this could come to benefit MSI tremendously. It would also give SSRLs an interesting thing to get involved in.
It is true that they don't NEED access to the private forums to get involved, but the involvement that I would expect coming from SSRLers is more on the high level end, rather than filling in a few script records every now and then.
It would also give the opportunity to other community projects to mix in with MSI.
^ About this, you guys will always have the ultimate say. But there is a lot of potential to try out new technologies" and so on by plucking it into MSI. I've post before a way to allow testing of features without stopping MSI from running properly, by using defines.
After all, it's this sort of development that makes us (SRL) stronger, and this as a community project is seeming to reach a level where it can bring sub-projects in.
We'd need to be very careful about that, so we don't drift off course, but it is definitely a possibility.
So the question is: Allow SSRLers to view these forums - or not?
~RM