# LibreTime services (and other ways to sustain the project)

**URL:** <https://discourse.libretime.org/t/libretime-services-and-other-ways-to-sustain-the-project/326>\
**Category:** Community\
**Created:** [July 31, 2019, 12:10am UTC](https://discourse.libretime.org/t/libretime-services-and-other-ways-to-sustain-the-project/326 "2019-07-31T00:10:30Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [January 29, 2020, 8:43pm UTC](https://discourse.libretime.org/t/libretime-services-and-other-ways-to-sustain-the-project/326/10 "2020-01-29T20:43:25Z")

</div>

> [@paddatrapper](#):
>
> The bug bounties would require us to have the funds to pay the developers for the issues, while eventually I would love to do that, we currently do not have the means to do so.

What about something like CiviCRM’s [Paid Issue Queue](https://civicrm.org/paid-issue-queue) where new features and bug fixes _may be prioritized_ by providing direct financial support.

> [@gusaus](#):
>
> [Make It Happen (MIH)](https://civicrm.org/make-it-happen) - campaigns to get or support new features that you’d like to see into the project but which hasn’t been included within core development

We’re already set up to create campaigns on LibreTime collective. [LibreTime API](https://discourse.libretime.org/t/planning-out-an-api/341) could provide us with an opportunity to define our own process.

> [@paddatrapper](#):
>
> Initially I think we should have a support tier where companies can pay a monthly donation and receive X number of hours a month in support. It would require probably 2 people to commit to being the support personnel (I’m happy to be one, but my PHP is lacking, so would be good to have someone who knows the PHP side of things). The project and the people providing support then agree on a hourly rate for that support, which is managed by the collective (the support members submit an invoice and get paid from the contributions made by the companies wanting support)

CiviCRM again provides [some good source material](https://civicrm.org/work-with-the-core-team) for types of services and processes. Main decision here is whether or not LibreTime core team is interested or has the capacity to provide client-facing services. Similar to a [LibreTime SaaS offering](https://discourse.libretime.org/t/any-interest-in-libretime-available-as-a-saas-with-hosting-and-support/121/21), this might be something core team members could collaborate on through a partner.

It would be great to have some sort of consensus from all maintainers about what LibreTime could provide through the website and collective.

---

_[View the full topic](https://discourse.libretime.org/t/libretime-services-and-other-ways-to-sustain-the-project/326)._