E-mail
Meeting Info
Date: Tueday November 24, 2009
Start Time: 12:00 PM Pacific Standard Time
End Time: 1:25 PM Pacific Standard Time
Dial-in Number: 1-219-509-8111 (East Coast US)
Access Code: 615815
See start time in other time zones
Back-channel on IRC #civicrm at irc.freenode.net
IRC in your browser
Agenda
- quick update on 3.1 - Core Team
-- sub contact types
-- html email
-- testing and code coverage (mosly see if we can get more people on
board for that) - what on the pipe for 3.2 (or what isn't) - Core Team
-- Canvass and Phonebank??
-- Integration with general ledger/accountancy?? - update on the reorganisation/branding of civicrm.org
- Finance/Accounting efforts with CiviCRM - Peter Davies
- Observations and thoughts on CiviCRM community - DharmaTech (a collection of our thoughts, comments from the Code Sprint, discussion from the NP Dev Summit, and guidance from Jono Bacon - Ubuntu Community Manager )
-- Improving CiviCRM Infrastructure
-- Building Buzz
-- Engaging the Community - Review of Advisory Group - DharmaTech
-- Michael McA's comments in his email - 6 month review: scratching itch = scratching another's back; where people can interact with the project in a way that satisfies what they want to do and also benefits the wider community; organising the London developer camp; alpha testing;
-- our purpose?? - guiding principle for the advisory group should be finding ways in which we can improve engagement with the community - ensuring the CiviCRM project is a place in which mutually beneficial interactions ways of participating happen naturally
Agenda Notes
Attendees
Xavier Michael Sarmeesha Wes Joe Lobo Dave Claire Cynthia Kurund Peter Michau
Update on 3.1
On ALpha 2 currently
Shortly Alpha 3
Lobo -> Beta
Mid of December projected for Beta
Stable before end of the year
HTML Emails
Contact Subtypes
New Fancy Date Widget (Woo hoo!)
Hopefully take time for alpha
Upgrades testing would be great on real client data!!!!
Canvas and Phone bank report
Get those reports in for beta
Testing -> 80% of the API
Code Coverage -> (clarification from Michau) -> BAO was being included
-> fixing the code coverage....hopefully will still be as high.
More testing place by 3.1 to improve test coverage
Trying to slim down core and shoring modules/ add ons
the canvas and phone banks are just reports
SUggestions on backchannel (drush and aegir)
Whats in the pipe for 3.2 still being decided Civicase some lists of stuff on 3.2 list talk of campaign stuff sessions tab problem maybe
Finance/Accounting Integration - Peter Davis
peter -> dharmatech please update wiki with progress so we can point customers
to it
sarmeesha -> waiting for funding for the project
Want to focus on basic elements (no clients have called, noone chimed in yet)
Happy to post another copy of current post
Talked internally about approaching companies in forums who have
posted with the need
We have done some prototypes -> Scope (income tracking)
Peter-> sounds like we don't have yet answer to 'What should civicrm
be doing with accounting data?"
Xavier -> working on some integration work will wait to see how this
will be applicable to this effort
Observations/Thoughts on the CiviCRM Community
Sarmeesha -> collecting comments on experience with civicrm (and community)
brought to test spring and then to Aspiration tech
just collection of thoughts right now... these are perhaps tasks that
advisory board folks can take on
Thoughts?
Joe -> thanks for pushing along, provide more on ramp, what is that
for different audiences, programmers, users, power users,
organizations, etc.
like the idea of focusing on benefits to the community
want to suggest should try to do a little more resources into the
community (time and money)
don;t think the advisory group should be coders
we haven't brought folks like Claire (much more user focused)
putting requirement like unit testing if skilld are available from pers
we should be trying to specialize
work on enabling and outreach (technologies and activities)
..... turns out Claire is actually there
If we have focused tasks it make things work much better
what holds me back is knowing what to do
sarmeesha ->
this is axactly the issue claire
we are developers and integrators
where do we focus our energies
how to we get a clear list of things to do and then commit to sign up
it takes all types
cynthia->
we talk about community but there are roles
there are advisory group members/ developers
get momentum by talking about expectations and wishes from the community
-> (Sarmeesha) testing, documentation, forum posts, talk about with
peers, talk about it at conferences, blogging about it
at conference came up with 11 different ways integrators can contribute
(lobo on irc) assistance with docs, responding to forum posts, writing
case studies, presenting at local meetups, blogging about it
upgrading the book
(12:34:59 PM) dlobo: creating and starting a local group
so perhaps we need to be kmore concrete on what we expect of folks ->
perhaps better coordination of resources for new features in forum or
website (money and time)
encouraging people who are executive decision makers
include communication to clients and interested parties is taking part
in a community
would like to see civi become hugely successful
kurund: may be use local meetup to get feedback on usability, use
them for testing early releases ??
building buzz-> ways of making more awareness
xavier -> something that I liked was a list of concrete actions
list is very valid but seeing some names and specific tasks/goals so
we can sign up
how do we get to htat point -> vote on priorities, allow people to
scratch their own itches
wes -> suggests karmic points -> RFE request for enhncemen ->they can
donate karma into tha i order to vote p features
perhaps something like thsfor prioritizing
problem is that unit testing is not going to get requested in a karma approach
things that core developers look after -> we create karmic
opportunities -> if i submit a patch then I also need to test and have
testing in place before I recieve karma
feel like we have lots of feature requests and not enough developers
people often care more about earning the karma versus using the karma
focus karma and key areas like answering posts and contributing code
-> like drupal has a way to beenfit from contributing patches
sarmeesha (recap) -> recognition and growing developer base -> does
anyone want to sign up to do this? ...perhaps drupal module...
will be investigated
how do we bring the goals listed here in line with org
feeling overwhelmed with user vs develoepr needs
foster group elemnts within civicrm -> organize groups -> segment
different audiences...etc. (submembers of the user base)
when drupal started using organiz groups....improved community involvment
take a similar approach to usability -> focus on some priorities ->
will focus on pbringing elemnts to EU conference (Michael and Xavier)
michael has been working on a regional area organic group (will link)
sarmeesha and roberto working on implmenting the groups in civicrm.org
get some sense of the size of the community -> perhaps that would be
useful to see that number (how do we collect those numbers...
sarmeesha, looked at Jira to contribute actively)
there are some good sources of information in Jira that can be mined
about the community
there is an additional piece of information from the ping back database
pull the forums and look at different posts
sarmeesha -> put together notes on measurement piece (forums, ping
back, karma points, etc)
dgg -> getting moretraining together with folks would help with the
user community and some of the pressures that being experiences by
raSA and Dharma
consider webinar model -> used before for CiviCASE, PHP willing to contribute
getting people to see other contributing helps them to contribute (Michael)
sarmeesha -> would you blog about how to put together a developer
meetup (Michael -> do have wiki page I can send around)
wes-> might be cool to try doing a bug day model and *online*
developer sprints (helps with developers who are far away or overseas)
have online traiing with posted schedule show up in IRC when your
topic is scheduled to be talked about
follow a lullabot model for sharing sessions
one thing that came up recently -> we used blogs and posts and forums
and emails.... and got no response for test sprint.... networking is
much more effective to get people hooked in
(on irc) session on how to write a test as a remote event
develop greater person to person network....works better than mass email blasts
