/Rant ON
I definitely feel ant when he said it's BS (can't find his so-called guide for dummies either)... I can't understand anything at all, after forking there are a billion options and it's just ridiculously unclear.
Also... https://github.com/elkarte/Elkarte/blob/development/CONTRIBUTING.md I'm either dumb or this is overly-techy, which makes it even harder, as I have to manually look up every single line for what it means! I know you'd like more contributors, well perhaps you may be improving the "how to do it" thing, because despite being able to do something with the code, that ugly interface got on my nerves after wasting an hour trying to understand it.
/Rant OFF
Please, consider it, I'd rather spend time to contribute rather than to figure out that $#!@ interface.
Fair enough, could get there after reading the help.
By clicking on where, for example? I can't see any "New branch" button. If you point me here: https://github.com/Kunena/Kunena-Forum/wiki/Create-a-new-branch-with-git-and-manage-branches and tell me to follow a similar nightmare just to do that, I will tell you good luck with that.
Didn't know the main language was Arabian... I know it's for a command line, but perhaps tell me where I should be throwing that into?
I don't even know where my "master" branch would be, let alone do the above, and I am not sure about what it means anyways.
Yeah yeah no problem on that one. Usual blah blah that needs to be followed :)
...
What?
...What does this mean? Like create a branch named "Theme" if I want to do theme fixes and a "Source" branch if I want to touch sources or what?
O.o a branch for every commit..?!
What?
Console commands again, but where to put them? After what? What do they do exactly?
Fair enough.. The rest is crazy complicated while this is almost Cpt Obvious ;D
PR to WHAT? You have multiple branches as well and never stated which one I should pick, if at all.
The above is the kind of ideal instructions that should be given...
Yeah the commit tab, see, here you state where I should be going.
Same.
Nearly Cpt Obvious part 2, but still good to mention it ;)
Yeah... If in a parallel world I managed to get here.
Like the current patch? In this case, 1.0.6? So I should fork that one and throw PR at it or at other branches?
This is Arabian again, maybe ahrasis knows what it means...
It's the world of GitHub! Go with the flow, and try things out.
You'll get used to it enough to at least get done what need to.
May take time, but it'll grow on you a bit. XD
So far, the only thing that grew is frustration, and I have quite enough stressing things on my own. If I want to actively contribute, at least it needs not to be stressing like this, I need to know exactly what to do.
Seen many things that can be improved theme-wise and I could help, but it goes with the old saying "Help me to help you" thingy.
Also, sorry if it sounds a bit angry (don't mean to be rude to anyone, at all, other than that """interface"""), try to remember back in the days when you started to use that site, then imagine yourself trying to follow that guide, and tell me how you'd feel.
Yeah I did realize there is also the application, I can understand even less, whether I need to use it or not...
Well; I believe there are two ways from the desktop computer. One is with a DOS box, which I think will use the commands that you have referred to in your earlier post. The second way is with the Windows application which is a GUI that interfaces GitHub.
I am taking baby steps so I did the Hello Word method first. :) I will probably go to the Windows GUI application next. I don't think I need to think any harder for doing a commit than what is necessary. I am not that smart. :)
Yeah I would be just like "You want to commit? Press this, here and there, in X order", it'd be fine enough, but otherwise nope, like I said I don't want to get mad about it, it should be a pleasure/fun/relaxing instead, otherwise there is no point.
Reminds me of my problems with Transifex. :-[
Interesting, I found Transifex quite straightforward. Minds are different I guess, something very hard for one, can be easy for the other and viceversa :)
Apparently you don't. :P
git is a command-line tool (there are some GUI built on top), you have to download a git client and use it.
If it is Arabic (I think the English equivalent is Greek ;)) to you... well, it's almost like CSS to me then. :P
Anyway, you download a client, you install it, you clone the repository on your own computer (and here we'll have to dig further once you get there) and do everything else.
http://bfy.tw/4GUb
That's English knowledge (actually it's not very different from the Italian "granulare"), not git. :P
Anyway, it means: better do a lot of (consistent) commits of 10 lines each, rather than a single one with 10,000 changed lines.
In theory, if you create a branch to work on the ban system you do not commit something related to the mentions in the same branch, you finish working on the "feature/fix", then create a new branch and work on something different (at least in theory, but that's just a guideline I do not follow all the times O:-)).
A branch for any series or related commits.
Flavio, git is a tool. It's a tool like SVN was and CVS before SVN.
Unfortunately, all of them have a learning curve. Some find more comfortable one, others find more comfortable another one.
We picked git because... well, it is among the most used version control systems (if not the most used) and for sure the most advanced and (probably) developed.
You should also consider that CONTRIBUTING.md is not intended as a fully fledged guide to the use of git, let alone github. It's a summary of the workflow, and it also assumes you are kind of familiar with git and some of its terminology.
That said, from what I read, I feel you are confusing git with github: the first is a version control software, the latter is a website that provides space/tools for git-based repositories with some more or less basic actions that can be performed on the repository directly from the webinterface.
Personal experience:
I started working with SVN when I first get the dev badge at sm.org and never liked it. It was a pain in the plumbers crack having to pull before being able to commit and all the messes about not being able to work on it without a server in the background, and so on. I dealt with it because this was the tool chosen by the project.
When I had the opportunity to chose the tool I wanted to use, I picked the one that looked better to me. Oddly enough, to me, git is 1000 times better and easier (although being slightly less easy to grasp at the beginning) than SVN.
SVN doesn't even have a web-based GUI like Github, you have to do everything on your own computer, the best you can hope to is have an SVN client with a kind of nice UI. From that on you have to do your homework to make it work.
Yeah, I know my post reads something like RTFM, but that's how I tend to do things... :P
Of course if you have a specific problem feel free to ask, but if the question is "how does it work" then... well... O:-)
Still liked it, althought it was sort of rtfm you actually clarified some points, thanks. Will have a look, slowly.
I've seen tons of things that could be improved css-wise and since it's my strongest field I feel I can easily help :)
Lol, I am not so sure about github myself but I was using the english version all the time.
That latter is the path I took. Worked for me but my needs at the moment are simple and I am learning. I simply did a copy from Notepad++ and pasted that into the file. Simple .... like me. ;D
Well, I tried the program and it doesn't even work because it can't even clone the repository, and I have no idea why. I give up with this fudge nuggets, best of luck with GitHub, sorry but I am not going to spend another minute trying to figure out this crap.
Thank you regardless for trying to help - locking as I don't even want to talk about it anymore.