From: Jeffrey M. <jef...@gm...> - 2011-05-11 00:26:33
|
Hello, As you may or may not be aware, development on the BZFlag project has been declining to nearly nothing over the past year. In order to see if there was some way to get any kind of development moving again I have had a recent chat with Tim Riker the project’s maintainer about how we could get BZFlag moving again. As part of this discussion the idea of breaking the maintainership into 2 parts came up. The idea would be to have Tim continue to be the Copyright holder and Intellectual Property Manager for the project, and a new position be created for managing day to day development and the production of releases. This would allow project developers to have a “go to” person for development issues, and allow Tim to continue spending the limited time he has on the project on the important ( read boring ) things that he’s already doing. I offered to do this job myself as I am a bit frustrated with the lack of movement in any direction for the project and Bullet Catcher recently has had some ideas on how to push some form of release ahead. These ideas have the best chance of working if the entire project is behind them and has some level of management to make sure they get done. Tim requested that we get some kind of consensus for who should be given this position and I agreed. So you are getting this email. That means you have committed some code in the past year or so, or were part of our last Google summer of code maintainer group. So… the idea is for everyone to comment on the idea, suggest people for the job, or say who you would endorse. I know Blast007 (Scott Wichser) has also expressed interest in this position and helping the project move forward but we have not heard of anyone else saying they want the job. Any other candidates? The position would be one where you would be responsible for getting releases out, going over code/design issues with developers, and working with Tim when conflicts arose. This includes things like making ( or having someone make) release roadmaps and the like so that developers can have a clearer picture of the next release. Let the discussion begin. Jeff Myers (jef...@gm...) |