Surely if someone gave you a few hundred dollars to sustain a staff member such as yourself to spend a few man days leveraging volunteer tech & design effort, you’d do it? So less a matter of prioritizing things and more a matter of the EA Community Fund covering low hanging fruit like this so you don’t have to take time you presumably don’t have laboriously convincing someone that this is worth those few hundred dollars.
I mostly agree. However there are definitely some strategic, management-level things that have to be decided when it comes to the Hub. There are an infinite number of fantastic ideas from EAs regarding what things they might want to see, and it’s not a straightforward matter to judge how best to go forward. Particularly when it also means making sure we complement the platform that CEA is developing. Some factors include major choices about things like which codebase we continue with, creating a structure that allows highly skilled EAs in tech to contribute to some degree when they want to, and also making sure we don’t waste resources making a start with something unless we’re confident we’ll be able to maintain it appropriately in the long run. Those are just some of the matters involved, and in this regard available bandwidth, both of myself and our tech labour has been a limiting factor for sure.
However we’ve been making a lot of fast gains since we hired our new tech officer, Larissa, in November. We also have the guidance of seasoned EAs working in tech, and I’m very optimistic about 2018!
Absolutely—but re-Richenda’s point about deliberations at a higher level, the Hub is one of many resources we provide, and we want to make sure every donation we receive is most impactful.
Even an earmarked donation for this purpose is not a straightforward proposition. Take the decision to potentially integrate with the CEA platform as a hypothetical. If we were to spend $300 - $1k tweaking the Hub, and then had to double back (likely to change the coding language) once we decided that linking up with the CEA platform is most effective for the community, we may have wasted considerable resources.
Surely if someone gave you a few hundred dollars to sustain a staff member such as yourself to spend a few man days leveraging volunteer tech & design effort, you’d do it? So less a matter of prioritizing things and more a matter of the EA Community Fund covering low hanging fruit like this so you don’t have to take time you presumably don’t have laboriously convincing someone that this is worth those few hundred dollars.
I mostly agree. However there are definitely some strategic, management-level things that have to be decided when it comes to the Hub. There are an infinite number of fantastic ideas from EAs regarding what things they might want to see, and it’s not a straightforward matter to judge how best to go forward. Particularly when it also means making sure we complement the platform that CEA is developing. Some factors include major choices about things like which codebase we continue with, creating a structure that allows highly skilled EAs in tech to contribute to some degree when they want to, and also making sure we don’t waste resources making a start with something unless we’re confident we’ll be able to maintain it appropriately in the long run. Those are just some of the matters involved, and in this regard available bandwidth, both of myself and our tech labour has been a limiting factor for sure.
However we’ve been making a lot of fast gains since we hired our new tech officer, Larissa, in November. We also have the guidance of seasoned EAs working in tech, and I’m very optimistic about 2018!
Wouldn’t even as small a donation as a few hundred dollars translate into more bandwidth?
Absolutely—but re-Richenda’s point about deliberations at a higher level, the Hub is one of many resources we provide, and we want to make sure every donation we receive is most impactful.
Even an earmarked donation for this purpose is not a straightforward proposition. Take the decision to potentially integrate with the CEA platform as a hypothetical. If we were to spend $300 - $1k tweaking the Hub, and then had to double back (likely to change the coding language) once we decided that linking up with the CEA platform is most effective for the community, we may have wasted considerable resources.