# LibreTime Development Priorities

**URL:** <https://discourse.libretime.org/t/libretime-development-priorities/51>\
**Category:** Dev Talk\
**Created:** [November 13, 2017, 2:22pm UTC](https://discourse.libretime.org/t/libretime-development-priorities/51 "2017-11-13T14:22:15Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![gusaus](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/gusaus/32/42_2.png) [@gusaus](https://discourse.libretime.org/u/gusaus)\
**Post date:** [October 11, 2019, 12:51am UTC](https://discourse.libretime.org/t/libretime-development-priorities/51/11 "2019-10-11T00:51:20Z")

</div>

> [@gusaus](#):
>
> Get a realistic sense of availability from @robbt & @hairmare. What is the average amount of hours/mo you’re able to commit without a budget? What is the average amount of hours/mo you’d be able to commit with a budget?

Bumping this up as we’ve had recent discussions in [https://chat.libretime.org/](https://chat.libretime.org/) on this topic.

There seems to be a consensus that @robbt @hairmare and @paddatrapper could use some help getting the [3.0 release](https://github.com/LibreTime/libretime/milestone/9) out the door (assuming that’s the priority). If we had a sense of the amount of time they’re able to commit (see above) we could then determine who/what we need.

We might be able to bring on and incentivize needed contributors by participating in Hacktoberfest (which [we’re already doing](https://github.com/LibreTime/libretime/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest)) and the [Open Collective sponsored sustainer initiative](https://discourse.libretime.org/t/libretime-participation-in-hacktoberfest/387/12).

Considering the latter would be more of a collaboration and partnership, we’d have a good bit of room to experiment.

> <https://twitter.com/GetOpenProducer/status/1181817614684655616>

---

_[View the full topic](https://discourse.libretime.org/t/libretime-development-priorities/51)._