Help Wanted

[jorn]

I concurr - of the same reasons as c-yro. I must also place myself in the same boat as him with reagrds to experience and skills. I know the basics well enough to set up and get it compiling, adding the occational extension to already existing code and such. I've also considered looking terminals, but it seems to be pretty dead as well (also I have no experiece whatsoever with c# )...

What worries me about mremoteng though, is that we might end up with loose ends and code noone knows or understands - like adtree.dll, I don't think the source there is availiable, no?

Anyways: I'm willing to parttake and spend some time where I can, but I don't feel compentent to lead either..

[rmcardle]

I think that's a good idea. Perhaps Andreas, Alex, Jorn and I could work together to manage the project?

Even if you don't have a ton of experience coding, there's plenty of other stuff to do. Replying to E-Mails, replying to posts on the forum, keeping track of bugs and new feature requests, adding/updating website content, keeping track of the translations and communicating with the translators, improving documentation, find beta testers and manage testing, etc., etc.

Also, as far as adtree.dll and other components, I went through everything and found copyright information and where the components came from. All of that information is in . The only component that was closed source is "Emergent OnLine WTSCOM". At some point we will have to write a replacement for that. I attempted to contact the current owner of the intellectual property to request explicit permission to use and distribute it but they never responded.

[jorn]

Great news friends!
Let's get this going

So I've created an account at github and "forked the tree" to create my own branch - it seemed to be the logical thing to do but from here on out I'm fairly blank... what git client do you reccomend? do you select the changed files and upload them, or does the client figure it out? what about the fork-queue, are those pending patches that haven't been integrated in the master yet?

[peltco]

You made any changes jorn?

anyone else got any changes?

I got some sponsorship to work on mremote so i'm collecting changes if noone else is doing so

[peltco]

Some things i'll be working on (the goal is to make good progress on in the next 12-16 months, and nothing set in stone)

- Passing of console sessions (instead of just stealing a console session away from someone to give a more gentle nudge to an other mremote user that they can take it)
- remote mremote files (be able to have mremote connection files be located at a remote location and just insert a URL in mremote
- tied to the above, credential management for all those having access to the remote mremote file.
- preprogram some common external tools
- time logging, log which connections where used when and for how long. also make it optional to see how you've been using a connection easily (like in the tab tied to the specific connection)
- investigate possibility of multi monitor remote connection
- long term, dual view, allow two mremote viewers to share a single connection

and of course anything else that comes up as more urgent.

[phil]

[peltco]

right now you can click "new external tool" (right mouse button)
i was thinking about making on option "new predefined external tool" which would show a list of maybe 5 or 10 'best picks" that would add the tool to your list. preferably ones that are based on common windows components or programs used in our company (i admit, i'm a bit biased here)

[phil]

That would do, but, in the longer term, the option to enable/disable specific external tools would be the way to go.

[jorn]

The changes I've made are pretty minor.
I added another option to the parser for ExternalPrograms %userAndDomain% that replaces with domainname\username (useful for executing psexec and similar tools). Also I extended the ADimport with an option to search the subtree, and to import only servers.
thing is I've never used git so I'm not very certain as to how commits and such are done. I guess I could make a patch first and email you, so we can get a interim-release with combined efforts so far?

(edit: I dunno how licensing would work, but shipping psexec together with mRemoteNG or enabeling some downloadFromSysInternals option would make it possible to have a checkbox on the ExternalPrograms list for "execute on remote host" - which I think would be incredibly helpful in lots of situations)

[thrilleratplay]

For the past year I have been independently working on modifying the source for mRemote for my position. When Googling for more information about vncsharp I stumbled upon mRemoteNG. I wish I came across it sooner. Many of the changes I made to my version were either completed in mRemoteNG or were geared to my work. The only useful two features I had in added were replacing putty with puttycyg to for cygwin connections and the addition of the InputSimulator library for saved command line snippets typed by double clicking a node in a tree view. As of a few days ago I have stopped work on my version to aid in mRemoteNG. Currently I am working on a .net control to replace Putty. See the post here viewtopic.php?f=3&t=1392#p1885 for more detail on this.

Reading through the help wanted topic, I get the sense that everyone thinks this is a worthy and valuable project to continue but do not have the time to devote to it and have lost interest as the development slowed. I also see that no one wants to be the project leader as they do no have the experience. I too fall into this category but feel mRemote is a needed too useful to let die again. I will volunteer to be the interim project leader if no one else will. Please keep in mind I have no experience, but if everyone else is a green as I am to open source projects and we help each other I think mRemoteNG has the potential to be far better than it currently is.

To give a quick outline of what should come next:
*replace putty- I'm on it
* replace translation code with reading from XML files and have a quick one off VB program to edit and generate this files for mRemoteNG- Does anyone want to volunteer for this? I will do it afterward the putty replacement, but it won't be for a bit of time.

Further along:
*replace out of date libraries-particularly the panel libraries. I would like to have this far more versatile (create independent windows, tabs drag and drop between panels,etc)
*Add in more supported connection types-VMware comes to mind. Defiantly Dos prompt
*remote conf files
*faster port scanner
*native support for all versions of mremote and memoteNG conf files (The user shouldn't needs to meddle around with this, it should be completed programmaticly and without user intervention)
*updates via mRemoteNG.org

pipedreams:
*plugins-all connection are plugins and add in what is needed per user. This would require a code overhaul.


I will do what I can but can not do this alone. Who is still on board to aid in development? user support? anything?