I want to help

[rguy]

I am Aleksandar Jovanov.
I am not a very good programer and my git skills are not at best.
I am very bad (read as noob) at 3D graphics,but I am smart so I can learn things fast.
I am not a begginer though.I can respect all coding policies and find my way in docs.I cannot promise to write optimised code.
I do not know MWScript,only c++.

Issues I might be able to fix :
http://bugs.openmw.org/issues/156
http://bugs.openmw.org/issues/81
http://bugs.openmw.org/issues/243

I tend not to respect deadlines and I sometimes just quit doing something for no reason.If someone is interested for me to work on small or medium tasks I will be really glad to join.

I also have a git question.
As far as I got it,this is what a openmw dev has to do :
1.git clone git://github.com/zinnschlag/openmw.git
2.git checkout -b my_edits (or is it git branch my_edits?)
3.do some stuff,git add some stuff,commit some stuff
4.compile (if fails ,git bisect HEAD my_edits)
5.git merge my_edits master
Now I do not know how to send the modifed files to Mr Zini for approval.
Should I send the whole repo or just my new branch?

EDIT 1 : I looked at setup dev environment and found the right git link.

[sirherrbatka]

Nice to meet you.

[sirherrbatka]

our dear admin lgro have problems with internet connection and asked me to post this:

Welcome!

I also have a git question.
As far as I got it,this is what a openmw dev has to do :
1.git clone https://github.com/zinnschlag/openmw.git
2.git checkout -b my_edits (or is it git branch my_edits?)
3.do some stuff,git add some stuff,commit some stuff
4.compile (if fails ,git bisect HEAD my_edits)
5.git merge my_edits master
Now I do not know how to send the modifed files to Mr Zini for approval.
Should I send the whole repo or just my new branch?

• You should create account on GitHub: http://github.com
• next make fork of https://github.com/zinnschlag/openmw repository
• and after that, run git clone from your fork, i.e. git clone [email protected]:<your nickname on github>/openmw.git openmw
• change directory to cloned openmw project: cd openmw
• create feature branch by running - git checkout -b <put here feature name>, i.e: git checkout -b bugfixes
• do some changes, commit them by running: git status (to check what was changed) and git commit
• push your changes to your github fork: git push origin <branch name>
• on github send pull request to Zini

And that's all For details how to use git, and github please read:
http://help.github.com/ and http://progit.org/book/

[Zini]

We have a checklist for new contributors.

About the issues you have linked in your post: Two of them are for 0.15.0 and we aren't really ready for them.

You can try your hands at the item stacking if you want (and also unstacking in one case, see the todo comment in the code). However I am currently working on related code and it would be best, if you can wait until I am finished with that (unless something goes very wrong, later today).

[corristo]

welcome!

[rguy]

Fail.I created a new topic instead of posting an answer here.

I was successfull in forking and commiting changes and reverting them.
When I make some more important changes I will send a pull request.
Just one question remains unanswered.
Should I merge my branch or let Mr Zini do that.
I will also register on the bugtracker now. (FINISHED)

I will seek some easy feature to implement and hopefully you will see my magic at work soon

[Zini]

You can merge my master branch into your topic branch, if you want to. It's generally not required though.

[rguy]

You can merge my master branch into your topic branch, if you want to. It's generally not required though.

Thanks,I will not merge.

[Zini]

Okay. It seems you have started on one of the 0.15.0 issues anyway. I moved it to 0.14.0, since it can be implemented now, even though it will stay completely useless until some other features have been implemented.

I also finished my work on auto equip. You can start working on item stacking any time you like.