<div dir="auto">Thanks. That's what I tried to say. Bad phrasing on "cheap", I meant using the money for extending it and making it our own.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El lun., 2 sept. 2019 20:42, Volker Mische <<a href="mailto:volker.mische@gmail.com" target="_blank" rel="noreferrer">volker.mische@gmail.com</a>> escribió:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
On 2019-09-03 02:00, michael terner wrote:<br>
> I am all for having a standard set of tools that are available to FOSS4G<br>
> teams whether the conferences are at the Global, National or Regional<br>
> levels.<br>
<br>
+1<br>
<br>
<br>
> That said, I firmly agree with Maria's statement that "we shouldn't<br>
> force any decision over the LOCs." For example, in the Boston<br>
> Conference, the Registration system and the Abstract submission/scoring<br>
> system was /provided by /our Professional Conference Organizer at a very<br>
> reasonable cost and part of the complete "package" they offered us. This<br>
> saved our volunteers time and focus and it worked very well (e.g., our<br>
> PCO also acted as our "bank" and the registration system they used<br>
> easily integrated with their banking).<br>
<br>
+1<br>
<br>
<br>
> I would also observe that "open source options" aren't necessarily<br>
> /always/ the lowest cost, if you look at them through the lens of "total<br>
> cost of ownership." [...]<br>
<br>
I'm in agreement with Michael here. For me using pretalx is not about<br>
reducing costs it's about spending money in a different way.<br>
<br>
> Is there really an open source option that is as good<br>
> and easy to administer as Attendify? The mobile app is mission critical<br>
> and Attendify has now proven itself as effective across 3 successive<br>
> FOSS4G's? Also, Attendify - at least for Boston - was extremely cost<br>
> effective and we spent only around $1,000 (I don't know what the current<br>
> cost for Bucharest was?). My point is that finding a volunteer to figure<br>
> out and successfully deploy (and extend?) an open source solution could<br>
> easily lead to a total cost of ownership that is higher for using an<br>
> open source solution (if you value the time that volunteers would need<br>
> to invest in making it work). Of course, the GDPR issue is different and<br>
> very important and needs to be resolved. I would hope that Attendify is<br>
> working on it. As per above, this should be an LOC choice and if there<br>
> is a good open source solution, and a team ready to deploy it, then more<br>
> power to that team.<br>
<br>
For the Bucharest LOC it was a good solution given the limited time (in<br>
the last week before the conference) they had to pull such a system of<br>
(that's a long story and wouldn't contribute any meaningful to this<br>
conversation). I've spoken with Codrina (the chair of the program<br>
committee) and she would not recommend it if you have the time to use<br>
another system. It wasn't straight forward to get all the information<br>
they needed into Attendify. Several scripts where needed to get the data<br>
from pretalx (the source of truth) into Attendify (the scripts can be<br>
published for the next team).<br>
<br>
If you use categories in Attendify, you won't have a way to see all the<br>
scheduled things at once. This can lead to people missing talks. Hence<br>
the Bucharest team was putting everything into one category (even the<br>
coffee breaks). This means that we didn't use Attendify the way it was<br>
supposed to be.<br>
<br>
The costs for Attendify were around $1000 USD.<br>
<br>
Hence I'd like to stress that Attendify may be used (perhaps even for<br>
2020) but we should definitely look for better solutions in the long run.<br>
<br>
Cheers,<br>
Volker<br>
<br>
<br>
> On Mon, Sep 2, 2019 at 12:15 PM María Arias de Reyna <<a href="mailto:delawen@gmail.com" rel="noreferrer noreferrer" target="_blank">delawen@gmail.com</a><br>
> <mailto:<a href="mailto:delawen@gmail.com" rel="noreferrer noreferrer" target="_blank">delawen@gmail.com</a>>> wrote:<br>
> <br>
> Hi,<br>
> <br>
> Good to start this already!<br>
> <br>
> For those of you who were not on the codesprint: the talk about<br>
> deploying an open source stack for conference management software in<br>
> OSGeo was to have a tool not only for the international event but also<br>
> for local and regional events. If I'm not mistaken, the stack<br>
> suggested was the same used in FOSSGIS (?) and has ticketing system,<br>
> program planning and mobile app:<br>
> <a href="https://pretix.eu/about/en/" rel="noreferrer noreferrer noreferrer" target="_blank">https://pretix.eu/about/en/</a><br>
> <br>
> I wasn't the full conversation so maybe there were more options<br>
> discussed there.<br>
> <br>
> In my opinion, we should get rid of Attendify ASAP. For a start, it is<br>
> not GDPR compliant (!!!!!), it has a strong vendor lock-in and, what<br>
> is worse, costs a lot of money every year (compared with open source<br>
> options) :-/ Let's apply what we always say of using "licensing" money<br>
> to extend and own the open source software :)<br>
> <br>
> At the same time, we could suggest options but we shouldn't force any<br>
> decision over the LOCs because maybe in some countries the software<br>
> stack chosen is not available/feasible/useful/possible for who knows<br>
> what reason. Thinking for example on blocked countries of the origin<br>
> company.<br>
> <br>
> Cross-posting to the local-chapters mailing list, where I think the<br>
> conversation was going to take place once people arrive at home. So in<br>
> case someone is there, conversation just started! Also there was<br>
> movement to start some shared knowledge between regional chapters<br>
> about how to build community and organize events. But maybe that<br>
> should continue only on the local-chapters mailing list?<br>
> <br>
> Thanks for bringing this up!<br>
> María.<br>
> <br>
> On Mon, Sep 2, 2019 at 4:59 PM Gavin Fleming <<a href="mailto:gavin@kartoza.com" rel="noreferrer noreferrer" target="_blank">gavin@kartoza.com</a><br>
> <mailto:<a href="mailto:gavin@kartoza.com" rel="noreferrer noreferrer" target="_blank">gavin@kartoza.com</a>>> wrote:<br>
> ><br>
> > Hi all<br>
> ><br>
> > The topic of consistent conference infrastructure came up again at<br>
> Bucharest, with the emphasis on giving conference teams maximum<br>
> space to focus on the conference rather than selecting and building<br>
> new back-ends each time. I’ve recently experienced ‘Open Source<br>
> Event Manager’ [1] through my interaction with the Postgresconf<br>
> coming up in Johannesburg [2]. It was a pleasant and slick<br>
> experience and seems to do most of what a FOSS4G would need.<br>
> ><br>
> > If we like it (or something else) we could specify it for 2021<br>
> (along with Attendify which seems to be and accepted component now)<br>
> ><br>
> > Gavin<br>
> ><br>
> > [1] <a href="https://github.com/PostgresConf/pgem" rel="noreferrer noreferrer noreferrer" target="_blank">https://github.com/PostgresConf/pgem</a>, which is a fork of<br>
> <a href="https://github.com/openSUSE/osem" rel="noreferrer noreferrer noreferrer" target="_blank">https://github.com/openSUSE/osem</a><br>
> > [2] <a href="https://postgresconf.org/" rel="noreferrer noreferrer noreferrer" target="_blank">https://postgresconf.org/</a><br>
> ><br>
> ><br>
> > --<br>
> ><br>
> ------------------------------------------------------------------------------------------<br>
> > Gavin Fleming - Joint MD - PrGISc [PGP1234]<br>
> > Visit <a href="http://kartoza.com" rel="noreferrer noreferrer noreferrer" target="_blank">http://kartoza.com</a> to find out about open source:<br>
> > * Desktop GIS programming services<br>
> > * Geospatial web development<br>
> > * GIS Training<br>
> > * Consulting Services<br>
> > Skype: phlemingo<br>
> > Office: +27(0)878092702<br>
> ><br>
> -------------------------------------------------------------------------------------------<br>
> ><br>
> > _______________________________________________<br>
> > Conference_dev mailing list<br>
> > <a href="mailto:Conference_dev@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">Conference_dev@lists.osgeo.org</a> <mailto:<a href="mailto:Conference_dev@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">Conference_dev@lists.osgeo.org</a>><br>
> > <a href="https://lists.osgeo.org/mailman/listinfo/conference_dev" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
> _______________________________________________<br>
> Conference_dev mailing list<br>
> <a href="mailto:Conference_dev@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">Conference_dev@lists.osgeo.org</a> <mailto:<a href="mailto:Conference_dev@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">Conference_dev@lists.osgeo.org</a>><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/conference_dev" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
> <br>
> <br>
> <br>
> -- <br>
> Michael Terner<br>
> <a href="mailto:ternergeo@gmail.com" rel="noreferrer noreferrer" target="_blank">ternergeo@gmail.com</a> <mailto:<a href="mailto:ternergeo@gmail.com" rel="noreferrer noreferrer" target="_blank">ternergeo@gmail.com</a>><br>
> (M) 978-631-6602<br>
> <br>
> _______________________________________________<br>
> Conference_dev mailing list<br>
> <a href="mailto:Conference_dev@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">Conference_dev@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/conference_dev" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
> <br>
</blockquote></div>