ok, draft now online at the wiki:
https://wiki.apache.org/incubator/March2016

we'd still have some time for any change you want to make before our
mentors sign it off

On Wed, Mar 2, 2016 at 3:19 PM, Stian Soiland-Reyes <[email protected]>
wrote:

> +1 - fair, honest and positive. :-)
>
> On 2 March 2016 at 13:35, Sergio Fernández <[email protected]> wrote:
> > report draft, please provide feedback so we can add it to the wiki by EOB
> > today
> >
> > --------------------
> > CommonsRDF
> >
> > Commons RDF is a set of interfaces and classes for RDF 1.1 concepts and
> > behaviours.  The commons-rdf-api module defines interfaces and testing
> > harness.  The commons-rdf-simple module provides a basic reference
> > implementation to exercise the test harness and clarify API contracts.
> >
> > CommonsRDF has been incubating since 2015-03-06.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Re-engage and grow the Commons RDF community base
> >   2. Work with key target communities (initially within Apache) to ensure
> >      Commons RDF meets potential user requirements and expectations
> towards
> >      next versions of the Commons API.
> >   3. Find lateral target goals that could make the project viable.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   n/a
> >
> > How has the community developed since the last report?
> >
> >   Sleeper community in the last months; very few mails and no commits.
> >
> > How has the project developed since the last report?
> >
> >   Project's development has completely stop in the last months. We
> expected
> >   a different engagement from major RDF toolkits, but since that does not
> >   happen we have start to discuss options to find the viability for the
> > project
> >   https://s.apache.org/oxqb For the next report we should have something
> >   more concrete towards the future or we could thunk about an exit
> strategy.
> >
> > Date of last release:
> >
> >   2015-05-07
> >
> > When were the last committers or PMC members elected?
> >
> >   n/a (no PPMC or Committers have been elected yet)
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Mar 1, 2016 at 11:39 PM, Stian Soiland-Reyes <[email protected]>
> > wrote:
> >
> >> +1 :-))
> >>
> >> Although this is starting to sound like my EU projects.. do we need
> >> User Stories and Personas? :)
> >>
> >> On 1 March 2016 at 11:16, Sergio Fernández <[email protected]> wrote:
> >> > Hi,
> >> >
> >> > On Mon, Feb 29, 2016 at 1:32 AM, Lewis John Mcgibbney <
> >> > [email protected]> wrote:
> >> >>
> >> >> There is doubt the project has been very quiet. Admitedly I have had
> >> little
> >> >> time to bootstrap anything significant e.g. embedding CommonsRDF into
> >> other
> >> >> projects.
> >> >> One question I would like to ask regards where commons RDF is
> currently
> >> >> being used?
> >> >> It might be worth us generating a target list of
> stakeholders/consumers
> >> and
> >> >> then working towards the implementations.
> >> >>
> >> >
> >> > I think it would be worth to explore that, and maybe combined with
> what
> >> > Stian suggested could be good path to find the project real fit.
> >> >
> >> > I we agree on that, by tomorrow I'll prepare a draft of the report
> >> > collecting those ideas.
> >> >
> >> >
> >> > --
> >> > Sergio Fernández
> >> > Partner Technology Manager
> >> > Redlink GmbH
> >> > m: +43 6602747925
> >> > e: [email protected]
> >> > w: http://redlink.co
> >>
> >>
> >>
> >> --
> >> Stian Soiland-Reyes
> >> Apache Taverna (incubating), Apache Commons RDF (incubating)
> >> http://orcid.org/0000-0001-9842-9718
> >>
> >
> >
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e: [email protected]
> > w: http://redlink.co
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/0000-0001-9842-9718
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: [email protected]
w: http://redlink.co

Reply via email to