-
-
Notifications
You must be signed in to change notification settings - Fork 17
I'm confused and don't understand how to contribute
We're building a framework like bootstrap or foundation, meant to be used on HubSpot.
This can be difficult for people to just go "okay got it, let me go to town and start building it"
Here's what I'm doing the concept is abstract, I've got experience building a framework like this but internally for company use only. I'm using my experience to create concrete github issues that are easy to understand, those issues all together when combined form the whole of the framework. My goal is that if you contribute to this framework you don't need to see the whole picture. You can work on small parts. Those small parts will start to inter-mingle and grow together over time.
All of the big topics that require more thought before code should be written get posted as "Ideas for discussion" issues. This is one of the ways I'm trying to get feedback from everyone so we can make smart decisions together, these are often the more abstract ideas, that will influence the smaller issues that are created. In addition, I continually ask for feedback via Slack.
Because I want to keep things moving on this I will make executive decisions if I feel something is just sitting idle because a decision hasn't been made. I am making these to get things moving because we can start coding based on one idea and if we find it was a bad route to go we can change it later, it's better to make mistakes than to never make progress at all.
You can take any role you want to take. This isn't your day job. If you feel like working on the grid is fun, do it, if you feel like creating the buttons/UI elements is fun, do it! If you have code that you've already written that would be useful, contribute it. If you find a bug, create an issue and tell us. If you feel like writing the documentation, awesome, write it! The issues are separated into 2 projects right now to make it clear which are for documentation, which are for the actual framework code itself.
Pick an issue that sounds fun/interesting, read it, if you don't understand what's needed, ask, at the very least you'll help someone else who can contribute to this task. Implement something and submit a pull request when done :)
Don't be afraid to break things.(we'll catch it in the Pull Request and can fix them before merging them) Don't be afraid of git, just code your thing, and we can help you on the git front. The beautiful thing about git is almost everything can be undone, so don't worry about screwing up.