Community
Participate
Working Groups
Please help find Eclipse project that would help onboard StartExplore project. The StartExplorer Eclipse plug-in offers tight integration of the system file manager (Windows Explorer, Gnome Nautilus, KDE Konqueror, Mac Finder, ...) and the shell (cmd.exe, Linux/Mac terminal) in Eclipse. It's APIs are used in PyDev. Author (and some other people) would live to contribute to Eclipse https://github.com/basti1302/startexplorer/issues/64
This is not a bug for Platform UI.
> This is not a bug for Platform UI. This is like saying "now, stupid user, try to guess which one of 200+ Eclipse projects your bug should be raised against"(In reply to Lars Vogel from comment #1) Please point to the right direction.
I think "Community, process" might be a home for this bug. I am assuming you are asking "how can this be proposed as a new Eclipse project"? If instead, you are asking "what project would this code be good in" ... then, that is a tough one to answer. I doubt anyone could really tell without extensive studying of your proposed contribution. We normally rely on originator "making proposals" and then they are assessed. By putting into "Community, Process", I'm mostly asking if Wayne has any (more) advice?
(In reply to Paul Verest from comment #0) > Author (and some other people) would live to contribute to Eclipse > https://github.com/basti1302/startexplorer/issues/64 I will also add, from the briefest reading of this "Maintainer wanted" discussion is seems like you are saying that you (or someone?) can no longer maintain the code, so you'd like to contribute it to Eclipse, and then someone else can maintain it. If I am reading that right, that's not a good reason to start a project at Eclipse. Has never worked, the few times I've seen people try it. You need to find a maintainer first, and that person must commit to maintaining the code. That said, yes, Eclipse is a great place to "build a community", but, you need some core people who are committed to doing the work, before it can become a project, or, even, a large contribution to an existing project. Hope that helps set expectations,
(In reply to David Williams from comment #3) > By putting into "Community, Process", I'm mostly asking if Wayne has any > (more) advice? Probably the right thing to do as I have the broadest view of the project landscape. I am investigating.
(In reply to Wayne Beaton from comment #5) > I am investigating. FYI - Please check also the discussion on https://github.com/basti1302/startexplorer/issues/64. AFAICS it indicates that most of the functionality of the plug-in is already available via another projects.
(In reply to Lars Vogel from comment #6) > FYI - Please check also the discussion on > https://github.com/basti1302/startexplorer/issues/64. AFAICS it indicates > that most of the functionality of the plug-in is already available via > another projects. Thanks Lars. I didn't know about _Show In > System Explorer_; that's my new favourite thing. It looks like there's a lot of great ideas in here. But I can see how the contribution in its entirety is difficult to accept. Ideally, it would be great if somebody could step through the various features and sort out how to use the ideas and implementation to improve what's already there. e.g. add a keyboard short cut for _Show In > System Explorer_. We can then sort out what to do with what's left. Doug's been kicking around the idea of a valuable-IDE-stuff-that-doesn't-fit-elsewhere project ("Eclipse Commons") and this might be the right kind of kick to get that started. This might be a good topic for the Hackathon at EclipseCon Europe. e.g. first turn this into a collection of bug reports each targeting some specific subset of the functionality, and then start creating contributions for them. At some point, we may want to consider moving this to the EclipseLabs GitHub organization and changing the names space to org.eclipselabs.* (it's probably best that we resolve the above first). Doing that will at least free it from Bastian's account. Paul: What do you think the prospects are of changing the license to EPL? The current state of code ownership has an impact here (i.e. all the current copyright holders would have to agree to changing the license). AFAICT, there are five distinct authors; have they signed any contribution agreement? Alternatively, how good are our prospects for contacting them to ask permission to use/change their contributions? Are any of the current authors interested in continuing in the development of this functionality?
As I commented on https://github.com/basti1302/startexplorer/issues/64#issuecomment-140122808 I think trying to bulk move startexplorer into eclipse is not the right path. Alot of startexplorer overlaps with features found in eclipse platform and as noted on the github issue eclipse platform already covers a lot of it and could be improved with a few specific bugfixes/feature improvements. Needs someone to "carry" it in though.
Could not be eclipselabs on GitHub a new home for this codebase? https://github.com/basti1302/startexplorer/issues/64#issuecomment-140342665
(In reply to Max Rydahl Andersen from comment #8) > Alot of startexplorer overlaps with features found in eclipse platform and > as noted on the github issue eclipse platform already covers a lot of it and > could be improved with a few specific bugfixes/feature improvements. Agree. > Needs someone to "carry" it in though. As I suggested, I'll look at this as part of the Hackathon at EclipseCon Europe. We can at least start that process. (In reply to Jeremie Bresson from comment #9) > Could not be eclipselabs on GitHub a new home for this codebase? > https://github.com/basti1302/startexplorer/issues/64#issuecomment-140342665 Sure. Moving the repo is pretty simple. I think that we'd want to change the package and bundle namespace as well. While moving it to EclipseLabs does get us closer to being an Eclipse project, it still doesn't make getting the code into our downloads any easier. The harder work of chopping it up and bringing in the pieces will still need to happen for that.
(In reply to Jeremie Bresson from comment #9) > Could not be eclipselabs on GitHub a new home for this codebase? > https://github.com/basti1302/startexplorer/issues/64#issuecomment-140342665 Just as you like when you step-in. For license issue Bastian Krol was saying to be ready to spend time. Even to refactor code for eclipse.org It is about finding new developer as of now. Please see also summary with pictures and links at https://github.com/basti1302/startexplorer/issues/64#issuecomment-140764586
Hi folks, Wayne's ideas on how to move this forward sound pretty good to me. Although, tbqh, I can also totally understand Davids position - nobody wants to inherit a pile of unmaintained code and just pushing it somewhere into an Eclipse repository without having a maintainer would probably not be a smart move. If something comes out of the hackathon idea or if StartExplorer is chopped up and pieces of it can be recycled for features in other projects, I'd be more than happy to support this (assist with necessary refactorings, answer questions, etc.). If for some reason this does not work out I would like to point out that the current status quo is also kind of okay. I never intended to completely abandon the project. I still do bug fixes from time to time (if they are not too time consuming) and I also merge pull requests. I'm just not using Eclipse myself anymore so my interest in StartExplorer is pretty low and if someone else would like to take over, I'd also be fine with it. Regarding the license issue: I guess this should not be a showstopper. Two of the original committers are me and Paul. I can sign a CLA if that helps. Of course I agree to change to EPL, I assume Paul also ;-) Another person listed on https://github.com/basti1302/startexplorer/graphs/contributors just made some minor doc changes, these docs are largely irrelevant when StartExplorer is dissected. This leaves two authors (of rather minor changes), chances are, we can get an agreement from them. Not sure if they'd sign a CLA for five or ten lines of code. Kind regards Bastian
> Regarding the license issue I'm also a contributor (sleicht) and also an eclipse commiter. From me also no objection to change the licence to epl.
The plug-in has found a new maintainer now. Since nothing has moved with respect to integrating parts of this into Eclipse core and there was also no real consensus about this, I'd say this can be closed.
