foundationkit / FoundationKit

Everything that really should be in Foundation, but isn't. Future-proof with ARC
Other
80 stars 9 forks source link

Remove forked repos from organization #12

Closed MSch closed 13 years ago

MSch commented 13 years ago

See https://github.com/foundationkit.

Since we merge and rename stuff we use anyways we don't need to clutter our beautiful organization page (look at it in incognitomode and imagine only three repos there: FoundationKit, UIKitSquared, AppKitSquared)

PS.: What about renaming FoundationKit to FoundationSquared to keep with UIKitSquared (since it's not UIKitKitSquared)

eaigner commented 13 years ago

Could we rename the organization? Peter also already purchased http://foundationk.it.

MSch commented 13 years ago

@eaigner: We have one rename left. But you're right, lets either discuss this in a separate issue or focus on the actual one: Removing forked repos from organization

steipete commented 13 years ago

The reason we forked the projects was, to support a high-level framework that's ready to be included and has all the nice stuff already in it - and history showed that forks are a good idea - otherwise a single update within those submodules is painful.

Would be cool to give them another color, or put them at the end of else...

MSch commented 13 years ago

So what do we do? Can't keep them at the end or change color.

+1 for letting them be and adding them to iOSKit later

steipete commented 13 years ago

It's still an in flux - for our goal of an high-level project, that provides common needs, we need the submodules. If we still think they suck, we can create a second organization, like "FoundationKitSupport" or whatever. But that just increases complexity - let's keep it for now.