I, as a fledgling woodworker, was able to make my own board with some guidance from a friend. It's definitely a rewarding and educational project! Plus it makes a nice wall decoration when not in use. I used Purple Heart wood for the edges, which looks gorgeous but was difficult to work with. It took a few days of 3-4 hour blocks, due to a busy schedule, so a more experienced woodworker should be able to do one pretty easily.
I've had to introduce this to my friends at work. Where I sit, I can't have my phone with me. So sometimes it'll take me four tries to leave the room, grab my phone, and actually remember to do the thing that I meant to do. Usually I get back to my desk after doomscrolling for a few minutes and remember.
I have fond(ish) memories of being at a hackathon and hearing Ignition Remix for two hours nonstop with Infinite Jukebox. I look forward to trying this new incarnation!
When we were migrating to git, some of the more senior engineers came up with a workflow that was described as "the best implementation of ClearCase in git that I've ever seen". It was meant as a compliment.
Meanwhile my coworkers refuse to run googletest tests in random orders, because their tests all rely on being run in the "right" order and affect global data...
Content already released, yes. The post says nothing about being able to make new things under 1.0a, which is where a lot of the nervousness comes in for people.
Sure, but "not being explicit" is very different than the way OP phrased it ("WoTC says in this post") -- it made me think I'd missed some explicit mention of it.
FWIW, I don't even believe they ever wanted to try to claw back e.g. the 3.5 SRD, so I'm not as concerned as other folk here. (But it's also clear that if they have no such intent, they'd need to make it legally binding for folk to trust them.)
If I had a nickel for every time WotC tried to change the OGL and the community got pissed, I'd have two nickels. Which isn't a lot, but it's weird that it happened twice!
(The first time is what gave us Pathfinder 1e in the first place, for those who don't know - they took D&D 3.5e, under the OGL 1.0, and made modifications and continued its spirit)
I thought I was the only one old enough to remember that we have been here before.
Back in the day I even had an email thread with Ryan Dancy about making software tooling based on the OGL, which was pretty non-committal and discouraged me from proceeding with any efforts.
My understanding of that discouragement in general was in how the exclusive nature of the OGL prevented it from being combined with software licenses. Implementing OGL-covered rules in or with code covered by a different license was fraught, which makes OGL software development difficult unless you get permission (aka, a commercial license) from the copyright holder (WotC/Hasbro).[1][2]
The existence of OGL-implementing tools is more a factor of WotC/Hasbro reserving attempts to enforce that on small fish in a small pond, but could be deployed against anything even marginally successful that wasn't tithing enough.
> ... you have to give all the recipients the right to extract and use any Open Game Content you've included in your application, and you have to clearly identify what part of the software is Open Game Content.
> One way is to design your application so that all the Open Game Content resides in files that are human-readable (that is, in a format that can be opened and understood by a reasonable person). Another is to have all the data used by the program viewable somehow while the program runs.
> Distributing the source code not an acceptable method of compliance. First off, most programming languages are not easy to understand if the user hasn't studied the language. Second, the source code is a separate entity from the executable file. The user must have access to the actual Open Content used.
> NOTE: The biggest problem we've found with software and the OGL is that programmers aren't paying attention to Section 8 of the OGL. Section 8 states: "If you distribute Open Game Content You must clearly indicate which portions of the work that you are distributing are Open Content." This doesn't mean you can say "all rules in my program are Open", the users need to be able to see all that Open Content. You can do this by putting Open Content in a format that is easy to understand. Popular solutions have been to place everything in text files that the program pulls info from, having everything in a viewable database within the software, using Java script on a webpage (viewing the source of the webpage will display the code and Java script is relatively easy for a user to interpret). The key is that the user has to see everything that is Open Content that the program uses and be able to understand it without too much effort. The whole point of the OGL is that once information is declared Open everyone has free access to it under the OGL. Compiling that information into a program denies the user that access and violates the spirit of the Open Gaming License.
