[jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools?

Fri May 30 04:25:27 EDT 2014

Hello All

I feel a bit uncomfortable posting to email list and not knowing how many people are reading and whether they really like reading what is a bit off-topic for JBoss dev list. With Mickael's encouragement I go on.

I am actually familiar with Eclipse process, but not with details as I have not practiced it.

I have signed CLA (not connected to any project),
but that was to not look like a outsider/stranger,
as I noticed quite often communication goes between eclipse committers that seems to know each other well,
while some post from users (in some project) may be overlooked.
That of course has its reason as often those bugs are not of good examples of problem reporting.
=> Instead of showing CLA tags that divides users into 2 categories, it would be better to have link to Eclipse profile,
where it could be seen for example that the person is contributor in those project or is active on Eclipse forums etc.

I was not contributing to Eclipse because
- there are no company to support that time (usually there should be some business that is interested to having base support for a technology as an Eclipse project)
- was mostly looking for quick solutions that would work, improve something or give value to end users
=> now looking for way to have some financial background for the Nodeclipse project
http://www.linkedin.com/groups/Nodeclipse-project-is-looking-partners-2906459.S.5877307858806136835

> What do you want to do?
> What is the question you're seeking answers for?

I have been contributing to several others projects. But at some point I decided to do it only for project that are on GitHub
- less overhead with other tech, like SVN on SourceForge
- I noticed that the project that are more on GitHub are generally more active than on SourceForge, Google Code, Apache
- GitHub is simpler and more transparent than other code repositories
- I can't be master of all trades, so I need to have some limit of scope for the projects.

> It may sound harsh, but I have the impression that many people just
    take the process as an excuse for not contributing, without having
    even evaluated the difficulty of adopting it or even tried it. I've
    sometimes heard "it's not on GitHub, I don't know how to contribute,
    so I don't contribute". In such case, it's also the responsibility
    of the developer to learn things and ask for questions in order to
    become a contributor.

    The Foundation isn't to blame. People who want to do things can do
    them, that's all that matters.
>

yes, that may be the case for some.
As there can't be one step solution to address precess issue, I think some discussion can help.
Also experiments like Eclipse project on GitHub  may find some better approaches.

There are some plugins that actually should be as Eclipse plugin, like
https://github.com/eclipse-color-theme/eclipse-color-theme/

This conversation may continue in some action with
https://github.com/hendrens/jdt.spelling/issues/13

Best regards,
Paul

    Date: Fri, 23 May 2014 11:14:39 +0200
From: mistria at redhat.com
To: paul.verest at live.com; manderse at redhat.com
CC: angelo.zerr at gmail.com; jbosstools-dev at lists.jboss.org
Subject: Re: [jbosstools-dev] Eclipse process vs just OSS RE: Nodeclipse IDE (or components) in JBoss Tools?

    On 05/23/2014 10:20 AM, Paul Verest
      wrote:

      Eclipse process adds a few steps
        - signing CLA [link]
        - setting up project on Github [link], Ecipse git [link]

    Most projects have an "How to contribute" or equivalent page where
    this is usually clearly explained.

    Many projects use the same development tools/workflows
    (Bugzilla/Gerrit/Git/Jenkins) so you only have to learn it once.

    If you need assistance on how to contribute, projects have open
    communication channels where this can be asked.

        I have never contributed to Eclipse project,
        so I don't know exact steps.

    What would be interesting is to first know if you tried, and if yes,
    where were you blocked ?

    In many cases, just trying is enough to accomplish something.

        http://www.eclipse.org/committers/
        I did not really know what to search.
        Eclipse has a lot of resources in many places with
          different level of relevance.

    What do you want to do?

    What is the question you're seeking answers for?

    It may sound harsh, but I have the impression that many people just
    take the process as an excuse for not contributing, without having
    even evaluated the difficulty of adopting it or even tried it. I've
    sometimes heard "it's not on GitHub, I don't know how to contribute,
    so I don't contribute". In such case, it's also the responsibility
    of the developer to learn things and ask for questions in order to
    become a contributor.

    The Foundation isn't to blame. People who want to do things can do
    them, that's all that matters.

      Well. That was discussion between the person who
        knows (Max)
        and the person who didn't see what he had imagine (Paul).

        Now I know how to start and where to ask when needed.

    Your feedback has a lot of value. It can be used to make the process
    and tools easier to understand and use, which is the main way to get
    more people contributing.

    The contribution process is a forever-evolving one, because of new
    constraints, new ideas, new tools, new technologies... You can use
    this bug to suggest some improvements to this process
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=435599

    Cheers,

    -- 

      Mickael Istria

      Eclipse developer at JBoss,
        by Red Hat

      My blog - My Tweets 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140530/df074d2b/attachment.html 