<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Stupid question maybe, but why does the LOC have to pay for this?
Why is it not covered by OSGeo?</p>
<p>Best regards,</p>
<p>Bart<br>
</p>
<div class="moz-cite-prefix">On 15-05-2020 22:17, Malena Libman
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALyHoKj8Q2rNe0Nt+Ta=WD3Zr5H1Xr4uAKr92eb=vqJQNDZM4g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default"
style="font-family:verdana,sans-serif">Thank for your answer
Eli.</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">I think some of my
answers are not as perfect in english as a thought they where.</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">I didn't mean we wanted
to start to pay whenever we want, it's just that with no
income for at least 4 months and the need to relieve the CLOC
of the MailChimp expense now (the next charge is may 19th), we
don't have the money yet to cover this.</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">As for the final
comment, I also meant to agree with you, not to say that the
CC should do any of our work. </div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Malena</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">El vie., 15 may. 2020 a las
17:10, Eli Adam (<<a href="mailto:eadam@co.lincoln.or.us"
moz-do-not-send="true">eadam@co.lincoln.or.us</a>>)
escribió:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On
Fri, May 15, 2020 at 12:48 PM Malena Libman <<a
href="mailto:malena.libman@gmail.com" target="_blank"
moz-do-not-send="true">malena.libman@gmail.com</a>>
wrote:<br>
><br>
> Hi all,<br>
><br>
> For the FOSS4G BALOC, the issue right now is that we
don't have the budget to support the mailchimp billing while
we are not using it.<br>
<br>
My question was more of, "When does BALOC want to send
messages?" And<br>
not, "When does BALOC want to start paying for the service?"
Many<br>
years, the next LOC is very ready to start sending messages
the<br>
day/week after the prior FOSS4G and sometimes (with careful<br>
coordination) before the prior event. If BALOC wants to start
sending<br>
messages in September (four months from now), we may want to
just<br>
leave it as is, even if BALOC doesn't yet take over payment of
it.<br>
<br>
><br>
> We are working on locking the exact dates, but as long as
we don't launch the CFP or the ticket sales, we don't need the
mailing platform and it's imperative we reduce expenses
considering the pandemic situation world wide and the
precarious future of the conference.<br>
><br>
> Thanks Steven for the suggestion on archive method, maybe
that's the best way to change the billing plan without
downloading information to avoid the concerns that Mark
mentions or losing important data.<br>
><br>
> As Eli mentioned, it would be good for us (as LOC) to
know exactly which tasks are managed by the committee and
which we need to take care of.<br>
<br>
I think the typical approach is that the LOC does almost 100%
of<br>
everything and the Conference Committee does very little
beyond the<br>
initial selection and being available for guidance or advice
or if<br>
issues need input. My (not directly related to this thread)
comment<br>
was about whether we would ever want to reconsider that and
establish<br>
some long term continuity that does some of the routine
conference<br>
logistics. That was mere commentary on my part.<br>
<br>
Best regards, Eli<br>
<br>
><br>
> Cheers<br>
><br>
> Malena<br>
><br>
> El vie., 15 may. 2020 a las 16:29, Eli Adam (<<a
href="mailto:eadam@co.lincoln.or.us" target="_blank"
moz-do-not-send="true">eadam@co.lincoln.or.us</a>>)
escribió:<br>
>><br>
>> I have some hesitancy to ever be in the situation of
"we can't send<br>
>> emails to our list" which could happen if we plan to
migrate later (or<br>
>> even, unarchive later). If there is some reliable
method to increase<br>
>> and decrease expense that doesn't conflict with other
uses of that<br>
>> function, that might be worthwhile if some individual
wants to<br>
>> reliably take that on. Do we know when FOSS4G 2021
wants to start<br>
>> sending messages?<br>
>><br>
>> I'm also open to evaluating options like <a
href="https://phplist.com/pricing" rel="noreferrer"
target="_blank" moz-do-not-send="true">https://phplist.com/pricing</a><br>
>> if it were found to be equivalent (or better) and
would support open<br>
>> source software while doing it. Generally, I think
there is some<br>
>> value to stability in things like this and we
shouldn't be changing<br>
>> too frequently. Any change should be done in
coordination with a LOC<br>
>> (or if it were to be part of a more centrally managed
service by the<br>
>> Conference Committee).<br>
>><br>
>> For straight cost, +1 to what Darrell and Mark said.
This cost is<br>
>> minor in the big picture. Generally sysadmin time is
one of the more<br>
>> scarce resources around OSGeo and I think that is
best reserved for<br>
>> other functions that can't easily be done
otherwise/elsewhere. We<br>
>> would need to talk to SAC before shifting
responsibility of FOSS4G<br>
>> emails going through correctly on tight timelines to
them.<br>
>><br>
>> More generally, evaluating which tasks are managed
centrally by the<br>
>> Conference Committee and which are shuffled from LOC
to LOC might be<br>
>> worth a larger conversation (maybe on some other
thread).<br>
>><br>
>> Best regards, Eli<br>
>><br>
>> On Fri, May 15, 2020 at 9:34 AM Darrell fuhriman <<a
href="mailto:darrell@garnix.org" target="_blank"
moz-do-not-send="true">darrell@garnix.org</a>> wrote:<br>
>> ><br>
>> > My general feeling on these things is that it’s
worth the money to not put any more burden on volunteers than
is necessary — especially if that burden can be easily
outsourced for what is frankly a pretty small charge in the
grand scheme of things.<br>
>> ><br>
>> > If you can revert to free and then upgrade as
necessary, that seems like an excellent investment to me.<br>
>> ><br>
>> > Darrell<br>
>> ><br>
>> > > On May 15, 2020, at 08:52, María Arias de
Reyna <<a href="mailto:delawen@gmail.com" target="_blank"
moz-do-not-send="true">delawen@gmail.com</a>> wrote:<br>
>> > ><br>
>> > > Dear Conference Committee,<br>
>> > ><br>
>> > > We just had a meeting with the Calgary team
to give us the credentials<br>
>> > > of the shared accounts by all LOCs.<br>
>> > ><br>
>> > > We have a question regarding MailChimp. We
understand this is an<br>
>> > > interesting tool that has been widely used
in the past. Right now it<br>
>> > > has a cost of 93€/month.<br>
>> > ><br>
>> > > Considering we are not going to widely use
it in the next few months,<br>
>> > > we are going to export all the contacts to
convert it to a free plan<br>
>> > > for the time being and then decide at a
later stage what to do with<br>
>> > > it. Possibly reimport all the contacts and
pay again, if there is no<br>
>> > > better alternative.<br>
>> > ><br>
>> > > Can the Conference Committee discuss to
have some FOSS version of<br>
>> > > this, like PHPList (<a
href="https://github.com/phpList/phplist3" rel="noreferrer"
target="_blank" moz-do-not-send="true">https://github.com/phpList/phplist3</a>
), on OSGeo<br>
>> > > servers that will allow us to do the same
without depending on an<br>
>> > > external provider?<br>
>> > ><br>
>> > > Cheers,<br>
>> > > María.<br>
>> > >
_______________________________________________<br>
>> > > Conference_dev mailing list<br>
>> > > <a
href="mailto:Conference_dev@lists.osgeo.org" target="_blank"
moz-do-not-send="true">Conference_dev@lists.osgeo.org</a><br>
>> > > <a
href="https://lists.osgeo.org/mailman/listinfo/conference_dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
>> > _______________________________________________<br>
>> > Conference_dev mailing list<br>
>> > <a href="mailto:Conference_dev@lists.osgeo.org"
target="_blank" moz-do-not-send="true">Conference_dev@lists.osgeo.org</a><br>
>> > <a
href="https://lists.osgeo.org/mailman/listinfo/conference_dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
>> _______________________________________________<br>
>> Conference_dev mailing list<br>
>> <a href="mailto:Conference_dev@lists.osgeo.org"
target="_blank" moz-do-not-send="true">Conference_dev@lists.osgeo.org</a><br>
>> <a
href="https://lists.osgeo.org/mailman/listinfo/conference_dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Conference_dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/conference_dev">https://lists.osgeo.org/mailman/listinfo/conference_dev</a></pre>
</blockquote>
</body>
</html>