Forum OpenACS Development: Call for AOLserver Core Team Nominees
We would like to establish an AOLserver core team made up of members from both here at AOL and the Open Source Community. The core team's main responsibility will be to lead the future direction of the AOLserver Open Source project, working to balance the internal requirements here at AOL with the requirements of the community at large.
We've decided to adopt the core team principles currently in use by the Tcl core team - it seems to have worked well for them, and seems to also be a good fit for the AOLserver project. There will probably be a few slight modifications made, but essentially the core team will function as described by the following:
If you are interested in becoming a member of the AOLserver core team, please send me (mailto:email@example.com) an email with a brief paragraph or two describing your qualifications, and why you think you would be a good candidate. We will then post the names and descriptions and allow everyone to vote for the top three.
Please let me know if there are any questions. Thanks!
I'm happy/willing/able to do this. So, question is am I suitable?
Why I'm a good choice
Why I'm not a good choice
So, there you have. I'd like and will do the job (or at least put myself forward), but I have reservations. Therefore if anyone wishes to object please do so (I won't take it personally), and I'll decide from there.
"The Tcl Core Team is a small group of people who are making major contributions to the development of the Tcl core and who are highly respected and trusted by the Tcl community. Team members are expected to invest significant amounts of their time to improve the Tcl core."
Simon, I think it's well recognized that you make a significant contribution in the openacs community, and possibly I'm wrong on this point, but members of the aolserver community probably wouldn't say the same thing.about you with regards to aolserver community. I think it's great that you're willing to volunteer, but the aolserver community would be better served by a core team member who has done significant aolserver development, and more importantly, has the time to invest in improving aolserver. You've stated that you're very busy, so it's not likely that you will have much time to invest in aolserver. For the benefit of openacs, I don't think it's as important that the aolserver core team has an openacs member as it is to have a core team that fit the criteria as spelled out in the excerpt that I've included above.
Would it still be possible to add more to your responsibilities. I am unsure of your qualification but it would be great if someone from OpenACS had a good voice in aolserver. We do depend on aolserver, of course John S work will make us more independent.
Anyway thanks for hearing me out. I do understand that we are all volunteers, so if no one volunteers and is qualified I am still happy. Thanks.
I think the members of the community that wish to be on the core team need to:
- Have very good knowledge of the C code and structure of the codebase
- Be able to attend or keep up with the AOLserver chats that occur weekly
- Work on communication from/to the rest of the community about what thoughts are going on and where things are going or need to go
- Be able to review/ make suggestions on new modules to conform to the new engineering standards for code/docs/testing that are being established now.
- Most likely be responsible for at least one AOLserver module (their own or an abandonded one)
- Follow the AOLserver mailing list and contribute when possible
The real point of this is that while I think there are a few people that might be a good fit for the core group in the OpenACS community, it shouldn't be thought of a as a necessary thing for OpenACS to have representation in the core. Its all good either way IMHO but don't think the OpenACS will miss out if not directly represented.
- Carl Garland
I'd like to make yet another plug for the AOLserver chats that take place every Thursday on AIM. Last week's had about sixteen people, including the AOL half of the core team. We discussed the formation of a core team, AOLserver 3.5.1 and 4.0, and the state of documentation. This week we'll be discussing adding Win32 support back into the core, among other things. I'd like to get OpenACS's remaining AOLserver issues on the agenda too. We need your input!
Unfortunately, I'm going to have my hands full for the next few months, and I think those months will determine the success or failure of this initiative. There are also oodles of better qualified people that I'm hoping will step up.
Come to today's chat!