Community
Participate
Working Groups
We are renaming the Mylar project and planning a move to the Tools PMC. Please see the attached FAQ for a detailed explanation and feel free to post additional questions here so that we can answer them or add them to the FAQ. This rename has been deemed necessary and we need to do it quickly to minimize its impact by having it completed in time for Europa . These changes signify how quickly Mylar has grown up from an incubator technology to a framework and tool whose adoption continues to grow rapidly. The new name that I have created for the project is Mylyn. In addition to being a name that's very simple, unique, elegant and only a two letter difference from the old name, it has a connotation that's closely related to the ideas behind our technology. I came up with this word when doing my PhD, while I was researching how to make tools better leverage our memory and engaged in an email exchange with a neuroscientist about the potential effects of the myelin substance on improving our ability to access memory. Myelin *accelerates our thoughts* by making neurons dramatically more efficient at conducting electricity. The Mylyn name is a tribute to this substance--on several occasions I have heard users state that our tool increases their efficiency to the point where they are able to *code at the speed of thought*. There are numerous constraints and tradeoffs in choosing a name, ranging from trademark issues to ease and uniqueness of Googling. I believe that this name will serve well at identifying the project in the long run while providing the easiest transition. In addition, we'll finally stop confusing kids Googling for the Mylar film when doing science fair projects. We will be taking numerous steps to make the transition as easy as possible for both users and integrators. Stay posted on the this bug, the newsgroup and mylar-dev list. We will be announcing the name change once we are far enough along, so we ask that you refrain from blogging this until we have made the announcement, at which point the FAQ will have any necessary questions addressed and the project's descriptive name will have been chosen. In my opinion the two best options for the descriptive name are: 1) Mylyn: Task-Focused Tools 2) Mylyn: Task-Focused Toolkit The first has the benefit of being more user-centric, whereas the second is slightly more integrator centric and probably more descriptive. Our charter is to build a Task-Focused UI framework for Eclipse, and to provide exemplary tools for that framework with reference implementations for task repositories such as Bugzilla and resources such as Java. A key reason our framework has been growing and maturing so rapidly is that we have made the tools be the framework, so Toolkit may be appropriate as long as users do not associate it with the download being framework only. If anyone has thoughts or preferences on the descriptive name please comment here.
Created attachment 70441 [details] project rename FAQ
BTW, how is it pronounced? Something like "my line"?
Phonetically the preferred pronunciation is 'mIl&n but when you say it sounds like one syllable. So just like the pronunciation of myelin (see http://m-w.com/cgi-bin/dictionary?va=myelin ) but without the "e". In English it's like saying "my" and "lynn" as one word. Thanks for asking Willian, I'll make sure to add that to the FAQ.
What about new package names? Please please please tell me it is org.eclipse.tft
I believe that the rule with package names is that the name of the project needs to be used, so that would make our package names look like: 1) org.eclipse.mylyn.tasks.ui Not: 2) org.eclipse.tft.tasks.ui There could be some vagueness in the rules because some projects short names are their acronyms (e.g. CDT, ECF, TPTP). When I discuss the move with Bjorn today I will ask whether there is an option here. If there is, we can get the committers to vote on this and get the opinions of any other interested parties.
Please note that plug-in and other renaming changes are being discussed on bug 191755.
I have updated the Tomcat configuration on the vserver.
Status update sent to mylar-dev: CONTRIBUTORS CVS is now ready to use again. The easiest way to get set up is to check out the updated project set. The port is far enough along that I have been able to bootstrap, although there are still many changes in progress so we do not recommend doing that yet. http://www.eclipse.org/mylyn/doc/dev/mylyn.psf INTEGRATORS Please wait until I have sent a message that the Porting Guide updates are done before attempting to migrate. Next week will be manually migrating connectors in order to make sure that the steps are easy enough to follow and plan on creating a separate mailing list for integration questions. We recommend waiting to migrate until Monday the 18th (RC1 will be released by then). USERS There will be no Mylyn dev build until we have created the facility for disabling the old Mylar plug-ins. The latest dev build is yesterday's 2.0.0.v20070607-1200.
(In reply to comment #0) > 1) Mylyn: Task-Focused Tools > 2) Mylyn: Task-Focused Toolkit > I would go for Mylin: Task-Focused Development, as that is what you get from using it, and the projects aims to enable and promote that. Anyway, I'm sorry to hear that as it will set back name awareness a couple of months. I've done a lawyer induced company name change for a startup once, such a waste...
> I would go for Mylin: Task-Focused Development Only problem is that "TFD" rolls of the tongue like "BFD", which is of course "big _____ deal". Still, it's better than WTP looking like WTF. ;-) At least you're not calling it Focused UI Controller (tool)Kit. How about TFDT (Task-Focused Development Tools) ?
He he, that's a neat suggestion. It's descriptive, and we can do all sorts of neat capitalizations of it, e.g. Focused Ui Control KIT. Maarten: regarding the Mylin spelling, it's good too, but it's way more common and we can't have mylin.{org,com} and we have mylin.{org,com}. Also, I worry that it doesn't have enough y's in it. I had TFDT on the board for a long time and do like that one, probably more than just Task-Focused Tools. And since we have a short name we can probably afford a longer descriptive name. So the current descriptive name list is the following, and I'll add (4) for parallelism with IDE: 1) Task-Focused Toolkit 2) Task-Focused Tools 3) Task-Focused Development Tools 4) Task-Focused Development Environment
In the spirit of "Eclipse is You", you should consider naming the project YourLar :-)
Project names in all .project need to be fixed too
The name sounds a lot like Milyn (http://milyn.codehaus.org/).
Yes, thanks Ken, that was pointed out to me very recently (it did not come up in our searches). Here is a portion of the email that I just sent to the lead of that project. I also referred him to this bug. I couldn't tell how active that project was because there were no posts on the mailing list. ------- In our searches we never tried the "Milyn" combination of spelling, however, it looks like pronunciation of our projects are very similar. The full name of our project is "Mylyn - Task-Focused Toolkit" (note that we are still in the process of choosing our descriptive name). Also, we qualify the name as "Eclipse Mylyn" on first use since we are an Eclipse project. So that will help disambiguate things. While our projects are drawing different crowds (and hence we did not pick up on this sooner), I wonder if it would be a good idea to also provide a descriptive name for your project and include that on your homepage?
Status: * Infrastructure changes have progressed well. * The main thing that still remains is eclipsepedia updates and some additional web site updates. * The main thing on the critical path now is bug 192308.
To avoid confusion with milyn, you could do something like what KDE did when they wanted to disavow any association with what the 'K' actually once stood for, and just make it part of the acronym, but never define what it stands for (anymore). Or drop the 'M' entirely. Some ideas: + ETF (Eclipse Task Focus) [not Emergency Task Force] + EFTE (Eclipse Focused Task Environment) [pronounced "efty", like "hefty" or like the ubuntu release] + MTFE (My*** Task-Focused Environment) + MTFT (My*** Task-Focused Tools/Toolkit) [not the Microsoft stock ticker] + EME (Eclipse My*** Environment) [pron. "eem" or "emmy"] + EMT (Eclipse My*** Tasks/Tools/Toolkit) [not Emergency Medical Technician] + MyTE (My*** Task-focused Environment) [pron. "mighty" or "mite"] + MyTEE (My*** Task-focused Eclipse Environment) [pron. "mighty"] + MyFT (My*** Focused Tasks) [not Myst; pron. "miffed"] + FETE (Focused Eclipse Task Environment) [pron. "fett" or "feet"] + FEE (Focused Eclipse Environment) + FREE (Focused Resources in an Eclipse Environment) [the best things in life] + TFEE (Task-Focused Eclipse Environment) [pron. "tee-fee"]
Wow, kool suggestions Nick (I had no idea that the K in KDE stook for "kool" until you prompted me to look). Next week I'll update the list of possible descriptive names (and acronyms) for the project so that we can take a poll. Regarding milyn.codehaus.org, the project lead got back to me and it is looking like this will not pose much of a problem or be a source of confusion, since the users communities appear to have no overlap. The project lead got back to me and said they'll try to put up a descriptive a name as possible. On our end we will make sure to do whatever we can to avoid any ambiguity and accommodate any requests that they may have (e.g. a FAQ entry).
There are still a few spots with the old name. - Europa Welcome Screen (when you start it for the first time, Help Text/Intro) - Notification Pop-Up titled 'Mylar Notifications' - Preferences defaulting to '.mylar' (I know, that one might be tricky due to backward compability with existing projects ;-)
some projects (mainly features) still have old name in .project
Links to old "New and Noteworthy" at http://www.eclipse.org/mylyn/doc/new.php are pointing to the old web site.
There is still about 7800 hits to "mylar" in the code base. Some of them in the copyright header, but there is also some in javadoc comments and in text messages.
Hi there. The Milyn project has been updated to include a descriptive name: "Milyn - Data Transformation & Analysis" Thanks for pointing this out... it prompted me to sort out a logo for the project :-)
Looks like org.eclipse.mylyn.monitor.ui.IMylarMonitorLifecycleListener was missed during the rename.
(In reply to comment #22) > There is still about 7800 hits to "mylar" in the code base. Some of them in the > copyright header, but there is also some in javadoc comments and in text messages. Renames that were pending the Europa release are now done. There are still 817 references to "mylar" in source and resource files, but these are legacy references that need to remain (e.g. old test data). (In reply to comment #23) > Hi there. The Milyn project has been updated to include a descriptive name: > "Milyn - Data Transformation & Analysis" Tom: thanks that's good to hear. I really like the stylized spelling that you used :) (In reply to comment #24) > Looks like org.eclipse.mylyn.monitor.ui.IMylarMonitorLifecycleListener was > missed during the rename. Yes, this is the one type name that we missed renaming. I have added it as a pending change for 3.0: http://wiki.eclipse.org/Mylyn_Porting_Guide
Slightly unrelated, but since you are changing everything anyways, some of the projects have repository templates that refer to ubc copyright, which doesn't seem right at least for some of them (I don't think jira was ever owned by ubc).
The rename is now complete. Any remaining references that are found can be submitted to this bug report or as separate bugs. (Eugene: I'm about to commit updates to the templates, they will all be the standard copyright header that you see on other source files). What remains to be done is to come up with a descriptive name for the project (comment#11). The last set of options listed are as follows. Note that these will not be used in acronym form, should not contain the word "Eclipse" and need to follow the guidelines at: http://www.eclipse.org/projects/dev_process/project-naming-policy.php 0) Task-Focused UI 1) Task-Focused Toolkit 2) Task-Focused Tools 3) Task-Focused Development Tools 4) Task-Focused Development Environment 5) Task-Focused Environment (0) is what we have been using to date but I'm wondering if we can improve on it. Upon further consideration (3) and (4) are problematic because a key aspect of Mylyn is that it provides a framework to that non-IDE applications can build on and integrate with. While the benefit of (2) and (5) are the most user-centric names, it has always sounded weird to me in part because it is plural and in part because it sounds overly generic. I definitely like "Toolkit" but have concerns that it could be wierd for non-plugin develops for whom Mylyn is more a tool than a toolkit. Then again, Toolkit does get used more broadly and this word does a good job at describing what we are. Could all interested please vote for their favorite or add any suggestions that I may have missed?
> 2) Task-Focused Tools +1 (for the shortness of the name and the consistency with other Eclipse project names)
You've missed to review and apply about 6 patches that were waiting for review before doing this last massive change.
> 2) Task-Focused Tools +1 as I hate toolkits. 0) is nice, too.
+1 Task-Focused Tools
(In reply to comment #29) > You've missed to review and apply about 6 patches that were waiting for review > before doing this last massive change. Most patches should not have been affected by this change and I should be through most of those already.
On http://wiki.mozilla.org/Bugzilla:Addons Under IDE integration the wiki is still using the Mylar name.
Done for 2.0.
