Requests to be a contributor of this repository

[titoBouzout]

Use this thread for requesting contributor permissions to this and the DefaultPackages repositories. Contributors may:

• edit, close and rename issues
• assign labels
• modify the source code (pull request for review preferred for larger changes)

There is no standardized review process, so each person will be reviewed individually.

[FichteFoll]

Alright, I said before that splitting the default package bugs/issues to a separate repo would be reasonable but I wouldn't be the one to do it. As a result, moving the two repos to a separate org is a perfectly fine move. (I've been waiting for your statement on this.)

You know what I did with the previous repo so you are free to add me as a contributor, unless you have some serious reclunctance against me for things that are not exactly in my hand, in which case I could put my spare time to some other use probably.

By the way, I'm for renaming this repo to "Core" so we get "SublimeTextBugs/Core".

[titoBouzout]

Thanks, added as a contributor with also others members I remember, if I forget someone, I'm sorry, please just let me know.

I'm for renaming this repo to "Core" so we get "SublimeTextBugs/Core".

I'm for the rename also, but github does not create redirects for renamed repos, so I guess we will have to live with this to keep the links intact.

[FichteFoll]

Sure it does. It creates redirects the same way as for owner changes. It did not a while ago, but it didn't for owner changes back then either.

Btw, please disable the IRC event hook until you are done with moving issues, it's kind of spammy.

[titoBouzout]

Sorry for the spamming IRC, I did not noticed. Repo renamed to "Core", what do you think about renaming the organization to "SublimeTextIssues", as suggested here: http://www.sublimetext.com/forum/viewtopic.php?f=2&t=12095&start=110#p64694

[FichteFoll]

Agree on that. For some reason I didn't actually think about it but this was also the reason why I suggested to rename the original repo to "Issues" and not "Bugs" somewhere in the early stages of the same thread.

[FichteFoll]

@titoBouzout, would you mind making me an admin or owner of (at least) the other repo? I'd like to set up the IRC hook.

[titoBouzout]

Sure, no problem, invitation sent

[FichteFoll]

Thanks, that was quick.

[qgates]

@FichteFoll re. #775, can't seem to adjust labels etc. on here, did you update my status to contributor?

[FichteFoll]

@qgates you didn't accept the invitation yet. Check your mail.

[qgates]

@FichteFoll Got it. Damn spam classifier ;-)

Thanks :-)

[FichteFoll]

I added @wbond as a contributer, since he is taking care of issues and pull requests over at https://github.com/sublimehq/Packages.

[titoBouzout]

Okei thank you

[FichteFoll]

I just sent an invite to @keith-hall, who has been a great help with feedback for issues and created numerous issues.

@keith-hall, I believe you don't need an introduction on how this repo works.

[keith-hall]

thanks @FichteFoll :)

created numerous issues

I prefer the term logged - created sounds like I am causing them :D

[keith-hall]

do we have some guidelines somewhere on how to classify issues please? :) i.e. what criteria makes an issue critical, major, minor or trivial? :)

[FichteFoll]

I prefer the term logged - created sounds like I am causing them :D

Blame Github then; they use "New Issue" on their button. 😄

do we have some guidelines somewhere on how to classify issues please?

Nothing written. I intended to do that a while ago but it's kinda hard to think of actual criteria.
I mostly base my decision on how many users it affects and how much if affects them. Crashes are usually major or critical category, as are security issues. Niche requests or bugs you can easily work with/around usually get the trivial treatment. Everything else is minor.

[FichteFoll]

Closing since we handed over the tracker to Sublime Hq.