Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # dev >> [DISCUSS] Hadoop SSO/Token Server Components


Copy link to this message
-
Re: [DISCUSS] Hadoop SSO/Token Server Components
Near the bottom of the bylaws, it states that addition of a "New Branch
Committer" requires "Lazy consensus of active PMC members."  I think this
means that you'll need to get a PMC member to sponsor the vote for you.
 Regular committer votes happen on the private PMC mailing list, and I
assume it would be the same for a branch committer vote.

http://hadoop.apache.org/bylaws.html

Chris Nauroth
Hortonworks
http://hortonworks.com/

On Tue, Aug 6, 2013 at 2:48 PM, Larry McCay <[EMAIL PROTECTED]> wrote:

> That sounds perfect!
> I have been thinking of late that we would maybe need an incubator project
> or something for this - which would be unfortunate.
>
> This would allow us to move much more quickly with a set of patches broken
> up into consumable/understandable chunks that are made functional more
> easily within the branch.
> I assume that we need to start a separate thread for DISCUSS or VOTE to
> start that process - correct?
>
> On Aug 6, 2013, at 4:15 PM, Alejandro Abdelnur <[EMAIL PROTECTED]> wrote:
>
> > yep, that is what I meant. Thanks Chris
> >
> >
> > On Tue, Aug 6, 2013 at 1:12 PM, Chris Nauroth <[EMAIL PROTECTED]
> >wrote:
> >
> >> Perhaps this is also a good opportunity to try out the new "branch
> >> committers" clause in the bylaws, enabling non-committers who are
> working
> >> on this to commit to the feature branch.
> >>
> >>
> >>
> http://mail-archives.apache.org/mod_mbox/hadoop-general/201308.mbox/%3CCACO5Y4we4d8knB_xU3a=hr2gbeQO5m3vaU+[EMAIL PROTECTED]%3E
> >>
> >> Chris Nauroth
> >> Hortonworks
> >> http://hortonworks.com/
> >>
> >>
> >>
> >> On Tue, Aug 6, 2013 at 1:04 PM, Alejandro Abdelnur <[EMAIL PROTECTED]
> >>> wrote:
> >>
> >>> Larry,
> >>>
> >>> Sorry for the delay answering. Thanks for laying down things, yes, it
> >> makes
> >>> sense.
> >>>
> >>> Given the large scope of the changes, number of JIRAs and number of
> >>> developers involved, wouldn't make sense to create a feature branch for
> >> all
> >>> this work not to destabilize (more ;) trunk?
> >>>
> >>> Thanks again.
> >>>
> >>>
> >>> On Tue, Jul 30, 2013 at 9:43 AM, Larry McCay <[EMAIL PROTECTED]>
> >>> wrote:
> >>>
> >>>> The following JIRA was filed to provide a token and basic authority
> >>>> implementation for this effort:
> >>>> https://issues.apache.org/jira/browse/HADOOP-9781
> >>>>
> >>>> I have attached an initial patch though have yet to submit it as one
> >>> since
> >>>> it is dependent on the patch for CMF that was posted to:
> >>>> https://issues.apache.org/jira/browse/HADOOP-9534
> >>>> and this patch still has a couple outstanding issues - javac warnings
> >> for
> >>>> com.sun classes for certification generation and 11 javadoc warnings.
> >>>>
> >>>> Please feel free to review the patches and raise any questions or
> >>> concerns
> >>>> related to them.
> >>>>
> >>>> On Jul 26, 2013, at 8:59 PM, Larry McCay <[EMAIL PROTECTED]>
> >> wrote:
> >>>>
> >>>>> Hello All -
> >>>>>
> >>>>> In an effort to scope an initial iteration that provides value to the
> >>>> community while focusing on the pluggable authentication aspects, I've
> >>>> written a description for "Iteration 1". It identifies the goal of the
> >>>> iteration, the endstate and a set of initial usecases. It also
> >> enumerates
> >>>> the components that are required for each usecase. There is a scope
> >>> section
> >>>> that details specific things that should be kept out of the first
> >>>> iteration. This is certainly up for discussion. There may be some of
> >>> these
> >>>> things that can be contributed in short order. If we can add some
> >> things
> >>> in
> >>>> without unnecessary complexity for the identified usecases then we
> >>> should.
> >>>>>
> >>>>> @Alejandro - please review this and see whether it satisfies your
> >> point
> >>>> for a definition of what we are building.
> >>>>>
> >>>>> In addition to the document that I will paste here as text and
> >> attach a
> >>>> pdf version, we have a couple patches for components that are