Project Governance
Austin Ziegler
1. I don't have time.
2. I don't use LDAP enough to be an expert, which I believe is needed
to lead this project.
I have, at best, seen myself as a caretaker until a leader stepped up.
In the interim, I have certainly put my opinion in the code with
respect to the project management and code style, but I am not
interested in any way of really *leading* this project. As a bit of
history, I created the Net::LDAP project *way* back when I was looking
for interesting projects, but it lay fallow and undeveloped until I
found Francis Cianfrocca who implemented the first few versions we had
before last year's short-lived "revival". Since then, I've been too
busy with projects at work, projects vaguely related to work, and life
in general to do anything related to this project.
After 0.2 goes out on Monday 3.21, I am formally bowing out of this
project (but it will take a little bit of time for that to happen
fully, see below). Just based on code contributions and activity,
there are several people who I think could lead this project.
Whoever becomes leader should review the changes in downstream forks
to see whether there are good changes that could be brought up and
developers who should be asked to become active on the main repo.
Please note that there is one person, who if he wants it, I will hand
the leadership to without a vote because I trust him that much.
Otherwise, I'd like to have people volunteer themselves and the
community/list as it exists vote on it. If we have more than one
candidate, I will organize the vote so that it is by secret ballot.
Voting will be open to members of this mailing list.
Once the project has a new leader, there are several resources that I
will be happy to transfer to the project leader. I just bought
rubyldap.com, .info, .org, and .net and will transfer them to the
project leader. They are theoretically set up to show what's at
ruby-ldap.github.com, but I'm having some technical issues right now
(a support request is with github). I have created a ruby-ldap GitHub
project. I will transfer ownership of the project to the new leader.
We also have the RubyForge project which, while we may wind down most
of the activities there, we should not close completely because
RubyForge is still one place people look for projects.
This is what I meant by the transition taking some time—there's a lot
of resources to play with and move around.
Let's discuss this until 0.2 goes out; after that, I'd like to take
nominations for a week or so and then move to elect a new leader ASAP.
-a
--
Austin Ziegler • halos...@gmail.com • aus...@halostatue.ca
http://www.halostatue.ca/ • http://twitter.com/halostatue
James Hewitt
Sounds like a sensible plan to me.
The one (pedantic) thing I would mention is that ruby/ldap and ruby-net-ldap are probably confused enough already, and it might be better to use ruby-net-ldap on github.