On Mon, Sep 24, 2018 at 2:43 PM Clement Verna <cverna@xxxxxxxxxxxxxxxxx> wrote: > > > > On Mon, 24 Sep 2018 at 11:30, Michal Novotny <clime@xxxxxxxxxx> wrote: >> >> Hello, >> >> could we use this? >> >> https://github.com/PostgREST/postgrest > > > While I don't have a strong preference for one or the other, the main reason we decided to use DRF is to be able to reuse some of code from PDC (https://github.com/product-definition-center/product-definition-center). We are currently working on the releases endpoint (https://github.com/fedora-infra/fpdc) and to be fair we did not reuse to much code so far, but I expect that it will be the case when working on components and composes endpoint. I guess it mainly depends on the people doing the work (that means you and the rest of the pack). clime > > >> >> we could trim down PDC to just db + REST API (+ git backend syncing >> through hooks?) >> >> It's written in Haskell (!!) and it looks really like a useful piece >> of technology. >> >> We could drop Django completely and have git for any write changes, which >> means we will automatically get: >> >> - version control >> - acls >> - public interface >> >> for free without any future maintenance. >> >> Only the writeable/interesting parts of PDC would be in DistGit. >> >> I don't know what will be stored in PDC at this point but I think >> just db + REST + git would be a suitable stack for a high-level >> release-engineering-like settings. >> >> clime >> >> P.S. I would personally be happy to help with this setup. >> >> On Wed, Sep 12, 2018 at 8:57 PM Randy Barlow >> <bowlofeggs@xxxxxxxxxxxxxxxxx> wrote: >> > >> > On 09/12/2018 04:01 AM, Clement Verna wrote: >> > > [0] https://github.com/dhatim/python-license-check >> > >> > This looks useful, thanks for sharing! >> > >> > _______________________________________________ >> > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx >> > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx >> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> > List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx >> _______________________________________________ >> infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
