SRL Archive - Reflection (Archive)

So, it was discussed, and now it is done.

We are officially on GitHub now!

What this means to you, the end users:

1. You no longer will get the newest changes from the SvN repository.
2. If you want to develop, you can very easily! Git is a much better environment for new users to develop.
3. Easier release packages available.

The new repository is located here: https://github.com/SRL/srl-reflection

If you want to develop, please feel free to fork the repository and submit changes as pull requests!

I will work on some documentation on the latter.

Cheers,
Nava2

Perhaps this should be in the SRL group instead of Nava2?

Won't the SVN still be updated with the git-svn-id (and hence won't make too major of a difference to end-users)?

From: Wizzup?
Perhaps this should be in the SRL group instead of Nava2?

Thats what I was thinking as well. :)

I cannot do that though, I need you to.

From: Wizzup?
Perhaps this should be in the SRL group instead of Nava2?

Didn't know we had an SRL group. Made an SRLReflection group o.o
Just add us to SRL :P (unless someone disagrees).

From: pyroryan
Didn't know we had an SRL group. Made an SRLReflection group o.o
Just add us to SRL :P (unless someone disagrees).

Nah, the point is that we keep the SRL group small, then every submits pull requests to the organisation. :)

Its the right step towards amalgamating the SRL and Reflection projects.

From: Nava2
Nah, the point is that we keep the SRL group small, then every submits pull requests to the organisation. :)

Its the right step towards amalgamating the SRL and Reflection projects.

amalgamating = big word :O
Plain person language please.

From: pyroryan
amalgamating = big word :O
Plain person language please.

Combining! :)

Do I need to do anything different now to update reflection now? Or can I just use simba's built-in updater?

The updater will need to be updated. That will involve updating the URL.

E: I will do that later, if someone wants to beat me to it: https://github.com/Nava2/srl-reflection/tarball/master

From: Harry
Won't the SVN still be updated with the git-svn-id (and hence won't make too major of a difference to end-users)?

Please don't ignore this question. I am pretty sure it works this way for SRL opendev, so why not for Reflection too?… End user should not need to change anything and SVN should continue to work, no?!

From: Harry
Please don't ignore this question. I am pretty sure it works this way for SRL opendev, so why not for Reflection too?… End user should not need to change anything and SVN should continue to work, no?!

SRL opendev doesn't use git.. Its mirrored there, but we commit via SvN. This is the opposite, so I'm not sure.

Ya, the svn can still be used for checking out.

From: mormonman
Ya, the svn can still be used for checking out.

I'm not maintaining both, thats not the point.

pyro has been committing to the SVN.

From: Nava2
I'm not maintaining both, thats not the point.

pyro has been committing to the SVN.

That is why Harry is suggesting what he is? So you need not to maintain the repo.

From: Sex
That is why Harry is suggesting what he is? So you need not to maintain the repo.

Its a waste of time, effort and computing power to maintain both.

True. Was just saying.
I don't think anyone other than developers actually checkout from the repo anymore. They just use the snapshots/tarballs that are downloaded with the updater. So yeah actually, I do agree SVN should be phased out :p.

From: Nava2
I'm not maintaining both, thats not the point.

pyro has been committing to the SVN.

Because I didn't know how to use GIT. Still don't, working out the details of it as I go along.

does this mean that i will no longer have an auto updater in simba for my reflection, aka "GitHub?"

From: donkey60000
does this mean that i will no longer have an auto updater in simba for my reflection, aka "GitHub?"

You will. The link in the updater will just need to be changed. I'm sure someone can post an updated extension.

Coh3n, the link doesn't have to be changed. :p
I just have to change something on my server.

From: Wizzup?
Coh3n, the link doesn't have to be changed. :p
I just have to change something on my server.

Lol, for some reason I'm not surprised. :p

I feel like Wizzup was already prepared for this.. :P

@pyro – don't worry, it wasn't a shot at you. I was just pointing it out. :)

From: Wizzup?
Coh3n, the link doesn't have to be changed. :p
I just have to change something on my server.

Woot woot! (: wizzups a pro.

So is the extension working yet? People are mentioning on my script that even when the extension says they've been updated, the script isn't getting IDs properly. This is obviously some kind of bug in reflection or it isn't updating right. Unless the IDs for all fishing objects just randomly changed.

Added https://github.com/SRL/srl-reflection

I've changed the updater link so it works with the new repository.

HOWEVER, the subversion repository is at 245 commits, whereas the git repository is at 243 commits. So once the git repo sees a few more commits, people will actually get auto updates again. (>245)

You can probably fix this for yourself by forcing a reflection update. (Simba 0.96 can do this, AFAIK)

The git repos should be up to date. I committed some of pyro's SvN commits to the git repos.

Just curious, does pyroryan not have direct access to the git repo? I don't know that much about git, but it would probably make updating for end-users quicker if pyroryan had access to publish his new hooks there.

From: Harry
Just curious, does pyroryan not have direct access to the git repo? I don't know that much about git, but it would probably make updating for end-users quicker if pyroryan had access to publish his new hooks there.

He doesn't.

From: Harry
Just curious, does pyroryan not have direct access to the git repo? I don't know that much about git, but it would probably make updating for end-users quicker if pyroryan had access to publish his new hooks there.

The point of git is to allow people to take things from others. With Hooks etc, if you require the bleeding edge version of things, perhaps pull from some of the devs and merge it into your personal repos rather than keeping the main one.

Something should be done a bit better for hooks though.. I'm trying to think of a better option. I wonder if using an external webpage might be a good call.. or perhaps a wiki.

The SRL repository will only be accessed by those in the organization, AKA developers. We do need some other developers to help out with the merges though. I am quite busy. I am usually able to manage pull requests every night, so its not a huge lag, but it is still there. I try my best and I am sorry.

We are not currently using git like we should be either. The way it is supposed to be used is by committing to personal repositories regularly for testing and usage, then you open pull requests for big things or when you finish what you are working on. I need to write up some documentation, but I do not have enough time for it right now.. :(

From: mormonman
He doesn't.

And he will not at this time, see the comments above.

I have access to push/pull, so I can accept pull requests. And I finally got my ssh sorted out.

Edit: hooks updated now harry.

sorry new to this, well i used to use this a long time ago, but it still says hooks outdated.. just wondering if its updated yet. i see someone has said something about it but it just wont let me.

It may take a while for the Simba updater to pick up the latest hooks. (Usually an hour)

Could TRiLeZ get commit access?

Could trilez not talk about himself in the third person? Its kinda weird