[Proposal Draft]BlueSky-Wish to ADD

[Ting Peng]

Hello, everyone!

Now, we are going to move our project BlueSky (Blue Sky Distance
Collaboration
System) to Apache Incubator for future development. Its aim is to make
people under the sky to communicate and share resources with each other
more easily. When, the system is employed, users can communicated via
audio/video(computer screen also included) and text at the same time.
In other words, Multi-Object Multimedia capable makes the system more
vivid and glamorous. Cosmic Resource Share & Management System is also
included. It provides unique portal for users to share resources(such as
multi-object multimedia course ware).  It's proposal is at
http://wiki.apache.org/incubator/BSDCSProposal
The system has been developed for years, more than 20 persons are
involved. It is used in distance learning in primary and middle schools
in China.  More than 40,000 students has benefited from it.  Our developing
website  is http://202.117.16.176/ , source code is also available.
All source code of this project is written by ourselves, no third
part components are included.

Currently, all developers of "Blue Sky Distance Collaboration System"
are not native speaker of  English.  But  we don't have any obstacles to
communicate in English on technical topics. We want to share our work
with people who is interested in it around the world. We want new
volunteers to make our team more diverse, active and creative.

For this is our first candidate project to Apache Foundation. We are
grateful for your ideas!

We are looking forward for your advice!


--

   Best regards!

Ting Peng ([EMAIL PROTECTED])
XJTU-IBM Open Tech. R&D Center

Re: [PROPOSAL] Apache RAT

[Niclas Hedhman]

On Wednesday 24 October 2007 03:59, Robert Burrell Donkin wrote:
> before i call for a VOTE.

I think you can go ahead with RAT.


Cheers
Niclas

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PROPOSAL] Apache RAT

[Hiram Chirino]

I like plain rat, and since rat is common word I doubt we have to
worry about trademark violations.  I also don't confuse it with any
other projects in the java space.. so I think it's ok.

On 10/23/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
> http://wiki.apache.org/incubator/RatProposal has been stable for a
> while now so i'd like to throw it open to final scrutiny before i call
> for a VOTE. (please don't vote yet ;-)
>
> the name "RAT" has been discussed previously - see
> http://mail-archives.apache.org/mod_mbox/incubator-general/200710.mbox/[EMAIL 
> PROTECTED]
> RAT is a good name and popular but i'm still a little concerned that
> there are existing open source projects named RAT as well as
> commercial software containing RAT in their name. Apache aRAT has the
> advantage of being unused but the disadvantage of being a common name
> in some other languages. if anyone strongly disagrees with the
> consensus that RAT is ok and prefers aRAT please jump in now.
>
> - robert
>
> Rat Proposal
> ==
> Abstract
> --
> RAT is comprehension and auditing for distributions and source code.
>
> Proposal
> ---
> RAT will provide a focus for components, applications and integration
> tools for the comprehension and audit of distributions and source
> code. It will collect data and meta-data as required. It will create
> suitable schemas for this data and meta-data as required.
>
> Background
> --
> RAT began as an attempt to automate the technical part of reviewing
> releases in the incubator. Following requests for access from release
> managers, RAT was developed as an open source project under the Apache
> License 2.0.
>
> Rationale
> ---
> Reviewing releases for compliance with Apache technical criteria and
> policies is time consuming. The Incubator requires that all releases
> are reviewed. Though small mistakes are common, this process typically
> adds only a little value. It is common for candidates to be presented
> with small but significant defects which then must be fixed and the
> candidate represented. Significant energy and good will is wasted by
> this process.
>
> This is unnecessary. Given effort, these technical criteria are
> capable of automation.
>
> Automated continuous checking of the source would allow the Incubator
> PMC to be alerted promptly to potential issues. Integration with build
> tools (such as Apache Ant and Apache Maven) would allow releases to be
> checked automatically and continuously.
>
> Initial Goals
> -
> * Read standard license meta-data for documents without license headers
> * Improved RAT reporting
> * RAT source reporting for major build tools
> * Continuous RAT
> * RAT analytics: using meta-data to verify rules
>   o Apache third party documents policy analysis
>   o license compatibility analysis
> * Discordia integration to allow distributed binaries to be recognised
> * RAT analytic integration for major build tools
> * Improved recursive RAT scripts for better analysis of release
> with many distributables
>
> Current Status
> 
> Meritocracy
> --
> I'm very happy to move from a solo development model towards a
> collective one as more active developers are recruited.
>
> Community
> -
> The RAT community needs to be developed. Having RAT here at Apache
> will hopefully encourage release managers to take a more active role
> in developing RAT.
> Core Developers
>
> It has been developed principally by myself but with significant
> contributions of small amounts of code from other Apache members and
> committers.
>
> Alignment
> 
> RAT has found itself becoming a standard part of the Apache release
> infrastructure. The Incubator needs fully featured release tools. It
> makes sense to bring the project here.
>
> Known Risks
> ==
> Orphaned Projects
> --
> This is a project with a set of definite goals aimed at serving the
> wider Apache community. There may well come a time when the coding is
> actually finished. It has a small set of developers who all have many
> other calls on their time. The target user audience is relatively
> small. So, this risk is real.
>
> I think that it's clear that something similar to RAT is required. So,
> unless another better product is developed, time will be found to push
> RAT forward. Even if one day, RAT is orphaned then it will have done
> it's job.
>
> Inexperience With Open Source
> -
> The contributors are Apache members or experienced Apache committers.
>
> Reliance On Salaried Developers
> ---
> I know of no one who's paid to work on RAT.
>
> Relationships with Other Apache Products
> --
> RAT contains an Ant reporting plugin. Codehaus hosts a Maven reporting
> plugin. Analytic plugins for Ant and Maven will be dev

Re: [PROPOSAL] Apache RAT

[Robert Burrell Donkin]

On 10/24/07, Jim Jagielski <[EMAIL PROTECTED]> wrote:
>
> On Oct 23, 2007, at 4:52 PM, Robert Burrell Donkin wrote:
>
> > On 10/23/07, Robert Burrell Donkin <[EMAIL PROTECTED]>
> > wrote:
> >> Mentors
> >> --
> >>
> >> * Yoav Shapira 
> >> * Ross Gardler 
> >>
> >> I would prefer mentors who have not been involved with RAT. This will
> >> allow a more objective perspective. I doubt that supervision will be
> >> too great a burden.
> >
> > RAT would benefit from another mentor if there's anyone willing to
> > volunteer
> >
>
> I volunteer :)

great thanks :-)

- robert

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 'Handling Crypto..' - River project

[Bob Scheifler]

Jim Hurley wrote:

Just to be clear, the Sun release was not a product, but rather
an open source (Apache 2 license) release. I could be wrong, but
I don't think it was handled as a commercial product.


You are correct.

- Bob

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 'Handling Crypto..' - River project

[Jim Hurley]

Thanks Bill -- I'll copy over to legal-discuss.

Just to be clear, the Sun release was not a product, but rather
an open source (Apache 2 license) release. I could be wrong, but
I don't think it was handled as a commercial product.

-Jim

On Oct 24, 2007, at 1:21 PM, William A. Rowe, Jr. wrote:
Keep in mind, "Sun" stuff wasn't necessarily handled under  
generally available
open source TSU (exception) classifications, but as commercial  
"product".  This
is, in part, why distributors may have issues using our exceptions  
and our

classifications (their export legal advisors know better).

For these questions, always kick them across to [EMAIL PROTECTED]  
please :)


Bill

Jim Hurley wrote:

We're (River incubator project) trying to comply with:
"Handling Cryptography within an ASF Release"

This process talks only about software that has been
self classified as 5D002 (has strong crypto classification).
Parts of the Sun Jini Technology Starter Kit (the base contribution
for the River project) were classified as 5D992.b.1, which is
a different classification.  From the ASF perspective, should
we treat this (5D992) classification as effectively "no crypto"?
Need some guidance and insight to help us understand
what we need to do to comply.
thanks -Jim
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 'Handling Crypto..' - River project

[William A. Rowe, Jr.]

Keep in mind, "Sun" stuff wasn't necessarily handled under generally available
open source TSU (exception) classifications, but as commercial "product".  This
is, in part, why distributors may have issues using our exceptions and our
classifications (their export legal advisors know better).

For these questions, always kick them across to [EMAIL PROTECTED] please :)

Bill

Jim Hurley wrote:

We're (River incubator project) trying to comply with:
"Handling Cryptography within an ASF Release"


This process talks only about software that has been
self classified as 5D002 (has strong crypto classification).
Parts of the Sun Jini Technology Starter Kit (the base contribution
for the River project) were classified as 5D992.b.1, which is
a different classification.  From the ASF perspective, should
we treat this (5D992) classification as effectively "no crypto"?

Need some guidance and insight to help us understand
what we need to do to comply.

thanks -Jim
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

'Handling Crypto..' - River project

[Jim Hurley]

We're (River incubator project) trying to comply with:
"Handling Cryptography within an ASF Release"


This process talks only about software that has been
self classified as 5D002 (has strong crypto classification).
Parts of the Sun Jini Technology Starter Kit (the base contribution
for the River project) were classified as 5D992.b.1, which is
a different classification.  From the ASF perspective, should
we treat this (5D992) classification as effectively "no crypto"?

Need some guidance and insight to help us understand
what we need to do to comply.

thanks -Jim
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PROPOSAL] Buildr

[Bertrand Delacretaz]

On 10/24/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:

> ...Sure, just added it. Right now diversity is not that good as we're all 3
> from the same company, but that's one of things we hope to fix during
> incubation

Cool, thanks for clarifying!

-Bertrand

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PROPOSAL] Buildr

[Matthieu Riou]

On 10/24/07, Yoav Shapira <[EMAIL PROTECTED]> wrote:
>
> Hey,
>
> On 10/24/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
> > On 10/24/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:
> >
> > > ...= Initial Committers =
> > >
> > >  * Assaf Arkin
> > >  * Alex Boisvert
> > >  * Matthieu Riou...
> >
> > Considering the recent discussions about diversity, would it be ok for
> > you to include these people's company affiliations in the proposal?
>
> My question exactly.


Just added it.

Otherwise, great proposal, and if you need more mentors I'll be glad to
> help.


Thanks a lot! Feel free to add yourself in the proposal.

Matthieu

Yoav
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [PROPOSAL] Buildr

[Matthieu Riou]

On 10/23/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
>
> On 10/24/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:
>
> > ...= Initial Committers =
> >
> >  * Assaf Arkin
> >  * Alex Boisvert
> >  * Matthieu Riou...
>
> Considering the recent discussions about diversity, would it be ok for
> you to include these people's company affiliations in the proposal?


Sure, just added it. Right now diversity is not that good as we're all 3
from the same company, but that's one of things we hope to fix during
incubation.

Thanks,
Matthieu

-Bertrand
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [PROPOSAL] Buildr

[Yoav Shapira]

Hey,

On 10/24/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
> On 10/24/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:
>
> > ...= Initial Committers =
> >
> >  * Assaf Arkin
> >  * Alex Boisvert
> >  * Matthieu Riou...
>
> Considering the recent discussions about diversity, would it be ok for
> you to include these people's company affiliations in the proposal?

My question exactly.

Otherwise, great proposal, and if you need more mentors I'll be glad to help.

Yoav

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PROPOSAL] Apache RAT

[Jim Jagielski]

On Oct 23, 2007, at 4:52 PM, Robert Burrell Donkin wrote:

On 10/23/07, Robert Burrell Donkin <[EMAIL PROTECTED]>  
wrote:

Mentors
--

* Yoav Shapira 
* Ross Gardler 

I would prefer mentors who have not been involved with RAT. This will
allow a more objective perspective. I doubt that supervision will be
too great a burden.


RAT would benefit from another mentor if there's anyone willing to  
volunteer




I volunteer :)



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PROPOSAL] Apache RAT

[Robert Burrell Donkin]

On 10/24/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
> I'll volunteer...having done lot's of releases for Geronimo I have an
> affinity for the little beast.

great :-)

thanks

- robert

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]