You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@celix.apache.org by Marvin <no...@apache.org> on 2013/09/29 21:29:25 UTC
Incubator PMC/Board report for Oct 2013 ([ppmc])
Dear podling,
This email was sent by an automated system on behalf of the Apache Incubator PMC.
It is an initial reminder to give you plenty of time to prepare your quarterly
board report.
The board meeting is scheduled for Wed, 16 October 2013, 10:30:00:00 PST. The report
for your podling will form a part of the Incubator PMC report. The Incubator PMC
requires your report to be submitted 2 weeks before the board meeting, to allow
sufficient time for review and submission (Wed, Oct 2nd).
Please submit your report with sufficient time to allow the incubator PMC, and
subsequently board members to review and digest. Again, the very latest you
should submit your report is 2 weeks prior to the board meeting.
Thanks,
The Apache Incubator PMC
Submitting your Report
----------------------
Your report should contain the following:
* Your project name
* A brief description of your project, which assumes no knowledge of the project
or necessarily of its field
* A list of the three most important issues to address in the move towards
graduation.
* Any issues that the Incubator PMC or ASF Board might wish/need to be aware of
* How has the community developed since the last report
* How has the project developed since the last report.
This should be appended to the Incubator Wiki page at:
http://wiki.apache.org/incubator/October2013
Note: This manually populated. You may need to wait a little before this page is
created from a template.
Mentors
-------
Mentors should review reports for their project(s) and sign them off on the
Incubator wiki page. Signing off reports shows that you are following the
project - projects that are not signed may raise alarms for the Incubator PMC.
Incubator PMC
Re: Feature priority next release
Posted by Alexander Broekhuis <a....@gmail.com>.
Hi,
2013/10/1 Gerrit Binnenmars <ge...@gmail.com>
> Hello,
>
> Everyone, thanks for the work done lately.
> I think it useful to discuss about the minimum features required in the
> next release.
> For me the priorities are:
> 1. Jira issues 80, 81 (remote service using shm)
> 2. Jira issue 68 (memory leaks)
> 3. Jira issue 81 (Log service), Pepijn or Alexander can one of you analyze
> what needs to be done?
> Nice to have:
> 4. Jira issue 77 (Config admin)
> 5. Jira issue 48 (Event admin)
This changes a bit from the list that was created a couple of months ago
[1]. But I don't have a problem with a change of focus. From the list on
[1], the following items are still open:
* CELIX-69 Check for win32 (visual studio) support
* CELIX-68 Check for memory leaks
* CELIX-65 add bonjour support for Remote Service Admin
* CELIX-64 Add support for ccputest
* CELIX-63 make cmake directory useable for custom bundle projects
* CELIX-61 use apr calls instead of malloc, free, pthreads, etc
Going through this list, I don't have any objections with postponing
CELIX-69 and CELIX-61. Reasons for this are a lack of Win32 users (if there
are any, please speak up! I still think Win32 should be supported, but just
not now). Regarding APR usage, I think we have to wait a bit and discuss
the usage of APR after a release. So heavily investing in APR usage now
doesn't make much sense imo.
So that leaves 63, 64, 65, 68 and now also 80, 81 (SHM remote services) and
87 (I assume you made a typo in your mail).
CELIX-87 has already been discussed on the list, and I agree that solving
framework logging makes sense.
CELIX-80, CELIX-81: Seeing the current state of the patch I don't see a
reason for not including it. So fine by me.
CELIX-68: Was already on the list.
CELIX-65: Not on your list, but for interoperability with Java-OSGi RSA I
do think it should be part of a next release
CELIX-64: I have invested quite some time in this already, and pushed a
large commit yesterday. So even though maybe not everything will be tested,
what is there can be part of the next release.
CELIX-63: To make it easier to use Celix I'd like to see this one fixed as
well. Some parts are already done.
Regarding 48 and 77, I don't know the state of the code, we should
check/test it. If it mostly works it can be added. But see my remark below
concerning versioning.
Versioning:
Although we are talking about a 1.0.0 release, this doesn't automatically
that all components (bundles) are also 1.0.0. So a subset can be bumped to
1.0.0 while others are still a bit behind. So even if we think the Event
and Config Admin (or the SHM RSA) isn't quite ready for 1.0.0, they can
still be part of the release. As Marcel mentions on [1], Apache is about
release source code, not binaries, so we release all sources. The fact that
the framework and all bundles are separate components makes it possible to
have different version internally.
Wdyt?
[1]: http://incubator.markmail.org/thread/fza43iypjutcw2rm
--
Met vriendelijke groet,
Alexander Broekhuis
Feature priority next release
Posted by Gerrit Binnenmars <ge...@gmail.com>.
Hello,
Everyone, thanks for the work done lately.
I think it useful to discuss about the minimum features required in the
next release.
For me the priorities are:
1. Jira issues 80, 81 (remote service using shm)
2. Jira issue 68 (memory leaks)
3. Jira issue 81 (Log service), Pepijn or Alexander can one of you
analyze what needs to be done?
Nice to have:
4. Jira issue 77 (Config admin)
5. Jira issue 48 (Event admin)
Greetings Gerrit
Re: Incubator PMC/Board report for Oct 2013 ([ppmc])
Posted by Alexander Broekhuis <a....@gmail.com>.
Hi all,
I've added the report to the Report [1] and Celix [2] site.
[1]: https://wiki.apache.org/incubator/October2013
[2]:
http://incubator.apache.org/celix/community/boardreports/boardreports.html
2013/10/1 Alexander Broekhuis <a....@gmail.com>
> Hi all,
>
> Does any one have any updates/omissions etc. I'll post the report
> tomorrow. So please reply today/tomorrow morning.
>
> --------------------
> Celix
>
> Celix is an OSGi like implementation in C with a distinct focus on
> interoperability between Java and C.
>
> Celix has been incubating since 2010-11-02.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Grow the community
> 2. Find more committers
> 3. Publish a new release
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None
>
>
> How has the community developed since the last report?
>
> Several new people are working on additional code for the project. One
> person is working on a GSoC project, someone else is working on a new
> remote services protocol and is actively communicating over the list and
> using jira to post patches. Overall this is an increase in activity.
> The Native-OSGi project is still progressing, but rather slow. So there
> isn't anything new on that end. Celix is still the reference
> implementation, so I still expect this to be a great drive for Celix, for
> the code as well as the committers.
>
> How has the project developed since the last report?
> As mentioned above, a student is working on a GSoC project and has
> implemented an Event Admin which will be included in Celix. Also a
> additional Remote Services implementation based on shared memory is being
> made.
> Work for a new release is still ongoing, the focus is slightly changing,
> one of the main users has requested a release. Since they don't use Win32,
> Win32 support can be stripped from the release plan and postponed to a
> later release.
>
> Date of last release:
>
> 16-12-2012
>
> When were the last committers or PMC members elected?
>
> 2013-01-07 Roman Shaposhnik joins as a mentor.
> 2012-03-20 Pepijn elected as committer.
>
>
> Signed-off-by:
>
> [ ](celix) Marcel Offermans
> [ ](celix) Karl Pauls
>
> Shepherd notes:
>
>
>
> 2013/9/30 <er...@jansman.eu>
>
>
>> > Hi all,
>> >
>> > Tomorrow I have some time to write the report. If there is someone who
>> > wants something in it please give a reply to this mail.
>> >
>> Hello,
>>
>> Since the GSOC project is now done, I'll send an update about it tonight
>> as it might be useful.
>>
>> Regards,
>>
>> Erik
>>
>> >
>> >
>> >
>> > 2013/9/29 Marvin <no...@apache.org>
>> >
>> >>
>> >>
>> >> Dear podling,
>> >>
>> >> This email was sent by an automated system on behalf of the Apache
>> >> Incubator PMC.
>> >> It is an initial reminder to give you plenty of time to prepare your
>> >> quarterly
>> >> board report.
>> >>
>> >> The board meeting is scheduled for Wed, 16 October 2013, 10:30:00:00
>> >> PST.
>> >> The report
>> >> for your podling will form a part of the Incubator PMC report. The
>> >> Incubator PMC
>> >> requires your report to be submitted 2 weeks before the board meeting,
>> >> to
>> >> allow
>> >> sufficient time for review and submission (Wed, Oct 2nd).
>> >>
>> >> Please submit your report with sufficient time to allow the incubator
>> >> PMC,
>> >> and
>> >> subsequently board members to review and digest. Again, the very latest
>> >> you
>> >> should submit your report is 2 weeks prior to the board meeting.
>> >>
>> >> Thanks,
>> >>
>> >> The Apache Incubator PMC
>> >>
>> >> Submitting your Report
>> >> ----------------------
>> >>
>> >> Your report should contain the following:
>> >>
>> >> * Your project name
>> >> * A brief description of your project, which assumes no knowledge of
>> >> the
>> >> project
>> >> or necessarily of its field
>> >> * A list of the three most important issues to address in the move
>> >> towards
>> >> graduation.
>> >> * Any issues that the Incubator PMC or ASF Board might wish/need to be
>> >> aware of
>> >> * How has the community developed since the last report
>> >> * How has the project developed since the last report.
>> >>
>> >> This should be appended to the Incubator Wiki page at:
>> >>
>> >> http://wiki.apache.org/incubator/October2013
>> >>
>> >> Note: This manually populated. You may need to wait a little before
>> this
>> >> page is
>> >> created from a template.
>> >>
>> >> Mentors
>> >> -------
>> >> Mentors should review reports for their project(s) and sign them off on
>> >> the
>> >> Incubator wiki page. Signing off reports shows that you are following
>> >> the
>> >> project - projects that are not signed may raise alarms for the
>> >> Incubator
>> >> PMC.
>> >>
>> >> Incubator PMC
>> >>
>> >>
>> >
>> >
>> > --
>> > Met vriendelijke groet,
>> >
>> > Alexander Broekhuis
>> >
>>
>>
>>
>
>
> --
> Met vriendelijke groet,
>
> Alexander Broekhuis
>
--
Met vriendelijke groet,
Alexander Broekhuis
Re: Incubator PMC/Board report for Oct 2013 ([ppmc])
Posted by Alexander Broekhuis <a....@gmail.com>.
Hi all,
Does any one have any updates/omissions etc. I'll post the report tomorrow.
So please reply today/tomorrow morning.
--------------------
Celix
Celix is an OSGi like implementation in C with a distinct focus on
interoperability between Java and C.
Celix has been incubating since 2010-11-02.
Three most important issues to address in the move towards graduation:
1. Grow the community
2. Find more committers
3. Publish a new release
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Several new people are working on additional code for the project. One
person is working on a GSoC project, someone else is working on a new
remote services protocol and is actively communicating over the list and
using jira to post patches. Overall this is an increase in activity.
The Native-OSGi project is still progressing, but rather slow. So there
isn't anything new on that end. Celix is still the reference
implementation, so I still expect this to be a great drive for Celix, for
the code as well as the committers.
How has the project developed since the last report?
As mentioned above, a student is working on a GSoC project and has
implemented an Event Admin which will be included in Celix. Also a
additional Remote Services implementation based on shared memory is being
made.
Work for a new release is still ongoing, the focus is slightly changing,
one of the main users has requested a release. Since they don't use Win32,
Win32 support can be stripped from the release plan and postponed to a
later release.
Date of last release:
16-12-2012
When were the last committers or PMC members elected?
2013-01-07 Roman Shaposhnik joins as a mentor.
2012-03-20 Pepijn elected as committer.
Signed-off-by:
[ ](celix) Marcel Offermans
[ ](celix) Karl Pauls
Shepherd notes:
2013/9/30 <er...@jansman.eu>
>
> > Hi all,
> >
> > Tomorrow I have some time to write the report. If there is someone who
> > wants something in it please give a reply to this mail.
> >
> Hello,
>
> Since the GSOC project is now done, I'll send an update about it tonight
> as it might be useful.
>
> Regards,
>
> Erik
>
> >
> >
> >
> > 2013/9/29 Marvin <no...@apache.org>
> >
> >>
> >>
> >> Dear podling,
> >>
> >> This email was sent by an automated system on behalf of the Apache
> >> Incubator PMC.
> >> It is an initial reminder to give you plenty of time to prepare your
> >> quarterly
> >> board report.
> >>
> >> The board meeting is scheduled for Wed, 16 October 2013, 10:30:00:00
> >> PST.
> >> The report
> >> for your podling will form a part of the Incubator PMC report. The
> >> Incubator PMC
> >> requires your report to be submitted 2 weeks before the board meeting,
> >> to
> >> allow
> >> sufficient time for review and submission (Wed, Oct 2nd).
> >>
> >> Please submit your report with sufficient time to allow the incubator
> >> PMC,
> >> and
> >> subsequently board members to review and digest. Again, the very latest
> >> you
> >> should submit your report is 2 weeks prior to the board meeting.
> >>
> >> Thanks,
> >>
> >> The Apache Incubator PMC
> >>
> >> Submitting your Report
> >> ----------------------
> >>
> >> Your report should contain the following:
> >>
> >> * Your project name
> >> * A brief description of your project, which assumes no knowledge of
> >> the
> >> project
> >> or necessarily of its field
> >> * A list of the three most important issues to address in the move
> >> towards
> >> graduation.
> >> * Any issues that the Incubator PMC or ASF Board might wish/need to be
> >> aware of
> >> * How has the community developed since the last report
> >> * How has the project developed since the last report.
> >>
> >> This should be appended to the Incubator Wiki page at:
> >>
> >> http://wiki.apache.org/incubator/October2013
> >>
> >> Note: This manually populated. You may need to wait a little before this
> >> page is
> >> created from a template.
> >>
> >> Mentors
> >> -------
> >> Mentors should review reports for their project(s) and sign them off on
> >> the
> >> Incubator wiki page. Signing off reports shows that you are following
> >> the
> >> project - projects that are not signed may raise alarms for the
> >> Incubator
> >> PMC.
> >>
> >> Incubator PMC
> >>
> >>
> >
> >
> > --
> > Met vriendelijke groet,
> >
> > Alexander Broekhuis
> >
>
>
>
--
Met vriendelijke groet,
Alexander Broekhuis
Re: Incubator PMC/Board report for Oct 2013 ([ppmc])
Posted by er...@jansman.eu.
> Hi all,
>
> Tomorrow I have some time to write the report. If there is someone who
> wants something in it please give a reply to this mail.
>
Hello,
Since the GSOC project is now done, I'll send an update about it tonight
as it might be useful.
Regards,
Erik
>
>
>
> 2013/9/29 Marvin <no...@apache.org>
>
>>
>>
>> Dear podling,
>>
>> This email was sent by an automated system on behalf of the Apache
>> Incubator PMC.
>> It is an initial reminder to give you plenty of time to prepare your
>> quarterly
>> board report.
>>
>> The board meeting is scheduled for Wed, 16 October 2013, 10:30:00:00
>> PST.
>> The report
>> for your podling will form a part of the Incubator PMC report. The
>> Incubator PMC
>> requires your report to be submitted 2 weeks before the board meeting,
>> to
>> allow
>> sufficient time for review and submission (Wed, Oct 2nd).
>>
>> Please submit your report with sufficient time to allow the incubator
>> PMC,
>> and
>> subsequently board members to review and digest. Again, the very latest
>> you
>> should submit your report is 2 weeks prior to the board meeting.
>>
>> Thanks,
>>
>> The Apache Incubator PMC
>>
>> Submitting your Report
>> ----------------------
>>
>> Your report should contain the following:
>>
>> * Your project name
>> * A brief description of your project, which assumes no knowledge of
>> the
>> project
>> or necessarily of its field
>> * A list of the three most important issues to address in the move
>> towards
>> graduation.
>> * Any issues that the Incubator PMC or ASF Board might wish/need to be
>> aware of
>> * How has the community developed since the last report
>> * How has the project developed since the last report.
>>
>> This should be appended to the Incubator Wiki page at:
>>
>> http://wiki.apache.org/incubator/October2013
>>
>> Note: This manually populated. You may need to wait a little before this
>> page is
>> created from a template.
>>
>> Mentors
>> -------
>> Mentors should review reports for their project(s) and sign them off on
>> the
>> Incubator wiki page. Signing off reports shows that you are following
>> the
>> project - projects that are not signed may raise alarms for the
>> Incubator
>> PMC.
>>
>> Incubator PMC
>>
>>
>
>
> --
> Met vriendelijke groet,
>
> Alexander Broekhuis
>
Re: Incubator PMC/Board report for Oct 2013 ([ppmc])
Posted by Alexander Broekhuis <a....@gmail.com>.
Hi all,
Tomorrow I have some time to write the report. If there is someone who
wants something in it please give a reply to this mail.
2013/9/29 Marvin <no...@apache.org>
>
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC.
> It is an initial reminder to give you plenty of time to prepare your
> quarterly
> board report.
>
> The board meeting is scheduled for Wed, 16 October 2013, 10:30:00:00 PST.
> The report
> for your podling will form a part of the Incubator PMC report. The
> Incubator PMC
> requires your report to be submitted 2 weeks before the board meeting, to
> allow
> sufficient time for review and submission (Wed, Oct 2nd).
>
> Please submit your report with sufficient time to allow the incubator PMC,
> and
> subsequently board members to review and digest. Again, the very latest you
> should submit your report is 2 weeks prior to the board meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
> ----------------------
>
> Your report should contain the following:
>
> * Your project name
> * A brief description of your project, which assumes no knowledge of the
> project
> or necessarily of its field
> * A list of the three most important issues to address in the move towards
> graduation.
> * Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> * How has the community developed since the last report
> * How has the project developed since the last report.
>
> This should be appended to the Incubator Wiki page at:
>
> http://wiki.apache.org/incubator/October2013
>
> Note: This manually populated. You may need to wait a little before this
> page is
> created from a template.
>
> Mentors
> -------
> Mentors should review reports for their project(s) and sign them off on the
> Incubator wiki page. Signing off reports shows that you are following the
> project - projects that are not signed may raise alarms for the Incubator
> PMC.
>
> Incubator PMC
>
>
--
Met vriendelijke groet,
Alexander Broekhuis