-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Welcome to the the-heap.github.io wiki!
If you don't know where you are or what The Heap is—don't worry. You're in the right place.
All repositories within this organization are open source and open for anyone to work on. These projects are relatively structured in that they are architected by an individual, originally, and will (likely) exist and be worked on over a restricted amount of time (ex. One month to create a project).
If you are interested in joining a project, you will need to find the repo for the project, and read it's README.md and CONTRIBUTING.md guidelines. In order to save The Heap-master's time and energy, there will be strict guidelines in terms code style, formatting, etc.
Videos will often accompany progress on a project -- sometimes in the form of live streams, intro or overview videos, or other times perhaps in a more tutorial-esque, "what I learned" etc. type videos.
Q: Are these projects courses?
A: No
Q: Do I have to pay $$$
A: No. This is FREEEEEEE.
Q: How come you didn't respond to my PR or issue?
A: There's a good chance you didn't read the readme, contribution guidelines, or read the project roadmap. Many projects will be taking place over a short window of time and so there will not always be time to get a project done if dealing with contributions that (majorly) deviate from the purpose / goals or general roadmap.
Q: How come projects are only worked on for X amount of time?
A: First off, projects can continually be worked on for as long as they are here, hosted on The Heap. However, the current initiative of The Heap Projects, is to get a project done, within a window of time. Deadlines make things happen. The purpose here is to focus on a single project by imposing restrictions — in this case time.
Q: Can I keep working or contributing to this after the time window is up?
A: Yes, but there is no promise that the maintainer of the project (The Heapmaster) will continue to maintain the project. You may be wasting your time creating issues or PR's if the participants have moved on in their lives to other greater things.
Q: Why did/didn't you choose X tool or Y library for Z project?
A: It could be that I chose to build things a certain way out of interest to try new tools, get away from tools. The main goal, is to keep things simple.
Q: Why are you focused on keeping things simple?
A: Because I believe you need to work simply / do the dumbest thing first to get things done. As developers, (I at least) I think we're susceptible to over engineering, pre-optimizing, nerd-sniping etc. Simplicity, and boring methodologies sometimes are best.
Q: Who's running the show here?
A: This guy
Q: I don't want to work on your project; your idea is dumb.
A: That's not a question!