On Fri, 2018-12-28 at 10:01 +0100, Fabiano Fidêncio wrote: > After a nice pub conversation a friend of mine suggested that *maybe* > the .treeinfo changes could be done as part of Google Summer of Code. > As a GNOME student/mentor/admin from previous years, I sincerely think > it may be a good idea *if* the work is not too short and/or something > else could be added to the same project in order to make it solid > enough for 3-ish months of work. At this point, Debian's level of participation in GSoC 2019 hasn't yet been determined but it looks like we at least have admins this year. Please note that the nature of Debian's participation will be different this year due to some policy changes added by this year's admins: https://lists.debian.org/msgid-search/20181121113859.GA22177@smithers.snow-crash.org > What would be the specific codebase that I could open an RFE kind of > issue just to keep track of this? I expect the main codebase for this is dak, since that controls what the Debian archive looks like. The Debian meta-package for reporting bugs and feature requests against dak is ftp.debian.org. Any software that would be used by dak to read/write treeinfo files would need to be packaged for Debian sid and then backported to stretch. https://salsa.debian.org/ftp-team/dak https://bugs.debian.org/ftp.debian.org https://www.debian.org/Bugs/Reporting https://mentors.debian.net/intro-maintainers http://backports.debian.org/Contribute/ > In case this idea is really too short ... what if someone spend some > time to briefly guide me through the relevant codebase so I could > provide the needed patch? I'm not familiar with dak but I expect that it wouldn't be a full 3 months worth of work. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part