Psema4Topic Web Development

From GTALUG

Sitemap > Culture > Psema4 > Psema4Topic Web Development

Contents 1 Purpose 2 Web Polls 2.1 Overview 2.2 Alternate solutions 2.2.1 Process 2.2.2 Implementation 2.3 Summary 2.4 Notes 3 Wiki content-programming links 3.1 The Handbook 3.1.1 Using HTML 3.1.2 Using Style 3.1.3 Namespaces 3.2 Additional Resources

Purpose

A location for discussing and/or attempting collaborative web development in a wiki.

Web Polls

Overview

A response to Semi-OT: Database for "average" users
(http://article.gmane.org/gmane.org.user-groups.linux.tolug/16624)

> How do you get a copy included on an installation CD?
> 
> For it to be treated as "infrastructure," you have to be able to
> include it on a Debian CD, a Fedora CD, a SuSE CD.
> 
> As far as I can tell, that can't be done without violating licensing
> agreeements.
> 
> I have a problem with the notion of making otherwise free software
> decidedly unfree by virtue of such requirements.

I'm curious about how TLUG'rs think (in general) when it comes to software licensing, but if the community responds openly then list bandwidth might become an issue.

I almost posted to the list, asking respondants to replace _ with an X for their selections. That way I could import the emails, run them through perl and look at the stats.

Considering that load balancing isn't terribly difficult with LAMP, I started looking for ways to optimize (not to mention getting rid of that terrible spammy feeling.)

Alternate solutions

Process

Generally speaking, the following steps should be covered:

• Collaboratively develop the poll station scripts here on the wiki. [1]
• Create a wiki page and let the community iron out poll questions for a week or so before the poll date.
• Open one or more poll station and collect results for 24 hours. [2]
• Post the results.

Implementation

List of potential implementations:

1. Use a SAL/Wiki solution. SAL is a set of perl modules (a Sub Application Layer) that I've been working-on (and off, and -with, for many moons now) to ease some web development pains.
   • Pros:
     1. SAL abstracts DBI, GD::Graph, and implements a data-driven web reporting module. It currently supports MySQL, ODBC, and SQLite. It's hardly perfect, but fairly easy to work with.
     2. A simple sample: salsurvey.cgi
   • Cons:
     1. Not yet packaged for CPAN.
     2. ODBC support has only been tested with unixodbc+freetds on rhl7.3 and fc1 boxes.

Summary

As a group, one way that we can help raise awareness is by asking questions.

(I'm too tired to do the summary tonight, but there's a number of benefits.  ;-)

Notes

[1]: See also: The wiki as a guiding light for open software development [2]: In the case of multiple poll stations, a redirector can be used for load balancing (eg. round-robin) and the stats can be calculated from the combined results.

Wiki content-programming links

A listing of links that might be handy for working-with and customizing MediaWiki pages.

The Handbook

Help:Contents

Using HTML

HTML in WikiText

Using Style

CSS and Style

Namespaces

Namespaces

Additional Resources

Sandbox