IEEE.org     |     IEEE Xplore Digital Library     |     IEEE Standards     |     IEEE Spectrum     |     More Sites

Commit 243574be authored by Alfredo Herrera's avatar Alfredo Herrera
Browse files

Minutes/2020Week23_2June.md created from https://stackedit.io/

parent 0cbce5de
### Agenda:
[Alfredo Herrera](https://opensource.ieee.org/alfredo.herrera), [Emilio Velis](https://opensource.ieee.org/emilio.velis), _(RSVP) [Martin Haeuer](https://opensource.ieee.org/martin.haeuer)_, [Stefano Zacchiroli](https://opensource.ieee.org/zack), [Tobias Wenzel](https://opensource.ieee.org/MakerTobey).
#### 1. Follow-up current issues:
Brainstorming on initial to-do list and self-assignment of tasks based on the **"Details"** section in [README.md](https://opensource.ieee.org/community/peer-review/admin/-/blob/master/README.md):
> - Definition of peer review services (description, purpose/objective , availability and applicability limitations, limitations on expectations)
> - Procedures for requesting peer review services
> - Processes for IEEE-SA to implement peer review services
> - Language about the peer review services for the [IEEE-SA Open Source Maintainers Manual](https://opensource.ieee.org/oscom/maintain)
> - How peer reviewers should be acknowledged and recognized
The committee decided to work collaboratively by drafting initial documents in the [Committee's Google Drive](https://drive.google.com/drive/folders/1A8Bji5MJHq-Ablsr9i8DnCsvWEJBp7WB?usp=sharing). Tasks were distributed as follows:
| Task (Issue URL) | Assignee | Deadline |
|----------------------|----------|----------|
|[Service definition](https://opensource.ieee.org/community/peer-review/admin/-/issues/15) | @zack | TBD |
|[Request procedure](https://opensource.ieee.org/community/peer-review/admin/-/issues/16) | @zack, @emilio.velis | TBD |
|[Reviewer acknowledgement](https://opensource.ieee.org/community/peer-review/admin/-/issues/17) | @MakerTobey| TBD |
|[Implementation](https://opensource.ieee.org/community/peer-review/admin/-/issues/18) | @alfredo.herrera | TBD |
|[Maintainer Manual language](https://opensource.ieee.org/community/peer-review/admin/-/issues/19) | @alfredo.herrera | TBD |
| | @alfredo.herrera | TBD |
#### 2. Call for participation template:
Emails were sent to a few [IEEE Societies and Technical Councils](https://docs.google.com/spreadsheets/d/1qWVfBJpXmz-Lk0sxTnT9lIMRjCd0dIxrFEcSWlymjjc/edit?usp=sharing) for participation in the open source peer review committee. Based on the feedback received, the following items need clarification:
- Clarify why IEEE-SA has established the[Open Source Committee](https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/other/OSCOM_Operations_Manual.pdf) instead of assuming it is commonly known.
- Clarify the value of open source for IEEE Societies and Technical Councils
- Clarify the object of peer review for open source on the IEEE platform, and also:
* that there will be a process to request peer review of projects on the IEEE platform
* that service is initially aimed at official IEEE open source projects
* that the open source peer review committee will help establish a list of subject-matter experts to review open source designs
- **[\[ACTION ITEM\]](https://opensource.ieee.org/community/peer-review/admin/-/issues/20)** all committee members are asked to review [call for participation template](https://opensource.ieee.org/community/peer-review/admin/-/blob/master/Call-for-Participation.md) and to comment and suggest rewording/edits to clarify the text so that it can be sent on behalf or our committee to all of IEEE to recruit new members for our committee.
#### 3. General discussion:
Finally, the following topics were discussed:
- **[\[ACTION ITEM\]](https://opensource.ieee.org/community/peer-review/admin/-/issues/21)** all committee members are asked to help clarify "the context of open source design" at IEEE: what exactly is that context? Linked to publication? Hosting of Open Research? Standards related? Project hosting?
- **[\[ACTION ITEM\]](https://opensource.ieee.org/community/peer-review/admin/-/issues/22)** there is a need to define the value proposition that peer-review adds to open source designs. One way to describe the value proposition was shared on a [LinkedIn article](https://www.linkedin.com/pulse/peer-review-open-source-alfredo-herrera-p-eng-msc-ieee-sm/) and is added here to spark our discussion:
> if two projects start from the same source files, by submitting one of them to planned review(s) by a group of subject-matter-experts (i.e. peers): it is reasonable to expect that through this process the design would gain a higher level of quality than the project that did not use peer-review.
- @zack suggested to clarify the "call for participation" template by adding to the first sentence a description of the new IEEE platform. This has been added to [Issue 20](https://opensource.ieee.org/community/peer-review/admin/-/issues/20)
- **[\[ACTION ITEM\]](https://opensource.ieee.org/community/peer-review/admin/-/issues/23)** we discussed the idea of asking IEEE-SA marketing to help us send a "Call for participation" email to all of IEEE; but it was decided to discuss this on our next call
- **[\[ACTION ITEM\]](https://opensource.ieee.org/community/peer-review/admin/-/issues/24)** it was suggested to remove "design" from first bullet in the **"Request for participation"** section of the "Call for participation" template. Issue was created to allow for discussion prior to change.
#### 4. Send minutes with action items, dates and name.
These meeting minutes mark the beginning of use of the Issues functionality in this platform. We will discuss their use on the next call and collect feedback on how to tailor to our needs.
> Written with [StackEdit](https://stackedit.io/).
<!--stackedit_data:
eyJoaXN0b3J5IjpbNDYxODQxMzRdfQ==
-->
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment