Hi Chet,
I have not receive any additional feedback beside Timo.
As FFM TC chair, I recommend to proceed to close FFM TC. As of committee Specification to OASIS Standard, I do not foresee it.
Regards,
Thinh
From: ffm@lists.oasis-open.org [mailto:ffm@lists.oasis-open.org]
On Behalf Of Chet Ensign
Sent: Monday, November 14, 2016 11:13 AM
To: Perala, Timo (Nokia - FI/Espoo) <timo.perala@nokia.com>
Cc: Nguyenphu, Thinh (Nokia - US/Irving) <thinh.nguyenphu@nokia.com>; FFM TC List <ffm@lists.oasis-open.org>
Subject: Re: [ffm] Status of the FFM TC - is it time to close?
Thinh, what do you think? Shall I proceed with closing the TC? Is there any likelihood that people will reengage to move it from Committee Specification to OASIS Standard?
On Tue, Nov 8, 2016 at 12:44 PM, Perala, Timo (Nokia - FI/Espoo) <timo.perala@nokia.com> wrote:
Chet, Thinh,
I support closing the shop. Or FFM TC.
cheers
Timo
From:
ffm@lists.oasis-open.org [mailto:ffm@lists.oasis-open.org]
On Behalf Of Chet Ensign
Sent: Tuesday, November 08, 2016 6:07 PM
To: Nguyenphu, Thinh (Nokia - US/Irving) <thinh.nguyenphu@nokia.com>
Cc: FFM TC List <ffm@lists.oasis-open.org>
Subject: Re: [ffm] Status of the FFM TC - is it time to close?
Hi Thinh,
Just touching base. Have you had any conversations on this? Do you want to hold the TC open for awhile?
On Tue, Nov 1, 2016 at 10:09 AM, Chet Ensign <chet.ensign@oasis-open.org> wrote:
It is straightforward. The TC can hold a vote to close. That requires a Full Majority Vote to pass. As it is just the three of you on the other hand, I can just call for objections
and if none of you object, I can close the TC.
The published work at
docs.oasis-open.org/ffm/ remain public and freely available. The fact that the FFM spec is a Committee Specification means that all the IPR protections remain in place so implementers can adopt it
with confidence.
The only issue would be if you wanted to continue to work on the specification - for example, develop a version 2.0 - or advance FFM as a Candidate OASIS Standard. Any action like
that would require starting a new Technical Committee. Likewise, if there was any maintenance to be done, a new TC would be needed. There'd be no way to work on the spec outside the TC.
If you think that might happen at some point, then the TC can be left open on the rolls.
On Tue, Nov 1, 2016 at 9:54 AM, Nguyenphu, Thinh (Nokia - US/Irving) <thinh.nguyenphu@nokia.com> wrote:
Hi Chet,
If we wishes to close the TC, what is the process? How are the specifications are maintained and classified
it status? Thinh
From:
ffm@lists.oasis-open.org [mailto:ffm@lists.oasis-open.org]
On Behalf Of Chet Ensign
Sent: Tuesday, November 01, 2016 8:46 AM
To: FFM TC List <ffm@lists.oasis-open.org>
Subject: [ffm] Status of the FFM TC - is it time to close?
I just took a look at the Field Force Management TC's web pages. It looks like the TC has been inactive now for some time. There doesn't appear to have been any activity since the
end of 2012 and you three are the only members and you are all from Nokia. So the TC is technically below minimum membership. Do you think it likely that the TC will begin work again or is it time for the TC to close?
There is certainly nothing wrong with declaring victory and wrapping things up. All the TC's work and historical record will continue to be available on the OASIS platform. Plus
you have Field Force Management Integration Interface Specification Version 1.0 and Field Force Management Integration Interface Requirements Version 1.0 approved as a Committee Specification and Committee Note respectively.
Please let me know your thoughts. I do not want to close a TC prematurely but if no further work is likely to happen then perhaps it is time to close
--
--
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
|