Distributed workflow

[GabeIsman]

Wanted to jot down some quick thoughts on workflow. The way I see it there are two basic opitons:

1. Everyone forks media-public/mediapublic-server and works in their own repository. This is the git distributed workflow.
2. Everyone is a contributor to media-public/mediapublic-server and works in branches. Some core group of contributors have commit bits to master. This is the more centralized workflow.
3. Core contributors use workflow 2., people contributing every now and then use 1.

I personally favor 2., because I think it is simpler. If @thequbit is working on some backend feature that hasn't been merged into master yet, I can test it/develop against it simply by merging in his branch. (I can still do this in the distributed workflow but it requires slightly more work). The code on your machine is always up to date after a git pull, no need to worry about merging in changes from other remotes.

Thoughts?

[thequbit]

eek! @GabeIsman this isn't the main repo any more ( we need to delete this account asap @melodykramer ).

@GabeIsman we live over at github.com/mediapublic now ...

Do you mind re-posting this question there ( I would do it, but I want the receipt that you saw this comment :p )

[GabeIsman]

@thequbit Whoops! Was too hasty in my clicking through.

[thequbit]

No worries, just wanted to make sure we all ended up in the right place!

[ryansb]

Maybe delete this repo/port over the issues?

I made the exact same mistake.

[thequbit]

Err, yea ... so I'll work on getting this entire account deleted ASAP. Thanks @GabeIsman and @ryansb.