On Jan 19, 2008 4:13 PM, Tiziano Müller <[EMAIL PROTECTED]> wrote:
> >> Possibilities:
> >> An element: <status>{active/inactive}</status>
> >
> > Status of what? seeing you have proposed a upstream-status and a
> > maintainer status. what else is there left to status :P
> There will be a <maintainer> tag within the <upstream></upstream>, not the
> same as our already existing <maintainer>
>
> But the question I tried to express (probably not clear enough) is:
> Should (if at all) the status being tracked for <upstream> or for
> <maintainer> (within upstream).
>
> As an example "dev-libs/xmlwrapp": The original maintainer is inactive, but
> there is a new one who took the package to sourceforge and it's not a fork
> since the original maintainer agreed up on this. Should such a case be
> tracked at all?
>
I think we don't want to track if previous maintainer is active or
not, or if it's changed. In your example, the important data is "who
is the current maintainer and how to contact him" and "is she
active?". Keeping an entry for the old maintainer as inactive when
there's a new one is not like an useful piece of info.
--
Santiago M. Mola
Jabber ID: [EMAIL PROTECTED]
ï¿½ï¿½í¢‡^�X��� ��(��&j)b� b�
