You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2012/01/12 11:20:57 UTC
Jena Incubation Report - Feb 2012
Jena reports next month (by the 9th). It probably a good time to do
more than just update the report. Also, there has been some debate on
general@incubator about reports being a bit weak.
Here's suggestions for content:
Key news for this time:
* We have done a release !!
* Apache website fully live ; redirection from old sites in-place.
* We are discussing graduation.
Important issues to address for graduation:
* Prepare graduation materials.
Issues for the Incubator PMC or ASF Board:
* None.
Plan:
* Graduation preparation
(checking, drafting the scope/charter, resolution, chair, more checking)
* Releases of the TDB, Fuseki, LARQ.
General:
* Some JIRA done (** Action:go count activity in the last 3 months).
[Timing :-) Significant contribution has just arrived - SyBase support
for SDB]
Technical:
(as Jena is an existing codebase, maintenance is going to be a major
part of the technical "plan")
* Final (known) bugs in Transactional TDB eliminated - can go for release
* Think about RDF 1.1
Any thing else to add?
Discuss.
Andy
Background:
1/ The report template
2/ The November report (^F for "Jena")
http://wiki.apache.org/incubator/November2011
Re: Jena Incubation Report - Feb 2012
Posted by Andy Seaborne <an...@apache.org>.
On 23/01/12 01:32, Ross Gardler wrote:
> The issue is that in order to graduate you must have all code IP
> clean. Since you will not have released all code the IPMC may ask
> questions about it. You need to be ready to demonstrate that it is all
> IP clean and that you know how to do a release.
>
> I've observed that less surprises for the IPMC at the time of a vote
> means (sometimes) less noise. So demonstrating that you recognise that
> you have code that has not been released but you have worked to ensure
> it is IP clean might smooth things.
>
> Ross
Less surprises for the IPMC the better. It's all quite busy for the IPMC.
Of the remaining code:
TDB, Fuseki, SDB are in the main svn area and should be clean. I tided
up as I want along with all the release related things.
Eyeball isn't in the main area - it may need a bit of cleaning (jars IIRC).
Checking welcome!
Andy
Re: Jena Incubation Report - Feb 2012
Posted by Ross Gardler <rg...@opendirective.com>.
The issue is that in order to graduate you must have all code IP
clean. Since you will not have released all code the IPMC may ask
questions about it. You need to be ready to demonstrate that it is all
IP clean and that you know how to do a release.
I've observed that less surprises for the IPMC at the time of a vote
means (sometimes) less noise. So demonstrating that you recognise that
you have code that has not been released but you have worked to ensure
it is IP clean might smooth things.
Ross
On 22 January 2012 16:10, Benson Margulies <bi...@gmail.com> wrote:
> On Sun, Jan 22, 2012 at 11:08 AM, Andy Seaborne <an...@apache.org> wrote:
>> On 21/01/12 21:03, Ross Gardler wrote:
>>>
>>> The key take away from the reports discussions is to ensure you address
>>> community development issues and demonstrate a plan for moving towards
>>> graduation.
>>>
>>> Jena reports have been doing this since day one.
>>>
>>> The only improvement I cab see (other than those suggested by Ian) is to
>>> indicate how much code had not been released, why and when it will be. I
>>> know this is partly covered already, but it might be good to be clearer
>>> since your mentors are pushing for graduation.
>>>
>>> Ross
>>>
>>> Sent from my mobile device, please forgive errors and brevity.
>>> On Jan 21, 2012 8:24 PM, "Ian Dickinson"<ia...@epimorphics.com> wrote:
>>>
>>>> On 21/01/12 17:47, Andy wrote:
>>>>>
>>>>> [...]
>>>>
>>>> Looks good.
>>>>
>>>> The project has successive produced a release.
>>>>>
>>>>>
>>>> s/successive/successfully/
>>>>
>>>> Also, do we want to be more precise about which components have been
>>>> released, since one of the plan items is to release further subsystems.
>>>>
>>>> We could also mention that most support traffic is now via
>>>> jena-users@apache, with very little flowing through Yahoo groups.
>>>>
>>>> There has been a lot of discussion about better podling reports on the
>>>> Incubator general list. I must admit I haven't bothered to trawl through
>>>> all of it. Mentors, are there any takeaways from that discussion that
>>>> might
>>>> bear on this month's report?
>>>>
>>>> Ian
>>
>>
>> Good sugegstions. It didn't occur to me that partial release might not
>> count as "have done a release". A partial involves the process but not the
>> formal review of content.
>
> My view is that you have indeed 'done a release.' However, having a
> big inventory of code that was last released outside ASF might raise
> an eyebrow or two. Explaining the scale of the issue and plan for
> releasing the rest of it would allow those eyebrows to relax.
>
>
>
>>
>> I didn't include anything about our technical plans, assuming the board is
>> not really interested. Having read other projects reports, I see
>> descriptions of technical work and I have no real idea what they are talking
>> about as they need project context.
>>
>> Revised wording below:
>>
>> Andy
>>
>> Jena
>>
>> Jena is a semantic web framework in Java that implements
>> the key W3C recommendations for the core semantic web technologies of
>> RDF and SPARQL.
>>
>> Jena entered incubation in November 2010.
>>
>> The project is discussing graduation.
>>
>> Progress since the last report:
>> * The project has voted for a new committer and IPMC member for the project.
>> This is the second person since the start of incubation.
>>
>> * The project has successfully produced a release.
>> The first incubator release included the system core
>> but not all the modules. TDB is in active development
>> and is only now ready for release.
>>
>> * Redirections placed at both old websites to point to the Apache incubator
>> website for Apache Jena.
>>
>> * About 20 JIRA items have been resolved since the last report.
>>
>> * Users email traffic on old, non-Apache lists continues to decline.
>>
>> Issues for the Incubator PMC or ASF Board:
>> * None.
>>
>> Plan:
>> * Graduation preparation
>> (checking, drafting the scope/charter, resolution, chair, more checking)
>> * There are no technical or infrastructure items blocking graduation.
>> * Releases of further subsystems: TDB, Fuseki, LARQ.
--
Ross Gardler (@rgardler)
Programme Leader (Open Development)
OpenDirective http://opendirective.com
Re: Jena Incubation Report - Feb 2012
Posted by Benson Margulies <bi...@gmail.com>.
fine by me.
On Sun, Jan 22, 2012 at 11:55 AM, Andy Seaborne <an...@apache.org> wrote:
> On 22/01/12 16:10, Benson Margulies wrote:
>
>> My view is that you have indeed 'done a release.' However, having a
>> big inventory of code that was last released outside ASF might raise
>> an eyebrow or two. Explaining the scale of the issue and plan for
>> releasing the rest of it would allow those eyebrows to relax.
>
>
> Is the text now included what you have in mind or should it say more?
>
> (The release covered >> 50% of the code)
>
> Release: 250104 lines (cloc)
>
> LARQ: 2861
> SDB: 17995
> TDB: 31687 lines
> Fuseki: 6738
> ==> 59281 lines
>
> or 80% released, 20% to go.
>
> Andy
>
Re: Jena Incubation Report - Feb 2012
Posted by Andy Seaborne <an...@apache.org>.
On 22/01/12 16:10, Benson Margulies wrote:
> My view is that you have indeed 'done a release.' However, having a
> big inventory of code that was last released outside ASF might raise
> an eyebrow or two. Explaining the scale of the issue and plan for
> releasing the rest of it would allow those eyebrows to relax.
Is the text now included what you have in mind or should it say more?
(The release covered >> 50% of the code)
Release: 250104 lines (cloc)
LARQ: 2861
SDB: 17995
TDB: 31687 lines
Fuseki: 6738
==> 59281 lines
or 80% released, 20% to go.
Andy
Re: Jena Incubation Report - Feb 2012
Posted by Benson Margulies <bi...@gmail.com>.
On Sun, Jan 22, 2012 at 11:08 AM, Andy Seaborne <an...@apache.org> wrote:
> On 21/01/12 21:03, Ross Gardler wrote:
>>
>> The key take away from the reports discussions is to ensure you address
>> community development issues and demonstrate a plan for moving towards
>> graduation.
>>
>> Jena reports have been doing this since day one.
>>
>> The only improvement I cab see (other than those suggested by Ian) is to
>> indicate how much code had not been released, why and when it will be. I
>> know this is partly covered already, but it might be good to be clearer
>> since your mentors are pushing for graduation.
>>
>> Ross
>>
>> Sent from my mobile device, please forgive errors and brevity.
>> On Jan 21, 2012 8:24 PM, "Ian Dickinson"<ia...@epimorphics.com> wrote:
>>
>>> On 21/01/12 17:47, Andy wrote:
>>>>
>>>> [...]
>>>
>>> Looks good.
>>>
>>> The project has successive produced a release.
>>>>
>>>>
>>> s/successive/successfully/
>>>
>>> Also, do we want to be more precise about which components have been
>>> released, since one of the plan items is to release further subsystems.
>>>
>>> We could also mention that most support traffic is now via
>>> jena-users@apache, with very little flowing through Yahoo groups.
>>>
>>> There has been a lot of discussion about better podling reports on the
>>> Incubator general list. I must admit I haven't bothered to trawl through
>>> all of it. Mentors, are there any takeaways from that discussion that
>>> might
>>> bear on this month's report?
>>>
>>> Ian
>
>
> Good sugegstions. It didn't occur to me that partial release might not
> count as "have done a release". A partial involves the process but not the
> formal review of content.
My view is that you have indeed 'done a release.' However, having a
big inventory of code that was last released outside ASF might raise
an eyebrow or two. Explaining the scale of the issue and plan for
releasing the rest of it would allow those eyebrows to relax.
>
> I didn't include anything about our technical plans, assuming the board is
> not really interested. Having read other projects reports, I see
> descriptions of technical work and I have no real idea what they are talking
> about as they need project context.
>
> Revised wording below:
>
> Andy
>
> Jena
>
> Jena is a semantic web framework in Java that implements
> the key W3C recommendations for the core semantic web technologies of
> RDF and SPARQL.
>
> Jena entered incubation in November 2010.
>
> The project is discussing graduation.
>
> Progress since the last report:
> * The project has voted for a new committer and IPMC member for the project.
> This is the second person since the start of incubation.
>
> * The project has successfully produced a release.
> The first incubator release included the system core
> but not all the modules. TDB is in active development
> and is only now ready for release.
>
> * Redirections placed at both old websites to point to the Apache incubator
> website for Apache Jena.
>
> * About 20 JIRA items have been resolved since the last report.
>
> * Users email traffic on old, non-Apache lists continues to decline.
>
> Issues for the Incubator PMC or ASF Board:
> * None.
>
> Plan:
> * Graduation preparation
> (checking, drafting the scope/charter, resolution, chair, more checking)
> * There are no technical or infrastructure items blocking graduation.
> * Releases of further subsystems: TDB, Fuseki, LARQ.
Re: Jena Incubation Report - Feb 2012
Posted by Andy Seaborne <an...@apache.org>.
On 21/01/12 21:03, Ross Gardler wrote:
> The key take away from the reports discussions is to ensure you address
> community development issues and demonstrate a plan for moving towards
> graduation.
>
> Jena reports have been doing this since day one.
>
> The only improvement I cab see (other than those suggested by Ian) is to
> indicate how much code had not been released, why and when it will be. I
> know this is partly covered already, but it might be good to be clearer
> since your mentors are pushing for graduation.
>
> Ross
>
> Sent from my mobile device, please forgive errors and brevity.
> On Jan 21, 2012 8:24 PM, "Ian Dickinson"<ia...@epimorphics.com> wrote:
>
>> On 21/01/12 17:47, Andy wrote:
>>> [...]
>> Looks good.
>>
>> The project has successive produced a release.
>>>
>> s/successive/successfully/
>>
>> Also, do we want to be more precise about which components have been
>> released, since one of the plan items is to release further subsystems.
>>
>> We could also mention that most support traffic is now via
>> jena-users@apache, with very little flowing through Yahoo groups.
>>
>> There has been a lot of discussion about better podling reports on the
>> Incubator general list. I must admit I haven't bothered to trawl through
>> all of it. Mentors, are there any takeaways from that discussion that might
>> bear on this month's report?
>>
>> Ian
Good sugegstions. It didn't occur to me that partial release might not
count as "have done a release". A partial involves the process but not
the formal review of content.
I didn't include anything about our technical plans, assuming the board
is not really interested. Having read other projects reports, I see
descriptions of technical work and I have no real idea what they are
talking about as they need project context.
Revised wording below:
Andy
Jena
Jena is a semantic web framework in Java that implements
the key W3C recommendations for the core semantic web technologies of
RDF and SPARQL.
Jena entered incubation in November 2010.
The project is discussing graduation.
Progress since the last report:
* The project has voted for a new committer and IPMC member for the
project.
This is the second person since the start of incubation.
* The project has successfully produced a release.
The first incubator release included the system core
but not all the modules. TDB is in active development
and is only now ready for release.
* Redirections placed at both old websites to point to the Apache
incubator website for Apache Jena.
* About 20 JIRA items have been resolved since the last report.
* Users email traffic on old, non-Apache lists continues to decline.
Issues for the Incubator PMC or ASF Board:
* None.
Plan:
* Graduation preparation
(checking, drafting the scope/charter, resolution, chair, more checking)
* There are no technical or infrastructure items blocking graduation.
* Releases of further subsystems: TDB, Fuseki, LARQ.
Re: Jena Incubation Report - Feb 2012
Posted by Ross Gardler <rg...@opendirective.com>.
The key take away from the reports discussions is to ensure you address
community development issues and demonstrate a plan for moving towards
graduation.
Jena reports have been doing this since day one.
The only improvement I cab see (other than those suggested by Ian) is to
indicate how much code had not been released, why and when it will be. I
know this is partly covered already, but it might be good to be clearer
since your mentors are pushing for graduation.
Ross
Sent from my mobile device, please forgive errors and brevity.
On Jan 21, 2012 8:24 PM, "Ian Dickinson" <ia...@epimorphics.com> wrote:
> On 21/01/12 17:47, Andy wrote:
> >[...]
> Looks good.
>
> The project has successive produced a release.
>>
> s/successive/successfully/
>
> Also, do we want to be more precise about which components have been
> released, since one of the plan items is to release further subsystems.
>
> We could also mention that most support traffic is now via
> jena-users@apache, with very little flowing through Yahoo groups.
>
> There has been a lot of discussion about better podling reports on the
> Incubator general list. I must admit I haven't bothered to trawl through
> all of it. Mentors, are there any takeaways from that discussion that might
> bear on this month's report?
>
> Ian
>
Re: Jena Incubation Report - Feb 2012
Posted by Ian Dickinson <ia...@epimorphics.com>.
On 21/01/12 17:47, Andy wrote:
>[...]
Looks good.
> The project has successive produced a release.
s/successive/successfully/
Also, do we want to be more precise about which components have been
released, since one of the plan items is to release further subsystems.
We could also mention that most support traffic is now via
jena-users@apache, with very little flowing through Yahoo groups.
There has been a lot of discussion about better podling reports on the
Incubator general list. I must admit I haven't bothered to trawl through
all of it. Mentors, are there any takeaways from that discussion that
might bear on this month's report?
Ian
Re: Jena Incubation Report - Feb 2012
Posted by Benson Margulies <bi...@gmail.com>.
Hmm. Not linked from http://wiki.apache.org/incubator/. How Odd.
On Sat, Jan 21, 2012 at 3:11 PM, Andy Seaborne <an...@apache.org> wrote:
> On 21/01/12 20:02, Benson Margulies wrote:
>>
>> Where is it on the Wiki? There isn't a feb page there at all yet?
>
>
> It must be my use of neutrinos:
>
> I see:
>
> http://wiki.apache.org/incubator/February2012
>
> Andy
Re: Jena Incubation Report - Feb 2012
Posted by Andy Seaborne <an...@apache.org>.
On 21/01/12 20:02, Benson Margulies wrote:
> Where is it on the Wiki? There isn't a feb page there at all yet?
It must be my use of neutrinos:
I see:
http://wiki.apache.org/incubator/February2012
Andy
Re: Jena Incubation Report - Feb 2012
Posted by Benson Margulies <bi...@gmail.com>.
Where is it on the Wiki? There isn't a feb page there at all yet?
On Sat, Jan 21, 2012 at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
> Draft text for the February report (due by 9th Feb).
>
> I've put the text below on the wiki and copied it here (because we then have
> a copy in case of wiki-accidents ... the report is quite early and before
> the page is properly templated :-)
>
> Comments here and I'll revise: this gives us-the-project a week or so to
> review before asking for mentor sign-off.
>
> Andy
>
> ----------------------------------------------------------
>
> Jena
>
> Jena is a semantic web framework in Java that implements
> the key W3C recommendations for the core semantic web technologies of
> RDF and SPARQL.
>
> Jena entered incubation in November 2010.
>
> The project is discussing graduation.
>
> Progress since the last report:
> * The project has voted for a new committer and IPMC member for the project.
> This is the second person since the start of incubation.
> * The project has successive produced a release.
> * Redirections placed at both old websites to point to the Apache incubator
> website for Apache Jena.
> * About 20 JIRA items have been resolved since the last report.
>
> Issues for the Incubator PMC or ASF Board:
> * None.
>
> Plan:
> * Graduation preparation
> (checking, drafting the scope/charter, resolution, chair, more checking)
> * There are no technical or infrastructure items blocking graduation.
> * Releases of further subsystems: TDB, Fuseki, LARQ.
>
> Signed off by mentor:
Re: Jena Incubation Report - Feb 2012
Posted by Andy Seaborne <an...@apache.org>.
Draft text for the February report (due by 9th Feb).
I've put the text below on the wiki and copied it here (because we then
have a copy in case of wiki-accidents ... the report is quite early and
before the page is properly templated :-)
Comments here and I'll revise: this gives us-the-project a week or so to
review before asking for mentor sign-off.
Andy
----------------------------------------------------------
Jena
Jena is a semantic web framework in Java that implements
the key W3C recommendations for the core semantic web technologies of
RDF and SPARQL.
Jena entered incubation in November 2010.
The project is discussing graduation.
Progress since the last report:
* The project has voted for a new committer and IPMC member for the
project.
This is the second person since the start of incubation.
* The project has successive produced a release.
* Redirections placed at both old websites to point to the Apache
incubator website for Apache Jena.
* About 20 JIRA items have been resolved since the last report.
Issues for the Incubator PMC or ASF Board:
* None.
Plan:
* Graduation preparation
(checking, drafting the scope/charter, resolution, chair, more checking)
* There are no technical or infrastructure items blocking graduation.
* Releases of further subsystems: TDB, Fuseki, LARQ.
Signed off by mentor:
Re: Jena Incubation Report - Feb 2012
Posted by Dave Reynolds <da...@gmail.com>.
On Thu, 2012-01-12 at 10:20 +0000, Andy Seaborne wrote:
> Jena reports next month (by the 9th). It probably a good time to do
> more than just update the report.
+1
> * Releases of the TDB, Fuseki, LARQ.
Nitpick: s/the//
> Any thing else to add?
Not that I can think of, we/you already reported completion of IP
cleanup and adding Stephen as a committer last time.
Dave