koha-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Koha-devel] Website / ID Meeting Notes


From: Joshua Ferraro
Subject: [Koha-devel] Website / ID Meeting Notes
Date: Wed Jun 29 16:28:09 2005
User-agent: Mutt/1.4.1i

Meeting Notes for Website / Interface Design Meeting

As always ... the meeting was logged at koha.org/irc

Present:
kados
rach
owen
slef
richard
russ
indradg
shawn
hdl

(big meeting!!)

1. Koha.org Website
 We discussed Russ's report:
  http://www.russandsarah.gen.nz/kohawebredev/

a. folks need to look at the wireframes and give feedback to russ

b. some feedback was given about objective and scope:

   opencms was introduced as a product: opencms.org
    some question was raised as to whether opencms or mambo would be
    a better choice
    mambo supports multiple languages and we're not sure if opencms does

   the koha team will be 'koha project managers' with bios, emails at
    koha.org, and maybe even images to lend credibility to the project

   librarians were defined as users

   a media link will be added under 'news'

c. we want to support multiple languages eventually -- at first we'll
    do the site in english

d. koha-fr.org will have to decide what to do if there are two french koha sites

e. shaun will make the site WCAG compliant  http://www.w3.org/TR/WCAG

f. the site will be mirrored by katipo and maybe by koha-fr and liblime too

2. Interface Design:

a. we will design a set of 'programmer templates' -- minimalist templates
   with only the functions of that template displayed to ease template
   maintenance for our interface designers

b. we will design a set of 'default templates' and the lead interface
   designer will be responsible for taking changes from the programmer
   templates and integrating those into the default templates

c. we will establish a set of guidelines for committing new features to
   CVS that will ensure that programmers commit only to programmer templates
   and not to default templates -- so that the ID can ensure QA on those
   templates

d. this does not mean that internal design groups can't maintain their own
   set of templates -- it simply means that when they commit the features to
   CVS they will commit a minimalist version of the feature to the
   programmer templates (and hopefully a good description of the feature)
   and leave the presentation up to the ID.

e. the success of this method will depend on all the programmers playing
   nicely and committing their additions to the minimalist templates in
   addition to their own project templates

-- 
Joshua Ferraro               VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE
President, Technology       migration, training, maintenance, support
LibLime                  Koha ILS, Mambo Intranet, DiscrimiNet Filter
address@hidden |  Full Demos at http://liblime.com  |  1(888)KohaILS



reply via email to

[Prev in Thread] Current Thread [Next in Thread]