I'd gladly look over rhino licensing project. In fact I planned to create an 
admin tool to manage key generations.

Sent from my HTC

-----Original Message-----
From: Humberto Franco <[email protected]>
Sent: 26 May, 2010 9:10 PM
To: [email protected]
Subject: Re: [rhino-tools-dev] Re: Project leaders

I can help out with Rhino.Security, but I would not be able to take a 
leadership role since I'm not as experience with NHibernate as other devs here.

On Wed, May 26, 2010 at 6:43 AM, Ayende Rahien <[email protected]> wrote:
Here are the projects on the table:

Rhino-ESB
Rhino-ETL
Rhino-Licensing
Rhino-Security
Rhino-DSL
Rhino-Queues
Rhino-Mocks
Rhino-PHT
Rhino-DHT
Note that Rhino Igloo is considered deprecated and Lorenzo Melato already took 
over Rhino Commons.

Pick your poison :-)

On Wed, May 26, 2010 at 4:38 PM, sbohlen <[email protected]> wrote:
I agree that the 'Castle model' is probably a good one to follow in
 re: dividing up the responsibilities.

 On May 25, 9:20 am, Ayende Rahien <[email protected]> wrote:
 > What I am thinking about is that we should do it like Castle did.
 > Assign project leaders for each specific project: mocks, security, igloo,
 > etc.
 >
 >
 >
> On Tue, May 25, 2010 at 5:24 PM, sbohlen <[email protected]> wrote:
 > > I am interested in assisting in keeping the 'Rhino Family' of projects
 > > 'alive' and healthy; over the years I have found great value in much
 > > of this tooling (and continue to do so for both professional and
 > > personal projects).  IMO it would be a tragedy if the community were
 > > unable to come together and find a group of people similarly
 > > interested in seeing it remain healthy and maintained.
 >
 > > The truth is, however, that I think the entire collection of tools
 > > here is probably too wide-ranging in overall scope for any one person
 > > (perhaps other than yourself as the author) to be able to provide
 > > adequate support, patches, features by themselves so the only way I
 > > could see this working is if a reasonable group of people similarly
 > > step up.  I would be more than glad to be one of those people or to
 > > even play the role of helping to coordinate some of the efforts of
 > > others at a higher level if that's seen as being of value as well.
 >
 > > -Steve B.
 >
 > > On May 25, 4:36 am, Ayende Rahien <[email protected]> wrote:
 > > > Guys,
 > > > As you know, the rhino tools set of projects have been my baby for a long
 > > > time. Unfortunately, I find myself in a position of having more projects
 > > > than I have time for.
 > > > Therefor, what I would like to do is ask members of the community to step
 > > in
 > > > and take charge on those projects, handling new features, bugs, support
 > > > requests, etc.
 >
 > > > If you are interested, please let me know.
 >
 > > > Thanks in advance,
 > > > ~ayende.
 >
 > > > --
 > > > You received this message because you are subscribed to the Google Groups
 > > "Rhino Tools Dev" group.
 > > > To post to this group, send email to [email protected].
 > > > To unsubscribe from this group, send email to
> > [email protected]<rhino-tools-dev%[email protected]>
> > .
 > > > For more options, visit this group athttp://
 > > groups.google.com/group/rhino-tools-dev?hl=en.
 >
 > > --
 > > You received this message because you are subscribed to the Google Groups
 > > "Rhino Tools Dev" group.
 > > To post to this group, send email to [email protected].
 > > To unsubscribe from this group, send email to
> > [email protected]<rhino-tools-dev%[email protected]>
> > .
 > > For more options, visit this group at
 > >http://groups.google.com/group/rhino-tools-dev?hl=en.
 >
 > --
 > You received this message because you are subscribed to the Google Groups 
 > "Rhino Tools Dev" group.
 > To post to this group, send email to [email protected].
 > To unsubscribe from this group, send email to 
 > [email protected].
 > For more options, visit this group 
 > athttp://groups.google.com/group/rhino-tools-dev?hl=en.

 --
 You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" group.
 To post to this group, send email to [email protected].
 To unsubscribe from this group, send email to 
[email protected].
 For more options, visit this group at 
http://groups.google.com/group/rhino-tools-dev?hl=en.


--
 You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" group.
 To post to this group, send email to [email protected].
 To unsubscribe from this group, send email to 
[email protected].
 For more options, visit this group at 
http://groups.google.com/group/rhino-tools-dev?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rhino-tools-dev?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rhino-tools-dev?hl=en.

Reply via email to