search

OpenSprites / OpenSprites-Origin

The original OpenSprites website, written in PHP. Discontinued - remains for historical reasons. See OpenSprites-Next for the new generation of Scratch resource sharing.
MIT License
19 stars 9 forks source link

Do you need a front end developer? #203

Closed QuillzLouis closed 8 years ago

QuillzLouis commented 8 years ago

Hi Louis/QuillzToxic Here, I was wondering if you are after another front end developer, I have taken a course on programming and want to get onto a project to improve my skills

jamesd-uk commented 8 years ago

I'm afraid that you've arrived a little too late; most of our frontend work had already been done!

QuillzLouis commented 8 years ago

What about issue 108?

QuillzLouis commented 8 years ago

And also, just a refresh, why did I get rekicked after you added me back in in issue #137

QuillzLouis commented 8 years ago

As far as I know, I'm still in the project, I just went inactive....

matthewr6 commented 8 years ago

I'm pretty sure being kicked out means being kicked out.

QuillzLouis commented 8 years ago

Actually if you read #137

@The-QullzToxic we removed you because you seriously screwed code up. I know you used the command line thing, and you're new at it, but that's not really an excuse. If you know you're bad at the command line git, you should have used a GUI-based git, especially on a critical project like OpenSprites. You can test command line git all you want on your own repos.

What you did was pretty bad. You deleted tons of our code, and apparently screwed up the blog layout or something.

We didn't mean to hate when we removed you from the organization. We just can't afford huge code-deletions and stuff in the future.

Just because you do not have write permissions to the repo does not mean you can't contribute. You can create your own fork, work there, and send a pull request when you're done. You can still comment on our issues and commits too. If you show that you can make significant changes and handle git responsibly in your fork, we'll give you write permissions back.

To be clear, you are not banned from the organization entirely. We want to be nice and give you a second chance, it's just that we can't give you write permissions at the moment, because of what happened.

I'm unlocking this issue so you can comment back if necessary, however please be respectful when commenting (ie, don't call yourself an idiot, don't accuse anyone of hate, and keep the sarcasm to a minimum).

MegaApuTurkUltra, and above James (Cheese) wrote

You know full well that we do not hate you quillz, I've known you for a year by now. I have invited him back into the team because this project deserves not to get into disputes. However, Quillz must understand this there is a limit to the amount of chances I can give before people start getting annoyed at having to revert changes all the time. With respect @andrewjcole, but you were not zeus trying to scrape backups from the developer site to patch the mess. I am acting as a admin within this project, and I intend to keep it that way; becoming a negotiator to solve personal disputes is certainly not high upon my agenda.

I'm tired of all that grumpy bore I just wrote, shall we have some lightheartedness and positivity again? :)

-Edit: Make the post clearer- -Edit @liam4: Blockquotes-

QuillzLouis commented 8 years ago

Sorry about my huge quotes

matthewr6 commented 8 years ago

Read this.

Just because you do not have write permissions to the repo does not mean you can't contribute. You can create your own fork, work there, and send a pull request when you're done. You can still comment on our issues and commits too. If you show that you can make significant changes and handle git responsibly in your fork, we'll give you write permissions back.

I would say you need to prove your aptitude with git before letting you back in, or doing some pull requests instead of getting write permissions. Preferably the latter.

QuillzLouis commented 8 years ago

@Firedrake969

Yeah, but you all seem to talk on gitter, and its sorta the only way to receive tasks.

QuillzLouis commented 8 years ago

Anyway, I'm going to have a go at fixing the themes, I'll leave this thread open for a bit to see what more people say.

matthewr6 commented 8 years ago

As if we're productive on Gitter :package: Well, there are tasks here you can start on.

QuillzLouis commented 8 years ago

Gitter is easier to get hold of people on, because your so active over there (Trust me.)

matthewr6 commented 8 years ago

We all see this too. Maybe I'm the only one bothering to reply to you? Considering the fact that you're not in our Gitter rooms, though, I would say that I have more authority about that than you... :/ The productivity is on Github, and the offtopicness is on Gitter. Just make PRs. Then we'll see.

Arinerron commented 8 years ago

We all see this too. Maybe I'm the only one bothering to reply to you? Considering the fact that you're not in our Gitter rooms, though, I would say that I have more authority about that than you... :/ The productivity is on Github, and the offtopicness is on Gitter. Just make PRs. Then we'll see.

^ that

QuillzLouis commented 8 years ago

@Firedrake969 Technically I made the gitter chat #92 .

matthewr6 commented 8 years ago

Ok... are you trying to imply anything?

QuillzLouis commented 8 years ago

Not really, working on the themes now.