Yes, I'm on my way to a meeting now.<br><br>That makes me happy because it means people are getting organized. :)<br><br>But ... meetings can be grueling, can't they?<br><br>So Walt's idea is excellent, because the way to avoid runaway coding is to make a spec, which would have the added advantage of being able to pick out the underlying architecture (modules, views, cck...)
<br><br>And who knows, with time and Drupal adoption, it might even start to cope with runaway meetings!<br><br>Victor Kane<br><a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a><br><br><div><span class="gmail_quote">
On 5/12/07, <b class="gmail_sendername">Walt Daniels</b> <<a href="mailto:wdlists@optonline.net">wdlists@optonline.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">Although one could easily generate an octopus monster if
everyone throws in their favorite meetting features, this looks like a genuinely
interesting mashup and worthy of spending a little time spec writing to get it
right (whatever that means for at least some significant subset of people). As
one who participates in far too many meetings, I would like to be part of that
process. Perhaps starting a new drupal group would get us off to a good start.
</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">Just to throw in a few more features, a lot of meetings
have preprepared documents for participants to read so there needs to an easy
way of including them. Some sort of an agenda template that can be tuned to your
organization would be good and then another template to construct the minutes
after the meeting. Both have to be pretty flexible judging by the various
meetings I go to where they only bear a passing resemblence. Audio, video or
even stenographers notes might be "full" record of the
meeting.</font></span></div><br>
<div dir="ltr" align="left" lang="en-us">
<hr>
<font face="Tahoma" size="2"><b>From:</b> <a href="mailto:development-bounces@drupal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">development-bounces@drupal.org</a>
[mailto:<a href="mailto:development-bounces@drupal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">development-bounces@drupal.org</a>] <b>On Behalf Of </b>Victor
Kane<br><b>Sent:</b> Saturday, May 12, 2007 3:32 PM<br><b>To:</b>
<a href="mailto:development@drupal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">development@drupal.org</a><br><b>Subject:</b> Re: [development] Newbie announcement
+ starting a new meeting related module<br></font><br></div><div><span class="e" id="q_11281eb5dd6b09f6_1">
<div></div>Apart from David's suggestions, you might want to consider splitting
the functionality up into different kinds of globs of
responsability.<br><br>Seems to me like you have meetings, tasks and a way to
view the minutes of a meeting together with the status of their embedded tasks,
as a report, and as an easy form of navigation. <br><br>For example, a meeting
can have tasks (issues, cases) referenced into it in some way.<br><br>Now, look
and see if there do not already exist content types/modules that can duplicate
PART of the total functionality, and then fashion a mashup with cck
(nodereference) and views. <br><br>Of course, you are behind the eight ball if
the module you want to re-use has no support for cck and/or views.<br><br>Then
consider using David's approach and fashion content types (meeting, with
usernode and/or user references, nodereferences; task; ...) and views (or embed
views into content type displays...). <br><br>Because part of the problem is not
only that of overlapping modules, but also modules which do not abide by any
architectural considerations in terms of fostering re-use, and separating
modules into convenient re-usable class-type entities. <br><br>Hope that
helps,<br><br>Victor Kane<br><a href="http://awebfactory.com.ar" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">awebfactory.com.ar</a><br><br>
<div><span class="gmail_quote">On 5/12/07, <b class="gmail_sendername">Bob</b>
<<a href="mailto:anarchybob@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> anarchybob@gmail.com</a>>
wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hey
there, I'm new to this so go easy if I make any blatant faux pas! <br><br>A
bit about me: I've been doing php & mysql programming for quite a<br>while
now, and make the odd hack application here and there. I think<br>like a lot
of people I've come round to the idea helping with a big <br>CMS is a much
better way to go! I've not contributed to a big project<br>before
either. I got a copy of the Drupal Pro Development book, and<br>it
all seems kinda straightforward so hopefully I'll be ok!<br><br>Anyway, I want
to create a new module. I've not seem anything<br>similar, but let
me know if I'm duplicating existing functionality (I<br>think there's some
crossover, but anyway). And also sorry if this is <br>the wrong
place for this, I couldn't see a suitable list otherwise!<br><br>I want to
make a module for meetings that tracks individual agenda<br>items and action
points. I'm involved in an activist community where <br>a lot of
people do a lot of different meetings all the time, and<br>there's rarely any
continuity. The module would work as follows.<br><br>1. Before a
meeting, people can add individual agenda items that allow<br>comments and
discussion.<br>2. Just before the meeting, the agenda can be printed off as a
time<br>saving device.<br>3. After the meeting, comments or minutes can be
recorded against<br>specific items to allow better tracking (keywords, etc)
<br>4. Also, and the main focus of this module, individual action
points<br>can be added and assigned to users.<br>5. In a way similar to case
tracker, people can then leave comments<br>and mark tasks when they're done.
<br>6. At the next meeting, it should be easy to keep a track of
what's<br>actually been done, and see what's dragging on.<br><br>As you can
see it's kind of a circular process, but I hope you kind of<br>get the idea!
<br><br>I have a few ideas how this will all work in my head, but if anyone
is<br>interested or would like to help that would be great, as I think
it's<br>quite an ambitious first project and a little mentoring would be
<br>appreciated!<br><br>A few notes:<br>- I was looking at making meeting node
types extensions of event<br>types, to keep all that functionality.<br>- Two
basic new node types would be involved - Action Point and Meeting. <br>- I was
thinking of using taxonomy to track things like meeting groups.<br>- For
action point entry, I was visualising posting them as a plain<br>text list,
which then gets parsed and each line added as a node.<br><br>As I've already
stressed, any and all input welcomed, even if it's a<br>case of 'don't bother
because of X reason'.<br><br>Thanks a
lot!<br><br><br>David<br>xx<br><br>--<br>phone: 0774 3917404<br>skype:
daresbalat <br>msn: <a href="mailto:bobulatorm@hotmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">bobulatorm@hotmail.com</a><br></blockquote></div><br></span></div></div>
</blockquote></div><br>