Re: Sharing nested subparts of large repository?

[Phil Hord <phil.hord@gmail.com>]

On Sun, Mar 25, 2012 at 12:38 PM, LordSmoke <dslice@morphometrics.org> wrote:
> I've been using git for a couple of months to get used to the system. Basic
> stuff - a few larger project repositories in unique directories, commits,
> pushes to a remote repository. Mostly as a kind of backup system.
>
> However, my ultimate goal is to share part of one large project currently
> being managed with git with my developers. I want them to have access to
> source code and test data, but not my manuscripts, correspondence, whatever.
>
> I also want to make a portion of what I will give my developers available as
> open source, e.g., on github, but not all of it. Just the stable,
> non-developmental parts. NOT the our development stuff and not the parts
> being used for private contracts.
>
> Submodules seem promising, but the examples are not quite what I am looking
> for, as far as I can tell. They talk about isolating submodules that depend
> on a larger project. I want to make available the larger project while
> keeping nested submodules (so to speak) private.
>
> Would someone point me in the right direction to achieve my goals?

There's a blog post detailing a similar workflow here:
http://www.braintreepayments.com/devblog/our-git-workflow

Grr... I think they used to have a section on keeping some parts of
the project "forever private", but I don't see that now.

Phil