incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "August2012" by RaymondFeng
Date Tue, 31 Jul 2012 16:46:04 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "August2012" page has been changed by RaymondFeng:
http://wiki.apache.org/incubator/August2012?action=diff&rev1=22&rev2=23

  = Incubator board report, August 2012 =
- 
  Podling reports are due on '''Wednesday, August 1st, 2012''' so that the Incubator PMC can
consider them and be ready for this month's board meeting. See also http://incubator.apache.org/report-next-month.html.
Your project might need to report even if it is not listed below, please check your own reporting
schedule or exceptions.
  
  Please remember to include:
@@ -34, +33 @@

    Low diversity: -
  
    We expect the next quarterly report of projects in this category to
-   include a summary of their actions and progress in solving these issues. 
+   include a summary of their actions and progress in solving these issues.
  
  Ready to graduate (N podlings)
  
@@ -63, +62 @@

  A list of the three most important issues to address in the move towards
  graduation
  
-   1. Airavata started to see active contributions from diverse organizations. 
+   1. Airavata started to see active contributions from diverse organizations.
-      Thanks to GSoC students, tutorial and outreach events conducted by dev's, 
+      Thanks to GSoC students, tutorial and outreach events conducted by dev's,
-      and growing general interest. The community would like to keep this momentum, 
+      and growing general interest. The community would like to keep this momentum,
       and encourage diverse participation and hoping to retain interest from GSoC students.
  
    2. Create a clear and concise roadmap.
  
-   3. Review the architecture and document the findings and improve incumbent documentation.

+   3. Review the architecture and document the findings and improve incumbent documentation.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
  
-   The community was very active this summer with large number of dev list 
+   The community was very active this summer with large number of dev list
    and code commit email traffic (May:Dev-220,Commit-169;June:Dev-371,Commit-366;July:Dev-271,Commit-226).
-   
+ 
-   Random community members have been proposing new use cases, and filing feature requests
in JIRA, 
+   Random community members have been proposing new use cases, and filing feature requests
in JIRA,
    this is a very good sign. Hoping to see some of them will turn into contributors and then
commiter.
  
  How has the community developed since the last report?
  
    Yes. Shahani Weerawarana from University of Moratuwa, Srilanka
    was voted in as a commiter and PPMC members based on her contributions.
-   A good number of community members are actively filing JIRA's and some have 
+   A good number of community members are actively filing JIRA's and some have
    started to contribute patches. Some of them seem to be potential commiters.
  
-   Of the 4 GSoC projects proposed on Airavata 3 students are actively developing 
+   Of the 4 GSoC projects proposed on Airavata 3 students are actively developing
-   and interacting with community. In addition to GSoC goals, these students also are 
+   and interacting with community. In addition to GSoC goals, these students also are
    actively participating in technical discussions and reviewing, testing and
    voting on releases.
  
  How has the project developed since the last report?
  
-   0.3-incubating has been released. 0.4-incubating release candidate has been voted by the

+   0.3-incubating has been released. 0.4-incubating release candidate has been voted by the
-   PPMC and has required IPMC 3 votes as well. The vote is on-going on IPMC general list
for lazy 
+   PPMC and has required IPMC 3 votes as well. The vote is on-going on IPMC general list
for lazy
    consensus.
  
  Signed-off-by:
@@ -116, +115 @@

  How has the community developed since the last report?
  
    We had a BOF at OSCON, which was attended by 8 people, 4 of whom were new to
-   the community and have expressed interest in participating and have joined the 
+   the community and have expressed interest in participating and have joined the
-   mailing lists. Other people at OSCON have expressed interest in the project, 
+   mailing lists. Other people at OSCON have expressed interest in the project,
    and we hope to see them join the lists soon.
  
    We have also had some offers of contribution from people at Bitergia who are
@@ -128, +127 @@

  
    This is our first report, as we have just begun the incubation process.
    Infra has set up our mailing lists, and discussions have started. Also,
-   since we will be self-hosted, Infra has created a VM for us, and we are 
+   since we will be self-hosted, Infra has created a VM for us, and we are
-   in the process of installing Allura on that VM. We are also in the process 
+   in the process of installing Allura on that VM. We are also in the process
-   of getting CLAs for all of our initial committers, and reaching out to 
+   of getting CLAs for all of our initial committers, and reaching out to
    anyone outside of the initial team for additional participants on the project.
  
  Signed-off-by: gstein
@@ -177, +176 @@

  
   * amber-0.22-incubating (Amber first release) has been officially approved and ready to
be used.
  
- Signed-off-by:
+ Signed-off-by: Raymond Feng (rfeng)
  
  --------------------
  Clerezza
@@ -201, +200 @@

  
  How has the community developed since the last report?
  
-   CloudStack has added 6 new committers in the month of July. 
+   CloudStack has added 6 new committers in the month of July.
  
    We had BOF and hackathon time at OSCON, which was a positive benefit for those
-   committers who attended, particularly in being able to delve into issues around 
+   committers who attended, particularly in being able to delve into issues around
    incubation, branding, and licensing. Additionally two committers presented tutorials
-   at OSCON one focused on end users deploying CloudStack and the other focused on 
+   at OSCON one focused on end users deploying CloudStack and the other focused on
-   developers hacking on CloudStack, both had great attendance. 
+   developers hacking on CloudStack, both had great attendance.
  
    We have also had some offers of contribution from people at Bitergia who are
    interested in contributing the work that they have done around metrics. which
@@ -215, +214 @@

  
  How has the project developed since the last report?
  
-   Lots of modularization has been injected into CloudStack, which makes some of our 
+   Lots of modularization has been injected into CloudStack, which makes some of our
    licensing issues far less of a problem as we can merely turn the affected code off
-   by default. 
+   by default.
  
-   The wiki has begun migration to an ASF hosted wiki instance. 
+   The wiki has begun migration to an ASF hosted wiki instance.
  
-   One of the CloudStack committers provided a dramatically easier way to be able to 
+   One of the CloudStack committers provided a dramatically easier way to be able to
-   test and develop for CloudStack in the form a completely contained CloudStack 
+   test and develop for CloudStack in the form a completely contained CloudStack
    environment that can be run as a VirtualBox VM. Much additional enhancement has been
-   contributed to this making the process easier and easier to update. 
+   contributed to this making the process easier and easier to update.
  
-   We also saw the movement of documentation from binary .docx files to DocBook XML; 
+   We also saw the movement of documentation from binary .docx files to DocBook XML;
    while this effort isn't complete it does permit folks to far more easily collaborate,
as
-   well as providing a far better interface for l10n. 
+   well as providing a far better interface for l10n.
  
  
  Signed-off-by:
@@ -315, +314 @@

    - Lucene 3.0.3 has taken longer to get out the door than expected - originally
      planned for June. We are still nearly ready to release, but we have added a
      lot of functionality - compatibility with .NET 3.5 (which we removed for the 2.9.4
-     release). CLS compliance for usage with other .NET languages (like VB.NET). We have

+     release). CLS compliance for usage with other .NET languages (like VB.NET). We have
      also done a lot of cleanup work on the code base.
    - Working through the graduation process and all the entails.
  
@@ -337, +336 @@

    We are submitting our resolution to the board, the vote has passed in our Lucene.Net community
as well as
    by the IPMC and incubator community.
  
- Signed off by mentor: 
+ Signed off by mentor:
  
  --------------------
  NPanday
@@ -380, +379 @@

  Community Development:
  
    The transition of previous users-base to the new ASF infrastructure was successfully completed.
-   user@ ML activity is raising, with new users evaluating the project and asking questions:

+   user@ ML activity is raising, with new users evaluating the project and asking questions:
    currently 35 subscribers, including 4 archive / non human addresses.
  
    Two contributors were voted and reported in project site's team list page.
-   The PPMC voted a new committer and PPMC member; this candidate declined our invitation.

+   The PPMC voted a new committer and PPMC member; this candidate declined our invitation.
-   dev@ ML activity is quite consistent: currently 35 subscribers, including 4 archive /
non human 
+   dev@ ML activity is quite consistent: currently 35 subscribers, including 4 archive /
non human
    addresses.
  
  Project Development:
  
    Commits activity is healthy, commits@ ML activity is high.
  
-   Three releases, carried out by two distinct release managers, have been successfully completed;

+   Three releases, carried out by two distinct release managers, have been successfully completed;
    the release process has been included in project website in order to facilitate new release
managers.
    The path to 1.0.0-incubating seems to be really short now.
  
-   The community discussed and elaborated the project roadmap currently drafted at 
+   The community discussed and elaborated the project roadmap currently drafted at
    https://cwiki.apache.org/confluence/display/SYNCOPE/Roadmap
  
  Web Site/Communication Development:

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message