tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Coty Sutherland <csuth...@redhat.com>
Subject Re: Things that we can do to increase contributor involvement?
Date Sun, 11 Jun 2017 20:57:24 GMT
On Sun, Jun 11, 2017 at 4:20 PM, Violeta Georgieva <violetagg@apache.org> wrote:
> Hi Coty,
>
> 2017-06-02 17:50 GMT+03:00 Coty Sutherland <csutherl@redhat.com>:
>>
>> On Fri, Jun 2, 2017 at 10:27 AM, Violeta Georgieva <violetagg@apache.org>
> wrote:
>> > Hi,
>> >
>> > 2017-05-31 6:07 GMT+03:00 Coty Sutherland <csutherl@redhat.com>:
>> >>
>> >> Hi all,
>> >>
>> >> I've been thinking about things that we could do for Tomcat to help
>> >> bring in new contributors and to be more appealing to new developers.
>> >> Right now we have http://tomcat.apache.org/getinvolved.html which has
>> >> a few bullet points and links to documentation, which is a bit verbose,
>> >> about how to contribute to an Apache project. We also have the wiki
>> >> (https://wiki.apache.org/tomcat/FrontPage), which mentions nothing
>> >> about contributing. Bugzilla is a bit daunting for newcomers (thought
>> >> we did create the "Beginners" tag to help identify some BZs for new
>> >> folks to work on) too. I've been looking around for some ideas on how
> to
>> >> make it easier for new people to contribute after having some
>> >> conversations with friends about contributing to Tomcat and found some
>> >> interesting examples other projects are using to help bring new people
>> >> in, such as https://wiki.gnome.org/Newcomers (which is my favorite)
>> >> and https://fedoraproject.org/wiki/Join. Obviously Tomcat isn't as
>> >> large of a project as those, but it does have multiple places for
>> >> people to contribute (Documentation, Patches, FAQ, wiki, etc) which
>> >> could use different skill sets. This site
>> >> http://whatcanidoforfedora.org/en would be really cool to implement,
>> >> but at the ASF level I think (Tomcat isn't complex enough to warrant
>> >> that, is it?).
>> >>
>> >> Anyway, the point of this email is really just to say that we should
>> >> take some cues from other projects and try and develop a solid entry
>> >> ramp to help entice new developers :) What does everyone else think?
>> >
>> > One thing that might help from my point of view is to provide README.md
> and
>> > CONTRIBUTING.md for those who are working with GitHub replications of
> the
>> > repository. It is convenient to have the contribution's instruction
>> > directly in the root of the repository.
>> > e.g.
>> > https://github.com/apache/jmeter/blob/trunk/README.md
>> > https://github.com/apache/flink/blob/master/README.md
>> >
>> >
>> > What do you think?
>>
>> Oh yeah. That's a great idea! I was just catching up on the thread and
>> was trying to think of a way a way to let github users know what
>> committers are doing with their PRs to get them committed (a README is
>> obvious). I think that adding some transparency there may help them
>> understand some issues that could cause latency.
>>
>
> If you didn't start with README.md I can prepare some initial version.

I hadn't started yet, but I intended to. It's on my TODO list :) If
you want, you can put something up and I'll edit it as soon as I make
time.

> Regards,
> Violeta
>
>> > Regards,
>> > Violeta
>> >>
>> >>
>> >> Thanks,
>> >> Coty
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: dev-help@tomcat.apache.org
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message