Kevan/all,

I trust you must have missed the full text I sent here a bit earlier, thus
here is the complete content.

And the first and most important issue rephrased. It is one thing to
demonstrate such a web based interface works, the other more important one
crucial to growing the community is "Can this work at Apache?"
Unfortunately the mindset is very code-driven, but this is not the case
here. A large majority of people contributing new device information to the
"data" project are unlikely to do this via "Git Pull-requests" though that
could be an improvement over XML, if we really want to

Does foundation bureaucracy allow a "contributor" to provide such
information just the way it works e.g. in a JIRA bug ticket (IMHO
attachment to JIRA may not work properly here, I don't think Gopal's
approach works like that, but I have not seen much of it yet)

 The last code release happened on March 24, both to the "data" and
"client" code. There is regular sync with OpenDDR and until we know the
data/resource gathering can be done at DeviceMap in a consistent and
approved way that helps grow the community, it is good to be backward
compatible with OpenDDR. Should it be necessary to use it as "fall-back"...


For the bottom parts including last time (code) committers were added,
please refer to earlier Wiki or ask Bertrand.


Cheers,

Werner

---------- Forwarded message ----------
From: Werner Keil <[email protected]>
Date: Thu, Jun 5, 2014 at 2:14 PM
Subject: Re: Incubator PMC/Board report for Jun 2014 ([ppmc])
To: "[email protected]" <[email protected]
>


That was done earlier, but let me try accumulate it here:

--------------------DeviceMapApache DeviceMap is a data repository
containing device information, imagesand other relevant information
for all sorts of mobile devices, e.g.smartphones and tablets. While
the focus is initially on that data, APIs willalso be created to use
and manage it.DeviceMap has been incubating since 2012-01-03.Three
most important issues to address in the move towards graduation:  1.
Does Appache support contribution throgh a Web based interface/API to
add new device specs (similar to e.g. Eclipse Babel)  2. Improved
support for additional languages/platform (.NET, PHP,...)  3. Any
issues that the Incubator PMC (IPMC) or ASF Board wish/need to beaware
of?How has the community developed since the last report?
Presentations at conferences like JavaLand raised awareness. A Mobile
Development MeetUp group in Germany is looking into the code, and
where they might contribute.How has the project developed since the
last report?Syncing device data with OpenDDR in regular intervals when
relevant changes occur. Update of the Java DDR Simple API and other
libraries.Date of last release:   2014-03-24When were the last
committers or PMC members elected?


The release is based on recent updates and SVN tags, it can be considered
"Milestone" or "Snapshot" release, while the project is incubating.

Please add anything that crosses your mind or other may still want to
mention, too.

I guess you know when the last committer was elected. That's been a while
ago, which is why a more "lightweight" alternative for contributing (only
device data, no executable source code) is important do explore and
implement[?]

We might share such contributions if the system is in place under
"community" if the people who do that are not seen as "committers" in
traditional sense, but it would clearly show what people do or don't.

Thanks,
Werner


On Thu, Jun 5, 2014 at 1:38 PM, Bertrand Delacretaz <[email protected]>
wrote:

> On Thu, Jun 5, 2014 at 11:23 AM, Werner Keil <[email protected]>
> wrote:
> >
> > No, it's that special (?) Wiki page for the PMC report...
>
>
> http://wiki.apache.org/incubator/June2014 ? I'm happy to give you
> write access if you tell me your username for that wiki, and if you
> cannot create a user please explain what you did and what happened.
>
> >
> > . And Gopal who already wanted to add his (important) sentence about the
> committer interface,
> > said he couldn't do so either...
>
> The report draft can also be discussed/amended on this list and we
> then post the result.
>
> -Bertrand
>

Reply via email to