On Fri, 13 Sep 2019 at 14:51, Ankur Sinha <sanjay.ankur@xxxxxxxxx> wrote:
On Fri, Sep 13, 2019 09:23:44 +0200, Clement Verna wrote:
> Yeah the packages app is really useful and used by many, this is the main
> reason it was not included in the application we are currently working on
> giving away / retiring. But to be honest I think the priority of the packages
> app is quite low. Following are some of the work we have in our Backlog :
> • Packager UX improvement. https://hackmd.io/DIz7xvfDSpyRu9y6BNG6aw
> • FAS replacement. Specification is work in progress
> • PDC replacement. https://hackmd.io/Ef4QgBwMSp-6eFQPChuWag
> • OSBS support for aarch64. No specification yet
> • End to End testing and monitoring for the flatpak build pipeline. Specification is work in progress
> • Package review process improvement. https://hackmd.io/TGbwd2yVTlmR_PKicI3CMA
> • Fedora Infra technical debt. https://pagure.io/fedora-infrastructure/issues :-D
Is there somewhere community members can read more on these tasks of the
CPE please?
Sure see links above, not all of these have a spec yet.
For the packages app---if it's in maintenance mode, I guess that's OK
for the time being until something breaks.
There are two aspects of the packages app that aren't available on
src.fp.o that make it important for me:
Not available now does not mean that it cannot be made available :-). We have so many code base it is difficult for us to maintain everything, I would rather identify the 2-3 features that the src.fp.o misses to replace the packages app and fill some RFE to the pagure-dist-git project (https://pagure.io/pagure-dist-git) than spend couple months rewriting the packages app which will fall into maintenance mode after the rewrite and then we will have the same problem in 2 or 3 years.
- bugz.fp.o/packagename -> but I expect this can be aliased to a direct
bugzilla query type URL? "Open bugs" on the packages app heads to
bugzilla already:
https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&product=Fedora&product=Fedora+EPEL&component=python-rosinstall_generator&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED
There are DDG bangs for bugzilla by the way but they don't search by
component (I'll suggest a new one soon): !rbugs, !rhbz
- "Install this package" -> this is critical. I was wondering if there
was a way to allow users to "click to install", but at least having
the `dnf` command there is very useful to most users.
I'm not flask etc savvy enough to know how easy/hard it is to add these
bits to src.fp.o, but given that src.fp.o is basically a pagure
instance aimed at the development side of things, I expect it isn't the
easiest thing to do?
Pagure supports third party plugins, which could be used to add specific functionality to src.fp.o that would not be needed for pagure.io. We are already doing that for the integration with release-monitoring which is currently being deployed.
On the other hand, maybe stuff that src.fp.o already provides can be
removed from the packages app to reduce the maintenance burden
---things like "Changelog" "Sources"?
I totally understand how busy the CPE team is and unfortunately I'm not
in a position to help much with the infrastructure side of things either.
Yes I know, we also wish we could help but trying to fix 10 things at the same time is not working well. So we are taking the approach of focusing on specific work until complete (currently rawhide gating), unfortunately this means low priority things will suffer from that. I honestly believe this is better, I prefer to tell you that the packages app will very likely be retired in the coming year rather than letting you hope that we will spend a lot of time on it and develop new features. But again this is my vision of the world :-).
Just for fun this is the list of the code bases the CPE team is maintains / look after.
- https://github.com/release-monitoring/anitya
- https://github.com/fedora-infra/the-new-hotness
- https://pagure.io/pagure/
- https://pagure.io/mdapi/
- https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/
- https://pagure.io/fedora-gather-easyfix
- https://pagure.io/is-it-in-rhel
- https://pagure.io/fedora-ci/simple-koji-ci
- https://github.com/fedora-infra/fedora-messaging
- https://github.com/fedora-infra/fedmsg-migration-tools
- https://github.com/fedora-infra/bodhi
- https://github.com/fedora-infra/fmn
- https://github.com/fedora-infra/fedora-packages
- https://github.com/repoSpanner/repoSpanner
- https://github.com/fedora-infra/fedimg
- https://pagure.io/sigul
- https://github.com/puiterwijk/flask-oidc/
- https://github.com/puiterwijk/libgit2-repospanner
- https://pagure.io/ipsilon
- https://github.com/fedora-infra/fas
- https://github.com/fedora-infra/fas-client
- https://pagure.io/robosignatory
- https://pagure.io/basset
- https://github.com/fedora-infra/python-fedora
- https://pagure.io/releng/tag2distrepo
- https://pagure.io/cccolutils
- https://github.com/fedora-infra/datagrepper
- https://github.com/fedora-infra/kitchen
- https://github.com/fedora-infra/datanommer
- https://github.com/fedora-infra/fedmenu
- https://github.com/fedora-infra/pkgwat.cli
- https://github.com/fedora-infra/pkgwat.api
- https://github.com/fedora-infra/asknot-ng
- https://github.com/fedora-infra/github2fedmsg
- https://github.com/fedora-infra/bugzilla2fedmsg
- https://github.com/fedora-infra/statusfpo
- https://github.com/fedora-infra/supybot-fedora
- https://github.com/fedora-infra/apps.fp.o
- https://pagure.io/pagure-dist-git
As it's stands today we are 5 developers (that is likely going to grow to 7 or 8) for almost 40 code bases. So If you know developer that enjoy working with legacy code base feel free to send them our way :-D
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
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://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
