Based on what I see, we're talking about EOF'ing a useful and still used feature of Solaris, with no replacement.

While there may be reasons that we are not in a position to fund integration of a replacement, I think this decision is impact-ful enough to go beyond a fast track. As it stands now, the question we have to answer Architecturally is, "do we need a SIP router for Solaris?"

I'm going to derail this case, because such a decision at least requires some basic discussion and a vote. I don't new materials are required, but if the project team has materials that they can submit which demonstrate that there is not a need for this functionality, that might helpful.

If there are business reasons for the EOF which cannot be shared publicly (and I'm not saying that there are -- I don't know!), then this case can be converted into a closed one.

    - Garrett


On 04/ 2/10 06:00 AM, Lukas Rovensky wrote:
On 4/2/10 2:44 PM, Andrew Gabriel wrote:
James Carlson wrote:
Peter Dennis wrote:
This FastTrack will EOF the Sip Express Router (SER) and its web based
interface -- SERWeb -- from Solaris Next and obsolete SER and SERWeb
in Solaris 10.

On November 4th 2008 a new SIP Router project was announced and joined
by SER developers, [1]. This also means that SER itself is no longer
developed in favour of the SIP Router, [2].

I think this project is incomplete.

Removal without replacement doesn't seem like the right response to
having the upstream open source project merely shutting down. Instead,
I'd expect that we'd at most mark Obsolete in S10, and then remove in
the current release when the new, replacement project is ready, and
(perhaps) there's some sort of transition story that can be told.

We've got a huge number of open source bits in OpenSolaris that have
either a long-dead upstream or no real maintainer to speak of. And
there are others that were considered "dead" for years only to come back
to life later. Why is this one special?

Why does removal from OpenSolaris necessarily follow an announcement
like that?

As a user of SER, I would agree with that.

By "as a user of SER" -- do you mean a paying customer?

EOF of VoIP routing in Solaris is not an appropriate thing to do.

Can you elaborate on why it is not appropriate? I am very interested in understanding the facts concerning how having SER in Solaris is important from architectural point of view and/or how it helps to earn money (e.g., do we have and evidence on how many paying customers use it? Marketing did not provide me with such data).

Thanks,
Lukas

I'd be happy if the removal is conditional on first providing a
replacement.




_______________________________________________
opensolaris-arc mailing list
[email protected]

Reply via email to