Hi Bert, Sorry - I should have made that clearer - it is also on the agenda.
Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: [email protected] twitter: @ianmcnicoll Co-Chair, openEHR Foundation [email protected] Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 4 January 2017 at 12:18, Bert Verhees <[email protected]> wrote: > Please, Ian, also discuss an announcementlist for free and open source > software (my favour is read-only, announcements only), and, also your own > suggestion, to have a low fee membership for single person or low income > business > > Thanks > Bert > > Op wo 4 jan. 2017 om 13:02 schreef Ian McNicoll <[email protected]>: >> >> Thanks for the input everyone. My feeling is that Discourse is worth a >> small experiment but we will discuss at the Mgt Board meeting in a >> couple of weeks. >> >> Ian >> Dr Ian McNicoll >> mobile +44 (0)775 209 7859 >> office +44 (0)1536 414994 >> skype: ianmcnicoll >> email: [email protected] >> twitter: @ianmcnicoll >> >> >> Co-Chair, openEHR Foundation [email protected] >> Director, freshEHR Clinical Informatics Ltd. >> Director, HANDIHealth CIC >> Hon. Senior Research Associate, CHIME, UCL >> >> >> On 2 January 2017 at 10:35, Pekka Pesola <[email protected]> wrote: >> > I agree that the channels need to be well thought but i also think the >> > community needs the best available platform for communication. I don't >> > find >> > the current solution inviting to new members at all. Web archive lacks a >> > good search and replying to old threads is not possible trough web >> > archive. >> > >> > That is in the end what implementers will do. When the specs don't >> > explicitly cover something they will search for information on how >> > others >> > have done the same thing and ask if required - this should be super easy >> > and >> > usable. >> > >> > -Pekka >> > >> > On Fri, Dec 30, 2016 at 4:41 PM, Pablo Pazos <[email protected]> >> > wrote: >> >> >> >> IMO we are over-engineering things that can be solved by agreeing on a >> >> set >> >> of rules. We even have two lists technical and implements and there >> >> might be >> >> just one. >> >> >> >> The active members of the community that participate in these channels >> >> is >> >> low. Adding more communication channels will just disperse the >> >> community. >> >> >> >> We need less channels and usage rules. >> >> >> >> >> >> >> >> On Dec 30, 2016 6:18 AM, "Thomas Beale" <[email protected]> >> >> wrote: >> >>> >> >>> >> >>> Following from what you and Bert have said, it seems that the >> >>> following >> >>> could make sense: >> >>> >> >>> Foundation announcements list / channel (= openehr-announce list we >> >>> have >> >>> now) >> >>> software / libraries / tools announcements (= web home page news items >> >>> with cog icon, also here) >> >>> >> >>> this includes open source software libs / projects >> >>> >> >>> commercial product offerings - currently we don't really have a way of >> >>> doing this, but Industry Partners can post on web home page (factory >> >>> icon) >> >>> >> >>> I'm not sure what the right approach is, since there are many >> >>> technical >> >>> possibilities. >> >>> >> >>> Marcus Baw has proposed moving to Discourse as a forum platform - >> >>> maybe >> >>> this is the kind of thing we should look at? >> >>> >> >>> - thomas >> >>> >> >>> >> >>> On 29/12/2016 17:16, Diego Boscá wrote: >> >>> >> >>> Well, we will provide for free a product that was behind a paywall >> >>> before (LinkEHR lite was the free version we had, and now the 'basic' >> >>> and free version is the equivalent to the past LinkEHR editor). I'm >> >>> curious what kind of announcement we could make :) >> >>> >> >>> >> >>> >> >>> _______________________________________________ >> >>> openEHR-technical mailing list >> >>> [email protected] >> >>> >> >>> >> >>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> >> >> >> >> >> _______________________________________________ >> >> openEHR-technical mailing list >> >> [email protected] >> >> >> >> >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> > >> > >> > >> > _______________________________________________ >> > openEHR-technical mailing list >> > [email protected] >> > >> > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> >> _______________________________________________ >> openEHR-technical mailing list >> [email protected] >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > _______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
