>>We already fixed several major bugs (especially working on several >>repositories and branches) and made also some usability enhancements. Great, so why don't you ask Zingo for access to push them into the main repo?
The following statements you made make me believe you're rather taking the project out of Zingo's hands than contributing to it: >>We will probably launch a version end of November and will provide more >>information about our road-map >>the plugin remains OPEN-SOURCE and FREE. Who's giving you the right to decide when a new version of MercurialEclipse is released, let alone deciding whether our project remains open source or not? Did Zingo transfer the project leader role to your company? I couldn't care less if you gave your project another (distinct) name but you're calling it HgEclipse. Don't get me wrong. I haven't contributed anything to ME so far but I'm using it and following the discussions here right from the start. I really like the way MercurialEclipse was being developed on so far, i.e. with a few people managing releases and keeping resources (wiki) up-to-date and a greater mass just contributing patches and new features, and just would love to see that continue instead of having a company taking control of the project. And of course the plugin will remain open source, anyone claiming the opposite should take a deep look at the license agreements of the EPL. I hope I didn't miss anything and am up-to-date, otherwise just forget about my post. ;) On Nov 2, 5:10 pm, "[email protected]" <[email protected]> wrote: > Dear MercurialEclipse users, > > my name is Zsolt Koppany ([email protected]) and I am the CTO > of Intland Software. > > First of all lot of thanks to people who developed/contributed the > MercurialEclipse plugin. > > Intland decided enhancing the plugin to be used in core development at > Intland and other Mercurial users. Why that is being done on > javaforge? Because this is our standard environment for OPEN-SOURCE > projects. > > First of all: the plugin remains OPEN-SOURCE and FREE!!!! Sorry about > some commits that might caused some misunderstandings! > > We haven't announced anything about this project yet and didn't think > that our OPEN project on javaforge would be discovered so fast and > thought having more time to explain the goals, targets and objectives > of the project. > > The plugin itself AND also our product codeBeamer are developed ONLY > and ONLY using Mercurial as source code repository. I don't know why > somebody thought that we use Subversion for the plugin development. > Javaforge supports Subversion (and most projects are in Subversion) > but also Mercurial, Git and CVS. > > We already fixed several major bugs (especially working on several > repositories and branches) and made also some usability enhancements. > > We will probably launch a version end of November and will provide > more information about our road-map but again: the plugin remains OPEN- > SOURCE and FREE. > > Please don't hesitate contacting me with your questions > > Zsolt Koppany > Follow @intland on Twitter:http://twitter.com/intland > Phone: +49-711-67400-679 > -- > Intland Software, Curiestr. 4 > D-70563 Stuttgart, Germany > Phone: +49-711-67400-677, e-mail:[email protected] > Fax: +49-711-67400-686 > > On Nov 1, 7:05 pm, "Zingo Andersen" <[email protected]> > wrote: > > > Hi > > > rupert.thurner wrote: > > > > hi, ismercurialeclipsenowbecomingproprietory software with > > >hgeclipse,http://javaforge.com/project/HGE, see the commit trail > > > here:http://javaforge.com/proj/sources/sccBrowseCommits.do?proj_id=2828, > > > and one example here: > > >http://javaforge.com/scmShowFileRevision?proj_id=2828&filename=test%2.... > > > > saying: > > > This software is the confidential andproprietaryinformation of > > > > very interesting style of opensource contribution. now one can easier > > > understand why matt mckall was so angry last time when people asked to > > > relicense mercurial to facilitate eclipse integration, see > > >http://groups.google.com/group/mercurial_general/browse_thread/thread.... > > > Janos Koppany (Intland) has been in contact with me asking if they could > > partitipate and as I > > understand from the discussion we had he agreeing to keep it EPL so I think > > this is just a standard > > company header that went in by mistake. > > > He also asked if the main reposetory could be put on javaforge in the > > future since they can host > > it there and it will be easier for them (is it a goof hosting site?) This I > > think will be a we a > > discussion that we shall take in the future and not know. > > > I have asked him to push back the stuff they make in there repository and I > > hope this will happen > > soon as they seem to have done some work there. And it might hinder others > > to start work in the > > main repo. Currently they are treated like any other contributer in the way > > that it will probably > > go into the main repo if it is good. > > > And I'm proud of what mercurialeclips has become and how many people uses > > this software today > > last release had about 15000 downloads,(I don't know if any of them are > > index-spiders, I counted on > > the .jar file). The thanx for this goes mostly to all that contributers as > > I should never been > > able to take it this far myself just look at the number of commits by me > > and by others at ohloh: > > >https://www.ohloh.net/p/mercurialeclipse/contributors > > > > and, it is hosted in subversion ..... > > > This is obvius something that probably need fixing before a "main-repo" > > switch can come into question or at least discussed alot to we get tired > > of that discussion :) > > > -- > > Zingo Andersen (zingo.org and vectrace.com) > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MercurialEclipse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mercurialeclipse?hl=en -~----------~----~----~----~------~----~------~--~---
