Jim Walker wrote: > Shawn Walker wrote: >>> I agree with you on "maintainership" even in the /pending repo. The >>> manifest needs to identify who submitted the package by name and email >>> address, and the submitter should assume maintainership unless they >>> defer it to someone else. The pkgfactory may be able to use the >>> project email address until individuals take over responsibility. >>> >>> Right. The repos are more like a dance floor than a dumping ground, >>> where everyone has a responsibility to not bump into each other. >> >> Contributing a package shouldn't require maintainership; there will be >> a lot >> of people willing to contribute packages but not be responsible for them. >> However, when reviewing the package, the indication of whether they are >> accepting maintainer-ship should obviously be a point of evaluation. > > /pending will allow people to contribute without commitment but people will > assume the submitter will maintain the package. Maybe we need another field > that indicates how much support the submitter will provide (ie. > support=none, > support=releasechange, support=bugfix). > > /contrib may need at least releasechange support (ie. the maintainer will > make best efforts to update the package when a new release is available).
I wouldn't put this information on the package since it can easily become out of date and then there's a broken point of communication or inaccurate information. Instead, there should probably just be a "support_url", or some such attribute in the package metadata that provides a generic link where current information can be found about it. As an example: http://pkg.opensolaris.org/contrib/support.html?fmri=XXX Going to that link would pull the most recent support information for the package from a database and display it. It could also have links to extended information about the package, any recent bug reports filed against it, and so on. I'm actually in the process of integrating a new templating system into the package depot, so it would be fairly easy for someone to implement this sort of application. Cheers, -- Shawn Walker _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
