Transfer of Ownership

[RandomDSdevel]

@BjarneStroustrup:

Per (and quoted directly from) the 'GitHub Repository for 'Programming: Principles and Practice Using C++' Support Code?' thread's original post on the ISO C++ std-discussion reflector from when I tried to reach you concerning the subject a while back:

Dear Mr. Stroustrup,

     I think it would very convenient and useful if you were to put the support code that you have published on your web page for Programming: Principles and Practice Using C++. Doing so would allow users like myself to be more proactive in suggesting and contributing improvements and code errata. For example, end users have previously contributed build support for additional compilers. I, myself, have created a GitHub repository containing the support code for the second edition of the book and, even though I haven’t yet gotten around to doing it, plan to add better support for Xcode, either directly via an Xcode template or indirectly through a CMake build profile. It would be nice if there were a central version of such a repository for me to submit my changes to with a pull request. A central location for the support files might also allow me to port my efforts back to the code for the book’s first edition as well. Could you, perhaps, look into setting this up for your readers?

Sincerely,
     Bryce Glover
     RandomDSdevel@gmail.com

P. S.: Yes, I know I should have gotten my contributions ready to merge by now, but I got distracted/derailed…oh, well; such is life (mine especially, it seems these days…sigh.)

[RandomDSdevel]

@BjarneStroustrup: I just began transferring this repository's ownership to you via its GitHub settings. If you wish for me to abort this action, please let me know here. Once this ownership transfer is complete, I will create my own fork of your new repository. (If you just want me to wait until you create your own repository containing similar files to this one, then I'll delete this repo and fork the new one.)

[BjarneStroustrup]

OK. Thanks.

[RandomDSdevel]

@BjarneStroustrup: You're welcome! Before I go, though, I should probably note that you might want to clean up this repository's commit history a bit (to perhaps squash commits and fix authorship metadata notations to your liking,) as my initial efforts trying to figure out why I seemed to be having trouble committing some files here left behind a bit of a mess (turns out it was due to journaled HFS+'s default semantics of being case-preserving but case-insensitive, which would of course be a problem to a Mac user like myself, but I've been doing what little development work I've managed since I figured that out off of an 'HFS+, Case-Sensitive, Journaled' disk image for quite some time now, so everything's ship-shape down here on my end now.)

P. S.: Since I'll be contributing via pull requests from a fork from now on, I don't need to be added to this repository as a co-maintainer, so you can undo that. (In addition, it appears GitHub seems to have conflated our two user account identities somehow, as this source repository is still listed as 'mine' on GitHub's home page under 'Your repositories' alongside my fork of it when I visit that page, strange as that sounds…)

[RandomDSdevel]

@BjarneStroustrup: Should I split my last comment's postscript into a new issue, or are you fine with the request I made in it and just haven't gotten around to fulfilling it yet?

[RandomDSdevel]

@BjarneStroustrup: I went ahead and forked the discussion present in this issue to further elaborate on my misgivings as to how you resolved it into Issue #3: 'Resolving Code Origin, Attribution, and Access Permissions'. It's quite formal (especially coming from me,) but I believe it suits the purpose of getting the points it makes across reasonably well regardless of this fact. Please take a look at and respond there to it.