Re: Incorrect use of "Sponsor".

[J Aaron Farr]

On Sun 05 Jul 2009 02:36, "Gavin"  wrote:

>> -Original Message-
>> From: Bob Schellink [mailto:sab...@gmail.com]
>> Sent: Sunday, 5 July 2009 12:13 AM
>> To: general@incubator.apache.org
>> Subject: Re: Incorrect use of "Sponsor".
>> 
>> Thanks for the clarification Niclas. I'll update the site.
>
> However, you are allowed to have them on the page, just with a 'thanks to
> ...' , be sure that any external links like these use the 'nofollow'
> attribute as specified by the PRC (so as to not water down the value of the
> main ASF thanks page.)

We put `nofollow` on the Bronze level sponsors and that was to stop the
sponsorship program from turning into a spam-ridden link farm.  I don't
recall the PRC requiring other links to use nofollow, but perhaps I
missed it.  Lots of projects have lists of companies which provide
commercial support or "powered by" sites.

-- 
   J. Aaron Farr
   馮傑仁
   www.cubiclemuses.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: Incorrect use of "Sponsor".

[Gavin]

> -Original Message-
> From: J Aaron Farr [mailto:fa...@apache.org]
> Sent: Sunday, 5 July 2009 9:03 PM
> To: general@incubator.apache.org
> Subject: Re: Incorrect use of "Sponsor".
> 
> On Sun 05 Jul 2009 02:36, "Gavin"  wrote:
> 
> >> -Original Message-
> >> From: Bob Schellink [mailto:sab...@gmail.com]
> >> Sent: Sunday, 5 July 2009 12:13 AM
> >> To: general@incubator.apache.org
> >> Subject: Re: Incorrect use of "Sponsor".
> >>
> >> Thanks for the clarification Niclas. I'll update the site.
> >
> > However, you are allowed to have them on the page, just with a 'thanks
> to
> > ...' , be sure that any external links like these use the 'nofollow'
> > attribute as specified by the PRC (so as to not water down the value of
> the
> > main ASF thanks page.)
> 
> We put `nofollow` on the Bronze level sponsors and that was to stop the
> sponsorship program from turning into a spam-ridden link farm.  I don't
> recall the PRC requiring other links to use nofollow, but perhaps I
> missed it.  Lots of projects have lists of companies which provide
> commercial support or "powered by" sites.

Yes you missed it then, Jim mailed it to all PMCs some time ago.

Gav...

> 
> --
>J. Aaron Farr
>馮傑仁
>www.cubiclemuses.com
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> Checked by AVG - www.avg.com
> Version: 8.5.375 / Virus Database: 270.13.3/2217 - Release Date: 07/04/09
> 17:55:00


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Proposal for Wookie a W3C Widget/Google Wave widget engine

[Sylvain Wallez]

Ross Gardler wrote:

I would like to submit the Wookie project proposal to the Incubator
PMC. Our draft is appended to the end of this mail and is available
at:

http://wiki.apache.org/incubator/WookieProposal

A quick overview of Wookie is:

Wookie is a Java server application that allows you to upload and
deploy widgets for your applications. Wookie is based on the W3C
Widgets specification, but widgets can also be included that use
extended APIs such as Google Wave Gadgets and OpenSocial.

I have agreed to champion and mentor this proposal, Gavin McDonald has
also agreed to mentor, more mentors are being sought - let me know if
you are interested.

At this stage I am seeking feedback on or questions about the Wookie
proposal.  The project team are subscribed to this list and ready to
respond to any queries.
  


The W3C widget spec is more targetted at standalone installation of 
widgets (like the Mac's Dashboard, Yahoo widgets, Vista widgets, etc) 
and Wookie as I understand it aims a providing a server-side 
implementation of this specification. This is an interesting point of 
view that can allow a wider audience to use this specification that is 
currently mostly of interest to mobile phone vendors. Now I'm curious to 
know if a server-side implementation will not hit some technical 
difficulities related to the implementation of a client-side 
specification (I saw that already with XForms).


What's interesting also, is that W3C widgets and OpenSocial gadgets are 
more or less competing specifications, and it seems from this proposal 
and what I saw in the code that Wookie would like to bridge the gap by 
providing OpenSocial features to W3C widgets. Is my understanding right?


This looks like an interesting proposal, and I'm willing to help it 
through incubation if it is accepted by mentoring it.


We must also consider the potential overlap with Shinding and Social 
Site and see what kind of collaboration (if any) with these projects 
would make sense.


As a side note, I'd love to run W3C widgets on my Android phone and my 
iPod Touch. Would client-side implementations of the W3C spec fit in the 
Wookie project?


Sylvain

--
Sylvain Wallez - http://bluxte.net


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Proposal][Vote] Traffic Server

[Sanjiva Weerawarana]

+1 (binding).

On Fri, Jul 3, 2009 at 4:33 AM, Leif Hedstrom  wrote:

> Good evening,
>
> As you know, we've been preparing our proposal to submit Traffic Server to
> the Incubator for a few weeks now. With the help from our champion (thanks
> Doug!), and the entire Incubator community, it's my pleasure to submit a
> request for Traffic Server to be accepted into the Incubator. The proposal
> is attached below, and is also available on the Wiki:
>
>  http://wiki.apache.org/incubator/TrafficServerProposal
>
>
> Since our first draft, we've added a number of mentors and contributors,
> and also added and improved on the proposal. I would like this to be
> considered our official application, and that the Incubator votes (+ or -)
> on our acceptance as a podling.
>
> Sincerely,
>
> -- leif
>
>
> Traffic Server
>
> 
>
>
> Abstract
>
> Traffic Server is fast, scalable and extensible HTTP/1.1 compliant caching
> proxy server.
>
>
> Proposal
>
> The goal is to create an Apache top level project to Open Source the
> existing Yahoo! Traffic Server code. Traffic Server (TS for short) is used
> in-house to deliver significant amount of HTTP traffic to millions of users.
>
> Key Features:
>
>   *
>
> HTTP/1.1 caching proxy server
>
>   *
>
> Scalable on SMP (TS is a hybrid thread + event processor)
>
>   *
>
> Extensible: TS has a feature rich plugin API
>
>   *
>
> Fast
>
>
> Background
>
> Traffic Server is a piece of software initially acquired by Yahoo! from
> Inktomi. The software has been actively developed and used at Yahoo for the
> last three years, and we're now getting ready to Open Source this project.
>
>
> Rationale
>
> Traffic Server fills a need for a fast, extensible and scalable HTTP proxy
> and caching. We have a production proven piece of software that can deliver
> HTTP traffic at high rates, and can scale well on modern SMP hardware. We
> have benchmarked Traffic Server to handle in excess of 35,000 RPS on a
> single box. Traffic Server has a rich feature set, implementing most of
> HTTP/1.1 to the RFC specifications.
>
>
> Initial goals
>
> The initial goal is to build a community of developers and users of the
> Traffic Server software. Longer term goal is to address a few feature
> additions that we think are beneficial:
>
>   *
>
> Full 64-bit support
>
>   *
>
> Porting to more Unix flavors (currently we only support Linux)
>
>   *
>
> Add missing features, e.g., CARP, HTCP, ESI and native IPv6
>
>   *
>
> Incremental improvements to existing features, and performance
>
>
> Current Status
>
>
>   Meritocracy
>
> Building our developer community using the meritocracy is important to the
> success of Traffic Server. We know there are many developers out there
> interested in the technology, and the meritocracy system is a great way to
> encourage participation.
>
>
>   Community
>
> Our hope is that our existing code, features and capabilities will attract
> a large community of both developers and users. We know that several
> developers who have previously worked on the code, are looking forward to
> participating in the Open Source efforts. We also believe that other
> organizations will find this project interesting and relevant, and
> contribute resources.
>
> The user community of Traffic Server would be similar to that of the Apache
> HTTP server, and in many cases they would overlap.
>
>
>   Core Developers
>
>   *
>
> Leif Hedstrom 
>
>   *
>
> Bryan Call 
>
>   *
>
> Vijaya Bhaskar Mamidi 
>
>   *
>
> Steve Jiang 
>
>   *
>
> Dima Ruban 
>
>   *
>
> Anirban Kundu 
>
>   *
>
> Andrew Hsu 
>
>   *
>
> Eric Balsa 
>   *
>
> BalaKrishna  JD
> 
>
>
>   Alignment
>
> Yahoo! is already a contributor to the Apache Foundation. We are already
> familiar with the ASF process, and we know it provides everything we need
> and require to be successful. We also feel there is a natural symbiotic
> relationship between Traffic Server and the Apache HTTP server, which is how
> TS is generally used at Yahoo!. The Traffic Server team is also in the same
> organization as the Yahoo! Hadoop developers, which is already an Apache
> TLP.
>
>
> Known Risks
>
>
>   Orphaned Products
>
> Traffic Server is widely used and deployed inside of Yahoo!. It's not going
> away anytime soon; in fact, it's growing fast.
>
>
>   Inexperience with Open Source
>
> All Yahoo! participants are active users and contributors to Open Source
> projects. Leif is a committer at Mozilla (although no longer active),
> creator of PerLDAP, as well as creator of a Yahoo! search API (pYsearch).
> Bryan Call is the creator of cksfv, and contributor to lmsensor. Dima Ruban
> has been an active developer in the FreeBSD project.
>
>
>   Homogeneous Developers
>
> The current list of committers are m

Re: Proposal for Wookie a W3C Widget/Google Wave widget engine

[Luciano Resende]

On Fri, Jul 3, 2009 at 7:01 AM, Ross Gardler wrote:
> I would like to submit the Wookie project proposal to the Incubator
> PMC. Our draft is appended to the end of this mail and is available
> at:
>
> http://wiki.apache.org/incubator/WookieProposal
>
> A quick overview of Wookie is:
>
> Wookie is a Java server application that allows you to upload and
> deploy widgets for your applications. Wookie is based on the W3C
> Widgets specification, but widgets can also be included that use
> extended APIs such as Google Wave Gadgets and OpenSocial.
>
> I have agreed to champion and mentor this proposal, Gavin McDonald has
> also agreed to mentor, more mentors are being sought - let me know if
> you are interested.
>

I'm willing to help Wookie as a mentor trough Incubation... feel free
to add my name to the proposal.

> At this stage I am seeking feedback on or questions about the Wookie
> proposal.  The project team are subscribed to this list and ready to
> respond to any queries.
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org