Options for project week hosting

(Jean Christophe Fillion Robin) #1

Update (2017-06-06):

We experimented with few approaches to improve and upgrade the presentation of projects worked on during the Slicer project week:

Despite our best effort, we resumed to use the traditional wiki https://na-mic.org/wiki/Project_Week_25

  • Google site did NOT provide a way to revision the different versions. It is not made for collaborative editing.
  • Discourse provided supports revision but we did NOT have a clear pathway to manage edit rights on existing “pages” (or post)

Each topic found in this sub-forum describes projects that attendees worked on during the project week.

What is a project week ?

The Project Week is a week-long hands on activity in which medical image computing researchers create solutions using the open source image computing platform, 3D Slicer, and VTK, ITK, and CMake libraries. Participants work collaboratively on solutions that lie on the interfaces of the fields of computer science, mechanical engineering, biomedical engineering, and medicine. In contrast to conferences and workshops where the primary focus is to report results, the objective of the Project Week is to provide a venue for creators of medical image computing open-source software creators to collaboratively work.

When, where, how much?

Twice a year - June in Europe, and January at MIT. Ad-hoc meetings are added occasionally. The registration fee is approximately 350 (USD or Euro), and is used to cover coffee and food.

How does it work?

Weekly videoconferences for preparation begin 8-12 weeks before an event. Potential participants propose projects during these meetings, and collaboratively create a list of projects that are of mutual interest. The projects include platform work, algorithm development, and biomedical applications. Through the course of the meetings, each participant selects one or more project teams and develops goals for the week. The first day of the Project Week itself begins with a 2-hour in-person introduction to all projects and participants. The rest of the week consists of a mix of working sessions and breakout sessions on special topics, as decided by the participants during the preparatory meetings.

Who can attend?

Project Weeks are open to all and publicly advertised. One-day participation is permitted for first-time attendees, but rest stay for the entire event. Email announcements are sent to the Project Week mailing list.

Who should attend?

This is harder to determine. Your best bet is to send an email (see below) or attend a preparatory videoconference.

What else?

The Project Week series was founded in 2005, along with the National Alliance for Medical Image Computing (NA-MIC), which was chartered by the NIH to build a computational infrastructure for biomedical research. Today, Project Week has become one of the major events in the calendars of several NIH-funded Center efforts. Participants in Project Week include NAC, NCIGT, QIICR, and OCAIRO. As of 2014, Project Week is also a MICCAI endorsed event.

Who to contact?

Project Weeks are led by Tina Kapur, PhD, who is happy to tell you more about them.

(Isaiah Norton) unpinned #2
(Tina Kapur) #3

In addition to the google sites and discourse-based options, we also tried the following:

  1. create a spreadsheet of all project using google sheets
  2. link the project details to a google slide within a continuous presentation

The order of experiments was:

  1. mediawiki (old style)
  2. combination of google sheets and google slides
  3. discovery of the new google sites
  4. google site (as mentioned by JC above)
  5. discourse (as mentioned by JC above)
  6. back to mediawiki
(Steve Pieper) #4

It’s been useful to explore these options - also good to know that the wiki wasn’t a terrible choice in the first place. It’s worked well enough that we can hold out for something that’s really good.

I do still think we should be encouraging Project Week attendees to start using the discourse forum for communication, as follow-ons to these discussions in the Winter:

https://na-mic.org/wiki/2017_Winter_Project_Week/UpdatingCommunityForums

https://na-mic.org/wiki/2017_Winter_Project_Week/Organizations

(Isaiah Norton) #5

FWIW, the way to do this currently is to:

  • restrict “See” permission for the category to the ProjectWeek group
  • make all posts into Wiki posts
  • give every group member “minimum wiki edit” trust (TL1)
  • then everyone in the group could edit all posts.

When the Discourse platform updates to the next release (I don’t know ETA) then it will be possible to have Wiki posts visible outside the group, but only editable by members of group with “Create” permission on the category:

https://github.com/discourse/discourse/commit/addc85cd08bbdab5e8cae8b5d041caa94791c67a

1 Like
(Andras Lasso) #6

We could have tried using github directly. You can create/edit files using only the web GUI and overall it’s not much more complicated than any other options.

There are several advantages compared to all alternatives:

  • full offline access! so you don’t have to worry about good internet connection during project presentations, even if you can attach high-resolution images or videos
  • storing project pages in a git repository for a project week is also a nice, compact, self-contained storage (easy to archive/migrate)
  • also possible to sphinx or other documentation generator to automatically convert to nicely formatted webpages or a single PDF
  • no need for yet another account (everybody has github account already)

Searching between multiple project weeks (if each project week is a separate repository) or indexing by search bots may be non-trivial, but maybe solvable by generating webpages. It may simplify things if all project week uses the same repository, as search within a single repository works quite nicely on github.

1 Like
(Jean Christophe Fillion Robin) #7

Agreed. For reference, here is what I suggested few weeks ago:

That said, if we are going to change the format, I would suggest we:

  • allow direct link to each project summary
  • make it easy to process by a script
  • think about exporting existing entries to that new format
  • consider data mining

With that, we could then easily create an index all the projects across all years… and allow search by keyword, > participant, etc …
Having one Google slides per project week would make that hard.

Idea could be to have everything in one GitHub repo, use markdown, look at https://gitpitch.com/ ,

(Andras Lasso) #8

We can try this at the next project week, with/without gitpitch or similar tools.

1 Like
(Isaiah Norton) archived #9