SRL Archive - General

Plans:

Simba compatability
Switching to GIT
Getting SRL Members involved
Coordinating the next part of the MSI
Tweaking MSI

Getting Members involved
– Typing out content
—- How to use MSI
—- How to help build MSI

Switching to GIT
– MSI SLs switch first
– Members keep on using tortoise
– Evenually we tell members about GIT

Simba Compatability
– Done by SLs ?
– Or Simba devs?
– Or general Simba supporters?

Tweaking MSI
– (I just noticed we need a section devoted to proggies and bugs and so on…)
– SRL Members + SLs tweaking and testing

Coordinating the next part
– Deciding on exactly what and how
– Who will be scripting this? How will we give Members something to do?

New SLs
– These will come in eventually, depending on current SL activity and Members activity.






Any other plans? Any thoughts on what should be done first, or in which order these should be done?

I typed it out in an order that seems sensible to me. Just so you know that's what I'd suggest :p

~RM

From: RM

Coordinating the next part
– Deciding on exactly what and how
– Who will be scripting this? How will we give Members something to do?

I thought we all kind of already agreed on a VEM for the next project? As far as giving members something to do, they can just post there thoughts/functions in the MSI SVN forum. Similar to what we do with the SRL SVN forum.

From: RM

New SLs
– These will come in eventually, depending on current SL activity and Members activity.

I think we can probably chill on that for a while. The last 2 or 3 SL's added haven't done a single thing from what I can see. The original SL's are the only ones with any work committed at all. Correct me if I'm wrong on that though.


I'm sure SL's can handle the Simba compatibility issue as well, though, I guess we will see when we go to do it.

From: NCDS
I thought we all kind of already agreed on a VEM for the next project? As far as giving members something to do, they can just post there thoughts/functions in the MSI SVN forum. Similar to what we do with the SRL SVN forum.

They still need to know what is needed ;)

I think we can probably chill on that for a while. The last 2 or 3 SL's added haven't done a single thing from what I can see. The original SL's are the only ones with any work committed at all. Correct me if I'm wrong on that though.

Naum and marpis weren't on the original team. But yes, I do agree we can chill, however it will be part of the future, certainly ;)

I'm sure SL's can handle the Simba compatibility issue as well, though, I guess we will see when we go to do it.

Guess so

~RM

From: Rasta Magician

Switching to GIT
– MSI SLs switch first
– Members keep on using tortoise
– Evenually we tell members about GIT

Members keep using SVN? Since they won't have write access, I'm assuming you mean they'll use it to download MSI until we have made the full transfer to git? If so, we'd still have to update the SVN in the meantime. I've never used git, but it shouldn't take much to move other than the moving of file, committing, and updating links.

From: Rasta Magician

Tweaking MSI
– (I just noticed we need a section devoted to proggies and bugs and so on…)
– SRL Members + SLs tweaking and testing

Coordinating the next part
– Deciding on exactly what and how
– Who will be scripting this? How will we give Members something to do?

See what I said below from NCDS's quote.

From: Rasta Magician

Any other plans? Any thoughts on what should be done first, or in which order these should be done?

Coming back to git, I don't really see the advantage of switching after we release. We would have to learn a couple new commands, so what? I would rather release with what we're going to use forever, then switch shortly after release. Seems logical to me, but there's probably a good reason why we haven't (aren't) switched yet. I think we should go:

• Switch to GIT/Simba compatibility
• Get the members involved
• Tweaking/testing
• Coordinating the next project

From: NCDS
I thought we all kind of already agreed on a VEM for the next project? As far as giving members something to do, they can just post there thoughts/functions in the MSI SVN forum. Similar to what we do with the SRL SVN forum.

Why don't we have a sticky in each skill's forum outlining what needs to be done for the current projects for that skill? We could also have it show who's working on which part so we don't have 5 people doing the same thing (unless they're working together).

From: NCDS

I'm sure SL's can handle the Simba compatibility issue as well, though, I guess we will see when we go to do it.

There isn't going to be much to change until we move to SRL 5. Having the Simba.simb file included is SRL already takes care of most of the different functions.

GIT isn't my top priority, nor even close to it. Best I can tell GIT is only more beneficial because you can commit offline (if someone could explain to me the rest of the upsides I'd like to know them). I think our first and foremost priority should be getting members involved, and scripting correctly when they are involved. Last thing we need is SL's having to rewrite code to standardize it.

Also, about the next projects. Moving one project at a time might be unappealing for members if they don't wish to work on the current script in progress. Although it might spread us a bit thin, I would suggest two new projects to move forward with, the VEM as one and a suggested one via members, their idea's with our direction should help to keep people interested. However, we could also just scratch VEM and start with a members chosen script. IMO that's the best way to get them hooked in and involved.

From: Blumblebee

Also, about the next projects. Moving one project at a time might be unappealing for members if they don't wish to work on the current script in progress. Although it might spread us a bit thin, I would suggest two new projects to move forward with, the VEM as one and a suggested one via members, their idea's with our direction should help to keep people interested. However, we could also just scratch VEM and start with a members chosen script. IMO that's the best way to get them hooked in and involved.

Or perhaps expand the woodcutter to more locations, as well as start on the VEM. That way people at least have a choice if they are truly against one. Leaving the woodcutter as we have it seems somewhat lame honestly :redface:
Wasn't the original plan to cover all the Varrock woodcutting locations, then do mining and other skills, but stay in Varrock?

Although, like you said, between the 4 or 5 of us that actually do anything, we may be a bit short handed for something like that.

From: Coh3n

Why don't we have a sticky in each skill's forum outlining what needs to be done for the current projects for that skill? We could also have it show who's working on which part so we don't have 5 people doing the same thing (unless they're working together).

I like that.

from msn:

yup, but that means that everyone (members) would have to switch to git as well to download the script
they're not used to git, therefore, reluctance to use it to download
plus installing git, getting it to work, etc

~RM

Internet failed and so I only saw the other posts now.

Blum, check the new thread I made about git. You might see the advantages of switching to it there.

As for what to do.. I agree with having a bit of several projects…

We have a propper hybrid walking system to complete. I suspect a few will be interested in that.

We have a lot to add-on to the woodcutter.

We have a lot to do in varrock, and we can indeed check what the members wish to do.

And we have the miner, which we already agreed on. So yeah, that might stretch us a little bit thin, but we can support more actively only 2 or so of the choices.

The woodcutter shouldn't be too much trouble. And the hybrid walking is no priority, although very cool.

I think we can easily enough support all 4, with emphasis on the miner and the member's choice.

~RM

From: Rasta Magician

The woodcutter shouldn't be too much trouble. And the hybrid walking is no priority, although very cool.

I think we can easily enough support all 4, with emphasis on the miner and the member's choice.

~RM

I think the hybrid walking needs to be improved. I wasn't able to test it much because the hooks kept breaking, but the reflection points need to be made closer to where the color points are meant to be. I think sometimes it would say that the color walking failed when it didn't. The color points are suppose to click in one area, and I don't think the reflection points are in the same area.

From: Coh3n
I think the hybrid walking needs to be improved. I wasn't able to test it much because the hooks kept breaking, but the reflection points need to be made closer to where the color points are meant to be. I think sometimes it would say that the color walking failed when it didn't. The color points are suppose to click in one area, and I don't think the reflection points are in the same area.

We'll need reflection for that…

I meant the actual system.

The gathering of colors by the script to then fix the color walk and etc.

~RM

From: Rasta Magician
We'll need reflection for that…

I meant the actual system.

The gathering of colors by the script to then fix the color walk and etc.

~RM

Yeah I know. I think TriLez has posted the post recent hooks. If I get time I can see if they work and maybe remake the paths.

We should probably start a thread about planning the color gathering information and how it would work. Maybe introduce that to the members and get their input?