Hi Sivan, Sivan Greenberg wrote: > I really liked the use of the median to conclude Prof. Knuth has not > done much of maintainer-ship over Tex the last couple of years, but > your account felt a bit too philosophical to me. But then again it is > late for me, and this is probably my own subjective experience :-)
Thanks (I think). > So - I am who I am. I now have a lot of free time. I am interested in > maintaining packages. I have experience in maintaining Ubuntu packages > (gnome-cups-manager, gnome-system-tools, my own hubackup, > notification-daemon and more). Not so much with RPM based packages. > > Bottom line, what do I do to start maintaining a MeeGo (core should > not be exempt!) package? What is my course of action? 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. 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. 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. Cheers, Dave. -- Email: [email protected] Jabber: [email protected] _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
