Community
Participate
Working Groups
There's a few issues in administering an Eclipse installation for multiple users that are not immediately apparent. Looking at the site, there's a total lack of information on the subject of actually deploying the IDE. The specific elements I would like to see addressed: Per-user plugin/feature directories on Windows or Unix, shell variable interpolation where appropriate, creating a new plugin site, etc... This information exists, but it is currently not aggregated in any useful way. I'd write it, but I'm looking for the answers to those questions.
Sounds like a good idea for an article. Although one of the Eclipse Themes is Enterprise-Ready, there's not much that covers what that means or how it's done.
Any takers to write this one yet?
Marking REMIND for housekeeping purposes.
From EclipseCon, it looks like we should maybe ask Michael Pellaton (http://www.eclipsecon.org/2006/Presenters.do?id=all#208) and the four gentlemen from the "Enterprise Ready: Deploying Eclipse in Large Enterprises" presentation (http://www.eclipsecon.org/2006/Sub.do?id=306) to chip in on a document for this.
I thought about writing at least parts of this article when I prepared my short talk, but I did not yet have time to do so. I suggest to first discuss briefly the topics that shall be covered and the structure of the article.
I work with Pär Emanuelsson at Ericsson (one of the panelists), so I can participate in the discussions. Here are some suggestions of topics that the article can deal with: - Eclipse Multiplatform Installers - Eclipse Plug-in Management and Certification - Eclipse Local Update Sites - Eclipse User Profiles and Common Preferences - Eclipse Remote Management - Eclipse Local Helpdesk Setups - Eclipse Local Knowledge Base Setups (Wikis)
I mostly agree, but I would clearly distinguish between Eclipse-technology related topics and others. I think wikis, newsgroups, helpdesks and so on are not Eclipse specific and there might be better places to find information about them. I agree that they are all crucial to a successful introduction of almost every software in a company, but they are not closely related with Eclipse. Why don't write two articles - one as a technical 'howto' describing what Eclipse offers and how it can be used and another one about processes in companies, support, building an 'inhouse community' and so on? Even mroe splitting might make sense as some topics are not only interesting in the scope of administration: update sites for example - I think there is enough to say about them to fill an entire article.
Doesn't appear to be any activity on this. Reopen if this changes.
LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Closing as WONTFIX. Reopen if you get the energy required to address this.
