monterail / guidelines

[DEPRECATED] We are Ruby on Rails experts from Poland. Think hussars. Solid & winged. These are our guidelines.
71 stars 17 forks source link

Describe what you're going to do in issue before doing anything #183

Closed sheerun closed 11 years ago

sheerun commented 11 years ago

As proposed by @Ostrzy. That way no one will be surprised by big pull-request, as everyone will be at least notified you're going to change something.

This is connected to my refactor in ghcr, but I see other people doing that as well, for example @teamon in rails-assets, which is indeed annoying.

This guideline is mainly for open source and internal projects.

Such issue can be easily converted to pull-request later on.

Ostrzy commented 11 years ago

:+1:

sheerun commented 11 years ago

@chytreg @jandudulski @teamon @tallica @porada @jcieslar @venticco

bartoszrega commented 11 years ago

:+1:

szajbus commented 11 years ago

meh :+1:

teamon commented 11 years ago

This is not as simple as it looks like, but :+1:

Ostrzy commented 11 years ago

@teamon Probably not, but better try something simple and adjust, than just being constantly pissed off ;)

porada commented 11 years ago

YOU GUYS OBVIOUSLY DON’T AIM FOR THE WOW EFFECT

porada commented 11 years ago

:+1:

jandudulski commented 11 years ago

This issue is going to achieve a gold medal in "Best issue of the year" category.

Obvious :+1:

sheerun commented 11 years ago

@teamon Please merge

teamon commented 11 years ago

Are you sure about the placement of this line in top-level README? This only applies to projects with issues on github.

sheerun commented 11 years ago

@teamon Where to put it?

porada commented 11 years ago
touch Internal.md
sheerun commented 11 years ago

I'd vote git.md, updated.

teamon commented 11 years ago

How is that a git guideline? oO

"Internal" or "GitHub" seems fine. (GitHub even more, all of guidelines are kind of internal)

sheerun commented 11 years ago

How it is not

porada commented 11 years ago

teamon commented 11 years ago

This is not general git rule for all projects, it is valid only for small part of them. I'd even go further and propose OpenSource.md.

sheerun commented 11 years ago

Maybe rename git to opensource...

teamon commented 11 years ago

Git.md applies to all projects. This guideline does not.

jandudulski commented 11 years ago

Git is git. Opensource is opensource.

If I would be looking for the preferred settings for git I will be looking for a git.md. If I would be looking for the preferred way to contribute - opensource.md will be my first hit.

sheerun commented 11 years ago

Whatever, here you have your open source md

teamon commented 11 years ago

Thank you :)