Bastian Doetsch wrote: >what do you think about trying to get a Google Summer of Code project >on the way?
Cool idea, I never thought the project would grow so big that we would be able to pull something like this off. But we have. > Some ideas would be: > - Mylyn integration > - Improving synchronize view (structural compare, visualization of the dag) => could use some of Brian Ws stuff Or even help Brian W to get a versiontree that ALL other tools could only dream of :) > - Extensive support for pbranch, attic extensions Are there other extentions that people use? >- Native Java implementation of mercurial (If I remember right, there >was a project called HGKit) Christian, are there special operation you hope will get faster with this. Label decoration comes to mind? As I only use mercurialeclipse on small projects I don't see the big scaling problems (sorry for that). Maybe the GSoC project should be "speed optimizeing X". One idea could be that we write some mercurial extension ourself just to improve mercurialeclipse in various ways. >- FreeHG (or other hosting services) integration: Create a new >repository (and maybe even a account) transparently from Eclipse. > And/or bitbucket.org. I also like this, maybe even some alien-subversion hosting sites hgsubversion support. To help people to not need subversion at all. We could just make a list of a few and make one(or a few) mandatory and the other optional. One thing that also spings to mind after reading the long threads on mercurial mailing list lately on popularety of mercurial compared to bzr/git is if there are some "heavy" workflow issues that we might be able to solve/ease up to make mercurial in general seem the nice solution for project developing/managements then that is a good thing. Some Ideas above make this happen. Are there other ways we could help mercurial to get "World Domination" or at least little better credit out there? Here is some other brainstorming ideas that need more "meat on the bones" the first one is the one I like most of the one below the other two is kind of "fluffy" but Ill list them anyway as someone might have some ideas about them. - patchflow * import patches from trac/bugzilla tickets with a gui (via mylyn maybe? I have not looked at mylyn for a while) * support some "send change for review" workflow. Most places where I worked you need to have you your changes review'ed by a colleague before pushing it. and there is usually no "integrator" review'ing and pulling the changeset into the "main" branch that is handled by the developer after his changest got approved. I have no idea on howto make this easier. - release management * A make release menu item that Change some file according to a template (version number in the manifest) commit, autogenerate a tag, commit tag, if its a eclipse plugin, generate a feature with the same version number and generate a release. Auto update version on Eclipse Plugin Central ... (it's not hard today just many smal steps maybe not worth it probably totaly different for different project What kind if steps do you need in your project) -- Zingo "Stefan" 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 -~----------~----~----~----~------~----~------~--~---
