[csw-maintainers] reminder on contributing on recipes

[Ben Walton]

I like that approach. Anyone else?

Thanks
-Ben
On Jan 9, 2013 8:24 PM, "Dagobert Michelsen" <dam at opencsw.org> wrote:

> Hi Ben,
>
> Am 09.01.2013 um 20:17 schrieb Ben Walton <bwalton at opencsw.org>:
> > This would be fine with me for all of the reasons you've listed. It's
> not a trivial change though as maintainership info is derived from package
> metadata. A gar override its the answer...
> >
> > In fact, simply making that info part of the recipe instead of storing
> it in .garrc would allow versioned take overs.
> >
> > Am I missing a downside here?
>
> We could add something like
>   MAINTAINER = dam
> in the Makefile with the person currently maintaining the package which
> then goes to
>   SPKG_EMAIL = $(MAINTAINER)@$(PKGDOMAIN)
> if MAINTAINER is set and falls back to already defined SPKG_EMAIL
> where PKGDOMAIN is preset in the global /etc/opt/csw/garrc
>
>
> Best regards
>
>   -- DAgo
>
> >
> > On Jan 9, 2013 7:10 PM, "Peter FELECAN" <pfelecan at opencsw.org> wrote:
> > "Maciej (Matchek) Bliziński" <maciej at opencsw.org> writes:
> >
> > > 2013/1/8 pfelecan <pfelecan at opencsw.org>:
> > >>   On the maintainers mailing list, announce your intention to work on
> > >>   the recipe and eventually take up the maintenance.
> > >
> > > What if I want to make a change and upload it, but not become a
> > > permanent maintainer of the package? I had loads of such cases,
> > > especially with packages depending on old libraries. I want to remove
> > > an old library, so I rebuild packages depending on it. Obviously, most
> > > of these packages are not maintained. But I only care about them not
> > > depending on a legacy dependency I want to kill, I don't want to spend
> > > weeks on all the bugs that such package might have filed in Mantis.
> > >
> > > Currently, the result is that I have a lot of bugs assigned to me,
> > > which are legitimate bugs, but I have no intention to fix them,
> > > because I didn't want to take over these packages. But the mechanics
> > > of our uploads work in such a way that it's impossible not to appear
> > > as the main maintainer after you've uploaded a package.
> >
> > Indeed, this is bothering me also: a maintainer correcting a lot of
> > packages that are orphaned acquire, by default, the maintenance of the
> > those packages.
> >
> > What if we change the uploader to have an option saying that the action
> > is on the behalf of the current maintainer --- even a retired one; we
> > can log that the upload was done by somebody else. Debian has a similar
> > feature...
> > --
> > Peter
> > _______________________________________________
> > maintainers mailing list
> > maintainers at lists.opencsw.org
> > https://lists.opencsw.org/mailman/listinfo/maintainers
> > .:: This mailing list's archive is public. ::.
> > _______________________________________________
> > maintainers mailing list
> > maintainers at lists.opencsw.org
> > https://lists.opencsw.org/mailman/listinfo/maintainers
> > .:: This mailing list's archive is public. ::.
>
> --
> "You don't become great by trying to be great, you become great by wanting
> to do something,
> and then doing it so hard that you become great in the process." - xkcd
> #896
>
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20130109/c2988169/attachment.html>