Hi Darrell, Those are great questions. This relates to project governance, so if you haven't already seen our bylaws, I recommend taking a look.
https://hadoop.apache.org/bylaws.html The word "bylaws" sounds intimidating, but don't worry. It's a short document. :-) What you're describing sounds like a project management or product management role. In Apache Hadoop (and probably the majority of other Apache projects), this role is not assigned to any one individual or set of individuals. Instead, the community has a collective responsibility to build consensus on which changes go into the software. This process culminates in binding +1 or -1 votes by committers and PMC members, as described in the bylaws. Non-committers are also encouraged to cast +1/-1 votes, but we ask that you call it out as a "non-binding" vote. The bylaws do not allow anyone to take action based on non-binding votes, but we still see them as an important part of gauging community interest (or objection) to a particular change. You asked if anyone could file a jira based on subjective opinion and push it through to trunk. Technically, this is true, but we rely on the above process to ensure there is some degree of consensus before a change is committed. Specifically, code cannot be committed to the repository until it receives a binding +1 from at least one committer or PMC member. That means at least two people agree with the proposal on the jira. If another committer or PMC member comes along later and casts a binding -1 vote, then that acts as a veto, and it goes back to the drawing board to try to reach agreement. Specifically for MAPREDUCE-5673, I do think it's a good idea for you to pursue it. It has been open for a long time, which suggests no one has considered it urgent, but I also see no objections from the people who have chosen to comment. For UI changes, I encourage you to do a quick mock-up and attach a screenshot for early review. That might reveal if adding a new column makes the UI look too crowded or if it needs further design though. Thank you for asking these questions, and we appreciate your contributions! Chris Nauroth Hortonworks http://hortonworks.com/ On 4/24/15, 9:09 AM, "Darrell Taylor" <darrell.tay...@gmail.com> wrote: >Hi Chris, > >Thanks for the info, I'm working through the newbie list and trying to >pick >anything up that seems simple. > >So, I got to MAPREDUCE-5673 and while this looks easy I asked myself if it >was even worth doing? My reasoning is that this was raised by somebody >who >thinks it's a good idea to have the host(IP) in the jobhistory webUI >(which >it probably is), is there any collective thought around whether people >think this is a good idea or not? Do the Jira's go through any sort of >vetting process? I guess what I'm asking is could anyone just submit a >Jira with a subjective opinion and there is a chance that it would make it >all the way through to trunk? > >I'll probably take a look through this anyway as it's a good way of trying >to learn what goes where. But I'm just curious how the process works. > >Thanks >Darrell > >On Thu, Apr 23, 2015 at 6:23 PM, Chris Nauroth <cnaur...@hortonworks.com> >wrote: > >> If you happen to know which committers tend to do a lot of code reviews >>in >> the specific area of the code covered by your patch, then tagging them >>in >> a jira comment is an effective approach. If you're unsure who to >>contact, >> then please feel free to email the appropriate project-specific *-dev >>list >> for help. >> >> I agree that our jira metadata can be messy, and that can make it >> challenging to find issues that really do need work. The committers >>have >> some efforts under way now to try to keep our bug tracking cleaner. One >> specific thing we can all do in this area is to apply the "newbie" label >> to appropriate issues, so that new contributors can run an easy jira >> query. Meanwhile, if there is every any doubt, please feel free to ask >> committers. In the case of HADOOP-10861, I think the right approach is >>to >> review the current web UI code, and if there are no occurrences of >>invalid >> HTML, then the issue can be resolved as Not a Problem. >> >> Chris Nauroth >> Hortonworks >> http://hortonworks.com/ >> >> >> >> >> >> >> On 4/23/15, 12:53 AM, "Darrell Taylor" <darrell.tay...@gmail.com> wrote: >> >> >Hi Tsuyoshi >> >On Wed, Apr 22, 2015 at 9:16 AM, Tsuyoshi Ozawa <oz...@apache.org> >>wrote: >> > >> >> Hi Darrell, >> >> >> >> Thank you for having interest for contributions to Hadoop project! >> >> >> >> > * How do I know if a newbie Jira is even still valid? >> >> >> >> Please ping committers whether the issue is valid when the issue >>looks >> >> to have been resolved already. >> >> >> > >> >What is the recommended way to do this? Tag them in a Jira comment? >>Send >> >a message to the mailing list? >> > >> > >> >> >> >> > * Does anybody have any suggestions for a suitable newbie ticket to >> >>pick >> >> up? >> >> >> >> One suggestion from me is to use JQL on JIRA to find issues for >>newbie. >> >> If you run following query, you will find fresh and open issues. >> >> >> >> project = "Hadoop Common" and labels = "newbie" and status = open >> >> ORDER BY updatedDate >> >> >> > >> >I have already been looking through these from a link Allen sent me, >>but >> >this is what prompted my previous post. It's hard to tell if something >> >has >> >been done elsewhere, e.g. HADOOP-10861 >> > >> > >> >> >> >> Also I think one good starting point is to fix documentation, typos >>in >> >> code, trivial changes, or something. >> >> >> > >> >OK, I'll take another sweep through and see what I can find. >> > >> >Thanks >> >Darrell >> > >> > >> > >> >> >> >> Thanks, >> >> - Tsuyoshi >> >> >> >> >> >> On Wed, Apr 22, 2015 at 4:47 PM, Darrell Taylor >> >> <darrell.tay...@gmail.com> wrote: >> >> > Hi All, >> >> > >> >> > First off I've submitted a patch for HADOOP-11813 as a starter for >>10, >> >> this >> >> > was an easy change and starts to get me familiar with where things >> >>are. >> >> > >> >> > Now I've been looking through the newbie Jira's to see what else I >> >>can do >> >> > to help, but I'm struggling to see the wood for the trees, which I >> >> suspect >> >> > is down to my lack of knowledge around how things hang together. >> >> > >> >> > I figured I'd go for some easy stuff to start with, so had a look >>at >> >> > HADOOP-10861. Most of the html I can find >> >> > under /hadoop-hdfs-project/hadoop-hdfs/src/main/webapps seems to be >> >> valid. >> >> > After further digging I found HDFS-274 which appears to be a patch >>for >> >> the >> >> > pages when they were .jsp instead of html, so does this just need >> >> closing? >> >> > >> >> > So essentially this boils down to two mains questions: >> >> > >> >> > * How do I know if a newbie Jira is even still valid? >> >> > * Does anybody have any suggestions for a suitable newbie ticket to >> >>pick >> >> up? >> >> > >> >> > Thanks >> >> > Darrell >> >> >> >>
