I've updated the list to include Bertrand's comments. Please note that I have no official affiliation with this conference; I'm just trying to keep things rolling [at least as far as the caudium stuff is concerned], so if I'm stepping on someone's feet, please let me know :)
Here's a list of the topics thrown out on the caudium devel list. Are there any others that I missed? (they get more directly pike related as you go down the list)
My thinking [and previous experience] is that we should think about whether we will discuss all of these topics, how much time we should devote to them, and see if someone wants to take a lead on that (sort of a session chair and/or discussion facilitator). They'd be responsible for having any supporting material (slides, handouts, presentations, etc) and for making sure that any discussions/outcomes were preserved for use later. Obviously, a session chair could delegate some of the responsibility to others.
Once you had an idea of what we were going to do and who would coordinate the various pieces, you could get a schedule together. Another thing to consider is if there will be enough people of different interestes to consider splitting up the group and having 2 or more concurrent sessions going at once. I'm not sure whether that's feasible or desireable, but figured I'd mention it anyhow.
I guess we probably need to know who is in overall command of the conference. Martin, do you know who's running the show? Is anyone from Paderborn listening? :)
Any thoughts?
Bill
Caudium 1.4 release plan Pike interface redesign (security) License change (code rewrite vs RIS grant vs separation of core) CIF rewrite RXML parser, and the future of RXML Martin's Stale code from his previous job ecommerce and other projects State of CAMAS/1.2/1.3 release Caudium module repository / website Plans for 2.0+ i18n /l10n Licensing policy Organization/management of the effort Marketing / popularity enhancement Hack sessions Bug Squash Sessions Pike module repository ala CPAN Pike module build system (problems, etc) Pike Namespace management
_______________________________________________ Caudium-devel mailing list devel@caudium.info http://listes.oav.net/wws/info/caudium-devel Archives are : http://listes.oav.net/wws/arc/caudium-devel
Hey list,
I've updated the list to include Bertrand's comments. Please note that I have no official affiliation with this conference; I'm just trying to keep things rolling [at least as far as the caudium stuff is concerned], so if I'm stepping on someone's feet, please let me know :)
Nice initiative :)
Here's a list of the topics thrown out on the caudium devel list. Are there any others that I missed? (they get more directly pike related as you go down the list)
looks like to me they're all there. Here's some thought/questions/comments/wishlist about some point for initial discussion:
License change (code rewrite vs RIS grant vs separation of core)
RIS people at the conference? :)
Seriously, what amount of time needed to rewritte RIS code? Is that doable for 1.4?
CIF rewrite
IIRC, Grendel began that.
What more feature people want?
I (and all the newbies i try to make switch to Caudium) are dispointed by the Virtual Host Matcher stuff. We discussed that a while ago in the devel mailing list and we came to a solution that seems to just have to be coded.
I'd change (read: allow to change/make default) the select multiple to checkboxes, since many people aren't familiar with these.
An interface ala "Resolv path" but for virtual host resolution would be nice too.
I guess CSS would be widely used.
RXML parser, and the future of RXML
Grendel has a piece of code for the new RXML parser. The key here is to know why it is important for RXML to be XML compliant. Then there are some problems we run into: - both actual RXML parser are not compatible - entities used by the XML-compliant RXML parser are not XML-compliant (and people having solutions for replacing them differs, especially for the tag-in-a-tag one: <tag arg="<othertag>">) - parser speed (read: Martin's RXML Vs PHP bench) - enhancement of do_output_tag()
Being fluent with the XML specifications could help to be part of this session. And, some discussion on the list as well as on IRC shows that this is a slippery one :)
ecommerce and other projects
The only ecommerce stuf i ever heard running on Caudium is iVend. Go for a demo, Bill :)
State of CAMAS/1.2/1.3 release
Methink vida and i should handle that :)
We can make a little demo of modularity: tags, actions and so on. We can talk about what is planned for 1.3 too.
Caudium module repository / website
Something allready exists on riverweb. Could we steal some code?
It should be integrated into caudium's website for people not having CVS write access to share their code. Finding a way to share RXML code could be cool too. And off course, the pseudo wiki could be there.
Organization/management of the effort
Organisation of "Cauding" during the year? :)
Marketing / popularity enhancement
What kind of people do we want to target? Coders? Web-literate webmasters? Newbies?
It's hard for people to hear about Caudium stuff, coz everything is talked into mailing lists you have to subscribe to.
Except if you have a killer app, noone could hear about us.
Taking the usenet example: http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&... http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&... http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&...
Then, writing tutorials, docs and packaging stuff is mandatory if we want new people to come. For example, i'm very responsible for allmost 0 CAMAS layout docs and darwin packaging.
On Tue, Aug 19, 2003 at 11:51:30AM -0400, Bill Welliver wrote:
I've updated the list to include Bertrand's comments. Please note that I have no official affiliation with this conference; I'm just trying to keep things rolling [at least as far as the caudium stuff is concerned], so if I'm stepping on someone's feet, please let me know :)
not at all. as far as caudium is concerned, it is as i saidi before, the community as a whole is responsible. as for the conference in general, i am probably the one representing the official afiliation of caudium to it, but this means that i'll try to concentrate on the things that need to be done locally, like making sure we have rooms and net-access. i am very glad for your (and everybody elses) initiative concerning things that can be done remotely.
My thinking [and previous experience] is that we should think about whether we will discuss all of these topics,
can we group the topics? like: pike / caudium user / devel
I guess we probably need to know who is in overall command of the conference. Martin, do you know who's running the show? Is anyone from Paderborn listening? :)
yes, they are. the team is ludger, daniel and me. ludger and me are on the list.
currently ludger is taking care of the program of the pike conference (finding speakers), i am the one to talk to for caudium specific needs.
some of the caudium topics may fit into the general pike program. (eg internationalization is not really a caudium specific problem, sTeam or other apps may as well benefit from any suggestions or solutions)
greetings, martin.
pike-devel@lists.lysator.liu.se
-
Bertrand LUPART -
Bill Welliver -
Martin Baehr