If you didn't respond to the Doodle poll but would like to join - if possible please send me a note beforehand so I can add you in advance, as Google Hangouts works more smoothly that way.
Please share your ideas for the structure and topics. I'll send a draft agenda tomorrow.
topics: - are current modules really modular (one DB, one REST backend)? aka monolithic vs modular architecture - strategy for REST API development (consolidation of authentication, naming resource naming conventions, JSON data structures) - REST API vs OC UI (widgets) - managing requests for community contributions (technical community needs to know, where the contributions may be necessary to keep the core functions free for use for everybody)
It is totally fair to change the business model as intended by OpenClinica. The first attempts towards paid add-on modules started years ago and this is the logical consequence. Breaking this monolithic code apart will make it more reliable, testable and manageable and that's a big plus from the validation perspective. I personally just like to know which existing functionality is intended to be core and which not. A well documented and implemented Rest-API will unfurl great potential since there are some very dedicated community members out there. I'm looking forward to participate in the development of some modules to leverage the potential of open source EDC.
@lindsay Thank you to emphasize clearly what's going wrong with external code contributions.
I'd add that we should discuss how to keep the community initiative moving - through future calls, assignment of leadership responsibilities, designate workgroups, etc. to align with progress on the technical front.
So, here's a proposed agenda:
- Introductions - 5 min - Objectives for the call - 5 min - Modular Architecture - 25+ min - Are current modules really modular (one DB, one REST backend)? aka monolithic vs modular architecture - Strategy for REST API development (consolidation of authentication, naming resource naming conventions, JSON data structures) - REST API vs OC UI (widgets) - Summary of work underway or in planning - toolkit for developers, core + modules, OSS vs non - Integration/relationships with other OSS health tools - Enable participation - 15+ min - Managing requests for community contributions (technical community needs to know, where the contributions may be necessary to keep the core functions free for use for everybody) - Handling pull requests - Better, more open test & CI workflow - What we can do now vs future when core+modules architecture is more clear - Keeping this community initiative moving - what's the model? what do we do next? - 10 min - Decide on and summarize next steps - 5 min
We had an excellent call last week. Here are some of the important points:
OpenClinica will become a modular, micro-services based platform to enable easier developer participation and faster, better feature development. It will ultimately enable development of your own modules, and sharing of modules in both commercial and open source-friendly ways.
A "core" will provide the data persistence, auditing/provenance, module registration/management, and a few other basic services, mostly via REST APIs. Everything else will be a module.
The "core" and most basic EDC modules will be open source.
A toolkit will help developers build OC modules with minimal learning curve by providing useful components and access to the core services in a packaged way
We will be setting up a working group to help guide the architecture and development efforts. Contact me off-list if you'd like to be part of this.
We'll have another call in mid/late May and discuss the new architecture and plan in more detail. Please respond to the doodle poll: http://doodle.com/poll/zxvq5nvpaz7hvhmx
I know this forum discussion has been dormant but as version 4 comes closer to reality (I hope). Can OpenClinica people gives us a peek behind the curtain as to new features particularly in the area of query processing, generating reports (dashboards) and monitoring. Some of us want to know what OpenClinica Enterprise 4.0 will provide and what we need to develop on our own.
I'll reach out off-list to set up a preview demo. We'll be going into alpha testing next month and will have more to share publicly soon after that. The Advisory Groups that originated from this thread have been immensely helpful in generating ideas and setting the direction for OC4. They've been dormant for the last few months as the development team has been focused on implementation but I'll be reaching out to activate them again.
Comments
T
OpenClinica Community Call - April 14 20:00 GMT (4pm EDT)
https://plus.google.com/hangouts/_/openclinica.com/oc-community1
If you didn't respond to the Doodle poll but would like to join - if
possible please send me a note beforehand so I can add you in advance, as
Google Hangouts works more smoothly that way.
Please share your ideas for the structure and topics. I'll send a draft
agenda tomorrow.
Best,
Cal
Please add me to the hangout,
Thanks and Regards
Ronald
On 11 April 2016 at 23:19, ccollins
wrote:
> OpenClinica http://openclinica.vanillaforums.com/
>
>
>
> ccollins commented on The future of OpenClinica and open source
>
>
>
> Yes, agreed. Here's a link to the hangout:
>
>
>
> OpenClinica Community Call - April 14 20:00 GMT (4pm EDT)
>
> https://plus.google.com/hangouts/_/openclinica.com/oc-community1
>
>
>
> If you didn't respond to the Doodle poll but would like to join - if
>
> possible please send me a note beforehand so I can add you in advance, as
>
> Google Hangouts works more smoothly that way.
>
>
>
> Please share your ideas for the structure and topics. I'll send a draft
>
> agenda tomorrow.
>
>
>
> Best,
>
> Cal
>
>
>
> --
>
> To manage your email notifications, please visit:
> https://www.openclinica.com/forums#/profile/preferences
>
>
>
> Reply to this email directly or follow the link below to check it out:
>
> http://openclinica.vanillaforums.com/discussion/comment/18076#Comment_18076
>
>
>
> Check it out:
> http://openclinica.vanillaforums.com/discussion/comment/18076#Comment_18076
>
>
- are current modules really modular (one DB, one REST backend)? aka monolithic vs modular architecture
- strategy for REST API development (consolidation of authentication, naming resource naming conventions, JSON data structures)
- REST API vs OC UI (widgets)
- managing requests for community contributions (technical community needs to know, where the contributions may be necessary to keep the core functions free for use for everybody)
T
hi Cal
It is totally fair to change the business model as intended by OpenClinica. The first attempts towards paid add-on modules started years ago and this is the logical consequence. Breaking this monolithic code apart will make it more reliable, testable and manageable and that's a big plus from the validation perspective. I personally just like to know which existing functionality is intended to be core and which not.
A well documented and implemented Rest-API will unfurl great potential since there are some very dedicated community members out there. I'm looking forward to participate in the development of some modules to leverage the potential of open source EDC.
@lindsay Thank you to emphasize clearly what's going wrong with external code contributions.
Regards,
Christian
I'd add that we should discuss how to keep the community initiative moving
- through future calls, assignment of leadership responsibilities,
designate workgroups, etc. to align with progress on the technical front.
So, here's a proposed agenda:
- Introductions - 5 min
- Objectives for the call - 5 min
- Modular Architecture - 25+ min
- Are current modules really modular (one DB, one REST backend)? aka
monolithic vs modular architecture
- Strategy for REST API development (consolidation of authentication,
naming resource naming conventions, JSON data structures)
- REST API vs OC UI (widgets)
- Summary of work underway or in planning - toolkit for developers,
core + modules, OSS vs non
- Integration/relationships with other OSS health tools
- Enable participation - 15+ min
- Managing requests for community contributions (technical community
needs to know, where the contributions may be necessary to keep the core
functions free for use for everybody)
- Handling pull requests
- Better, more open test & CI workflow
- What we can do now vs future when core+modules architecture is more
clear
- Keeping this community initiative moving - what's the model? what do
we do next? - 10 min
- Decide on and summarize next steps - 5 min
We had an excellent call last week. Here are some of the important points:
- OpenClinica will become a modular, micro-services based platform to enable easier developer participation and faster, better feature development. It will ultimately enable development of your own modules, and sharing of modules in both commercial and open source-friendly ways.
- A "core" will provide the data persistence, auditing/provenance, module registration/management, and a few other basic services, mostly via REST APIs. Everything else will be a module.
- The "core" and most basic EDC modules will be open source.
- A toolkit will help developers build OC modules with minimal learning curve by providing useful components and access to the core services in a packaged way
- We will be setting up a working group to help guide the architecture and development efforts. Contact me off-list if you'd like to be part of this.
- We'll have another call in mid/late May and discuss the new architecture and plan in more detail. Please respond to the doodle poll: http://doodle.com/poll/zxvq5nvpaz7hvhmx
- Detailed meeting notes: https://docs.google.com/document/d/1GOpEAxe7szT6jAClvw5XxRoCo-CoTjx68jG8nw121F8/edit?usp=sharing
Best,Cal
Thanks to those of you who responded to the Doodle poll. The next community call will be May 24th 8am EDT / 1200 UTC.
Join the hangout at https://plus.google.com/hangouts/_/openclinica.com/openclinica
Preferably email me beforehand and I'll add you to the invite.
Best,
Cal
I'll reach out off-list to set up a preview demo. We'll be going into alpha
testing next month and will have more to share publicly soon after that.
The Advisory Groups that originated from this thread have been immensely
helpful in generating ideas and setting the direction for OC4. They've been
dormant for the last few months as the development team has been focused on
implementation but I'll be reaching out to activate them again.
Best,
Cal