Rebecca and Ali have been sending emails to this distribution for
help. We're making this a little more formal by asking they enter the
issues into the issue tracker.
Notification of activity will be sent to my email account to start
with. That way I can forward email to this distribution where
warranted and avoid having all activity hit this account. It may make
sense to set up a separate distribution list for notifications as we
learn how much traffic this generates and who wants to see changes to
issue status.
Does this replace the list we've been compiling? If so, do we need to
review that list and re-submit issues via this app?
Ali
> --
> You received this message because you are subscribed to the Google Groups "Atlanta Bike Geeks" group.
> To post to this group, send email to atlanta-b...@googlegroups.com.
> To unsubscribe from this group, send email to atlanta-bike-ge...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/atlanta-bike-geeks?hl=en.
>
>
--
Ali Mangkang, Outreach Manager
Atlanta Bicycle Coalition
404-881-1112
a...@atlantabike.org
www.atlantabike.org
Follow us: http://twitter.com/atlantabike
Fan us: http://bit.ly/ABConFB
I understand that you're referring to the "Current Goals" page
(http://groups.google.com/group/atlanta-bike-geeks/web/current-goals) as our
compilation, right?
There are different levels of granularity. A list of Goals is broad. A
list of tasks to accomplish those goals narrows the scope.
I would say we don't need to replicate the goals or list of projects in the
issue tracker, but if you are compiling a list that is separate from the
Current Goals, then it would be good to divide them into updates to the
goals or enter as issues.
Perhaps a good rule of thumb is: if it involves lots of steps, it is
probably a project or a goal, and otherwise, it is an issue/task.
Jett
Ali