messformakers

Domesticated-Apricot

At MakeICT, we have gotten tired of fighting with our current system for managing members and events. Lack of features, lack of support, broken API's, the list goes on. So we've decided to make a better system, since we're makers and all. This will give us the access we need to our users and events, and give us opportunities to implement new features like equipment management and to work with new developers. We are in the very first stages of this project, so if you would like to be involved but don't have a lot of experience, now is a great time. Wee need developers at all levels, front end, back end, user experience, database, API and more.

The first steps are to get something minimal that can begin to take the place of the current system used by MakeICT. In brief, that means it will need to be a web-based system that allows us to create events, reserve space, and allow users to register for those events. We also would like to give users some more control over the profiles and data registered in the system, and give administrators more tools for reporting usage and metrics. We have also decided to continue supporting those who wish to pay for classes and membership dues via cash or check, so we will need at least a minimal invoicing system at the start. For a more complete list of features, including future wishes, check out the Google Doc.

We also hope to make this project about a lot more than just MakeICT. We feel that every makerspace could use a good management tool for free. We'd like to keep in mind a design philosophy that makes it easy for other organizations to deploy, customize, and extend this platform.

Resources

You can join the discussion on Slack, or come to a scheduled meeting. Check out devICT's home page for information on joining Slack and for joining the Meetup for event notifications.

Our current design mockups are on NinjaMock. Check them out to see the direction we are taking, especially if you would like to help with the front-end development.

The list of requirements for the software is in this Google Doc.

//TODO Expand this with getting started resources for the different technologies used in this project.

Contributing

Contributions are welcome, you can start by reading this section for some of the best practices and methods for managing this project. Next, check the TODO or requirements document for something that interests you, or that you have skills that you could offer. When you find something, see if there is a branch for that feature or bug, if not make a new one.

What technology does this prjoect use?

We are currently building the server backend in Go (1.7.3), the frontend with Material.io, and using PostgreSQL (9.3) for storage. Various other libraries may be used, but those will be explained in the comments in the files that use them.

How should I add or work on a feature?

Check the TODO or requirements to find something you want to work on.  Then, check the branches to see if someone is already working on it.  If they are, you can join that branch, or if not, you will need to create a new branch. More information on the git Feature Branch workflow can be found in [this tutorial](https://www.atlassian.com/git/tutorials/comparing-workflows#feature-branch-workflow) by Atlassian.  It also has a very good beginners guide to using Git if you never have before.
After you have worked on your feature and have it working you can submit a pull request and after your code is reviewed it will be merged into the main branch.

How will all this code be tested?

At this time, with very little written in the way of code or tests, the plan is to use acceptance testing to make sure that routes, validation, server responses, etc are working. Unit tests may be used in some cases to prove that specific bugs are fixed and prevent regression.