Developer Space Repository

From wiki.gpii
Revision as of 20:48, 4 August 2015 by Anastasiac (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

If you are looking for concrete components to include in your software visit Developer Space/Components until the repository has its own landing page

Developer Space Repository Discussion Page

For now this page hosts the ongoing discussion about the Developer Space Repository, a web based entry point, that will be based on the Developer Space/Components listing.

Current work items are collected within JIRA Component

Contribute to the Discussion on Talk:Developer Space Repository.

The repository is particularly particularly planned to link components developed inside and outside the GPII.

The discussion on this is closely linked to the discussion on how the developer space should look like (see [Talk:Developers_Space]).

This will be a long process, however for now we are focussed with one pressing question:

  • How can we identify the best components that can be used by implementers for early pilots?
  • How can we bootstrap a collection of component code, documentation and other resources so that implementers have a choice?

Building a first Idea

For this Martin, Chris from FHTW and Till, Matthias from KIT had a discussion on 2014-02-27.( FHTW leading the work on building the repository and KIT leading in the Evaluation with Implementers in the P4A Project)

The result of the discussion was (see more input on [Talk:Developer_Space_Repository]):

  • At the meeting a lot of ways to set up the repository were discussed (see below)
  • We were aware that our discussion can only represent a very small fraction. Choosing one way or the other contains a lot of risks:
    • Developers spend great amount of time documenting their systems but Implementers need totally different information?
    • Is the way of looking for something from an AT perspective really that different?
    • What needs to be communicated as a minimum amount of information (about targeted needs , maturity, compatibility)
  • The ways to use this repository will be very different.
  • As discussed at the P4A Kickoff we will therefore organize workshop with "early movers" consisting of volunteers from the P4A Project (Dev: FHTW, KIT, IDRC + Impl: Lifetool, OpenDir, CERTH).
  • The goal of this workshop is to host an open discussion only (not to make any decissions) between implementers and developers
  • We want to build first developer personas and implementer personas (groups of 3)
    • the participants understand their roles and viewpoints
    • we want to use those personas to reflect some of the possibilities
    • we need to collect certain views on the systems to be able to ask for fitting documentation
  • In a second phase of the Workshop we want the participant to discuss important aspects
    • How should the information be structured (Hierarchy, Graph, Heap: pure search-oriented):
      • We will start with 2-3 different mockups of possible repository views to start the discussion that the participants can further develop
    • What information you want in there:
    • We will develop scenarios to understand how information should be structured to be usable and discoverable.

Implementation Plan

How to get to the ontologies / component descriptions ? and How to structure the SW / HW info

  • Exemplary own components describe consider meaningful criteria
  • After similar ontologies in the network such as search Amazon webshop, pdadb , google play gates, EASTIN and out of there looking for the similarities
  • Define Personas : Who should visit the site , what is his motivation / objective
    • Developer
      • what developer who implements a sub-component of a larger SW / HW system
      • . Motivation / Objective: Seeking concrete after
        • 1:1 ready-made solutions or
        • adaptable solutions or
        • examples or
        • Instructions / Tutorials / Webinars / assistance a la Forum

or linked , itself documented components , examples

    • . Technical Expert

How can the application / use case are described ?

    • What derpends on: Experienced developers , technical expert
      • Depending on Motivation / Goal:
        • Link / document components
        • Creating tutorials / webinars, examples
        • Provides help in forums
    • . AT / Rehab . Expert
      • What : "User - expert" : rehabilitation technicians, experts in the AT field , medical rehabilitation with focus ?
      • . Motivation / Goal:
        • Writes Tutorials / Feedback / need / literature from the user's perspective
    • Product Manager / Implementer
      • What : Responsible for the design of integrated solutions
      • . Motivation / Goal:
        • Seeking compatible / combinable components
        • Is feedback regarding demand because practical experience with users is available
    • Consumer ?
      • What : Dedicated users of AT, AT- components
      • . Motivation / Goal:
        • Want to contribute his part, that he is doing or like-minded people better
  • Provides feedback , describes his situation or describes required

How to proceed towards the Component Repository

  • Per component descriptions
  • Describe Use Cases
  • defne requirements
  • Choose CMS / Tools
  • iteratively improve

Some Notes

Notes from KIT internal discussion on possible influencing factors that need documentation:

  • Licenses
    • free software
    • payed licenses?
  • API
  • Modules and interfaces
  • Target needs of end users
    • common terms repository
  • GPII comaptibility
  • Use Case Examples
    • one could be adapter to GPII Autopersonalization?
  • Standards
  • Technology / Platform
  • Maturity "Rating" / Experiences
  • Problem Solving/Pratical Feedback from existing users
    • stackoverflow nad alike

Prototypes of Open Developer Space Repositories

Most important part is the forum.

First thread post (editable) normally discribes a software contribution.

You can thank people and donate to ppl doing developer work

Similar old school forum with a lot of resources for the area.

developer zone with lots of subtopics

The good old open directory project

Other Code hosting

See also Comparison of open-source software hosting facilities on Wikipedia.

Once the most popular open source forge featuring wikis, forums, etc.. Lightweight categorization

Was criticized lately for injecting installers. Originally run by geeknet (slashdot).

Mostly code hosting only with mostly issue tracking and wikis added

Mostly code hosting only with mostly issue tracking and wikis added, but has evolved to social network

Code hosting for everybody (not only projects) . Rather a network of individual projects. No real frontpage or defined structure.

Not just for software, but according to the Wikipedia entry, there are a few restrictions on the licences that can be used. For example, BSD (which version?), MPL and AGPL are fine, but the Apache licence is not listed.

Focus on software engineering tools.

Wiki based ressources from TI

Classical Faceted Search approach for Hardware components

Semantic Media Wiki Site of the FSF that enables semantic search

Examples for Search User Interfaces for Component Repository

Intelligent selector per parameter

By categories/classifications and different modalities