SS P03 23MAY2013

From PHUSE Wiki
Jump to: navigation, search

Agenda:

1. License update

2. Click-through license agreement

3. Inventory page draft

Attendees:
Mike Carniello – Takeda
Joy Li – FDA
Sam Tomioka – Sunovion
Kim Musgrave – Amgen
Yingshan You – Johnson & Johnson
Nancy Brucken - inVentiv
Dirk Spruck – Accovion (and PhUSE)
Jingyee Kou - FDA
Dany Guerendo - StatProg LLC
Hanming Tu - Accenture

Regrets:
Ian Fleming - d-Wise
Lina Jørgensen - Novo Nordisk

Rambling notes collected by Mike C:

Agenda Items 1 and 2:

Dirk: Didn't we agree on the MIT license? Mike: Yes, trying to finalize that stuff. Sally Cassells is working with a PhUSE lawyer on this.

Here's an example of a "click through" license:

http://i3.iis.net/media/7187340/installing-and-configuring-ftp-7-on-iis-7-263-2.jpg?cdn_id=2013-05-01-001

But ... typical Open Source software has a big disclaimer on website.

Idea: Maybe put something on the main page? With some explanation of what the actual license is.

Action: Ask Hanming to add some text pointing out the license, as there is no mechnical way to have a click-through license agreement with Google Code.

Action: Mike to update list of project members on the Project 03 Wiki page.

As a follow up, here's an updated on the license issue from Chris Decker of PhUSE: We have contracted (at a deep discount) with a US lawyer to review the agreement and update any pieces that are specific to US law. So we will have a US version and a UK version. We're going to have to stop there as we can't afford to adjust for the other 191 (194 depending on who you talk to) countries in the world so this will have to suffice.

Agenda Item 3
Inventory suggestions: -- add some hierarchy (Kim)


Dirk: adding a button the PhUSE main web page, linking to the Script Inventory

Some editing going on during the conference.

Should scripts be recruited into the repository? Or should they be jointly developd among PhUSE WG members?

What else to do?

Look into some technical issues (save/publish, rollback, lock, block-on, etc.) - Hanming T.

Actions:

Hanming to add some text pointing out the license, as there is no mechnical way to have a click-through license agreement with Google Code.

Mike C to add project members to Wiki Page, but not emails, and send links etc. to the 10 people on the call today.

All: edit the Inventory Page

All: Get access to the repository in code.google.com, and make sure you are in the repository as a committer.

All: Mike will set up a real script that we can jointly collaborate on, so that all can get a good taste within google code.

Users will need to send Hanming email address to get on Google Code.