El jue, 28-03-2019 a las 15:53 +0100, Michał Górny escribió: > Hello, > > In context of the recent plan of disbanding the Samba team, I'd like to > ask for better ideas on how to deal with projects that technically make > sense but are currently dead/defunct. This means that either they have > no members, all their members are inactive or simply don't want to work > on the specific project anymore. > > Of course, the first step is to look for new project members. However, > let's assume we've already done that and unsuccessfully. What should > happen next? > > So far I've been leaning towards disbanding the project and moving > packages to maintainer-needed. This has the advantage of clearly > indicating that those packages are unmaintained, with all the common > implications of that. > > However, it also has been pointed out that this frequently 'ungroups' > packages while being maintained by a single project makes sense for > them. I don't really have a strong opinion on this -- especially that > sometimes this actually helped people decide to take at least some of > the packages. On the other hand, Ada is an example of project that has > been recreated after being disbanded. > > Do you have any suggestions how we could effectively achieve the effect > similar to 'maintainer-needed' without disbanding projects? >
Personally I would keep moving them to maintainer-needed. If some packages really need to be bumped in sync, we can add a comment to the affected ebuilds to remember it for any developer taking the package or going to fix some issue for it. About recreating the project after, it's ok for me as soon as the new project has active people for it. Regards
signature.asc
Description: This is a digitally signed message part
