archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy <ol...@apache.org>
Subject Re: Board report for December
Date Wed, 14 Dec 2011 10:41:02 GMT
perfect.
Thanks!
--
Olivier

2011/12/14 Deng Ching <oching@apache.org>:
> Hi All,
>
> Below is the draft of the board report for December. Let me know if I
> missed anything.. Thanks!
>
> -Deng
>
> ===
> Archiva Board Report for December 2011
> ----------------------------------
>
> Apache Archiva is an extensible repository management software that helps
> taking care of your own personal or enterprise-wide build artifact
> repository. It is the perfect companion for build tools such as Maven,
> Continuum, and ANT.
>
> Releases
> --------
>
> * 1.4-M1 release 2011-10-26
>
> Community
> ---------
>
> * A number of users and contributors, including a past GSoC (2010)
> participant, has expressed their interest in working on the project.
>
> Development
> -----------
>
> * As reported in the previous board reports, there were a number of planned
>  refactorings of Archiva trunk. Below are the status of each of them:
>
>  - moving the UI to another framework (in-progress)
>
>  - removal of all plexus components (completed)
>
>  - replace or overhaul the security system used (UI overhaul of current
>    security system used has been done to integrate with the UI refactorings
>    in Archiva)
>
> * For Archiva's UI refactoring, the aim is to make it fast and simple, and
> to de-couple it with the core. For the latter aspect, the REST services for
> Archiva's functionalities are already complete. The UI overhaul will start
> at the integration with the recent UI changes made in the security system
> used, which is Redback (http://redback.codehaus.org/).
>
> * Patches have also started coming in for the OSGI integration with Apache
> Karaf.
>
> * 1.4-M2 release discussion is currently underway. The release will
> possibly include improvements for the Maven index support, upgrades on some
> of the libraries used and a number of bug fixes.
>
> Project Branding Requirements
> -----------------------------
>
> * Project Website Basics - done
> * Project Naming and Descriptions - not yet done
> * Website Navigation Links - not yet done
> * Trademark Attributions - not yet done
> * Logos and Graphics - not yet done
> * Project Metadata - not yet done
> * Read PMC Branding Responsibilities - not yet done
>
> Issues
> ------
>
> No board level issues at this time.



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

Mime
View raw message