A central database will allow all of our systems to connect and allow the capacity to track any sort of data regarding hatchers, community, technologies, development, anything. Django is an open source web framework written in Python. It is the most popular and robust web framework in the python ecosystem and has been used in production for a very large amount of production environments. The Django Rest Framework is a specific application of Django that is used specifically for backend API services.
Proposal Rationale Essentially, this allows us to have a database that we can store any sort of data in, and we can access this data via web requests, so any system can get or post from these data tables. This would aid in processes like the praise quantification or tracking results of the commons simulator over time.
Expected duration or delivery date (if applicable): This should take about 4 hours of development time. Two devs working in tandem for 2 hours would be ideal. Adding additional tables to the database can be done in 1 dev hour batches.
Team Information (For Funding Proposals)
ygg_anderson (github: linuxiscool)
Skills and previous experience in related or similar work: I’ve deployed various django production deployments in professional environments. I generally use the django rest framework as a web database solution for various data science projects.
Funding Information (For Funding Proposals)
4 Dev hours equivelent for initial launch. Additional hours may be required for specification gathering depending on what kind of data we want to maintain and for what purposes.
Ethereum address where funds shall be transferred:
More detailed description of how funds will be handled and used:
Funds will be directly transferred to the devs upon deployment of the database.
Thanks @HBesso31! It needs a certain critical mass of interest to be maintainable and usable, we will need a few community members who are comfortable being maintainers, and comfortable being responsive when people want to make changes / upgrades to the database. If they are to stop being a maintainer, they will have to find and hand off to another maintainer. I would be happy to teach a couple of programmer community members how to pull this off, but I won’t have the availability for maintenance / upgrades.
Sounds like @Tonga is down to join the team, if we get another committed co-vestor than we can talk about initializing the project upon approval.
To further clarify the cost of this project, since we should have some redundant knowledge keepers, I will say 3 programmers (Me and @Tonga make 2) 2 hours each for development + 2 hours each for deploy, and an average of 2 hours each per month for maintenance and upgrades, thus for a 6 month commitment, that is:
3*(2+2) <- develop and deploy
3 * 2 * 6 <- 6 months maintenance and upgrades
12 + 36 = 48 Dev Hours.
Let’s say dev hours earn between 30 and 60 DAI per hour, that gives the following budget:
1440 DAI - 2880 DAI for deploy and 6 months support, 540 DAI per month after that for upgrades, maintenance, and support.
We could probably end paid support at some point if we have a critical mass of knowledge keepers who are comfortable tweaking and making upgrades, but then again it’s nice to pay people for good work
Keep in mind, this funds 3 TEC community devs and is an excellent opportunity for dissemination of knowledge for utilizing the Django REST framework!