[webdev] Re: webdev meeting

["Dale W Hodge" <dwh@xxxxxxxxxxxxxxxx>]

> -----Original Message-----
> From: webdev-bounce@xxxxxxxxx [mailto:webdev-bounce@xxxxxxxxx]On Behalf
> Of Tom Hull

> OK, I'm back in Wichita now. As per previous mail, we need to
> get together and thrash out some details on how to get the
> ACLUG website project moving again. Given that we've never
> had more than 4-5 people attend in the past, please, anyone
> who would attend under any circumstances, please write back
> and say when you could/could not make a meeting. Also, any
> proposals on where? The meeting should occur no later than
> two weeks from today (Oct. 6, so that means Oct. 20).

I can make a meeting just about any night you schedule, as long as I have a
couple days notice. As for where, how about a restaurant of some kind? I usually
don't have time to eat before most meetings, and since there'll probably be only
a few people, a restaurant shouldn't pose a problem.

> The assumption at this point is that we will be building the
> website using PostNuke (PHP, MySQL, Apache). Any alternative
> proposals to this should be stated in writing to the webdev
> list ahead of the meeting, and will only be considered if
> there are at least 2-3 people willing and able to make a
> credible commitment to such a project.



> I'll publish an agenda the day before the meeting. Minimally,
> it will include:
>
>   * web connection and host machine

John Goerzen has offered to host the new site on the same machine as the current
site. We would have to work out what we need in terms of access (ssh shell, etc)
and see if he would be willing to provide such.

>   * system admin on host machine

That would depend on where it is hosted. However, there should be several people
with admin rights over the web content / CMS / database.

>   * revision control (cvs) on website source

Only neccessary if we do a lot of hacking ourselves. I would suggest that we
only look at developing modules, and leave the core system alone at this time.
Anyone who wants to make changes to the core should probably sign up as part of
the PostNuke development team.  There are some major changes in the works, and I
wouldn't want to find ourselves doing a lot of work needlessly.

>   * bug tracking system

Only needed on modules we produce. Bugs in PostNuke itself should be filed at
the development site.

>   * mail lists

Do we really need more?  We will have the web forums available.

>   * graphic design

Something to consider, but I wouldn't expend too much effort in customization
until the new rendering engine is complete.  Currently, the separation of HTML
and code is incomplete, and requires way too much hand coding to make changes.
That should begin to change after 0.7.2.5 is released.

>   * content development plan

The old question of what kind of content?  It might be wise to poll our user
base and see what they feel they need.


> The latter is by far the largest/most openended issue.
> People should take a close look at what PostNuke provides
> (news, stories, reviews?), and how easy it is to add new
> features.

Don't base your conclusions on what you see at http://aclug.neuralmatrix.org,
instead take a look at http://developers.postnuke.com. There are a number of
things that are due to be changed in the next couple releases.  I'm still
running 0.7.1.4 because of a couple issues in the current version (0.7.2.1) that
prevented some of the installed modules from working. Hopefully things will be
sorted by the time 0.7.2.5 is released, if not, then I'll have to take a look at
my modules and decide if I can do without them or not.


> Please comment. BTW, is there a Oct. 7 meeting? (I haven't
> seen an announcement.)

The *second* Monday meeting would be the 14th! ;-)  We still need to decide a
topic for that meeting, less we go with the Q&A session.

--dwh

---
Dale W Hodge - dwh@xxxxxxxxxxxxxxxx
Vice Chairman & Secretary - info@xxxxxxxxx
Air Capital Linux User's Group  (ACLUG)
---