[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [modeling-pmc] RE: [mdt.dev] RE: Termination Review for MDT EODM
|
So why not open a community bug that outlines the general improvements we'd
like to see for all terminated projects? Termination is a new trend with
lots to learn about how to best cover all the bases, so I'm sure your input
would be welcome.
As mentioned previously, it seems we need to have all links from terminated
projects point to one Eclipse Project Archive page that lists each
terminated project and their materials for those interested in digging into
the past.
- Rich
On 10/1/08 10:50 AM, "Nick Boldt" <codeslave@xxxxxxxxxx> wrote:
> I suppose it's important to distinguish between "died due to lack of
> developer involvement" and "died due to lack of anyone using it."
>
> SDO & EMF Query, for example, still get used -- in products, even -- but
> increasingly no one wants to develop them. Should they "vanish into the
> ether" or simply stop ongoing development, while remaining available in
> their current, final forms?
>
> Not all software needs active maintenance and development to be useful.
> Consider Eudora, which my wife's been using for ages for POP mail
> access. It died at version 7, but still works great. I still use Win2000
> and WinXP, even though they're techinically past their expiration date.
> And ubuntu 7.04 is about to expire, but I'll still run it until I
> absolutely need to upgrade.
>
> I'm not advocating code dumping, just that we have an Eclipse Wayback
> Machine for old, as-is/unsupported projects with active communities
> behind them so that if, one day, someone wants to resurrect them,
> they'll be more easily accessible. (We can track how often people access
> these dead projects too, and if after a year discover no one's visiting,
> THEN we can beam them into deep space.
>
> (Oh, and as to the "not inventing policy" idea, we're already known for
> improving processes at Eclipse. Consider the recent
> "components-are-now-subprojects" policy change. That one is a direct
> result of Modeling pushing to change the rules for the better of the
> community, and for more agile development.)
>
> That said, I'm not a PMC here, so I'll follow your collective leadership
> with whatever you decide is best for Modeling and these terminated projects.
>
> $0.02,
>
> Nick
>
> Richard Gronback wrote:
>> I don't think the Modeling project should invent our own policy/procedure
>> for terminated projects. The Foundation should treat all similarly and
>> redirect links to a common "Terminated Projects" page where related
>> artifacts can be found. I've mentioned this once already to the webmaster,
>> so I suggest we all do so again.
>>
>> I don't have a problem with the "ether destination" for terminated projects.
>> If it was terminated for the right reasons, there should be nobody looking
>> for it. And what I don't want to promote is a sense that "code dumping" is
>> OK, and that if your project fails it just gets move to this little corner
>> of the website.
>>
>> - Rich
>>
>>
>> On 10/1/08 12:36 AM, "Ian Bull" <irbull@xxxxxxxxxx> wrote:
>>
>>
>>> +1
>>>
>>> It was actually pretty funny, no sooner did I submit a research paper
>>> with a footnote pointing to the EODM project, did I get the e-mail about
>>> the termination review. :-)
>>>
>>> It would be nice if the URLs redirected to a page that said the project
>>> has been archived, the source is here and the final builds are there.
>>>
>>> Cheers,
>>> Ian
>>>
>>> Nick Boldt wrote:
>>>
>>>> So the download page will be updated to say "this project has been
>>>> archived, see archived builds below?"
>>>>
>>>> What about the update sites? Release notes? Search CVS commit data?
>>>>
>>>> Or should we create a new folder on the website, /modeling/archives/,
>>>> and put all the dead projects there? If so, any old links (home,
>>>> downloads, release notes) for EODM could bounce to that "project" and
>>>> its "components." This has precedent in that we've done many moves
>>>> from EMFT into EMF; this would be a similar "move."
>>>>
>>>> I've seen other projects get terminated and vanish into the ether; I'd
>>>> like to think we can do better than that in Modeling.
>>>>
>>>> Thoughts?
>>>>
>>>> Nick
>>>>
>>>> On Tue, Sep 30, 2008 at 8:46 PM, Kenn Hussey
>>>> <Kenn.Hussey@xxxxxxxxxxxxxxx <mailto:Kenn.Hussey@xxxxxxxxxxxxxxx>> wrote:
>>>>
>>>> Ian,
>>>>
>>>> The source code for the project will be archived in a ZIP file,
>>>> and I assume that builds will be moved to the build archive
>>>> server. If you're interested in taking a snapshot of the source,
>>>> now would be a good time. ;)
>>>>
>>>> Cheers,
>>>>
>>>> Kenn Hussey
>>>> Program Manager, Modeling and Design Solutions
>>>>
>>>> Embarcadero Technologies, Inc. | www.embarcadero.com
>>>> <http://www.embarcadero.com>
>>>> 82 Peter Street, Second Floor | Toronto, ON M5V 2G5
>>>> Kenn.Hussey@xxxxxxxxxxxxxxx <mailto:Kenn.Hussey@xxxxxxxxxxxxxxx>
>>>> Mobile: 613-301-9105
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: modeling-pmc-bounces@xxxxxxxxxxx
>>>> <mailto:modeling-pmc-bounces@xxxxxxxxxxx>
>>>> [mailto:modeling-pmc-bounces@xxxxxxxxxxx
>>>> <mailto:modeling-pmc-bounces@xxxxxxxxxxx>] On Behalf Of Ian Bull
>>>> Sent: Tuesday, September 30, 2008 6:48 PM
>>>> To: PMC members mailing list
>>>> Cc: Anne Jacko; MDT developers; EODM Dev list
>>>> Subject: Re: [modeling-pmc] RE: [mdt.dev] RE: Termination Review
>>>> for MDT EODM
>>>>
>>>> Kenn and Anne,
>>>>
>>>> Just out of curiosity, where does a project go when it dies? In
>>>> the case
>>>> of EODM, I actually use a small part of it. While I don't have the
>>>> expertise, time or interest in maintaining it, I was just wondering if
>>>> the current builds / source will still be available, or if I
>>>> should grab
>>>> the code before it disappears?
>>>>
>>>> cheers,
>>>> ian
>>>>
>>>> Kenn Hussey wrote:
>>>>
>>>>> Anne,
>>>>>
>>>>> The slides for the MDT EODM termination review are attached.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> **
>>>>>
>>>>> *Kenn Hussey**
>>>>> **Program Manager, Modeling and Design Solutions*****
>>>>>
>>>>> *[Embarcadero Technologies Logo]* <http://www.embarcadero.com/>
>>>>>
>>>>> *Embarcadero Technologies, Inc. | **www.embarcadero.com
>>>>>
>>>> <http://www.embarcadero.com>*
>>>>
>>>>> <http://www.embarcadero.com/>* **
>>>>> **82 Peter Street, Second Floor | Toronto, ON M5V 2G5**
>>>>> **Kenn.Hussey@xxxxxxxxxxxxxxx
>>>>>
>>>> <mailto:Kenn.Hussey@xxxxxxxxxxxxxxx>*
>>>> <mailto:Kenn.Hussey@xxxxxxxxxxxxxxx
>>>> <mailto:Kenn.Hussey@xxxxxxxxxxxxxxx>>
>>>>
>>>>> *Mobile: 613-301-9105*
>>>>>
>>>>> *From:* mdt.dev-bounces@xxxxxxxxxxx
>>>>>
>>>> <mailto:mdt.dev-bounces@xxxxxxxxxxx>
>>>>
>>>>> [mailto:mdt.dev-bounces@xxxxxxxxxxx
>>>>>
>>>> <mailto:mdt.dev-bounces@xxxxxxxxxxx>] *On Behalf Of *Kenn Hussey
>>>>
>>>>> *Sent:* Thursday, August 28, 2008 9:24 PM
>>>>> *To:* Anne Jacko
>>>>> *Cc:* MDT developers; EODM Dev list; PMC members mailing list
>>>>> *Subject:* [mdt.dev] RE: Termination Review for MDT EODM
>>>>>
>>>>> Anne,
>>>>>
>>>>> We would like to schedule the review for October 8 instead. I'll get
>>>>> the slides to you by October 1.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> **
>>>>>
>>>>> *Kenn Hussey
>>>>> Program Manager, Modeling and Design Solutions*****
>>>>>
>>>>> *[Embarcadero Technologies Logo]* <http://www.embarcadero.com/>
>>>>>
>>>>> *Embarcadero Technologies, Inc. | **www.embarcadero.com
>>>>>
>>>> <http://www.embarcadero.com>*
>>>>
>>>>> <http://www.embarcadero.com/>*
>>>>> **110 Spadina Avenue, Suite 400 | Toronto, ON M5V 2K4
>>>>> **Kenn.Hussey@xxxxxxxxxxxxxxx
>>>>>
>>>> <mailto:Kenn.Hussey@xxxxxxxxxxxxxxx>*
>>>> <mailto:Kenn.Hussey@xxxxxxxxxxxxxxx
>>>> <mailto:Kenn.Hussey@xxxxxxxxxxxxxxx>>
>>>>
>>>>> *Mobile: 613-301-9105*
>>>>>
>>>>> *From:* Anne Jacko [mailto:emo@xxxxxxxxxxx <mailto:emo@xxxxxxxxxxx>]
>>>>> *Sent:* Thursday, August 28, 2008 5:30 PM
>>>>> *To:* Kenn Hussey
>>>>> *Cc:* PMC members mailing list; MDT developers; EODM Dev list;
>>>>> lzhangl@xxxxxxxxxx <mailto:lzhangl@xxxxxxxxxx>
>>>>> *Subject:* Re: Termination Review for MDT EODM
>>>>>
>>>>> Hello Kenn (et al),
>>>>>
>>>>> Apologies for the delay in responding -- it's been busy. For a
>>>>> Termination Review, you need review docuware (slides), and PMC
>>>>> approval to have the review. We also suggest that you give the
>>>>> developers on the project notice that the review is being planned.
>>>>>
>>>>> Since you are a PMC member, and you have copied the dev list on this
>>>>> email, the only thing you still need to do is create a set of
>>>>>
>>>> slides.
>>>>
>>>>> These are due at least one week before the scheduled review date.
>>>>>
>>>>> We are doing reviews on Wednesday, Sept. 17, at 8am PT. Will
>>>>>
>>>> that time
>>>>
>>>>> work for you? Thanks.
>>>>>
>>>>>
>>>>> Anne Jacko
>>>>>
>>>>> emo@xxxxxxxxxxx <mailto:emo@xxxxxxxxxxx> <mailto:emo@xxxxxxxxxxx
>>>>>
>>>> <mailto:emo@xxxxxxxxxxx>>
>>>>
>>>>> On Aug 21, 2008, at 12:46 PM, Kenn Hussey wrote:
>>>>>
>>>>> I would like to request a Termination Review for the EODM
>>>>>
>>>> component of
>>>>
>>>>> the MDT sub-project. There has been no activity in CVS by the
>>>>> committers on this component for a very long time (see
>>>>>
>>>>>
>>>>
>>>> http://dash.eclipse.org/dash/commits/web-app/active-committers.cgi?project=
>>>> mo
>>>> deling.mdt)
>>>>
>>>>
>>>> <http://dash.eclipse.org/dash/commits/web-app/active-committers.cgi?project
>>>> =m
>>>> odeling.mdt%29>,
>>>>
>>>>> and none of them has plans to further develop the component. We have
>>>>> identified parties interested in pursuing an implementation of the
>>>>> Ontology Definition Metamodel (ODM) at Eclipse, but we feel it would
>>>>> be best to do so as part of a new component with a new team of
>>>>> committers/contributors.
>>>>>
>>>>> Please advise as to how to proceed.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> *Kenn Hussey
>>>>> Program Manager, Modeling and Design Solutions*
>>>>>
>>>>> *<image001.jpg>* <http://www.embarcadero.com/>
>>>>>
>>>>> *Embarcadero Technologies, Inc. | **www.embarcadero.com
>>>>>
>>>> <http://www.embarcadero.com>*
>>>>
>>>>> <http://www.embarcadero.com/>*
>>>>> 110 Spadina Avenue, Suite 400 | Toronto, ON M5V 2K4
>>>>> **Kenn.Hussey@xxxxxxxxxxxxxxx
>>>>>
>>>> <mailto:Kenn.Hussey@xxxxxxxxxxxxxxx>*
>>>> <mailto:Kenn.Hussey@xxxxxxxxxxxxxxx
>>>> <mailto:Kenn.Hussey@xxxxxxxxxxxxxxx>>
>>>>
>>>>> *Mobile: 613-301-9105*
>>>>>
>>>>>
>>>>> --
>>>>> This message has been scanned for viruses and
>>>>> dangerous content by *MailScanner*
>>>>>
>>>> <http://www.mailscanner.info/>, and is
>>>>
>>>>> believed to be clean.
>>>>>
>>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>> _______________________________________________
>>>>> modeling-pmc mailing list
>>>>> modeling-pmc@xxxxxxxxxxx <mailto:modeling-pmc@xxxxxxxxxxx>
>>>>> https://dev.eclipse.org/mailman/listinfo/modeling-pmc
>>>>>
>>>> --
>>>> R. Ian Bull, PhD
>>>> University of Victoria
>>>> http://www.ianbull.com
>>>> http://irbull.blogspot.com/
>>>>
>>>>
>>>> --
>>>> This message has been scanned for viruses and
>>>> dangerous content by MailScanner, and is
>>>> believed to be clean.
>>>>
>>>> _______________________________________________
>>>> modeling-pmc mailing list
>>>> modeling-pmc@xxxxxxxxxxx <mailto:modeling-pmc@xxxxxxxxxxx>
>>>> https://dev.eclipse.org/mailman/listinfo/modeling-pmc
>>>> _______________________________________________
>>>> modeling-pmc mailing list
>>>> modeling-pmc@xxxxxxxxxxx <mailto:modeling-pmc@xxxxxxxxxxx>
>>>> https://dev.eclipse.org/mailman/listinfo/modeling-pmc
>>>>
>>>>
>>>>
>>>> --
>>>> This message has been scanned for viruses and
>>>> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
>>>> believed to be clean.
>>>> ------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> modeling-pmc mailing list
>>>> modeling-pmc@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/modeling-pmc
>>>>
>>>>
>>
>>
>> _______________________________________________
>> modeling-pmc mailing list
>> modeling-pmc@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/modeling-pmc
>>
