I think this also underscores something we as an Incubating community should think about in terms of process. Obviously, it is great to give credit, but sometimes we also need to give people a chance to contribute, too. Even on seemingly trivial things (I don't have anything specific in mind) sometimes it makes sense to wait before making the change. For instance, say someone opens an issue, it might work to say something like "Hey, great catch. Could you generate a patch? See https://cwiki.apache.org/confluence/display/CONNECTORS/HowToContribute for info on how to do that." If they do give one, then commit it promptly and give them credit. If not, let it sit for a few days before making the change to see if someone else steps up. Sure, it slows down some things, but it gives people a chance to help out and be involved. These smaller issues are also a great way for us "newbie" committers to get our hands dirty with the code.
-Grant On Aug 23, 2010, at 4:46 PM, <karl.wri...@nokia.com> wrote: > +1 from me. > Karl > > -----Original Message----- > From: ext Robert Muir [mailto:rcm...@gmail.com] > Sent: Monday, August 23, 2010 4:05 PM > To: connectors-dev@incubator.apache.org > Subject: change the format of CHANGES.txt > > Hello, > > I wanted to suggest that we slightly alter the format of CHANGES.txt. > Most important I think is to add the names of non-committers who contribute > any patches, JIRA comments, reports of bugs on the user list, etc to the > issue. > > This is how the CHANGES.txt is formulated for Lucene and Solr and I think it > encourages contributors to come back, because they get some credit for their > contributions. > > Any thoughts? I think it would be really good to add all contributors to any > jira issues before the first release especially. > > -- > Robert Muir > rcm...@gmail.com
