I know that some of the competitors are using some sort of automated
License parsing based on the repo, might just do the trick.
Yaron Shahrabani

<DevOps - Hebrew translator>



On Wed, May 20, 2020 at 9:32 PM David Planella <[email protected]>
wrote:

> Thanks a lot Michal for your answer.
>
> Is there anything I can do on my side? What's the general expectation for
> an ETA, is it more like weeks, months?
>
> Missatge de Michal Čihař via Weblate <[email protected]> del dia
> dc., 20 de maig 2020 a les 20:24:
>
>> Hi
>>
>> Yes it is. Unfortunately we have huge backlog of requests and are slow in
>> processing them. What we really need is to automate most of that workflow
>> to get rid of the manual steps needed from our side.
>>
>> --
>>
>> Michal Čihař | https://cihar.com/ <http://cihar.com/> |
>> https://weblate.org/
>>
>>
>> David Planella píše v St 20. 05. 2020 v 20:07 +0200:
>>
>> Hi,
>>
>> I decided to try hosted Weblate for one or my open source projects, and
>> applied for the open source program as per the info on
>> https://weblate.org/en/hosting (Gratis for libre projects).
>>
>> It's been about two weeks, and other than an automated reply from the RT
>> system, I've not heard about the status of the application*
>> (support.weblate.org <http://support.weblate.org> #1521).*
>>
>> Is the open source program still active? If it is, what's the expected
>> processing time for applications?
>>
>> Thanks,
>> David.
>>
>> _______________________________________________
>>
>> Weblate mailing list --
>>
>> [email protected]
>>
>>
>> To unsubscribe send an email to
>>
>> [email protected]
>>
>>
>> _______________________________________________
>> Weblate mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>>
> _______________________________________________
> Weblate mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
Weblate mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to