Tyler2005
Obviously we would like to be able to grow the membership of ByteClub significantly. Currently we have about 30 people registered on Tyler. Unfortunately, of these, only a half dozen seem to be active. This may change once the semester starts.
O-Week is set to be an opportunity for us (ByteClub and Monkeys alike) to recruit. Russel, Xavier and Matt are actively discussing ideas on the forum (www.byteclub.net/forum ) for O-week activities (coming up *very* soon). Keep it up. How much input do you guys want from Clinton, John, myself etc? Naturally you have our support.
(I'm speaking here for everyone without even checking with them. How nice of me
)
But do you want anything else from us? How can we help?
I have some nice little monkey logos printed in colour on A4. Poster fodder for whoever wants them.
Other business…
I would personally like to see a major overhaul of the web site, but not quite sure just what to do with it. Input is welcome. Failing helpful input, arbitrary decisions will be made.
Clinton and I have been looking at some kind of CMS system that could help unify the site, making navigation and logins easier/smoother/more consistent. We have deployed one such system (Drupal) at http://test.byteclub.net/ for testing. Feel free to create an account (currently anyone can set up accounts) and start playing with it and give us feedback. The default account has limited functionality, but as I see people jumping on board, I’ll start elevating privileges.
Blogs…
Russel is working on a new blog engine as I write this. But do we also want to give people a choice of engines? While I have been happy with the SimplePHPBlog engine we have been using, it has obvious drawbacks. Do people want the option of switching to something else? I h!
ave been using WordPress on another site and am quite happy with it. W
e could have the SimplePHPBlog, Wordpress and Russel's Blog installed as options for people who want Blogs.
But again we could be back to issues of separate logins and maintenance issues for sys admins, although with a bit of scripting (sigh), I’m sure this could be easily resolved.
We have had some notable defections from our Blogs (Euan and now Andrew Cain). There is no official word on why, but I did hear some mumblings about wanting more features in their Blogs. Something the current solution doesn’t offer.
If so, what features do people want from Blogs (tell us on the Drupal forum?). Russel started a wiki entry, but there was little feedback, but if we are ready to make change, now’s the time to get involved and speak up. At this ponit, I’m willing to consider the possibility of deploying different blog engines at request, although I’d like to keep the number of different solutions to a minimum to save maintenance h!
eadaches
If there is something you want, speak up and you might just get it .
Is it time to prune inactive Blogs? I am inclined to just delete all the Blogs that have never been used, and cast a suspicious eye over any that aren’t getting much activity.
All in favour..?
Logins are still an issue. But people have indicated to me that they are happy to have a separate login for their own personal blog, from the rest of the system. Perhaps we could get the Blog to use Drupals user authentication?
Or make the Blog a module of Drupal?
Or…?
…
Wiki…
What to do with the Wiki?
Do we wish to continue it's use? It hasn't been a huge success so far (Only the Blogs have been *really* popular). Is this an accessibility/login issue? Or have others, like myself, found mediawiki difficult to use? I still like the idea of using the wiki, but is mediawiki, the current engin!
e, gross overkill for our needs? I like the simplicity of docuwiki (ww
w.byteclub.net/~lstals/DocuWiki for a sample installation). It auto indexes pages (something I still can't get MediaWiki to do), and it has syntax highlighting of code which I really like since the ByteClub wiki is primarily a code repository, or at least largely technical in orientation. The main drawback of DocuWiki is that it has no support for user accounts. It is essentially faithful to the wiki philosophy of being open (read and write) to all. Can we accept this? (It's called security?). Could mean vandalism?
Drupal has a wiki syntax plug-in, but honestly, it sucks. On the other hand, Drupal *is* a Content Management System, and entries can be set to be editable by others. It may not use wiki syntax, but the idea is the same. Plus Drupal could manage user authentication, and I have managed to get a code syntax highlighting module working.
Can we formally drop the wiki? We can try to migrate content from what we have onto Drupal. Shou!
ldn’t be *too* hard, right?
Have a play with it and tell us what you think.
Enough for now.
Lucien (on behalf of Clinton and John as well.
PS, thanks to John for setting up the virtual host for Drupal.a
]]>


