- Clone the AStarStartup git repos recursively (you can download it at https://git-scm.com).
git clone https://github.com/AStarStartup/AStarStartup --recursive
Copyright 2014-23 AStartup; all rights reserved.
A guide on how to invent, document, launch, and run a startup on GitHub with the AStartup Toolkit and I am You Language (IMUL).
Home Page: https://astartup.net
License: Other
git clone https://github.com/AStarStartup/AStarStartup --recursive
Copyright 2014-23 AStartup; all rights reserved.
We need a Don't Repeat Yourself (DRY) contributors Guide for all of the a-startup, oregon-cooler, kabuki-starship, future, and third-party organizations.
I've never documented how to make a branch, commit, and pull requests.
We have a new product, the Astartup Mission Control Center browser extension.
First and foremost, we nee a description of what the MCC, Format for a Startup Synidcaiton, and Astartup Toolkit all do and how it is organized.
I don't want to do this. I was also supposed to put a ™ on our trademarks.
Use a templating engine.
I've been just pushing the project onto the stack because the initial overview of the prior day sounded exactly the same.
Start the Secondary Log with a brief progress report. Example: Yesterday I worked on WikiSpy and I made good progress. This way I can work on my startup and not for my startup.
For instruction on how to perform Issue-driven Development and contribute to this project please read the Contributing Guide at <>.
Copyright 2021 © Cale McCollough; most rights reserved, Third-party commercialization prohibited, mandatory improvement donations, licensed under the Kabuki Strong Source-available License that YOU MUST CONSENT TO at https://github.com/CookingWithCale/AStartupCookbook.
We don't need a unique chapter for Astartup OS.
Just rename the chapter.
The repo link in the License is broken. Issue-driven development is a very technical subject worthy of its own chapter but it's part of Development. We also need a DRY instruction on how to make a Cookbook.
Development is not a Part that contains a Chapter on IDD. Fix the broken link.
I need to show you how the ITS works.
Use the GitHub organization projects.
The problem that I am addressing is that I didn't describe IDD, yet I'm linking to it in other repos as DRY documentation.
The solution to the Problem is to give an overview of what IDD is.
For instruction on how to perform Issue-driven Development and contribute to this project please read the Contributing Guide at <>.
Copyright 2021 © Cale McCollough; most rights reserved, Third-party commercialization prohibited, mandatory improvement donations, licensed under the Kabuki Strong Source-available License that YOU MUST CONSENT TO at https://github.com/CookingWithCale/AStartupCookbook.
I was tired and slopped out the commit without the ending of the story.
It messes you up to do a HoSe when you have to watch videos to learn. You need to do things quickly in the HoSe.
Just skip the HoSe if you have to watch videos or if you're not set up the night before. It's better to pause the videos and just be an active learner. It sucks to have to stop making progress to deal with the logs.
Any changes to the license requires changing all of the files.
The abbreviated license points to the full DRY license. Now changes to the license only require changing one file.
~/*
Copyright 2021 © Cale McCollough; most rights reserved, Third-party commercialization prohibited, mandatory improvement donations, licensed under the Kabuki Strong Source-available License that YOU MUST CONSENT TO at https://github.com/CookingWithCale/AStartupCookbook.
I'm utterly shocked there is nothing in the Mission Ticket section.
Currently only one of my repos links here on the contributing section but this is linked to now in every project I do so the instructions need to be top-notch.
~/Dev/IDD/*
The chapter is lacking the psychology of attention.
Do some research because I do not claim to know this, only to know of it.
The session tickets will start to become noise with thousands of developers.
The Workspace repo shares the same name as the GitHub account or organization, for example, the a-startup Workspace Repo is located at<github.com/a-startup/a-startup>. The link format for the Hierarchy IDD Tickets is:
The header IS HUGE with the full license language! We also need a method to publish the book.
Copy the Mozilla Public License header. Add a KabukiPress client app Visual Studio project and template files.
Often I will need to add a commit to a botched commit.
Put the current template inside of a markdown header tag A, and make A the first commit on each mission ticket.
For instruction on how to perform Issue-driven Development and contribute to this project please read the Contributing Guide at <>.
Copyright 2021 © Cale McCollough; most rights reserved, Third-party commercialization prohibited, mandatory improvement donations, licensed under the Kabuki Strong Source-available License that YOU MUST CONSENT TO at https://github.com/CookingWithCale/AStartupCookbook.
I started this Cookbook when Jekyll wasn't integrated into GitHub so there aren't any Jekyll files, it just compiles to vanilla Jekyll.
I'm adding a basic vanilla Markdown Cookbook Jekyll theme along with a donate page.
Copyright 2021 © Cale McCollough; most rights reserved, Third-party commercialization prohibited, mandatory improvement donations, licensed under the Kabuki Strong Source-available License that YOU MUST CONSENT TO at https://github.com/CookingWithCale/AStartupCookbook.
Missed a link.
I can't stand saying underscore in filenames.
Use Case-insenative UppercaseCamel.
Rename files to UppercaseCamel and into the /temp
directory.
Move all files from /temp
into /
.
I missed a couple of lower_snake_case filenames. Rename files to UppercaseCamel and into the /_Assets
directory.
Move all files from /_Assets/_Seams
into /
.
We need these super cook markdown templates that need DRY instructions.
Add a section that covers how to use the Markdown Software Engineering, Markdown Game Design, and Markdown Cookbook templates. We need to make the chapter generalizable to other industries so we need to re-add the Markdown Hardware Engineering templates ASAP.
Where do I start at? Do I skip the intro?
No, you need to read the Getting Started chapter and the H1 is supposed to read Astartup Cookbook.
GitHub's relative references don't work unless it's named readme.md
.
~/*
For instruction on how to perform Issue-driven Development and contribute to this project please read the Contributing Guide at <>.
Copyright 2021 © Cale McCollough; most rights reserved, Third-party commercialization prohibited, mandatory improvement donations, licensed under the Kabuki Strong Source-available License that YOU MUST CONSENT TO at https://github.com/CookingWithCale/AStartupCookbook.
New users don't know where to start. There is a root scope of what again?
Use the /docs/ReadMe.md
to put the IMUL tags.
What exactly does IssueType even mean?
They are tags such as Bug, Confusing, FAQ, etc.
There is confusion about (R) vs (TM), and this caused me to lose a grant once because someone on the panel called me out for using a (TM) when that was the appropriate usage.
(TM) is for a common law trademark and there are requirements to publicize your copyright in specific contexts. (R) is a legally registered trademark, which is not required.
Everything has changed and the Getting Started chapter need to get detailed.
The templates are badly out of date.
I'm going to use this one as the copy and paste and ensure it's the most up to date because I can use AStartupCookbook for DRY documentation for contributors.
Fixed license in the root directory I forgot to update.
Copyright 2021 © Cale McCollough; most rights reserved, Third-party commercialization prohibited, mandatory improvement donations, licensed under the Kabuki Strong Source-available License that YOU MUST CONSENT TO at https://github.com/CookingWithCale/AStartupCookbook.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.