Skip to content

Move accessory features of CocoaPods to plugins #1589

Closed
fabiopelosin opened this Issue Nov 13, 2013 · 14 comments

3 participants

@fabiopelosin
CocoaPods member

One good candidate is the $ pod podfile-info command.

@Kapin
CocoaPods member
Kapin commented Nov 13, 2013

@irrationalfab should these be hosted under the Cocoapods banner or personal repos? Since they are already in the project I think the former might make more sense.

@fabiopelosin
CocoaPods member

I would prefer to keep those plugins under the CocoaPods organization because in this way the Core team has push access. However if you somebody would like to maintain one of them, depending on the feature, I'm open to discuss it.

@fabiopelosin
CocoaPods member

Also GitHub integration could be moved out, the main reason for moving it out (gem dependencies) is not very strong. However moving it to a dedicated plugin could enable workflows much more oriented to GitHub (i.e. pull requests).

@Kapin
CocoaPods member
Kapin commented Nov 15, 2013

First stab at porting it. Still needs a bunch of work and we need to move it under the CocoaPods banner (and credit whoever added it originally properly), but it's on the right track. https://github.com/Kapin/podfile_info

@fabiopelosin
CocoaPods member

:+1:

@fabiopelosin
CocoaPods member

To move to the CocoaPods organization you should be able to just transfer the repo.

@Kapin
CocoaPods member
Kapin commented Nov 27, 2013

@irrationalfab I need admin rights to do that. I've added you as a collaborator to the repo so we can sync up to transfer it properly.

@fabiopelosin
CocoaPods member

I did and experiment and just forked it. I don't know if now you can transfer the ownership or what happens if you delete yours. However I would even be comfortable keeping the fork as a tribute for the great work! Thoughts?

@xslim
xslim commented Dec 4, 2013

As a person who initially commited this code to cocoapods I think it's better if @Kapin will just transfer a repo to CocoaPods organization...

@fabiopelosin
CocoaPods member

@xslim Ouch... sorry about this. It is my fault as I didn't consider that this patch was contributed by you when I decided to fork. I'm all about properly crediting people and I consider not doing so no cool at all. We will fix this before releasing it by:

  • Prepending your name in the license.
  • List you as the author in the gemspec.
  • Transfer the repo instead of forking.

I have also to point, for clarity, out that in another discussion @Kapin stated that he was looking for a way to properly credit you (another issue or in the CocoaPods Campfire).

Also as we prefer to keep the CocoaPods gem lean while allowing the community to customize it with plugins, I was wondering if you would like to have this repo transferred to you. I think that this could be a great solution as you have a stronger incentive to evolve this subcommand and you would properly preserve all the credits.

@xslim
xslim commented Dec 4, 2013
@fabiopelosin
CocoaPods member

Cool! Thanks for understanding!

@Kapin
CocoaPods member
Kapin commented Dec 6, 2013

@xslim the published gem's repo is here https://github.com/cocoapods/cocoapods-podfile_info. If you would like to do a pass over and see if I missed anything, it would be totally awesome :smiley_cat:

@fabiopelosin
CocoaPods member

Closing as there are no other suggestions for the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.