District0x has and will maintain a development team currently working towards the migration and release of EthLance, Meme Factory, and Name Bazaar. These are the first 3 projects specified in the white paper and will be the projects that the development team work on until they are released and seen through the Aragon main net release (assumed by me). Once voting is closed and winners are chosen, new districts will be built with the assistance of District0x developers if it is required. Again, once these are released and new districts are selected to be built they will assist in the build process. On top of all this, the d0xINFA framework will provide district creators the levers necessary to set-up their district with reusable modular templates that help standardize the back-end and brand the front-end.
Iron Triangle Problem
Time, Quality, Features, Cost...In the cryptosphere throwing money or developers at a problem does not help a project move towards their goal. Quality and meticulous code review is the current status quo puts a premium on developers time and availability. In the case of District0x this opens up questions revolving around how the District0x development team is best utilized and whether or not stipulations need to be made on when to bring in a third party. Possible tasks that could fall into this decision (and I'm sure many that are not listed) are any of the following:
creation of a district
customize district after push button creation
custom application for a district
maintenance of district templates
maintain district when bugs arise
It can be imagined that each district would vote on whether or not to wait for District0x developers to be available or hire someone from as a third-party (i.e. EthLance) to design new features or updates. If District0x developers are getting involved this could bring up the following issues:
Feature request is unfeasible
Feature request requires too much time
A small feature requests turn into a large one due to unforeseen cascading effects
Who is managing the District0x development team and time?
If a third-party developed application breaks, can/should District0x developers help?
Possible Solutions
There are certain issues that come to mind that the District0x development team should be on the hook for every time issues or maintenance arise:
District0x platform
Ethereum stack issues/upgrades
Ethereum
Aragon
Re-usable template issues that have the possibility of affecting all districts
District considerations when it is not one of the above:
Vote to use District0x developer(s)
For low or no fee, you will have to wait until a team member can be assigned
If task turns out to be feature complex a larger fee should be applied to the district
For a scaling fee (based on feature request), you can pay for District0x developers time
For a large fee, a customized project can be developed
Vote to use third-party developer(s)
This should trigger a post to EthLance or similar site with feature request, time frame, expected cost, and developers desired
If larger problems arise that threaten the survival of a district (i.e. in house or third-party development gone wrong), the entirety of DNT holders can vote and decide if emergency development resource should be assigned to assist when it is necessary.
District0x Development Team
District0x has and will maintain a development team currently working towards the migration and release of EthLance, Meme Factory, and Name Bazaar. These are the first 3 projects specified in the white paper and will be the projects that the development team work on until they are released and seen through the Aragon main net release (assumed by me). Once voting is closed and winners are chosen, new districts will be built with the assistance of District0x developers if it is required. Again, once these are released and new districts are selected to be built they will assist in the build process. On top of all this, the d0xINFA framework will provide district creators the levers necessary to set-up their district with reusable modular templates that help standardize the back-end and brand the front-end.
Iron Triangle Problem
Time, Quality, Features, Cost...In the cryptosphere throwing money or developers at a problem does not help a project move towards their goal. Quality and meticulous code review is the current status quo puts a premium on developers time and availability. In the case of District0x this opens up questions revolving around how the District0x development team is best utilized and whether or not stipulations need to be made on when to bring in a third party. Possible tasks that could fall into this decision (and I'm sure many that are not listed) are any of the following:
It can be imagined that each district would vote on whether or not to wait for District0x developers to be available or hire someone from as a third-party (i.e. EthLance) to design new features or updates. If District0x developers are getting involved this could bring up the following issues:
Possible Solutions
There are certain issues that come to mind that the District0x development team should be on the hook for every time issues or maintenance arise:
District considerations when it is not one of the above:
If larger problems arise that threaten the survival of a district (i.e. in house or third-party development gone wrong), the entirety of DNT holders can vote and decide if emergency development resource should be assigned to assist when it is necessary.