Talk:Citizen App: Difference between revisions
No edit summary |
|||
(5 intermediate revisions by 2 users not shown) | |||
Line 33: | Line 33: | ||
;Next Steps | ;Next Steps | ||
Tyler and Wilf working to make the code base easily accessible in time for the Citizen App code open sourced date of February 1st | Tyler and Wilf working to make the code base easily accessible in time for the Citizen App code open sourced date of February 1st | ||
: [https://github.com/citizen-app/HAT2.0 PDS] - PDS forked from HAT2.0 | |||
: [https://github.com/citizen-app/localdockerdb localdockerdb, convenient Local Postgres] | |||
: [https://github.com/citizen-app/rumpel-react Rumpel-React, the Front-end for the PDS] | |||
== Meeting February 8th 2022 == | |||
'''Code Status''' | |||
The Citizen App (HAT2.0, Rumpel) code has been moved to a new GITHUB repository under the Mozilla license. This needs to be moved to [https://github.com/opencommons OpenCommons] | |||
'''[[User:Wpinfold|Wilf]]''': Will invite Ty's Dataswifty persona to OpenCommons | |||
'''[[Tyler Weir|Ty]]''': Will move the code | |||
'''Transcript App Status''' | |||
CASE students have decided to use a Block Search Data Wallet Application. | |||
For this code to be useful to the open source community it is important that it be developed under an OSI-approved license. Popular licenses include. | |||
*[https://opensource.org/licenses/Apache-2.0 Apache License 2.0] | |||
*[https://opensource.org/licenses/MIT MIT license] | |||
*[https://opensource.org/licenses/MPL-2.0 Mozilla Public License 2.0] | |||
*[https://opensource.org/licenses/EPL-2.0 Eclipse Public License version 2.0] | |||
The code should also be developed using tools like GIT so its provenance can be tracked and submissions managed during and after the student's project. | |||
'''[[User:Wpinfold|Wilf]]''': Will introduce Youngjin to the [https://ospoplusplus.com/ OSPO++ group]. This group is working with Universities to establish a network of University Open Source Programming Offices to manage Open Source with sufficient discipline that it becomes a university wide asset. | |||
'''WIKI Text''' | |||
We want some text that can be added to the OpenCommons WIKI and the READ.ME of all data wallet and associated applications to explain the value of joining the community, how it works, govenance and where to find all the parts. | |||
'''[[User:Wpinfold|Wilf]]''': Develop first draft and circulate before next meeting for review. | |||
'''Timeline''' | |||
There was discussion about upcoming meeting dates. Current dates show | |||
*Feb 24: Dataswift US/Europe monthly Partner Updates and Discussions - [[User:Wpinfold|Wilf]] to discuss this project at 6am Pacific. | |||
*March 1: 5th Digital Person Symposium - Partners to promote their work - 2am-10am Pacific | |||
'''[[Irene Ng|Irene]]''': Check schedule of Feb 24 meeting (Concerned it may be earlier) and provide agenda for Mar 1 meeting | |||
'''Legal''' | |||
There was a discussion of the data trust infrastructure. Irene is working on defining the legal framework. The objective is to develop a No-legal environment that is similar to the No-code environment in that No-legal is an approach to data sharing that requires few, if any, legal skills. | |||
There was a discussion of legal contracts written in code. [[Irene Ng|Irene]] explained this is already well represented in the Citizen App platform through the concept of HMIC (HAT Microserver Instruction Contracts). |
Latest revision as of 17:12, February 8, 2022
Meeting January 25th 2022
This is the first meeting of the Citizen App Steering Committee.
Attendees Ben Forbes, Erman Ayday, Irene Ng, Paul Tasker, Tyler Weir, Wilfred Pinfold, Youngjin Yoo
Decisions Made and Agreed during the meeting
- Timeline
- 1 Feb: Citizen App code open sourced by Dataswift for initial collaboration
- 1 Feb: Urban Systems join Citizen App project to assist with documentation
- 1 Feb: XLab/Case Western Reserve University students join the project group
- 10 Feb: Basic documentation ready for Citizen App project by Urban Systems.
- 10 Feb: Information to developers community that the project is now open for collaboration
- 16 Feb: Urban Systems CEO, Wilfred Pinfold, Dataswift CEO Irene Ng have a pre-Symposium fireside chat on the Citizen App, its importance, its purpose and how to get involved.
- 21 Feb: Blogpost on citizen app with video of fireside chat and the Citizen app manifesto is out
- 1 Mar: Citizen app project official launch at the 5th Symposium of the Digital Person
- License
The HUT and Rumple code bases will be made available under the Mozilla Public License 2.0. This was selected over the AGPL license to improve adoption particularly by commercial users.
- Meetings
This group will meet bi-weekly during the launch phase of this project to set direction of the project. Next meeting will be at 7am Pacific on February 8th.
- Host
Opencommons will act as host to the project. We will establish a membership fee designed to cover costs of code management and legal defense. Benefits of paying the membership fee will be eligibility to join the 'Citizen App Steering Committee' which will become an elected position among members. Membership Fee structure and amount is to be set by the Steering Committee at a future meeting.
- Policy
Opencommons Privacy Policy Statement will be used. Suggestions for improving this policy should be brought to future meetings.
Opencommons Policies and Procedures refer to Apache License Version 2.0 unless otherwise specified. We will discuss this wording at a future meeting since the code will refer to the Mozilla License explicitly this should be fine but some modification may be beneficial for clarity.
- Next Steps
Tyler and Wilf working to make the code base easily accessible in time for the Citizen App code open sourced date of February 1st
- PDS - PDS forked from HAT2.0
- localdockerdb, convenient Local Postgres
- Rumpel-React, the Front-end for the PDS
Meeting February 8th 2022
Code Status
The Citizen App (HAT2.0, Rumpel) code has been moved to a new GITHUB repository under the Mozilla license. This needs to be moved to OpenCommons
Wilf: Will invite Ty's Dataswifty persona to OpenCommons Ty: Will move the code
Transcript App Status
CASE students have decided to use a Block Search Data Wallet Application. For this code to be useful to the open source community it is important that it be developed under an OSI-approved license. Popular licenses include.
The code should also be developed using tools like GIT so its provenance can be tracked and submissions managed during and after the student's project.
Wilf: Will introduce Youngjin to the OSPO++ group. This group is working with Universities to establish a network of University Open Source Programming Offices to manage Open Source with sufficient discipline that it becomes a university wide asset.
WIKI Text
We want some text that can be added to the OpenCommons WIKI and the READ.ME of all data wallet and associated applications to explain the value of joining the community, how it works, govenance and where to find all the parts.
Wilf: Develop first draft and circulate before next meeting for review.
Timeline
There was discussion about upcoming meeting dates. Current dates show
- Feb 24: Dataswift US/Europe monthly Partner Updates and Discussions - Wilf to discuss this project at 6am Pacific.
- March 1: 5th Digital Person Symposium - Partners to promote their work - 2am-10am Pacific
Irene: Check schedule of Feb 24 meeting (Concerned it may be earlier) and provide agenda for Mar 1 meeting
Legal
There was a discussion of the data trust infrastructure. Irene is working on defining the legal framework. The objective is to develop a No-legal environment that is similar to the No-code environment in that No-legal is an approach to data sharing that requires few, if any, legal skills.
There was a discussion of legal contracts written in code. Irene explained this is already well represented in the Citizen App platform through the concept of HMIC (HAT Microserver Instruction Contracts).