Good Morning Everyone,
So yesterday we held a meeting on #fedora-apps about the future of PDC in Fedora.
We kept notes in etherpad at: http://etherpad.osuosl.org/pdc_fedora
Here is the gist of it:
What do we currently store in PDC:
* modules data - the list of what modules have been built, what rpms are in them,
and which ones are active or not.
* Stream branches, branch ownership, retirement dates (EOL/SLE)
* release/life-circle tracking
* product and product versions (fedpkg gets active Fedora and EPEL releases
from product versions endpont)
* critpath boolean on packages (bodhi uses this)
* metadata from composes (RPMS/images)
* "dependency" data about which rpms depend on which other rpms and which
containers include other rpms. This is not used by anything and can be
de-prioritized, dropped. (It was originally going to be used in Freshmaker.)
* List of all packages: fedora-packages uses this list to know what to index.
It sets up the "for loop" from which fedora-packages pulls data from all
After some discussion the decision we reached was:
* The "dependency" data in its current form can be dropped. It's something
need in the future but the data structure will most likely need to be
adjusted so let's just drop the existing data and worry about this later.
* The critpath boolean can just be imported into bodhi itself, especially
considering that bodhi is the only tool using this flag.
* The modules data is entirely going to move into MBS
Everything else (ie: composes metadata, release/life-circle tracking,
package/branches information) will need to find a new home.
This new home will be a new django app using the Django Rest Framework (DRF) in
which we will import the PDC apps as needed (potentially adjusting them where
- kellin has agreed to be the project leader for this work but needs a team to
do the actual work.
- pingou has agreed to look for said team
If you have any worries, questions or suggestions or if you want to join the
effort, please let us know :)
Finally some links:
Have a nice day,