<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p><font size="+1"><font face="Lucida Grande">I find this weird. If Tapani is correct, why on earth are we spending so much on a system that relies on Gmail? I am no geek as you all know, but it does seem to me that since I get all the applications when they
come in, It ought to be within my limited powers of observation to notice when the apps have stacked up enough to nag the EC to take a look.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Which is where we are today, I have done my homework, could the EC please get in there and review the pile so we can have a chat next week? Thanks. I will send a doodle for a call time shortly....</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Steph</font></font><br>
</p>
<div class="moz-cite-prefix">On 2019-04-25 18:51, Tapani Tarvainen via NCSG-EC wrote:<br>
</div>
<blockquote type="cite" cite="mid:20190425225132.GA32074@jay.tarvainen.info">
<pre class="moz-quote-pre" wrap="">Hi all,
The description sounds like they'd tie CiviCRM email setup to Gmail.
Not everybody would be happy to be dependent on Google that way;
indeed one key reason behind the entire project was to get rid of
Google dependency. Not that it's my call to make now, just wanted to
raise the point.
I'm also somewhat confused as to why they'd want to do that, but
then I'm not sure what that RFI tracking system is supposed to do.
Somewhat guessing here, it may be it would be worthwhile to think
about the possible mailing list migration at the same time, as
it might make the Gmail hack here unnecessary as a side-effect
or otherwise involve overlapping work.
I could take a bit closer look at this when I return home next week
and possibly attend another call with Wapix.
Tapani
On Apr 25 13:51, Raphaël Beauregard-Lacroix (<a class="moz-txt-link-abbreviated" href="mailto:rbeauregardlacroix@gmail.com">rbeauregardlacroix@gmail.com</a>) wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
Hi all
An update from Josh on point 3:
*3) New system for tracking RFI's.* Unfortunately, CiviCRM no longer
supports the old email to activity integration so we would need to develop
this using custom code. If we use the simpler IMAP implementation (you have
to set Gmail to allow less secure apps), you are looking at about 20 hours
to integrate one Gmail inbox with CiviCRM activities. If you want that
information not only copied into CiviCRM, but also included in the form for
reviewers, it will require about an additional 10 hours. If you choose not
to implement the additional form integration, you could still view the
email exchange via activities on the CiviCRM contact record.
*Please give me your thoughts on that and point 1 and 2 by Friday COB.*
Thanks
Have a nice day,
On Mon, Apr 22, 2019 at 5:49 PM Raphaël Beauregard-Lacroix <
<a class="moz-txt-link-abbreviated" href="mailto:rbeauregardlacroix@gmail.com">rbeauregardlacroix@gmail.com</a>> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi just a bump on that so that I can go back to Josh from Wapix ASAP
Thanks!
On Sun, Apr 21, 2019 at 1:12 AM Raphaël Beauregard-Lacroix <
<a class="moz-txt-link-abbreviated" href="mailto:rbeauregardlacroix@gmail.com">rbeauregardlacroix@gmail.com</a>> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi all
Follow up from Josh below. Let me think what you would prefer for 1) and
what you think of 2) for peeps in the EC.
Have a nice Easter (or just a nice Sunday!)
***
1) *Configure an automated email to EC members. *You have three options
here. Configuring an email to remind all reviewers when there are pending
membership applications will take about an hour. Configuring an email to
remind only those reviewers who have not reviewed the application yet will
take about 9 hours. Configuring an email to remind only those reviewers who
have not reviewed the application and including a list in the email of the
applications that have not been reviewed will take about 15 hours.
2) *Improve front end column layout.* We have implemented the new column
structure here <a class="moz-txt-link-rfc2396E" href="https://crmtest.ncsg.is/"><https://crmtest.ncsg.is/></a> for your review. Several
things to note: a) The backlink from the reviewers page has not yet been
implemented b) There is apparently nothing to show for the SOI field on the
organization membership page. Do you want something different on this page?
c) Some of the hyperlinks are hard coded to the live site so you'll have to
keep an eye on the URL when testing. If you like what you see here, we are
looking at about 4 hours all together to get this implemented on live.
On Fri, Apr 12, 2019 at 9:05 PM Raphaël Beauregard-Lacroix <
<a class="moz-txt-link-abbreviated" href="mailto:rbeauregardlacroix@gmail.com">rbeauregardlacroix@gmail.com</a>> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi all
A quick update:
The call went well today, Tapani (thanks again!) was there too to
provide some info on points 3,4 and 5 and add #6 which is migrating the
mailing lists and archives.
Wapix will come back to us with an estimate which I will circulate for
approval once I get it.
Have a nice weekend,
Raphael
On Fri, Apr 12, 2019 at 12:42 PM Raphaël Beauregard-Lacroix <
<a class="moz-txt-link-abbreviated" href="mailto:rbeauregardlacroix@gmail.com">rbeauregardlacroix@gmail.com</a>> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">FYI, in case : Postponed by 15 min from original schedule
On Wed, Apr 10, 2019, 19:34 Raphaël Beauregard-Lacroix <
<a class="moz-txt-link-abbreviated" href="mailto:rbeauregardlacroix@gmail.com">rbeauregardlacroix@gmail.com</a>> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi all
Zoom link here for those who would be interested (1 pm EDT this
Friday)
<a class="moz-txt-link-freetext" href="https://zoom.us/j/9965095294">https://zoom.us/j/9965095294</a>
<a class="moz-txt-link-rfc2396E" href="https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F9965095294&sa=D&usd=2&usg=AFQjCNHXvBC9yL4WzPHKSnYbORcH54Kiiw"><https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F9965095294&sa=D&usd=2&usg=AFQjCNHXvBC9yL4WzPHKSnYbORcH54Kiiw></a>
Best,
On Tue, Apr 9, 2019 at 11:50 AM Raphaël Beauregard-Lacroix <
<a class="moz-txt-link-abbreviated" href="mailto:rbeauregardlacroix@gmail.com">rbeauregardlacroix@gmail.com</a>> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi Tapani,
Yes, the call will be taking place Friday at 1pm EDT. Just got a
reply from Wapix a minute ago, so timely!
I don't have the details yet but will share them here when I do
Best,
On Tue, Apr 9, 2019 at 11:17 AM Tapani Tarvainen via Techteam <
<a class="moz-txt-link-abbreviated" href="mailto:techteam@lists.ncsg.is">techteam@lists.ncsg.is</a>> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi Raphaël,
Will you post the call time and details here when the time is fixed?
I might join, depending on the time.
Thanks,
Tapani
On Tue, Apr 09, 2019 at 10:49:13AM -0400, Raphaël Beauregard-Lacroix
via Techteam (<a class="moz-txt-link-abbreviated" href="mailto:techteam@lists.ncsg.is">techteam@lists.ncsg.is</a>) wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
Hi both (and everyone else)
Thanks for your comments. As for the complexity level of these
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">issues, it
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">is something that I will discuss with them before they start on
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">anything.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
If the estimate for each is more than a few hours at most, that is
something that would substantially deplete our remaining
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">development
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">blocks, I would come back here and ask for your input.
Farrell, I don't think there is a "need" for you to join, but I
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">did not
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">mean this to be a secret call or anything, hence my invitation :)
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">But yes I
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">will report here after the call and also as the work progresses.
Have a nice day,
On Mon, Apr 8, 2019 at 4:35 AM Ekue Farell Folly <
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap=""><a class="moz-txt-link-abbreviated" href="mailto:farell@benin2point0.org">farell@benin2point0.org</a>>
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Dear Raphael,
Interesting and great job. I have no additional concerns. For a
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">first
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">meeting, I think that everything is covered.
As far as being on the call is concerned, If you think that it
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">might be
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">useful (for NCSG representativity, for instance) I could join,
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">otherwise;
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">reading your minutes notes afterwards should be sufficient.
Good luck.
On Sun, 2019-04-07 at 19:05 -0400, Raphaël Beauregard-Lacroix
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">via Techteam
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">wrote:
Dear all,
I would like to schedule a call this week with Wapix in order to
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">inform
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">them of our priorities list with regards to the currently
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">outstanding
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">issues we have with our membership database and management
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">software. We
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">still have some development time to use.
I would suggest moving forward with the following order of
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">priorities:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
1. Configuring an automated email reminder to EC members
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">every two
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> weeks when there are pending membership applications (let us
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">say, every 2
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> weeks)
2. Cleaning the front end of useless information and changing
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">what we
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> have now into a four column layout: name, SOI, who (among EC
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">folks) has not
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> evaluated yet and an "evaluation" link to the form where we
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">(EC folks) put
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> our evaluation of the members.
3. A new system to track RFIs, so that we could see both the
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">RFI and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> eventually the answer of that person in the evaluation form
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">(but not
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> directly on the main front end page with pending members, to
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">keep that one
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> as clean as possible). This new system would dispense Maryam
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> copy-pasting everything manually
4. Resolving a display issue when a voter's list is pulled
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">out through
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> the backend. This is entirely a backend thing, but I
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">understand that it is
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> quite inconvenient when holding the elections.
5. Ensuring that the current existing "relations" (a CIVI
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">term)
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> between "individual" and "organisation" contacts reflects the
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">reality of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> how NCSG/NCUC/NPOC are actually structured (and how certain
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">individuals may
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> have several hats, etc.). This is especially important in the
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">context of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> elections.
Let me know if you have suggestions, comments, edits, or another
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">vision of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">our priorities and if you would be interested in joining the
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">call (who
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">knows ;))
Maryam, I will probably need your assistance when we get to 4
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">and 5, so
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">that I understand correctly the problem and the desired
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">solution; I will be
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">in touch with you when the time comes.
Have a nice week!
Raphael
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Techteam mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Techteam@lists.ncsg.is">Techteam@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/techteam">https://lists.ncsg.is/mailman/listinfo/techteam</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
</body>
</html>