Hi all,

> -> Restructure amdatu.org wiki for clarity and accessibility (allready 
> started)
> -> Document Amadatu Platform mechanisms / architecture up to current state
> -> Work with subprojects to get things consistent / up-to-date

I have restructured the wiki and added some info in several areas.
Giving it back to collective ownership. Feedback is welcome,
contributions are better ;)

> -> Create an initial milestone based roadmap
> -> Define core/compendium API/SPI model

We have documented an initial milestone based roadmap ofr Amdatu
Platform at http://www.amdatu.org/confluence/display/Amdatu/Milestones
that we'd like to discuss with the board. Feel free to comment.

grz
Bram


On Thu, Apr 7, 2011 at 11:27 AM, Bram de Kruijff <[email protected]> wrote:
> Hi List,
>
> Marcel and I just had our first Platform PMC call to discuss things to
> do, planning and actions base on the offline discussions we had last
> week at the Amdatu Dev Day. Here are the minutes. Feel free to comment
> and give us feedback.
>
> 1) Switching to Apache License 2.0 (lead: Marcel)
>
> We want to set things in motion with regard to our licensing. Starting
> with Amdatu Platform, but possibly including all subproject in one go.
>
> This requires the following things to be done:
> -> Clearify what part (if not all) of the Amdatu code base can switch
> to ASL and get approval from the board.
> -> Scan codebase for possible ASL conflicts (eg gpl code). If there
> are any we need to resolve them.
> -> Change codebase to conform to Apache License requirements
> (classheaders, notice files etc)
>
> 2) Contribution to ASF incubator (lead: Marcel)
>
> We want to set things in motion with regard to a possible contribution
> of Amdatu Platform to ASF incubator.
>
> This requires the following things to be done:
> -> Clearify what part (probably platform) of the Amdatu code base will
> be part of the proposal and get approval from the board.
> -> Make sure Amdatu Platform is a "working code base"
> -> Write and submit a proposal to Apache incubator.
>
> 3) Platform definition and documentation (lead: Bram)
>
> The restructuring and explicit separation between platform and
> subprojects requires a clear definitions of what is what for our
> stakeholder. At the same time moving to Apache license we hope will
> bring in new members to the community. All in all this requires a well
> documented / accessible amdatu.org.
>
> This requires the following things to be done:
> -> Restructure amdatu.org wiki for clarity and accessibility (allready 
> started)
> -> Document Amadatu Platform mechanisms / architecture up to current state
> -> Work with subprojects to get things consistent / up-to-date
>
> 4) Platform workbreakdown  and milestones(lead: Bram)
>
> The biggest need with regard to the Amdatu Platform is an initial
> "full version" that delivers the core mechanisms and stabilizes APIs.
> This will still require a lot of work and therefore we will create and
> document a workbreakdown and milestone based roadmap to structure and
> coordinate the effort.
>
> This requires the following things to be done:
> -> Create an initial milestone based roadmap
> -> Define core/compendium API/SPI model
>
> 5) Miscellaneous
>
> Additional topics discussed and/or moved to next meeting:
> -> Marcel will put some BndTools based contributions to the sandbox
> and think about the development/deployment flow. This will allow us to
> discuss the future of our build/release infrastructure in more detail
> at a later point.
> -> To get going with provisioning we will need to port configurations
> to metatype. Would make sense to get a proof of concept going for the
> platform providing a basis for subsequents efforts.
> -> We need to start thinling about conferences as CFP dates are
> comming up. ApacheCon / EclipseCon are in the same week. Maybe
> coordinate the effort.
>
>
> That's all folks!
>
> Regards,
> Bram
>

_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers

Reply via email to