@DaveHiggins I might add another degree. But not before October. First I have to remember what having a life feels like. Enjoy summer. Read. Write code for FUN for a change ^^
Ok wow there are 18 people in the gitlab group now? #pcode #practicecoding
What's the etiquette on #Github projects, do I fork even if I probably won't contribute any changes, or do I just copy/download and then fork later if I happen to find something I think I can fix/add?
All I want to do right now is look at the code for #Tusky and perhaps build my own version. So is forking still the way to go, or just take a copy of the code?
@TQ It's like: I posted a question/opened an Issue and now everyone can discuss it. This is a "yes" 🐹
@TQ :) I thought it would help if someone just started to do it, changes are always possible.
But I should go and do other things now :D
Dear #practicecoding #pcode people,
please have a look at the Issues in the firststeps project on gitlab. (Join the pcode group first: https://gitlab.com/pcode).
Issues are the place to discuss all our issues, obviously ^^
@TQ Ok now you can do it yourself ^^
@TQ sure!
Just tell me which users I should assign Owner rights to (everyone I guess?)
I just made this group. We don't need to use it, but we could ^^
We could use #pcode instead of #practicecoding? Because all the typing ^^
@vfrmedia There kinds of people are everywhere in tech world so I wouldn't be surprised. I think a group on gitlab is best, because we can have private and public projects there. So people can decide which one they prefer for their different projects that might come out of this. @TQ @ekaitz_zarraga
@ekaitz_zarraga Yes, private repositories were my argument for gitlab. Just thought I was the only one who cared ^^
@TQ I don't want this to take forever so I'm ok with github, but still prefer gitlab.
oh and tea, please! very queer and autistic. disability. fibre. they-pronouns.
not much tech-related tooting but feelings and everything.
I like tea but: http://ko-fi.com/A674QB4