Mail Archives: geda-user/2015/12/29/13:57:26
To clarify my role in gEDA...
I never intended to be "in charge of" gEDA - it fell on me because
everyone else who was in charge left. Leadership through attrition
sucks but I didn't want the whole project to vanish so I gave it a
home and kept it alive.
So now I'm "in charge of" gEDA only because I own the domain names and
master accounts, which gives me control over all the project
resources. That doesn't mean (nor preclude) that I run any of the
gEDA projects, although since the people who did run the projects were
the ones who left, it didn't take much to be the one seen as "running"
the projects also.
My goals since then were to babysit the projects and hope that people
would "rise to the challenge" and become project leads for the gEDA
projects. To that end, I've been liberal with accounts and
permissions, relying on git to be able to "undo" mistakes. I wanted
to make it as easy as possible for developers to contribute, to
hopefully rebuild the robust community we once had. Sadly, I've spent
more time dealing with the hostility on the mailing list (which is why
the original developers left) than bringing in new developers.
As for Xorn, there was a contributor who had an exciting new idea and
was willing to do the work. Should I have sent him off on his own?
One more person lost to geda? If you have issues with the xorn
integration, discuss them and fix them, or agree to un-git them. I
will not apologize for trying to inspire new developers.
What we NEED are project leaders who:
1. Inspire development in their project
2. Resolve issues between developers
3. Coordinate development direction
4. Manage releases, code sprints, reviews, etc.
5. Present a positive "face" to the public
- Raw text -