You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Christian Müller <ch...@gmail.com> on 2011/08/02 22:45:42 UTC
[DISCUSS] Supporting our users to be more involved with our project
Hello!
I love to see as we asking our users to be more involved with our project.
I would like to add the label "Contributor" or "Beginner" (or something
similar) to issues which are easy to be resolve (by interested
users/customers). We should not fix these issues so soon (unless it's an
urgent fix) to get the users/customers the chance to pick them up, adding a
comment that other knows they are working on this issue and providing a
patch for it. I could create a view in JIRA which lists all open issues with
this label and add a link from the contributing page [1] to this view. I
think then it is much more easier for our users/customers to "being more in
touch" with our project and evolve from a user to a contributor to ...
I know what this is for a great feeling to see its own (first) patch
committed, to add his name to the team page [2] later, ...
What do you think?
[1] http://camel.apache.org/contributing.html
[2] http://camel.apache.org/team.html
Best,
Christian
Re: [DISCUSS] Supporting our users to be more involved with our
project
Posted by "E.Gherardini" <e....@hotmail.com>.
Hi,
I would personally love it, since I am willing to contribute.
I started developing a new component, but having also the change to join the
project resolving small tasks/issues (without the need to harass devs on
chat asking advices to avoid doing big mistakes...which I did indeed ;) )
would be lovely.
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Supporting-our-users-to-be-more-involved-with-our-project-tp4660329p4660526.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] Supporting our users to be more involved with our project
Posted by Zbarcea Hadrian <hz...@gmail.com>.
Christian, couldn't agree more! The best way for us to help is to add a few pointers and review patches and provide feedback.
We could probably use this process to improve the documentation as well. Contributions welcome!
Hadrian
On Aug 2, 2011, at 4:45 PM, Christian Müller wrote:
> Hello!
>
> I love to see as we asking our users to be more involved with our project.
>
> I would like to add the label "Contributor" or "Beginner" (or something
> similar) to issues which are easy to be resolve (by interested
> users/customers). We should not fix these issues so soon (unless it's an
> urgent fix) to get the users/customers the chance to pick them up, adding a
> comment that other knows they are working on this issue and providing a
> patch for it. I could create a view in JIRA which lists all open issues with
> this label and add a link from the contributing page [1] to this view. I
> think then it is much more easier for our users/customers to "being more in
> touch" with our project and evolve from a user to a contributor to ...
>
> I know what this is for a great feeling to see its own (first) patch
> committed, to add his name to the team page [2] later, ...
>
> What do you think?
>
> [1] http://camel.apache.org/contributing.html
> [2] http://camel.apache.org/team.html
>
> Best,
> Christian
Re: [DISCUSS] Supporting our users to be more involved with our project
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
FYI,
in Karaf and ServiceMix, we added the low-hanging-fruit Jira tag to
classify the Jira "easy" to fix.
Regards
JB
On 08/03/2011 06:34 AM, Taariq Levack wrote:
> +1
>
> This is great stuff, it will be really helpful to see the estimated
> complexity, because we often don't have the full picture of the issue
> immediately and some are on much more limited time than those
> dedicated half or full time to the project.
>
> Taariq
>
> On Wed, Aug 3, 2011 at 3:24 AM, Daniel Kulp<dk...@apache.org> wrote:
>> On Tuesday, August 02, 2011 10:45:42 PM Christian Müller wrote:
>>> Hello!
>>>
>>> I love to see as we asking our users to be more involved with our project.
>>
>> +1
>>
>>
>>> I would like to add the label "Contributor" or "Beginner" (or something
>>> similar) to issues which are easy to be resolve (by interested
>>> users/customers).
>>
>> In CXF, we have a custom "Estimated Complexity" field on the issues. I went
>> ahead and added that field to the Camel project for now for you to take a
>> look. We can always remove it if you prefer a label approach. :-)
>>
>>
>>> We should not fix these issues so soon (unless it's an
>>> urgent fix) to get the users/customers the chance to pick them up, adding a
>>> comment that other knows they are working on this issue and providing a
>>> patch for it. I could create a view in JIRA which lists all open issues with
>>> this label and add a link from the contributing page [1] to this view. I
>>> think then it is much more easier for our users/customers to "being more in
>>> touch" with our project and evolve from a user to a contributor to ...
>>>
>>> I know what this is for a great feeling to see its own (first) patch
>>> committed, to add his name to the team page [2] later, ...
>>>
>>> What do you think?
>>
>> I'm COMPLETELY in support of this. From experience, it's extremely hard to
>> "learn" though and will take a conscious effort, especially from the code
>> leaders of a project. I know in CXF, it took me a LONG time to learn to not
>> just fix things immediately and instead say "Good idea, care to submit a
>> patch?" In general, I had to force myself into a mode of letting things sit
>> a bit. A week or so before a release, I'll run through things that have been
>> sitting and fix any "low hanging" things real quick just to get the fixes in
>> and keep the bug count down, but I definitely try to ask for patches a LOT
>> more often than I used to. At this point, I consider it a good day if I spend
>> more time reviewing and applying patches than fixing issues. That's a good
>> thing. :-) Yes, in many cases, it probably takes less time for me to just
>> fix the issue than to help someone, review a patch, etc.... However, it's
>> better for the community.
>>
>>
>> Dan
>>
>>
>>>
>>> [1] http://camel.apache.org/contributing.html
>>> [2] http://camel.apache.org/team.html
>>>
>>> Best,
>>> Christian
>> --
>> Daniel Kulp
>> dkulp@apache.org
>> http://dankulp.com/blog
>> Talend - http://www.talend.com
>>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] Supporting our users to be more involved with our project
Posted by Taariq Levack <ta...@gmail.com>.
+1
This is great stuff, it will be really helpful to see the estimated
complexity, because we often don't have the full picture of the issue
immediately and some are on much more limited time than those
dedicated half or full time to the project.
Taariq
On Wed, Aug 3, 2011 at 3:24 AM, Daniel Kulp <dk...@apache.org> wrote:
> On Tuesday, August 02, 2011 10:45:42 PM Christian Müller wrote:
>> Hello!
>>
>> I love to see as we asking our users to be more involved with our project.
>
> +1
>
>
>> I would like to add the label "Contributor" or "Beginner" (or something
>> similar) to issues which are easy to be resolve (by interested
>> users/customers).
>
> In CXF, we have a custom "Estimated Complexity" field on the issues. I went
> ahead and added that field to the Camel project for now for you to take a
> look. We can always remove it if you prefer a label approach. :-)
>
>
>> We should not fix these issues so soon (unless it's an
>> urgent fix) to get the users/customers the chance to pick them up, adding a
>> comment that other knows they are working on this issue and providing a
>> patch for it. I could create a view in JIRA which lists all open issues with
>> this label and add a link from the contributing page [1] to this view. I
>> think then it is much more easier for our users/customers to "being more in
>> touch" with our project and evolve from a user to a contributor to ...
>>
>> I know what this is for a great feeling to see its own (first) patch
>> committed, to add his name to the team page [2] later, ...
>>
>> What do you think?
>
> I'm COMPLETELY in support of this. From experience, it's extremely hard to
> "learn" though and will take a conscious effort, especially from the code
> leaders of a project. I know in CXF, it took me a LONG time to learn to not
> just fix things immediately and instead say "Good idea, care to submit a
> patch?" In general, I had to force myself into a mode of letting things sit
> a bit. A week or so before a release, I'll run through things that have been
> sitting and fix any "low hanging" things real quick just to get the fixes in
> and keep the bug count down, but I definitely try to ask for patches a LOT
> more often than I used to. At this point, I consider it a good day if I spend
> more time reviewing and applying patches than fixing issues. That's a good
> thing. :-) Yes, in many cases, it probably takes less time for me to just
> fix the issue than to help someone, review a patch, etc.... However, it's
> better for the community.
>
>
> Dan
>
>
>>
>> [1] http://camel.apache.org/contributing.html
>> [2] http://camel.apache.org/team.html
>>
>> Best,
>> Christian
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
> Talend - http://www.talend.com
>
Re: [DISCUSS] Supporting our users to be more involved with our project
Posted by Daniel Kulp <dk...@apache.org>.
On Tuesday, August 02, 2011 10:45:42 PM Christian Müller wrote:
> Hello!
>
> I love to see as we asking our users to be more involved with our project.
+1
> I would like to add the label "Contributor" or "Beginner" (or something
> similar) to issues which are easy to be resolve (by interested
> users/customers).
In CXF, we have a custom "Estimated Complexity" field on the issues. I went
ahead and added that field to the Camel project for now for you to take a
look. We can always remove it if you prefer a label approach. :-)
> We should not fix these issues so soon (unless it's an
> urgent fix) to get the users/customers the chance to pick them up, adding a
> comment that other knows they are working on this issue and providing a
> patch for it. I could create a view in JIRA which lists all open issues with
> this label and add a link from the contributing page [1] to this view. I
> think then it is much more easier for our users/customers to "being more in
> touch" with our project and evolve from a user to a contributor to ...
>
> I know what this is for a great feeling to see its own (first) patch
> committed, to add his name to the team page [2] later, ...
>
> What do you think?
I'm COMPLETELY in support of this. From experience, it's extremely hard to
"learn" though and will take a conscious effort, especially from the code
leaders of a project. I know in CXF, it took me a LONG time to learn to not
just fix things immediately and instead say "Good idea, care to submit a
patch?" In general, I had to force myself into a mode of letting things sit
a bit. A week or so before a release, I'll run through things that have been
sitting and fix any "low hanging" things real quick just to get the fixes in
and keep the bug count down, but I definitely try to ask for patches a LOT
more often than I used to. At this point, I consider it a good day if I spend
more time reviewing and applying patches than fixing issues. That's a good
thing. :-) Yes, in many cases, it probably takes less time for me to just
fix the issue than to help someone, review a patch, etc.... However, it's
better for the community.
Dan
>
> [1] http://camel.apache.org/contributing.html
> [2] http://camel.apache.org/team.html
>
> Best,
> Christian
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
Re: [DISCUSS] Supporting our users to be more involved with our
project
Posted by "E.Gherardini" <e....@hotmail.com>.
Christian Mueller wrote:
>
> The "easy to resolve" issues have the Novices annotation.
> Dan created and shared the new JIRA view which is called "Camel-Novice"
> [1].
> I have linked this page from our contribution page [2].
>
> I hope our users/contributors will like it and are more easily involved.
>
> [1]
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12316782
> [2] http://camel.apache.org/contributing.html
>
> Best,
> Christian
>
Nice!
I will drill down them as soon as I find time from my "paid" work ;)
Thanks a lot!
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Supporting-our-users-to-be-more-involved-with-our-project-tp4660329p4751573.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] Supporting our users to be more involved with our project
Posted by Claus Ibsen <cl...@gmail.com>.
On Fri, Aug 12, 2011 at 8:10 PM, Christian Müller
<ch...@gmail.com> wrote:
> The "easy to resolve" issues have the Novices annotation.
> Dan created and shared the new JIRA view which is called "Camel-Novice" [1].
> I have linked this page from our contribution page [2].
>
> I hope our users/contributors will like it and are more easily involved.
>
> [1]
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12316782
> [2] http://camel.apache.org/contributing.html
>
> Best,
> Christian
>
Nice the contributing page is updated, and the link works with the new
"easy to resolve" issue JIRA page.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Supporting our users to be more involved with our project
Posted by Christian Müller <ch...@gmail.com>.
The "easy to resolve" issues have the Novices annotation.
Dan created and shared the new JIRA view which is called "Camel-Novice" [1].
I have linked this page from our contribution page [2].
I hope our users/contributors will like it and are more easily involved.
[1]
https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12316782
[2] http://camel.apache.org/contributing.html
Best,
Christian
Re: [DISCUSS] Supporting our users to be more involved with our project
Posted by Christian Müller <ch...@gmail.com>.
Ok, I created a new view in JIRA (Camel Outstanding Issues For Novices)
which I planned to share with all of you. Unfortunately I doesn't have the
right to share my view with all users. Who can help me here?
Afterwards I will update the contribute page.
In the next couple of days I plan to go through the older issues and check
whether we have some more issues for our Novices.
Best,
Christian
Re: [DISCUSS] Supporting our users to be more involved with our project
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Good idea about the field in JIRA.
We should probably add some details about that in the contributing
page, which we refer people to, when they ask about how to contribute:
http://camel.apache.org/contributing.html
We should probably also encourage people to contribute with other kind
of material than source code patches. For example to help with
documentation, writing new examples, tutorials, better getting started
guides, blog posts, being active on the mailing list, help people on
stackoverflow or other 3rd party forums etc. Its all great
contributions.
For example we have JIRA tickets where we ask for help to for example
- at each EIP page, to ensure there is at least 1 Java DSL and 1 XML DSL example
That would be an excellent JIRA for people to help with. So far it has
been Ben and me that have contributed the most for this JIRA. But
would love more help from the community and others from the Camel
team.
Likewise we should in fact ensure that on each component page there is
an example as well in both Java DSL and XML DSL (if possible.). I
think we may lack this in quite a few components. These last two
really helps with beginners and people who are getting started with a
new component, how to use it. I will log a JIRA about the component
examples, so we wont forget.
On Tue, Aug 2, 2011 at 10:45 PM, Christian Müller
<ch...@gmail.com> wrote:
> Hello!
>
> I love to see as we asking our users to be more involved with our project.
>
> I would like to add the label "Contributor" or "Beginner" (or something
> similar) to issues which are easy to be resolve (by interested
> users/customers). We should not fix these issues so soon (unless it's an
> urgent fix) to get the users/customers the chance to pick them up, adding a
> comment that other knows they are working on this issue and providing a
> patch for it. I could create a view in JIRA which lists all open issues with
> this label and add a link from the contributing page [1] to this view. I
> think then it is much more easier for our users/customers to "being more in
> touch" with our project and evolve from a user to a contributor to ...
>
> I know what this is for a great feeling to see its own (first) patch
> committed, to add his name to the team page [2] later, ...
>
> What do you think?
>
> [1] http://camel.apache.org/contributing.html
> [2] http://camel.apache.org/team.html
>
> Best,
> Christian
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Supporting our users to be more involved with our project
Posted by Kutsal Kaan Bilgin <ku...@kutsalkaanbilgin.com>.
Hi Christian & everyone on the list,
Great idea. We are currently using Camel in the ESB implementation of a
large-scale project and loving it. Me and my senior teammate would love
to get involved with the internals of Camel and finally contribute back
to the community after receiving so much from it - we will be looking
forward to the minor issues you mentioned about.
Thanks,
Kutsal
On 02.08.2011 23:45, Christian Müller wrote:
> Hello!
>
> I love to see as we asking our users to be more involved with our project.
>
> I would like to add the label "Contributor" or "Beginner" (or something
> similar) to issues which are easy to be resolve (by interested
> users/customers). We should not fix these issues so soon (unless it's an
> urgent fix) to get the users/customers the chance to pick them up, adding a
> comment that other knows they are working on this issue and providing a
> patch for it. I could create a view in JIRA which lists all open issues with
> this label and add a link from the contributing page [1] to this view. I
> think then it is much more easier for our users/customers to "being more in
> touch" with our project and evolve from a user to a contributor to ...
>
> I know what this is for a great feeling to see its own (first) patch
> committed, to add his name to the team page [2] later, ...
>
> What do you think?
>
> [1] http://camel.apache.org/contributing.html
> [2] http://camel.apache.org/team.html
>
> Best,
> Christian
>