On Wed, January 18, 2017 12:54, W. Trevor King wrote:

>> As to trying to make the underlying changes within the existing
>> shell-extras repo, I can't say that I can see how I'd fork a repo of
>> "old templated" existing content that would then follow the use
>> patterns with the new template, and associated lesson repos,
>> ...
>
> It's a big change, so it's a bit messy to read the final diff, but [1]
> is where this transition happened for git-novice.
>
> ...
>
> [1]: https://github.com/swcarpentry/git-novice/pull/308

OK,

so that /can be/has been/ done. Bingo!

I was really struggling to think of a way in which it could be.

Cheers for the pointer.


>> If, of course, it's easier for me to simply start a new lesson
>> template PR that only has the lesson style as an upstream repo,
>> whilst the shell-extras maintainers decide how to port their
>> existing content, at which point I could easily meld their
>> decisions into my PRs, then I'll happily do that.
>
> This works too.
> ...

In which case, I think that's what I'll look to do for now, not
least as:

a) I have already done it "offline", so effectively with just the
    lesson style as the "upstream repo" but without it being the
    online repo !

b) it would get the existing shell-extras content, presented within
    the same Look-and-Feel as the rest of SWC ,"out there".


> ...
> It's possible that there just isn't enough maintainer
> time to keep a SWC-standard shell-extras going (I'm not sure either
> way).  But this is also orthogonal to the changes you're proposing.
> If you like what you have, you can keep rolling forward with your
> version of the lesson regardless of what happens upstream.

Presumably whilst maintaing a branch within the existing shell-extras
repo that mirrors any changes in the content alone? Yes, I think I can
see how to make that work.


Thanks again, there were a number of dark areas fpr me, and this input
has been very illuminating,
Kevin


PS

Why, when the page detailing the Mailman lists,

  https://software-carpentry.org/join/#discussion

shows the discuss@ list as

  unmoderated

have all my messages to discuss@, so far, generated a

        Your message to Discuss awaits moderator approval

reply ?


_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/listinfo/discuss

Reply via email to