Hello, at irc channel was a talk about the needed of new contrib members. Someone proposed to make a query in channel's topic and I made one directly on channel. Why wait to people became to be one contrib member? Why not recruit members? Core/dev members or contrib with experiencie can take a look to private repos, look for ports that are not in contrib and try to talk to maintainer to propose him to became a contrib member and maintain that port in contrib. With time and experiencie may be he can give a hand to other contrib members who maintain lot of ports. Also can be added to contrib a few "interesting/well done" ports from private repos. Only an idea. I hope it can be discussed here and we can read opinions or another suggestions. (on irc channel did not get any of them). Sorry if this is a crazy idea. Reegards. Learning bit by bit. - pitillo -
Hi, I think pitillo has a good idea. It has the advantage that if a person has a special interest in some area, that person might be willing to maintain ports in that area on contrib. People with a special interest may not be sufficently dedicated to Crux to spend time outside of their area, but Crux would get the benefit of their expertise in their specialty. thanks to you all clare On 2/28/07, pitillo <pitillo@ono.com> wrote:
Hello, at irc channel was a talk about the needed of new contrib members.
Someone proposed to make a query in channel's topic and I made one directly on channel.
Why wait to people became to be one contrib member? Why not recruit members? Core/dev members or contrib with experiencie can take a look to private repos, look for ports that are not in contrib and try to talk to maintainer to propose him to became a contrib member and maintain that port in contrib. With time and experiencie may be he can give a hand to other contrib members who maintain lot of ports. Also can be added to contrib a few "interesting/well done" ports from private repos.
Only an idea. I hope it can be discussed here and we can read opinions or another suggestions. (on irc channel did not get any of them). Sorry if this is a crazy idea.
Reegards.
Learning bit by bit. - pitillo -
Hello, at irc channel was a talk about the needed of new contrib members. I kinda miss an argument why there should be more members... while I'm not at all opposed, clearly identifying the issue might help to find a
Hi pitillo, On Wed, Feb 28, 2007 at 12:51:41 +0100, pitillo wrote: proper solution. [...]
Why wait to people became to be one contrib member? Why not recruit members?
One thing you have to keep in mind is that no one can be forced into contrib. core/contrib devs have asked maintainers to join in the past, so actively recruiting is not a new idea. Unfortunately "being part of contrib" as a reason to join was sometimes not convincing enough. IMHO the important question is "how can we motivate people to join?". There's basically two main reasons you mention why people should join contrib, and I fully agree:
Also can be added to contrib a few "interesting/well done" ports from private repos.
at irc channel was a talk about the needed of new contrib members. I think the members that were missed in that discussion are mainly from
In my words: 1. someone ports software a number of others use, either directly or as dependencies for their ports ("interesting ports") 2. someone's a competent maintainer and active member of the community, future core/opt maintainer candidate ("well done ports") Now, the first group should probably be spotted by the existing contrib maintainers (note that I'm omitting core devs since contrib is meant to regulate itself), and is usually easy to motivate to join. It's a completely different thing with the second group: To me it seems best if _users_ ask the maintainers to join contrib, like "I'm using port XY from your repo and believe it would be nice if it was available from contrib. Have you considered joining?". I believe that this is much more motivating for a maintainer than a random dev who might never have used a single port of your repo asking you to join. Repeating your opening statement: the second group, and that it'll be much easier to motivate them to join contrib if they feel that the users of their ports want the to join. So pitillo, have you previously contacted a non-contrib maintainer to let him/her know that you use his/her ports? :-) Just my two cents. Regards, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
On Thu, Mar 01, 2007 at 11:00:07 +0100, Johannes Winkelmann wrote: [...]
There's basically two main reasons you mention why people should join contrib, and I fully agree:
Also can be added to contrib a few "interesting/well done" ports from private repos.
In my words: 1. someone ports software a number of others use, either directly or as dependencies for their ports ("interesting ports") 2. someone's a competent maintainer and active member of the community, future core/opt maintainer candidate ("well done ports")
Note that I changed the ordering of the list after writing the rest of the mail, so in the following paragraphs, "first group" refers to item #2, and "second group" to item #1.
Now, the first group should probably be spotted by the existing contrib maintainers (note that I'm omitting core devs since contrib is meant to regulate itself), and is usually easy to motivate to join.
It's a completely different thing with the second group: [...]
Sorry for the confusion. Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
Hi Johannes, thank you for the reply and the explanation,
On Thu, 1 Mar 2007 11:00:07 +0100 Johannes Winkelmann <jw@smts.ch> wrote:
Hi pitillo,
Hello, at irc channel was a talk about the needed of new contrib members. I kinda miss an argument why there should be more members... while I'm not at all opposed, clearly identifying the issue might help to find a
On Wed, Feb 28, 2007 at 12:51:41 +0100, pitillo wrote: proper solution.
like I said, it was suggested at irc channel. I think can be good more people working in this project, and I know (with my little experience) that people who want to contribute in all aspects are welcome. I think the problem begins with contrib members who are maintaining lot of ports. I think this is a good way to give them support.
[...]
Why wait to people became to be one contrib member? Why not recruit members?
One thing you have to keep in mind is that no one can be forced into contrib. core/contrib devs have asked maintainers to join in the past, so actively recruiting is not a new idea. Unfortunately "being part of contrib" as a reason to join was sometimes not convincing enough.
I am new here and hope I can stay more time. Do know about that was talked about this point before. (I do not want to seem a flamer or something similar and start discussionns if they were closed before). The point is to suggest someone who is maintaing a private repo with non dups (new ports) to start being a contributor. That is only a suggestion and not a way to force him/her. (I talked this with sepen before and he tell me about contrib rules and the fact to be the person who needs to follow them. The most important is one who talks about sending a mail suggestion be a contributor). May be starting maintaining a few ports can be a good way to see how he/she answer to this position (how he/she works). Then suggest to help in some big ports wich is using.
IMHO the important question is "how can we motivate people to join?".
I think this is the point. Is help really needed? . If it is, that is the motivation to keep CRUX up/update/KIS. If you were waiting the user movement (I mean asking the comunity to be one of them) and there were only a few, may be is time to change it with some people, who really has a contribution to the comunity (ports or the knowledge to maintain).
There's basically two main reasons you mention why people should join contrib, and I fully agree:
Also can be added to contrib a few "interesting/well done" ports from private repos.
In my words: 1. someone ports software a number of others use, either directly or as dependencies for their ports ("interesting ports") 2. someone's a competent maintainer and active member of the community, future core/opt maintainer candidate ("well done ports")
Now, the first group should probably be spotted by the existing contrib maintainers (note that I'm omitting core devs since contrib is meant to regulate itself), and is usually easy to motivate to join.
Then try to talk to them and make the suggestion. Seems easy and can not be lost anything to try to add someone who has this pattern.
It's a completely different thing with the second group: To me it seems best if _users_ ask the maintainers to join contrib, like "I'm using port XY from your repo and believe it would be nice if it was available from contrib. Have you considered joining?". I believe that this is much more motivating for a maintainer than a random dev who might never have used a single port of your repo asking you to join.
Nice. Did not thought in that fact. Really you are in true here. Nice point and strong reason to tell users about this.
Repeating your opening statement:
at irc channel was a talk about the needed of new contrib members. I think the members that were missed in that discussion are mainly from the second group, and that it'll be much easier to motivate them to join contrib if they feel that the users of their ports want the to join.
Sure.
So pitillo, have you previously contacted a non-contrib maintainer to let him/her know that you use his/her ports? :-)
I never did it. I was using some private repos and in some cases, I was sad. With my little knowledge and without the supervision needed before add them, I broke things. I hope I can only use core/opt/contrib far. (bigger and trully ones too, xorg, gnome, kde)
Just my two cents. Regards, Johannes
I am happy to know you are supervising the ML. And sorry for my english level and this big letter (seems a letter instead a email). May be it is to big and hard to read. I use this way to give thanks and regards to all. I am happy to have find the temple. :) Learning bit by bit. - pitillo -
participants (3)
-
Clare Johnstone -
Johannes Winkelmann -
pitillo