Create CocoaLumberjack organization #150

Closed
rivera-ernesto opened this Issue Nov 1, 2013 · 16 comments

Comments

Projects
None yet
4 participants
Member

rivera-ernesto commented Nov 1, 2013

It is entirely up to @robbiehanson, but I think we should move the repository to its own free CocoaLumberjack/CocoaLumberjack organization.

Advantages:

  • Easier to add and manage contributors.
  • Support Travis CI to show a nice build status badge we can all access. This will also check any pull request for build errors automatically.
  • Show our CocoaLumberjack membership on our GitHub accounts ;)

Steps needed:

  • Create the organization.
  • Add owners and contributors, @robbiehanson being the owner should be enough.
  • Transfer ownership to the organization.
  • @robbiehanson should fork to his personal account the moved repository to avoid braking Cocoapods and people's links, etc. Also maybe change the description to point to the new repository address.
  • Release 1.6.3? #135.

@ghost ghost assigned robbiehanson Nov 1, 2013

Member

bpoplauschi commented Nov 7, 2013

@robbiehanson could you comment on this?

Contributor

robbiehanson commented Nov 8, 2013

This sounds like a pretty good idea. I'll look into setting this up tomorrow.

Member

rivera-ernesto commented Nov 8, 2013

Nice!

Member

rivera-ernesto commented Nov 11, 2013

Travis configuration working, will be great for pull requests.

Member

bpoplauschi commented Nov 19, 2013

@robbiehanson Did you come to a conclusion yet?

Contributor

robbiehanson commented Dec 4, 2013

Sorry this took me so long!

I created the organization, and transferred the CocoaLumberjack project to the CocoaLumberjack organization.

@robbiehanson should fork to his personal account the moved repository to avoid braking Cocoapods and people's links, etc.

Wanted to double-check about this. From the docs (https://help.github.com/articles/how-to-transfer-a-repository) I see this:

Redirects and git remotes

When a repository is transferred, all requests to the previous location are automatically redirected to the new
location. External links should continue to function.

In addition to redirecting web traffic, all git clone, git fetch, or git push operations targeting the previous location
will continue to function as if made on the new location.

This seems to be working right now. But if I fork the organization project into my personal account, might this break the auto redirect stuff that's already working?

Like you said, we should still update links in the source code though.

Member

dvor commented Dec 4, 2013

Thanks a lot @robbiehanson! Redirection is working fine now. I can't find any information on Internet but I think that it would break in case of forking - the fork would have same url as the old repository.

We can update all Lumberjack's podspec files in CocoaPods/Specs to use new url. Anyway, before that even if you'll create a fork it will still contain all tags and CocoaPods wouldn't break.

I'll start updating urls all over the project and will create pull request asap.

BTW it seems that you didn't enable push access for Collaborators team so we can't maintain the repo.

Contributor

robbiehanson commented Dec 4, 2013

BTW it seems that you didn't enable push access for Collaborators team so we can't maintain the repo.

What a rookie mistake... fixing...

Member

dvor commented Dec 4, 2013

I've created pull request updating all specs to new urls CocoaPods/Specs#5900

Contributor

robbiehanson commented Dec 4, 2013

It should be fixed. Let me know if not.

Member

dvor commented Dec 4, 2013

@robbiehanson It's fixed, thanks!

Member

rivera-ernesto commented Dec 5, 2013

Great @robbiehanson, Thanks!

Member

rivera-ernesto commented Dec 5, 2013

BTW I think we could move CocoaLumberjack-related projects and forks there too. Like your XcodeColors fork, and in the future their party loggers, etc.

Contributor

robbiehanson commented Dec 5, 2013

Like your XcodeColors fork

Great idea!

Member

rivera-ernesto commented Dec 5, 2013

One more thing. I'm trying to enable Travis CI to enable automatic checking of all commits and pull requests.

As we're not organization admins I need to turn on this switch:

https://travis-ci.org/profile/CocoaLumberjack

You may also need to add a hook:

https://github.com/theintern/intern/wiki/Travis-CI-integration

Right now it is enabled only on my fork, so only my pull requests get tested:

https://travis-ci.org/rivera-ernesto/CocoaLumberjack/builds

Member

bpoplauschi commented Jan 20, 2014

@robbiehanson Hi Robbie. Could you take care of @rivera-ernesto 's request above by enabling Travis CI for Lumberjack?

@bpoplauschi bpoplauschi added this to the 1.7.0 milestone May 16, 2014

@bpoplauschi bpoplauschi removed the Started label Jun 24, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment