Re: Podling Report Reminder - September 2016

[Stian Soiland-Reyes <st...@apache.org>]

On 30 August 2016 at 11:46,  <jo...@apache.org> wrote:
> 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.

Hi, it's that time of month again.  (Don't worry - this changes later
to a 3-monthly report once we're no longer 'getting started').

Any volunteers for the Juneau incubator report at
http://wiki.apache.org/incubator/August2016 ?
(see below)


Last month we said:


> Three most important issues to address in the move towards graduation:
>
> 1. Build up community with non-IBM and non-Salesforce contributors.
> 2. Finish creating website.
> 3. Finish populating Git repo.

Both the website and git repository are live and progressing well.

BTW - I wonder why the URL at http://juneau.incubator.apache.org/
does not change when I click the links - it makes it hard to link to
sub-pages.

http://juneau.apache.org/issueTracking.html says tongue in cheak:
"Juneau has no bugs. However, in the extremely unlikely event that you
happen to find a bug, please report it at the JIRA repository listed
below."

I can see the humour :-) - but perhaps not everyone will.. it's good
to be as welcoming as possible for any bug reports and pull requests.



It seems we are making good progress towards a Maven build [1] - which
should help with doing a Release (using the maven-release-plugin) and
also things like checking license headers and dependency licenses.


August is traditionally a slow month - but now as autumn comes we
should think about how to expand the community.

An early release will also help with that - what are the main
blockers? Mainly sort out the unit tests..?



[1] mvn clean install -DskipTests=true works.

mvn verify fails on:
[INFO] Apache Juneau Core ................................. FAILURE [ 10.505 s]

(see https://paste.apache.org/qt9I )


mvn apache-rat:check only fails on a couple of configuration files
which should be simple to modify or add to ignore list.

mvn license:aggregate-add-third-party don't seem to list anything
forbidden by https://www.apache.org/legal/resolved



> The board meeting is scheduled for Wed, 21 September 2016, 10:30 am PDT.
> 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, September 07).
>
> 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/September2016
>
> Note: This is 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



-- 
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons
http://orcid.org/0000-0001-9842-9718

Re: Podling Report Reminder - September 2016

[James Bognar <ja...@salesforce.com>]

I'll do the podling report.

1) The maven build "seems" to be working, although I'm an ANT person and
new to Maven, so I can't tell.  I did figure out how to build the aggregate
javadocs and upload the contents to the asf-site, but some sort of
automated process for that would be nice.  I've asked Peter Haumer to
update the instructions for using the Maven scripts here
<https://cwiki.apache.org/confluence/display/JUNEAU/Setting+up+your+Eclipse+workspace>,
but I haven't heard back from him.

2) The Jenkins build is "mostly" working, although temperamental.  I'm
seeing this error occasionally...

FATAL: Couldn’t find any executable in
/home/jenkins/tools/maven/apache-maven-3.0.5


3) I'll see what I can do about the website links.

4) I see how to run apache-rat:check now.  I'll fix those files.

5) I'm not seeing the same JUnit failures as you.  The failing JUnits are
testing serialization of dates and so are sensitive to timezones and
locales.  I thought I had fixed these issues, but I'll have to revisit.

6) There are two things I'd like to finish up before a release.  I hope to
do these this weekend....
   a) I'm working on a feature for defining class lexicons on beans and
POJOs.
https://cwiki.apache.org/confluence/display/JUNEAU/Design%3A+Bean+Names+and+Class+Lexicons
   b) I need to go through all the Javadocs and make sure everything is
up-to-date.



On Fri, Sep 2, 2016 at 7:04 AM, Stian Soiland-Reyes <st...@apache.org>
wrote:

> On 30 August 2016 at 11:46,  <jo...@apache.org> wrote:
> > 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.
>
> Hi, it's that time of month again.  (Don't worry - this changes later
> to a 3-monthly report once we're no longer 'getting started').
>
> Any volunteers for the Juneau incubator report at
> http://wiki.apache.org/incubator/August2016 ?
> (see below)
>
>
> Last month we said:
>
>
> > Three most important issues to address in the move towards graduation:
> >
> > 1. Build up community with non-IBM and non-Salesforce contributors.
> > 2. Finish creating website.
> > 3. Finish populating Git repo.
>
> Both the website and git repository are live and progressing well.
>
> BTW - I wonder why the URL at http://juneau.incubator.apache.org/
> does not change when I click the links - it makes it hard to link to
> sub-pages.
>
> http://juneau.apache.org/issueTracking.html says tongue in cheak:
> "Juneau has no bugs. However, in the extremely unlikely event that you
> happen to find a bug, please report it at the JIRA repository listed
> below."
>
> I can see the humour :-) - but perhaps not everyone will.. it's good
> to be as welcoming as possible for any bug reports and pull requests.
>
>
>
> It seems we are making good progress towards a Maven build [1] - which
> should help with doing a Release (using the maven-release-plugin) and
> also things like checking license headers and dependency licenses.
>
>
> August is traditionally a slow month - but now as autumn comes we
> should think about how to expand the community.
>
> An early release will also help with that - what are the main
> blockers? Mainly sort out the unit tests..?
>
>
>
> [1] mvn clean install -DskipTests=true works.
>
> mvn verify fails on:
> [INFO] Apache Juneau Core ................................. FAILURE [
> 10.505 s]
>
> (see https://paste.apache.org/qt9I )
>
>
> mvn apache-rat:check only fails on a couple of configuration files
> which should be simple to modify or add to ignore list.
>
> mvn license:aggregate-add-third-party don't seem to list anything
> forbidden by https://www.apache.org/legal/resolved
>
>
>
> > The board meeting is scheduled for Wed, 21 September 2016, 10:30 am PDT.
> > 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, September 07).
> >
> > 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/September2016
> >
> > Note: This is 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
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons
> http://orcid.org/0000-0001-9842-9718
>



-- 
James Bognar