2017-06-01 15:05 GMT+03:00 Coty Sutherland <csuth...@redhat.com>: > Hi, > > On Wed, May 31, 2017 at 12:08 PM, Igal @ Lucee.org <i...@lucee.org> wrote: >> Hi all, >> >> On 5/31/2017 1:12 AM, Mark Thomas wrote: >>> >>> On 31/05/17 04:07, Coty Sutherland wrote: >>>> >>>> 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. >>> >>> https://helpwanted.apache.org/ >> >> >> I would like to offer the perspective of the "new contributor" here. I, for >> one, would love to contribute and be more involved with the Tomcat project, >> and I believe that thanks to Tomcat's popularity there are many out there >> just like me. >> >> As a new contributor, the most important thing is to get some feedback. The >> "worst" thing from a new contributor's perspective is that he/she will put >> much time into work that will never be looked at, and all that time will go >> to waste. > > I agree :) Thanks for the feedback. By voicing concerns like these we > can get them addressed. > >> We understand that not all contributions will be accepted, and that they >> must adhere to the standards set by the project. We also realize that this >> is open source, and that the people who review the submission are usually >> volunteers who do the best they can in the time that they can afford to >> contribute to the project. >> >> We still need, however, to get some feedback on our submitted work in a >> timely manner before we can try again, or submit some other work.
1. Do you read dev@tomcat ? Do you review others' commits? Do you test release candidates? For me, new contributions come after that. >> Take for example the PRs on Github (sorry, but SVN feels like the 1980s -- >> great time for partying, not so much for writing code -- and I know, >> ironically the SVN project started in 2000, but I digress): >> https://github.com/apache/tomcat/pulls > > Hm, using Git was mentioned at the TomcatCon but I can't recall if the > git repository on github is bi-directional or just a clone of svn. Can > anyone answer that? 2. ASF Git repository is read-only mirror of svn repository. Github repository is mirror of ASF Git repository. It is possible to use git-svn bridge to commit to svn with git commands (git-svn metadata are present in commits and it is possible), but I prefer to overlap git checkout over svn working copy and commit with svn. This way it is easier to review. > Have we made a decision about the best way to > submit patches? BZ attachment, github PR, email, other? How often do > we check the github projects for contributions? 3. The work-to-do is tracked via Bugzilla. The changelog file references Bugzilla. Thus it is better when a PR references a Bugzilla issue. For me, PRs are equivalent to attached patches. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
