You are viewing a plain text version of this content. The canonical link for it is here.
Posted to alois-dev@incubator.apache.org by no...@apache.org on 2010/11/01 14:00:08 UTC
Incubator PMC/Board report for November 2010 (alois-dev@incubator.apache.org)
Dear ALOIS Developers,
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, 17 November 2010, 12 pm Pacific. The report
for your podling will form a part of the Incubator PMC report. The Incubator PMC
requires your report to be submitted one week before the board meeting, to allow
sufficient time for review.
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 one week 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/November2010
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: Incubator PMC/Board report for November 2010 (alois-dev@incubator.apache.org)
Posted by Scott Deboy <sc...@gmail.com>.
Yes that's correct - ALOIS can use jfreechart while in the incubator. I'm
not sure how, but Apache Struts does something with JFreeChart - you could
look into what they are doing with it to see if it would work for us.
Scott
On Fri, Nov 12, 2010 at 6:56 PM, Urs Lerch <ma...@ulerch.net> wrote:
> Hi
>
> As far as I have seen, the third-party depencies of Ruby and RubyOnRails
> are no problem. And I would say these two would have been dealbreakers.
>
> JFreeChart should be replaced. I don't think that this is critical,
> although a good piece of work. Scott, did I get you right, that this
> library can be used as long as we are in the incubator? This would give
> us some extra time to do the necessary work.
>
> For libisi: I would say changing the licence from LGPL to ASL is not
> possible due to incompatibility of the licences of used third-party
> software. Flavio, what does it mean, when you say libisi "is not part of
> ALOIS"? Can ALOIS be build and run without this tool? If so, we
> shouldn't have a problem.
>
> In summary, I would say that we have do not have a severe licence
> problem, but still a lot of work to do to rectify this.
>
> Best
> Urs
>
>
> Am Mittwoch, den 10.11.2010, 08:53 -0800 schrieb Scott Deboy:
> > See
> > http://www.apache.org/licenses/GPL-compatibility.html
> >
> > And particularly, the list of licenses which may be included in Apache
> > projects here:
> > http://www.apache.org/legal/resolved.html
> >
> > I apologize for not making this clear prior to entry into the incubator.
> I
> > wasn't clear what your third-party dependencies were and I should have
> > asked.
> >
> > Let me know if this is a dealbreaker for this project.
> >
> > Scott
> >
> > On Wed, Nov 10, 2010 at 7:50 AM, Flavio Pellanda <
> > flavio.pellanda@logintas.ch> wrote:
> >
> > > Hi,
> > >
> > > This means, ALOIS may not depend on GPL software?
> > >
> > > Maybe someone should check compatibility of Apache License against
> these
> > > main
> > > components:
> > > RubyGems and Ruby: Ruby License
> > > RubyOnRails: MIT license
> > > JFreeChart: LGPL
> > >
> > > Who knows more about that?
> > >
> > > Thanks
> > >
> > > On Wednesday, November 10, 2010 04:10:44 pm Scott Deboy wrote:
> > > > That's fine. My point was the next todos are not likely to be the
> > > > three most important steps toward graduation (likely licensing,
> > > > community etc).
> > > >
> > > > By the way, gpl dependencies will need to be replaced prior to
> > > > graduation with dependencies compatible with the Apache License 2.0.
> > > >
> > > > Scott
> > > >
> > > >
> > > >
> > > > On Nov 10, 2010, at 1:32 AM, Flavio Pellanda <
> > > flavio.pellanda@logintas.ch
> > > >
> > > > > wrote:
> > > > > Hi,
> > > > >
> > > > >> 1. Can you elaborate on the mailing list (and provide a quick
> > > > >> explanation
> > > > >> in the wiki) on the libisi rubygems release? I assume this is a
> > > > >> project
> > > > >> dependency...will that be released as a part of ALOIS? How is it
> > > > >> licensed, etc?
> > > > >
> > > > > Libisi is a small library to help programming ruby scripts. In
> ALOIS
> > > > > It is
> > > > > used for logging and some userinteraction stuff like
> passwordprompt,
> > > > > progresbar
> > > > > or asking the user a question.
> > > > >
> > > > > Libisi is released as GPLv3 and is not part of ALOIS. Logintas uses
> > > > > this
> > > > > library to keep recurrent tasks/functions at one place. The second
> > > > > goal, that
> > > > > libisi solves, is that we can use one library (one interface), that
> > > > > supports
> > > > > multiple implementations of common tasks.
> > > > >
> > > > > E.g. a interface to interact with the user that supports console
> > > > > password
> > > > > prompt and progress bar, but can also use KDE dialogboxes and
> > > > > progressbars.
> > > > >
> > > > > Or let us generate simple documents for html, wiki or text with one
> > > > > codebase.
> > > > >
> > > > > Package short description:
> > > > > Library for easy and fast shell script developing.
> > > > > * Optparse
> > > > > * Logging: log4r
> > > > > * UI: console, kde, X
> > > > > * Progressbars: console, kde
> > > > > * Charts: jfreecharts
> > > > > * Bridges: java, python
> > > > > * DocRender: html, wiki, text
> > > > > * DataAccess: activerecord, ldap
> > > > >
> > > > >> 2. The 'next steps todo' is great to have in the report, but I
> want
> > > > >> to make
> > > > >> sure we follow the podling report template and provide responses
> to
> > > > >> these
> > > > >> requests:
> > > > >>
> > > > >> A list of the three most important issues to address in the move
> > > > >> towards
> > > > >> graduation.
> > > > >
> > > > > Aren't the "Next steps todo" these important issues? What are you
> > > > > missing?
> > > > >
> > > > >> Any issues that the Incubator PMC or ASF Board might wish/need to
> > > > >> be aware
> > > > >> of
> > > > >
> > > > > I think we're on the way. On Monday we (Urs, Marcus and myself)
> will
> > > > > discuss a
> > > > > roadmap for ALOIS. I will post results here on the mailinglist.
> > > > >
> > > > >> How has the community developed since the last report
> > > > >> How has the project developed since the last report.
> > > > >>
> > > > >> Obviously, the last two don't really apply in this report, but we
> > > > >> could add
> > > > >> them and put 'N/A', just for completeness.
> > > > >
> > > > > Yes, nothing done yet.
> > > > >
> > > > > I see that you already signed off the report, probably I should not
> > > > > change it
> > > > > anymore, should I? I will include your point in next report. Is
> that
> > > > > ok?
> > > > >
> > > > > Cheers Flavio
> > >
>
>
Re: Incubator PMC/Board report for November 2010
(alois-dev@incubator.apache.org)
Posted by Urs Lerch <ma...@ulerch.net>.
Hi
As far as I have seen, the third-party depencies of Ruby and RubyOnRails
are no problem. And I would say these two would have been dealbreakers.
JFreeChart should be replaced. I don't think that this is critical,
although a good piece of work. Scott, did I get you right, that this
library can be used as long as we are in the incubator? This would give
us some extra time to do the necessary work.
For libisi: I would say changing the licence from LGPL to ASL is not
possible due to incompatibility of the licences of used third-party
software. Flavio, what does it mean, when you say libisi "is not part of
ALOIS"? Can ALOIS be build and run without this tool? If so, we
shouldn't have a problem.
In summary, I would say that we have do not have a severe licence
problem, but still a lot of work to do to rectify this.
Best
Urs
Am Mittwoch, den 10.11.2010, 08:53 -0800 schrieb Scott Deboy:
> See
> http://www.apache.org/licenses/GPL-compatibility.html
>
> And particularly, the list of licenses which may be included in Apache
> projects here:
> http://www.apache.org/legal/resolved.html
>
> I apologize for not making this clear prior to entry into the incubator. I
> wasn't clear what your third-party dependencies were and I should have
> asked.
>
> Let me know if this is a dealbreaker for this project.
>
> Scott
>
> On Wed, Nov 10, 2010 at 7:50 AM, Flavio Pellanda <
> flavio.pellanda@logintas.ch> wrote:
>
> > Hi,
> >
> > This means, ALOIS may not depend on GPL software?
> >
> > Maybe someone should check compatibility of Apache License against these
> > main
> > components:
> > RubyGems and Ruby: Ruby License
> > RubyOnRails: MIT license
> > JFreeChart: LGPL
> >
> > Who knows more about that?
> >
> > Thanks
> >
> > On Wednesday, November 10, 2010 04:10:44 pm Scott Deboy wrote:
> > > That's fine. My point was the next todos are not likely to be the
> > > three most important steps toward graduation (likely licensing,
> > > community etc).
> > >
> > > By the way, gpl dependencies will need to be replaced prior to
> > > graduation with dependencies compatible with the Apache License 2.0.
> > >
> > > Scott
> > >
> > >
> > >
> > > On Nov 10, 2010, at 1:32 AM, Flavio Pellanda <
> > flavio.pellanda@logintas.ch
> > >
> > > > wrote:
> > > > Hi,
> > > >
> > > >> 1. Can you elaborate on the mailing list (and provide a quick
> > > >> explanation
> > > >> in the wiki) on the libisi rubygems release? I assume this is a
> > > >> project
> > > >> dependency...will that be released as a part of ALOIS? How is it
> > > >> licensed, etc?
> > > >
> > > > Libisi is a small library to help programming ruby scripts. In ALOIS
> > > > It is
> > > > used for logging and some userinteraction stuff like passwordprompt,
> > > > progresbar
> > > > or asking the user a question.
> > > >
> > > > Libisi is released as GPLv3 and is not part of ALOIS. Logintas uses
> > > > this
> > > > library to keep recurrent tasks/functions at one place. The second
> > > > goal, that
> > > > libisi solves, is that we can use one library (one interface), that
> > > > supports
> > > > multiple implementations of common tasks.
> > > >
> > > > E.g. a interface to interact with the user that supports console
> > > > password
> > > > prompt and progress bar, but can also use KDE dialogboxes and
> > > > progressbars.
> > > >
> > > > Or let us generate simple documents for html, wiki or text with one
> > > > codebase.
> > > >
> > > > Package short description:
> > > > Library for easy and fast shell script developing.
> > > > * Optparse
> > > > * Logging: log4r
> > > > * UI: console, kde, X
> > > > * Progressbars: console, kde
> > > > * Charts: jfreecharts
> > > > * Bridges: java, python
> > > > * DocRender: html, wiki, text
> > > > * DataAccess: activerecord, ldap
> > > >
> > > >> 2. The 'next steps todo' is great to have in the report, but I want
> > > >> to make
> > > >> sure we follow the podling report template and provide responses to
> > > >> these
> > > >> requests:
> > > >>
> > > >> A list of the three most important issues to address in the move
> > > >> towards
> > > >> graduation.
> > > >
> > > > Aren't the "Next steps todo" these important issues? What are you
> > > > missing?
> > > >
> > > >> Any issues that the Incubator PMC or ASF Board might wish/need to
> > > >> be aware
> > > >> of
> > > >
> > > > I think we're on the way. On Monday we (Urs, Marcus and myself) will
> > > > discuss a
> > > > roadmap for ALOIS. I will post results here on the mailinglist.
> > > >
> > > >> How has the community developed since the last report
> > > >> How has the project developed since the last report.
> > > >>
> > > >> Obviously, the last two don't really apply in this report, but we
> > > >> could add
> > > >> them and put 'N/A', just for completeness.
> > > >
> > > > Yes, nothing done yet.
> > > >
> > > > I see that you already signed off the report, probably I should not
> > > > change it
> > > > anymore, should I? I will include your point in next report. Is that
> > > > ok?
> > > >
> > > > Cheers Flavio
> >
Re: Incubator PMC/Board report for November 2010 (alois-dev@incubator.apache.org)
Posted by Scott Deboy <sc...@gmail.com>.
Notice there is a section addressing Ruby in the second link, and at the
bottom it explains setup.rb may also be distributed.
http://www.apache.org/legal/resolved.html#ruby-license
Scott
On Wed, Nov 10, 2010 at 8:53 AM, Scott Deboy <sc...@gmail.com> wrote:
> See
> http://www.apache.org/licenses/GPL-compatibility.html
>
> And particularly, the list of licenses which may be included in Apache
> projects here:
> http://www.apache.org/legal/resolved.html
>
> I apologize for not making this clear prior to entry into the incubator. I
> wasn't clear what your third-party dependencies were and I should have
> asked.
>
> Let me know if this is a dealbreaker for this project.
>
> Scott
>
>
> On Wed, Nov 10, 2010 at 7:50 AM, Flavio Pellanda <
> flavio.pellanda@logintas.ch> wrote:
>
>> Hi,
>>
>> This means, ALOIS may not depend on GPL software?
>>
>> Maybe someone should check compatibility of Apache License against these
>> main
>> components:
>> RubyGems and Ruby: Ruby License
>> RubyOnRails: MIT license
>> JFreeChart: LGPL
>>
>> Who knows more about that?
>>
>> Thanks
>>
>> On Wednesday, November 10, 2010 04:10:44 pm Scott Deboy wrote:
>> > That's fine. My point was the next todos are not likely to be the
>> > three most important steps toward graduation (likely licensing,
>> > community etc).
>> >
>> > By the way, gpl dependencies will need to be replaced prior to
>> > graduation with dependencies compatible with the Apache License 2.0.
>> >
>> > Scott
>> >
>> >
>> >
>> > On Nov 10, 2010, at 1:32 AM, Flavio Pellanda <
>> flavio.pellanda@logintas.ch
>> >
>> > > wrote:
>> > > Hi,
>> > >
>> > >> 1. Can you elaborate on the mailing list (and provide a quick
>> > >> explanation
>> > >> in the wiki) on the libisi rubygems release? I assume this is a
>> > >> project
>> > >> dependency...will that be released as a part of ALOIS? How is it
>> > >> licensed, etc?
>> > >
>> > > Libisi is a small library to help programming ruby scripts. In ALOIS
>> > > It is
>> > > used for logging and some userinteraction stuff like passwordprompt,
>> > > progresbar
>> > > or asking the user a question.
>> > >
>> > > Libisi is released as GPLv3 and is not part of ALOIS. Logintas uses
>> > > this
>> > > library to keep recurrent tasks/functions at one place. The second
>> > > goal, that
>> > > libisi solves, is that we can use one library (one interface), that
>> > > supports
>> > > multiple implementations of common tasks.
>> > >
>> > > E.g. a interface to interact with the user that supports console
>> > > password
>> > > prompt and progress bar, but can also use KDE dialogboxes and
>> > > progressbars.
>> > >
>> > > Or let us generate simple documents for html, wiki or text with one
>> > > codebase.
>> > >
>> > > Package short description:
>> > > Library for easy and fast shell script developing.
>> > > * Optparse
>> > > * Logging: log4r
>> > > * UI: console, kde, X
>> > > * Progressbars: console, kde
>> > > * Charts: jfreecharts
>> > > * Bridges: java, python
>> > > * DocRender: html, wiki, text
>> > > * DataAccess: activerecord, ldap
>> > >
>> > >> 2. The 'next steps todo' is great to have in the report, but I want
>> > >> to make
>> > >> sure we follow the podling report template and provide responses to
>> > >> these
>> > >> requests:
>> > >>
>> > >> A list of the three most important issues to address in the move
>> > >> towards
>> > >> graduation.
>> > >
>> > > Aren't the "Next steps todo" these important issues? What are you
>> > > missing?
>> > >
>> > >> Any issues that the Incubator PMC or ASF Board might wish/need to
>> > >> be aware
>> > >> of
>> > >
>> > > I think we're on the way. On Monday we (Urs, Marcus and myself) will
>> > > discuss a
>> > > roadmap for ALOIS. I will post results here on the mailinglist.
>> > >
>> > >> How has the community developed since the last report
>> > >> How has the project developed since the last report.
>> > >>
>> > >> Obviously, the last two don't really apply in this report, but we
>> > >> could add
>> > >> them and put 'N/A', just for completeness.
>> > >
>> > > Yes, nothing done yet.
>> > >
>> > > I see that you already signed off the report, probably I should not
>> > > change it
>> > > anymore, should I? I will include your point in next report. Is that
>> > > ok?
>> > >
>> > > Cheers Flavio
>>
>
>
Re: Incubator PMC/Board report for November 2010 (alois-dev@incubator.apache.org)
Posted by Scott Deboy <sc...@gmail.com>.
See
http://www.apache.org/licenses/GPL-compatibility.html
And particularly, the list of licenses which may be included in Apache
projects here:
http://www.apache.org/legal/resolved.html
I apologize for not making this clear prior to entry into the incubator. I
wasn't clear what your third-party dependencies were and I should have
asked.
Let me know if this is a dealbreaker for this project.
Scott
On Wed, Nov 10, 2010 at 7:50 AM, Flavio Pellanda <
flavio.pellanda@logintas.ch> wrote:
> Hi,
>
> This means, ALOIS may not depend on GPL software?
>
> Maybe someone should check compatibility of Apache License against these
> main
> components:
> RubyGems and Ruby: Ruby License
> RubyOnRails: MIT license
> JFreeChart: LGPL
>
> Who knows more about that?
>
> Thanks
>
> On Wednesday, November 10, 2010 04:10:44 pm Scott Deboy wrote:
> > That's fine. My point was the next todos are not likely to be the
> > three most important steps toward graduation (likely licensing,
> > community etc).
> >
> > By the way, gpl dependencies will need to be replaced prior to
> > graduation with dependencies compatible with the Apache License 2.0.
> >
> > Scott
> >
> >
> >
> > On Nov 10, 2010, at 1:32 AM, Flavio Pellanda <
> flavio.pellanda@logintas.ch
> >
> > > wrote:
> > > Hi,
> > >
> > >> 1. Can you elaborate on the mailing list (and provide a quick
> > >> explanation
> > >> in the wiki) on the libisi rubygems release? I assume this is a
> > >> project
> > >> dependency...will that be released as a part of ALOIS? How is it
> > >> licensed, etc?
> > >
> > > Libisi is a small library to help programming ruby scripts. In ALOIS
> > > It is
> > > used for logging and some userinteraction stuff like passwordprompt,
> > > progresbar
> > > or asking the user a question.
> > >
> > > Libisi is released as GPLv3 and is not part of ALOIS. Logintas uses
> > > this
> > > library to keep recurrent tasks/functions at one place. The second
> > > goal, that
> > > libisi solves, is that we can use one library (one interface), that
> > > supports
> > > multiple implementations of common tasks.
> > >
> > > E.g. a interface to interact with the user that supports console
> > > password
> > > prompt and progress bar, but can also use KDE dialogboxes and
> > > progressbars.
> > >
> > > Or let us generate simple documents for html, wiki or text with one
> > > codebase.
> > >
> > > Package short description:
> > > Library for easy and fast shell script developing.
> > > * Optparse
> > > * Logging: log4r
> > > * UI: console, kde, X
> > > * Progressbars: console, kde
> > > * Charts: jfreecharts
> > > * Bridges: java, python
> > > * DocRender: html, wiki, text
> > > * DataAccess: activerecord, ldap
> > >
> > >> 2. The 'next steps todo' is great to have in the report, but I want
> > >> to make
> > >> sure we follow the podling report template and provide responses to
> > >> these
> > >> requests:
> > >>
> > >> A list of the three most important issues to address in the move
> > >> towards
> > >> graduation.
> > >
> > > Aren't the "Next steps todo" these important issues? What are you
> > > missing?
> > >
> > >> Any issues that the Incubator PMC or ASF Board might wish/need to
> > >> be aware
> > >> of
> > >
> > > I think we're on the way. On Monday we (Urs, Marcus and myself) will
> > > discuss a
> > > roadmap for ALOIS. I will post results here on the mailinglist.
> > >
> > >> How has the community developed since the last report
> > >> How has the project developed since the last report.
> > >>
> > >> Obviously, the last two don't really apply in this report, but we
> > >> could add
> > >> them and put 'N/A', just for completeness.
> > >
> > > Yes, nothing done yet.
> > >
> > > I see that you already signed off the report, probably I should not
> > > change it
> > > anymore, should I? I will include your point in next report. Is that
> > > ok?
> > >
> > > Cheers Flavio
>
Re: Incubator PMC/Board report for November 2010 (alois-dev@incubator.apache.org)
Posted by Flavio Pellanda <fl...@logintas.ch>.
Hi,
This means, ALOIS may not depend on GPL software?
Maybe someone should check compatibility of Apache License against these main
components:
RubyGems and Ruby: Ruby License
RubyOnRails: MIT license
JFreeChart: LGPL
Who knows more about that?
Thanks
On Wednesday, November 10, 2010 04:10:44 pm Scott Deboy wrote:
> That's fine. My point was the next todos are not likely to be the
> three most important steps toward graduation (likely licensing,
> community etc).
>
> By the way, gpl dependencies will need to be replaced prior to
> graduation with dependencies compatible with the Apache License 2.0.
>
> Scott
>
>
>
> On Nov 10, 2010, at 1:32 AM, Flavio Pellanda <flavio.pellanda@logintas.ch
>
> > wrote:
> > Hi,
> >
> >> 1. Can you elaborate on the mailing list (and provide a quick
> >> explanation
> >> in the wiki) on the libisi rubygems release? I assume this is a
> >> project
> >> dependency...will that be released as a part of ALOIS? How is it
> >> licensed, etc?
> >
> > Libisi is a small library to help programming ruby scripts. In ALOIS
> > It is
> > used for logging and some userinteraction stuff like passwordprompt,
> > progresbar
> > or asking the user a question.
> >
> > Libisi is released as GPLv3 and is not part of ALOIS. Logintas uses
> > this
> > library to keep recurrent tasks/functions at one place. The second
> > goal, that
> > libisi solves, is that we can use one library (one interface), that
> > supports
> > multiple implementations of common tasks.
> >
> > E.g. a interface to interact with the user that supports console
> > password
> > prompt and progress bar, but can also use KDE dialogboxes and
> > progressbars.
> >
> > Or let us generate simple documents for html, wiki or text with one
> > codebase.
> >
> > Package short description:
> > Library for easy and fast shell script developing.
> > * Optparse
> > * Logging: log4r
> > * UI: console, kde, X
> > * Progressbars: console, kde
> > * Charts: jfreecharts
> > * Bridges: java, python
> > * DocRender: html, wiki, text
> > * DataAccess: activerecord, ldap
> >
> >> 2. The 'next steps todo' is great to have in the report, but I want
> >> to make
> >> sure we follow the podling report template and provide responses to
> >> these
> >> requests:
> >>
> >> A list of the three most important issues to address in the move
> >> towards
> >> graduation.
> >
> > Aren't the "Next steps todo" these important issues? What are you
> > missing?
> >
> >> Any issues that the Incubator PMC or ASF Board might wish/need to
> >> be aware
> >> of
> >
> > I think we're on the way. On Monday we (Urs, Marcus and myself) will
> > discuss a
> > roadmap for ALOIS. I will post results here on the mailinglist.
> >
> >> How has the community developed since the last report
> >> How has the project developed since the last report.
> >>
> >> Obviously, the last two don't really apply in this report, but we
> >> could add
> >> them and put 'N/A', just for completeness.
> >
> > Yes, nothing done yet.
> >
> > I see that you already signed off the report, probably I should not
> > change it
> > anymore, should I? I will include your point in next report. Is that
> > ok?
> >
> > Cheers Flavio
Re: Incubator PMC/Board report for November 2010 (alois-dev@incubator.apache.org)
Posted by Scott Deboy <sc...@gmail.com>.
That's fine. My point was the next todos are not likely to be the
three most important steps toward graduation (likely licensing,
community etc).
By the way, gpl dependencies will need to be replaced prior to
graduation with dependencies compatible with the Apache License 2.0.
Scott
On Nov 10, 2010, at 1:32 AM, Flavio Pellanda <flavio.pellanda@logintas.ch
> wrote:
> Hi,
>
>> 1. Can you elaborate on the mailing list (and provide a quick
>> explanation
>> in the wiki) on the libisi rubygems release? I assume this is a
>> project
>> dependency...will that be released as a part of ALOIS? How is it
>> licensed, etc?
> Libisi is a small library to help programming ruby scripts. In ALOIS
> It is
> used for logging and some userinteraction stuff like passwordprompt,
> progresbar
> or asking the user a question.
>
> Libisi is released as GPLv3 and is not part of ALOIS. Logintas uses
> this
> library to keep recurrent tasks/functions at one place. The second
> goal, that
> libisi solves, is that we can use one library (one interface), that
> supports
> multiple implementations of common tasks.
>
> E.g. a interface to interact with the user that supports console
> password
> prompt and progress bar, but can also use KDE dialogboxes and
> progressbars.
>
> Or let us generate simple documents for html, wiki or text with one
> codebase.
>
> Package short description:
> Library for easy and fast shell script developing.
> * Optparse
> * Logging: log4r
> * UI: console, kde, X
> * Progressbars: console, kde
> * Charts: jfreecharts
> * Bridges: java, python
> * DocRender: html, wiki, text
> * DataAccess: activerecord, ldap
>
>
>> 2. The 'next steps todo' is great to have in the report, but I want
>> to make
>> sure we follow the podling report template and provide responses to
>> these
>> requests:
>>
>> A list of the three most important issues to address in the move
>> towards
>> graduation.
> Aren't the "Next steps todo" these important issues? What are you
> missing?
>
>> Any issues that the Incubator PMC or ASF Board might wish/need to
>> be aware
>> of
> I think we're on the way. On Monday we (Urs, Marcus and myself) will
> discuss a
> roadmap for ALOIS. I will post results here on the mailinglist.
>
>> How has the community developed since the last report
>> How has the project developed since the last report.
>>
>> Obviously, the last two don't really apply in this report, but we
>> could add
>> them and put 'N/A', just for completeness.
> Yes, nothing done yet.
>
> I see that you already signed off the report, probably I should not
> change it
> anymore, should I? I will include your point in next report. Is that
> ok?
>
> Cheers Flavio
Re: Incubator PMC/Board report for November 2010 (alois-dev@incubator.apache.org)
Posted by Flavio Pellanda <fl...@logintas.ch>.
Hi,
> 1. Can you elaborate on the mailing list (and provide a quick explanation
> in the wiki) on the libisi rubygems release? I assume this is a project
> dependency...will that be released as a part of ALOIS? How is it
> licensed, etc?
Libisi is a small library to help programming ruby scripts. In ALOIS It is
used for logging and some userinteraction stuff like passwordprompt, progresbar
or asking the user a question.
Libisi is released as GPLv3 and is not part of ALOIS. Logintas uses this
library to keep recurrent tasks/functions at one place. The second goal, that
libisi solves, is that we can use one library (one interface), that supports
multiple implementations of common tasks.
E.g. a interface to interact with the user that supports console password
prompt and progress bar, but can also use KDE dialogboxes and progressbars.
Or let us generate simple documents for html, wiki or text with one codebase.
Package short description:
Library for easy and fast shell script developing.
* Optparse
* Logging: log4r
* UI: console, kde, X
* Progressbars: console, kde
* Charts: jfreecharts
* Bridges: java, python
* DocRender: html, wiki, text
* DataAccess: activerecord, ldap
> 2. The 'next steps todo' is great to have in the report, but I want to make
> sure we follow the podling report template and provide responses to these
> requests:
>
> A list of the three most important issues to address in the move towards
> graduation.
Aren't the "Next steps todo" these important issues? What are you missing?
> Any issues that the Incubator PMC or ASF Board might wish/need to be aware
> of
I think we're on the way. On Monday we (Urs, Marcus and myself) will discuss a
roadmap for ALOIS. I will post results here on the mailinglist.
> How has the community developed since the last report
> How has the project developed since the last report.
>
> Obviously, the last two don't really apply in this report, but we could add
> them and put 'N/A', just for completeness.
Yes, nothing done yet.
I see that you already signed off the report, probably I should not change it
anymore, should I? I will include your point in next report. Is that ok?
Cheers Flavio
Re: Incubator PMC/Board report for November 2010 (alois-dev@incubator.apache.org)
Posted by Scott Deboy <sc...@gmail.com>.
Thanks for updating the Wiki..
I have two requests:
1. Can you elaborate on the mailing list (and provide a quick explanation in
the wiki) on the libisi rubygems release? I assume this is a project
dependency...will that be released as a part of ALOIS? How is it licensed,
etc?
2. The 'next steps todo' is great to have in the report, but I want to make
sure we follow the podling report template and provide responses to these
requests:
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.
Obviously, the last two don't really apply in this report, but we could add
them and put 'N/A', just for completeness.
Thanks
Scott
On Fri, Nov 5, 2010 at 1:16 AM, Marcus Holthaus (IMSEC) <
Marcus.Holthaus@imsec.ch> wrote:
> Hi all
>
> I would propose ALOIS (all upper case),
> Originally this stood for "Advanced Logging and Intrusion Detection
> System" (my creation). However, ALOIS has evolved more into a Log Data
> Collection and Log Data Mining Tool and into a Security Incident Event
> Management System (SIEMS) than an into an IDS. Doing the IDS part was
> always intended to be done by analyzing log data, and since ALOIS's
> inception, the IDS label has moved to other types of systems.
> So I propose ALOIS should stand for "Advanced Log Data Insight System"
> from now on.
>
> (In German context, "Alois" is an old-fashioned male first name, and as
> people bearing this name are mostly of older age now, using this name
> was an intended to link it to some kind of "wisdom" or "insight").
>
> -- Marcus
>
> Am 04.11.2010 23:27, schrieb Scott Deboy:
> > One other thing:
> > I used a mixed-case version of the project name in my prior email, but I
> see
> > some links with Alois and some with ALOIS.....is our project name Alois,
> > ALOIS, alois, or some other variation?
> >
>
Re: Incubator PMC/Board report for November 2010 (alois-dev@incubator.apache.org)
Posted by "Marcus Holthaus (IMSEC)" <Ma...@imsec.ch>.
Hi all
I would propose ALOIS (all upper case),
Originally this stood for "Advanced Logging and Intrusion Detection
System" (my creation). However, ALOIS has evolved more into a Log Data
Collection and Log Data Mining Tool and into a Security Incident Event
Management System (SIEMS) than an into an IDS. Doing the IDS part was
always intended to be done by analyzing log data, and since ALOIS's
inception, the IDS label has moved to other types of systems.
So I propose ALOIS should stand for "Advanced Log Data Insight System"
from now on.
(In German context, "Alois" is an old-fashioned male first name, and as
people bearing this name are mostly of older age now, using this name
was an intended to link it to some kind of "wisdom" or "insight").
-- Marcus
Am 04.11.2010 23:27, schrieb Scott Deboy:
> One other thing:
> I used a mixed-case version of the project name in my prior email, but I see
> some links with Alois and some with ALOIS.....is our project name Alois,
> ALOIS, alois, or some other variation?
>
Re: Incubator PMC/Board report for November 2010 (alois-dev@incubator.apache.org)
Posted by Scott Deboy <sc...@gmail.com>.
I just wanted to make sure we had enough time for everyone to review &
provide updates if needed prior to the due date.
One other thing:
I used a mixed-case version of the project name in my prior email, but I see
some links with Alois and some with ALOIS.....is our project name Alois,
ALOIS, alois, or some other variation?
Thanks
Scott
On Thu, Nov 4, 2010 at 2:05 PM, Flavio Pellanda <flavio.pellanda@logintas.ch
> wrote:
> Hi,
>
> yes, I'll do that. I scheduled this for Monday, but it seems that this is
> too
> late. I'll do it tomorrow.
>
> Cheers
>
> Flavio
>
> On Thursday, November 04, 2010 08:35:51 pm Scott Deboy wrote:
> > Hi Alois folks -
> >
> > There is less than a week before our podling report is due - I see it
> > hasn't been updated yet.
> >
> > I just wanted to make sure someone is going to take responsibility for
> > updating the wiki page:
> > http://wiki.apache.org/incubator/November2010
> >
> > See notes below on what the report should contain.
> >
> > Thanks
> > Scott
> >
> > On Mon, Nov 1, 2010 at 7:00 AM, <no...@apache.org> wrote:
> > > Dear ALOIS Developers,
> > >
> > > 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, 17 November 2010, 12 pm
> Pacific.
> > > The report
> > > for your podling will form a part of the Incubator PMC report. The
> > > Incubator PMC
> > > requires your report to be submitted one week before the board meeting,
> > > to allow
> > > sufficient time for review.
> > >
> > > 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 one week 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/November2010
> > >
> > > 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: Incubator PMC/Board report for November 2010 (alois-dev@incubator.apache.org)
Posted by Flavio Pellanda <fl...@logintas.ch>.
Hi,
yes, I'll do that. I scheduled this for Monday, but it seems that this is too
late. I'll do it tomorrow.
Cheers
Flavio
On Thursday, November 04, 2010 08:35:51 pm Scott Deboy wrote:
> Hi Alois folks -
>
> There is less than a week before our podling report is due - I see it
> hasn't been updated yet.
>
> I just wanted to make sure someone is going to take responsibility for
> updating the wiki page:
> http://wiki.apache.org/incubator/November2010
>
> See notes below on what the report should contain.
>
> Thanks
> Scott
>
> On Mon, Nov 1, 2010 at 7:00 AM, <no...@apache.org> wrote:
> > Dear ALOIS Developers,
> >
> > 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, 17 November 2010, 12 pm Pacific.
> > The report
> > for your podling will form a part of the Incubator PMC report. The
> > Incubator PMC
> > requires your report to be submitted one week before the board meeting,
> > to allow
> > sufficient time for review.
> >
> > 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 one week 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/November2010
> >
> > 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: Incubator PMC/Board report for November 2010 (alois-dev@incubator.apache.org)
Posted by Scott Deboy <sc...@gmail.com>.
Hi Alois folks -
There is less than a week before our podling report is due - I see it hasn't
been updated yet.
I just wanted to make sure someone is going to take responsibility for
updating the wiki page:
http://wiki.apache.org/incubator/November2010
See notes below on what the report should contain.
Thanks
Scott
On Mon, Nov 1, 2010 at 7:00 AM, <no...@apache.org> wrote:
> Dear ALOIS Developers,
>
> 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, 17 November 2010, 12 pm Pacific.
> The report
> for your podling will form a part of the Incubator PMC report. The
> Incubator PMC
> requires your report to be submitted one week before the board meeting, to
> allow
> sufficient time for review.
>
> 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 one week 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/November2010
>
> 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
>
>