[MeeGo-dev] Precision of what it means to 'be responsible for' / committing to maintaining a feature/package/whatever in MeeGo?
sivan at omniqueue.com
Wed Jan 12 02:13:34 PST 2011
On Wed, Jan 12, 2011 at 10:28 AM, Dave Neary <dneary at maemo.org> wrote:
> re. Core should not be exempt: if we look at Debian, you can't become a
> maintainer of a package unless the maintainer(s) invite you to be, or
> the package is abandoned. I don't think any core packages will be
> abandoned any time soon, so the short answer there is to start packaging
> newer versions of core packages, and submitting them to the maintainer.
What if I want to change something or add functionality to an existing
package? For instance, what if I want to provide fixes or apply
somebody else's fixes to improve the core UX in meego to be more
suitable for the idea pad, and I do have the time for that. Perhaps
we could at least assign a mentor or a sponsor that would review
packages and upload them on my behalf? I even touched sysvinit in
Ubuntu through this process. Martin only physically uploaded it.
> For other packages, I hope that David or Arjan have a good answer - I'd
> love to see something like a package wishlist + list of orphaned
> packages, where new packagers can cut their teeth.
Yes, that is highly desirable. Do we have an ITP request queue like
Debian has? If not, can we please start it? We still need some people
to be able to review packages or help people get their first package
the #debian-mentors style , although I've seen that already happening
in #meego. Do we keep this that way?
> In any case, your question clarifies that we're talking about "package
> maintainer" not "project maintainer", which is, as I pointed out, a
> different role.
Well, in Ubuntu when you wanted to add a feature you ultimately became
the package's maintainer. When writing a spec you would even detail
which packages you would have to depend on, possible workflows for
upgrades, interaction with packaging system etc. So development or
working on a new feature at least for the first runs meant you'd be
maintaining the package.
Where do we stand with regard to that? I hope mentioning packages
need be abandoned to be cared for by the community does not imply
that's core is mostly for Intel / Nokia or other funded stakeholders
in the project?
And yes, I know this is not Ubuntu :) So this is only suggestions from
past experiences and questions, not criticism in any way.
More information about the MeeGo-dev