Re: [VOTE] Apache CouchDB 0.8.1-incubating release

[Noah Slater]

On Wed, Aug 13, 2008 at 08:10:05PM +0200, Gianugo Rabellino wrote:
> +1

Binding?

-- 
Noah Slater, http://people.apache.org/~nslater/

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

Re: [VOTE] Apache CouchDB 0.8.1-incubating release

[Noah Slater]

On Thu, Aug 14, 2008 at 06:25:55AM +0100, ant elder wrote:
> The rest of the release looks fine to me too, so +1.

Binding?

-- 
Noah Slater, http://people.apache.org/~nslater/

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

Re: [VOTE] Apache CouchDB 0.8.1-incubating release

[Thilo Goetz]

Noah,

here's a list of the IPMC members:
http://incubator.apache.org/whoweare.html

It's not always up to date, so there can be false
negatives, but you can safely assume that whoever
is listed there has a binding vote.  Both Gianugo
and Ant are on the list :-)

--Thilo

Noah Slater wrote:

On Wed, Aug 13, 2008 at 08:10:05PM +0200, Gianugo Rabellino wrote:

+1


Binding?



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

Re: [VOTE] Apache CouchDB 0.8.1-incubating release

[ant elder]

Yes.

   ...ant

On Thu, Aug 14, 2008 at 1:31 PM, Noah Slater <[EMAIL PROTECTED]> wrote:

> On Thu, Aug 14, 2008 at 06:25:55AM +0100, ant elder wrote:
> > The rest of the release looks fine to me too, so +1.
>
> Binding?
>
> --
> Noah Slater, 
> http://people.apache.org/~nslater/
>

Re: [VOTE] Apache CouchDB 0.8.1-incubating release

[Noah Slater]

Thanks!

On Thu, Aug 14, 2008 at 02:38:54PM +0200, Thilo Goetz wrote:
> Noah,
>
> here's a list of the IPMC members:
> http://incubator.apache.org/whoweare.html
>
> It's not always up to date, so there can be false
> negatives, but you can safely assume that whoever
> is listed there has a binding vote.  Both Gianugo
> and Ant are on the list :-)
>
> --Thilo
>
> Noah Slater wrote:
>> On Wed, Aug 13, 2008 at 08:10:05PM +0200, Gianugo Rabellino wrote:
>>> +1
>>
>> Binding?
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

-- 
Noah Slater, http://people.apache.org/~nslater/

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

Re: [VOTE] accept Tashi into the Incubator

[Matt Hogstrom]

+1


On Aug 4, 2008, at 1:48 PM, Doug Cutting wrote:


Please vote on accepting Tashi into the Incubator.

Tashi's proposal is at:

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

Thanks!

Doug


-
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]

[Proposal] Windmill

[Mikeal Rogers]

This is a proposal to enter the incubator.

See http://wiki.apache.org/incubator/WindmillProposal for the most
up-to-date version.

We look forward to comments and discussion.

= Abstract =

The goal of Windmill is to build the best tool for automated testing  
of dynamic Web applications across all major browsers.


= Proposal =

Windmill provides a full-stack automation solution for dynamic Web- 
application testing.


It accomplishes this by implementing an extensive test API in  
JavaScript, and providing an intelligent proxy that can overcome the  
browser's same-domain security policy. The test API allows a single  
test to run on every major browser across all major operating systems.


Windmill boasts a wide range of debugging and test-authoring tools  
that make test writing, debugging, and editing a more streamlined  
process.


= Background =

Windmill was created at the Open Source Applications Foundation by  
Mikeal Rogers and Adam Christian to test the Chandler Server Web UI.  
It was announced more broadly at OSCON 2007 and has since enjoyed a  
wide range of use and contributions.


In January 2008, all the full-time, paid contributors from OSAF moved  
on to other employment. The project has since retained steady  
contribution despite having no full-time, paid contributors.


In July 2008, we proposed the project move its hosting away from OSAF  
because of uncertainty about long term sustainability -- due to OSAF's  
transition to a smaller-scale, mostly volunteer structure.


= Rationale =

Windmill was created to fulfill a need for a better dynamic Web- 
application testing tool after much frustration with existing  
solutions. We believe it has accomplished this goal and continues to  
improve, with ongoing, open interaction with the community.


What the project currently lacks is clear direction, leadership, and  
process. We believe the project would benefit greatly from Incubator  
mentorship, which would allow it to see much wider adoption, and grow  
a broader community.


= Current Status =

== Meritocracy ==

Since the project's inception, its development has been coordinated  
through collaborative decision-making (e.g., "+1 voting") on the  
mailing list, and open discussion on IRC.


== Community ==

Although the list of Core Developers has remained small we’ve welcomed  
outside contributions. Along with a few small but good patches, we’ve  
received some very good bugs and numerous features requests from the  
community. Our wiki documentation is being continually improved by our  
users.


We also have a very good reputation of providing support and resolving  
problems on IRC (#windmill on irc.freenode.net).A number of our users  
have stayed around to help others in need.


== Core Developers ==

Mikeal Rogers (Most of the Python code)
Adam Christian (Most of the JavaScript code)

== Alignment ==

Since Windmill was started at OSAF, it has enjoyed contributions from  
a variety of paid staff at OSAF. All of those employees are now  
employed elsewhere -- below are the ones that are still active.


 * Mikeal Rogers (Mozillla)
 * Adam Christian (Slide)
 * Matthew Eernisse (Seesmic)

= Known Risks =

== Orphaned Products ==

The project has survived the loss of paid contributions and continues  
to grow in use, despite a clear lack of leadership (I have only myself  
to blame).


== Inexperience with Open Source ==

All the contributors have a history in open-source development and the  
policies of the project were developed with the help of Ted Leung.


== Reliance on Salaried Developers ==

As of July 2008 one developer is paid part-time for his work on  
Windmill. The rest of the contributions are all volunteer at this time.


== A Excessive Fascination with the Apache Brand ==

One can’t ignore the impact the Apache brand has on a project, but  
what this project needs isn’t branding -- it’s the benefit of  
Incubator mentorship, direction, leadership, and process.


= Documentation =

http://windmill.osafoundation.org/

= Initial Source =

The code is currently hosted on OSAF’s Subversion server.

http://svn.osafoundation.org/windmill/

= Source and Intellectual Property Submission Plan =

We’ve gotten consent from OSAF to move the project to new location.

= External Dependencies =

We have a long list of external Python dependencies. These  
dependencies are managed via setuptools and are not distributed with  
the Windmill product and as such should not need be a licensing concern.


= Required Resources =

== Mailing lists ==

 * windmill-commits
 * windmill-dev
 * windmill-users

== Subversion Directory ==

https://svn.apache.org/repos/asf/incubator/windmill

== Issue Tracking ==

JIRA Windmill

= Initial Committers =

 * Mikeal Rogers
 * Adam Christian
 * Matthew Eernisse

= Sponsors =

== Champion ==

Ted Leung

== Nominated Mentors ==

 * Ted Leung


-
To unsubscribe, e-mail: [EMAIL PROTECT

Re: [Proposal] Windmill

[Les Hazlewood]

Just out of curiosity, where does this fit in versus, say, Selenium, MaxQ,
Canoo WebTest, and others?

There's nothing wrong if Windmill does the same stuff - I'm just curious
what it can do in comparison.

Cheers,

Les

On Thu, Aug 14, 2008 at 4:32 PM, Mikeal Rogers <[EMAIL PROTECTED]>wrote:

> This is a proposal to enter the incubator.
>
> See http://wiki.apache.org/incubator/WindmillProposal for the most
> up-to-date version.
>
> We look forward to comments and discussion.
>
> = Abstract =
>
> The goal of Windmill is to build the best tool for automated testing of
> dynamic Web applications across all major browsers.
>
> = Proposal =
>
> Windmill provides a full-stack automation solution for dynamic
> Web-application testing.
>
> It accomplishes this by implementing an extensive test API in JavaScript,
> and providing an intelligent proxy that can overcome the browser's
> same-domain security policy. The test API allows a single test to run on
> every major browser across all major operating systems.
>
> Windmill boasts a wide range of debugging and test-authoring tools that
> make test writing, debugging, and editing a more streamlined process.
>
> = Background =
>
> Windmill was created at the Open Source Applications Foundation by Mikeal
> Rogers and Adam Christian to test the Chandler Server Web UI. It was
> announced more broadly at OSCON 2007 and has since enjoyed a wide range of
> use and contributions.
>
> In January 2008, all the full-time, paid contributors from OSAF moved on to
> other employment. The project has since retained steady contribution despite
> having no full-time, paid contributors.
>
> In July 2008, we proposed the project move its hosting away from OSAF
> because of uncertainty about long term sustainability -- due to OSAF's
> transition to a smaller-scale, mostly volunteer structure.
>
> = Rationale =
>
> Windmill was created to fulfill a need for a better dynamic Web-application
> testing tool after much frustration with existing solutions. We believe it
> has accomplished this goal and continues to improve, with ongoing, open
> interaction with the community.
>
> What the project currently lacks is clear direction, leadership, and
> process. We believe the project would benefit greatly from Incubator
> mentorship, which would allow it to see much wider adoption, and grow a
> broader community.
>
> = Current Status =
>
> == Meritocracy ==
>
> Since the project's inception, its development has been coordinated through
> collaborative decision-making (e.g., "+1 voting") on the mailing list, and
> open discussion on IRC.
>
> == Community ==
>
> Although the list of Core Developers has remained small we've welcomed
> outside contributions. Along with a few small but good patches, we've
> received some very good bugs and numerous features requests from the
> community. Our wiki documentation is being continually improved by our
> users.
>
> We also have a very good reputation of providing support and resolving
> problems on IRC (#windmill on irc.freenode.net).A number of our users have
> stayed around to help others in need.
>
> == Core Developers ==
>
> Mikeal Rogers (Most of the Python code)
> Adam Christian (Most of the JavaScript code)
>
> == Alignment ==
>
> Since Windmill was started at OSAF, it has enjoyed contributions from a
> variety of paid staff at OSAF. All of those employees are now employed
> elsewhere -- below are the ones that are still active.
>
>  * Mikeal Rogers (Mozillla)
>  * Adam Christian (Slide)
>  * Matthew Eernisse (Seesmic)
>
> = Known Risks =
>
> == Orphaned Products ==
>
> The project has survived the loss of paid contributions and continues to
> grow in use, despite a clear lack of leadership (I have only myself to
> blame).
>
> == Inexperience with Open Source ==
>
> All the contributors have a history in open-source development and the
> policies of the project were developed with the help of Ted Leung.
>
> == Reliance on Salaried Developers ==
>
> As of July 2008 one developer is paid part-time for his work on Windmill.
> The rest of the contributions are all volunteer at this time.
>
> == A Excessive Fascination with the Apache Brand ==
>
> One can't ignore the impact the Apache brand has on a project, but what
> this project needs isn't branding -- it's the benefit of Incubator
> mentorship, direction, leadership, and process.
>
> = Documentation =
>
> http://windmill.osafoundation.org/
>
> = Initial Source =
>
> The code is currently hosted on OSAF's Subversion server.
>
> http://svn.osafoundation.org/windmill/
>
> = Source and Intellectual Property Submission Plan =
>
> We've gotten consent from OSAF to move the project to new location.
>
> = External Dependencies =
>
> We have a long list of external Python dependencies. These dependencies are
> managed via setuptools and are not distributed with the Windmill product and
> as such should not need be a licensing concern.
>
> = Required Resources =
>
> == Mailing lists ==
>
>  * windmill-commi

Re: [Proposal] Windmill

[Mikeal Rogers]

Of those 3 it's the most like Selenium.

As far as I know the "proxy spoof" method was pioneered by Selenium  
and we've continued to use/evolve that method of "tricking" the  
browser's same domain security policy. Our implementation of the test  
API has been very different from selenium as is our proxy <->  
javascript communication workflow.


Since our initial release we've done a lot of feature work around the  
recording, debugging, and test editing workflows. We've also done a  
good amount of work both in the proxy and in the javascript layer to  
make having a single test move around different target domains remain  
seamless and transparent.


It's been a while since I used Selenium so I can't comment on their  
current feature list compared to ours, but at the time we decided to  
write Windmill we were incredibly frustrated with the process of  
maintaining tests written in Selenium in an environment where the  
target product changed rapidly. We found that debugging and editing a  
test after changes to the product to be as difficult as writing the  
entire test all over again from scratch and have continued to improve  
windmill around our own use cases as well as user community feedback.


I hope that answers your question, this was a fairly high level  
answer, if you'd like I can go over any of those features/differences  
in more detail and point you at any code.


-Mikeal

On Aug 14, 2008, at August 14, 20081:40 PM, Les Hazlewood wrote:

Just out of curiosity, where does this fit in versus, say, Selenium,  
MaxQ,

Canoo WebTest, and others?

There's nothing wrong if Windmill does the same stuff - I'm just  
curious

what it can do in comparison.

Cheers,

Les

On Thu, Aug 14, 2008 at 4:32 PM, Mikeal Rogers <[EMAIL PROTECTED] 
>wrote:



This is a proposal to enter the incubator.

See http://wiki.apache.org/incubator/WindmillProposal for the most
up-to-date version.

We look forward to comments and discussion.

= Abstract =

The goal of Windmill is to build the best tool for automated  
testing of

dynamic Web applications across all major browsers.

= Proposal =

Windmill provides a full-stack automation solution for dynamic
Web-application testing.

It accomplishes this by implementing an extensive test API in  
JavaScript,

and providing an intelligent proxy that can overcome the browser's
same-domain security policy. The test API allows a single test to  
run on

every major browser across all major operating systems.

Windmill boasts a wide range of debugging and test-authoring tools  
that

make test writing, debugging, and editing a more streamlined process.

= Background =

Windmill was created at the Open Source Applications Foundation by  
Mikeal

Rogers and Adam Christian to test the Chandler Server Web UI. It was
announced more broadly at OSCON 2007 and has since enjoyed a wide  
range of

use and contributions.

In January 2008, all the full-time, paid contributors from OSAF  
moved on to
other employment. The project has since retained steady  
contribution despite

having no full-time, paid contributors.

In July 2008, we proposed the project move its hosting away from OSAF
because of uncertainty about long term sustainability -- due to  
OSAF's

transition to a smaller-scale, mostly volunteer structure.

= Rationale =

Windmill was created to fulfill a need for a better dynamic Web- 
application
testing tool after much frustration with existing solutions. We  
believe it
has accomplished this goal and continues to improve, with ongoing,  
open

interaction with the community.

What the project currently lacks is clear direction, leadership, and
process. We believe the project would benefit greatly from Incubator
mentorship, which would allow it to see much wider adoption, and  
grow a

broader community.

= Current Status =

== Meritocracy ==

Since the project's inception, its development has been coordinated  
through
collaborative decision-making (e.g., "+1 voting") on the mailing  
list, and

open discussion on IRC.

== Community ==

Although the list of Core Developers has remained small we've  
welcomed

outside contributions. Along with a few small but good patches, we've
received some very good bugs and numerous features requests from the
community. Our wiki documentation is being continually improved by  
our

users.

We also have a very good reputation of providing support and  
resolving
problems on IRC (#windmill on irc.freenode.net).A number of our  
users have

stayed around to help others in need.

== Core Developers ==

Mikeal Rogers (Most of the Python code)
Adam Christian (Most of the JavaScript code)

== Alignment ==

Since Windmill was started at OSAF, it has enjoyed contributions  
from a
variety of paid staff at OSAF. All of those employees are now  
employed

elsewhere -- below are the ones that are still active.

* Mikeal Rogers (Mozillla)
* Adam Christian (Slide)
* Matthew Eernisse (Seesmic)

= Known Risks =

== Orphaned Products ==

The project 

Re: [VOTE] accept Tashi into the Incubator

[Matthieu Riou]

So shouldn't this vote get tallied now? Seems that we're well passed the 72
hours.

Matthieu

On Thu, Aug 14, 2008 at 12:44 PM, Matt Hogstrom <[EMAIL PROTECTED]> wrote:

> +1
>
>
> On Aug 4, 2008, at 1:48 PM, Doug Cutting wrote:
>
>  Please vote on accepting Tashi into the Incubator.
>>
>> Tashi's proposal is at:
>>
>>  http://wiki.apache.org/incubator/TashiProposal
>>
>> Thanks!
>>
>> Doug
>>
>>
>> -
>> 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: Jt Pattern Oriented Framework (looking for champion/mentors)

[David S]

Hi folks,

I've updated the proposal with names:

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

I'll need to update the page again since a couple of people joined the project 
recently.

Regards,

Edgar

P.S. Jt 2.7 has been released.


Jt Proposal 
Project Name: Jt Pattern Oriented Framework 

 

Introduction

This proposal describes a Pattern Oriented Framework for the rapid
implementation of Java applications. This integrated framework is based
on a messaging architecture which provides strong encapsulation and
loose coupling; framework components can be interchangeably plugged
into complex framework applications using a “Lego" approach. This
framework provides capabilities for the implementation of applications
based on design patterns. The framework itself is conceived, from the
ground up, based on design patterns. Jt is probably one of the first
Pattern Oriented Frameworks (open source). 

Goals

The framework addresses the following goals: 
A) The pattern oriented framework implements and/or facilitates the
implementation of well-known design patterns like Gang Of Four design
patterns (GoF) and J2EE Design patterns. The framework itself is
conceived and implemented based on design patterns (from the ground
up). The framework also facilitates and accelerates the implementation
of applications based on design patterns. 
b) The framework architecture is based on a messaging design
pattern: framework objects are able to interchange information and
perform computations by sending, receiving and processing messages. A
messaging API provides strong encapsulation and loose coupling;
framework components can be interchangeably plugged into complex
framework applications using a “lego/messaging” architecture. The
framework takes full advantage of the power and simplicity of the
messaging design pattern/API. 
C) The framework lego/messaging architecture provides transparent
access to remote components: remote framework objects are treated as
local objects. Design patterns implemented by the framework (adapters,
remote proxies and facades) make this possible by hiding the
complexities associated with remote APIs. 
D) The framework provides transparent integration with other
technologies via framework adapters, proxies and the implementation of
related design patterns. These technologies include BPM, Data Access
Object implementations (DAO), Model View Controller implementations
(MVC), EJBs, AJAX, JMS, XML and Web Services. 
E) The framework is designed to be lightweight and fast (low overhead/small 
footprint). 
F) The framework messaging/lego architecture should improve and
simplify design/development efforts. There should be a tight
correspondence between UML design diagrams and the framework messaging
based applications and components needed for the implementation. The
framework should provide wizards and automated capabilities for
generating framework applications. Framework components should be
easily added to BPM process diagrams. In future versions of the
framework, it should be possible for application modules to be
generated directly from the UML design diagrams. This goal is still
work in progress. There is an early version of the Jt Wizard. 
G) The framework messaging architecture facilitates testing and
debugging efforts. It provides capabilities for testing components as
independent units by sending messages to the component and verifying
the expected reply messages. 
H) In order to provide additional productivity, the framework has been 
integrated with open source IDEs. 

Main Features

- Implemented J2EE design patterns include J2EE business delegate,
J2EE Session Facade, J2EE Service Locator and J2EE Value Object. 
- Web Services integration via the implementation of Web Services
adapters and proxies. The Jt messaging API greatly simplifies the
development and deployment of web services. 
- Integration with the MVC (Model View Controller) design pattern
and Ajax. Universal Jt components and adapters provide a transparent
interface between the Jt framework API and these technologies. The
business logic (controller piece) can be implemented using Jt framework
components and/or BPM business processes. 
- Integration with J2EE Enterprise Java Beans (EJBs) via Jt Adapters
and proxies. EJB clients are able to gain transparent access to remote
framework objects. No need to deal with the complexities of EJB
application development. An implementation of the J2EE Service Locator
pattern is also provided. 
- Easy customization of framework applications. This is done via
resource files: object attributes can be automatically loaded from a
resource file. 
- Integration with the XML APIs via XML adapters, helpers and built-in bean/XML 
mapping capabilities. 
- Built-in logging/debugging capabilities. Messages between
framework objects are automatically logged. This simplifies the
debugging and testing tasks. 
- Built-in  testing capabilities. 
- Efficient and lightweight in terms of memory uti

Re: [Proposal] Windmill

[Mikeal Rogers]

Of those 3 it's the most like Selenium.

As far as I know the "proxy spoof" method was pioneered by Selenium  
and we've continued to use/evolve that method of "tricking" the  
browser's same domain security policy. Our implementation of the test  
API has been very different from selenium as is our proxy <->  
javascript communication workflow.


Since our initial release we've done a lot of feature work around the  
recording, debugging, and test editing workflows. We've also done a  
good amount of work both in the proxy and in the javascript layer to  
make having a single test move around different target domains remain  
seamless and transparent.


It's been a while since I used Selenium so I can't comment on their  
current feature list compared to ours, but at the time we decided to  
write Windmill we were incredibly frustrated with the process of  
maintaining tests written in Selenium in an environment where the  
target product changed rapidly. We found that debugging and editing a  
test after changes to the product to be as difficult as writing the  
entire test all over again from scratch and have continued to improve  
windmill around our own use cases as well as user community feedback.


I hope that answers your question, this was a fairly high level  
answer, if you'd like I can go over any of those features/differences  
in more detail and point you at any code.


-Mikeal

On Aug 14, 2008, at August 14, 20081:40 PM, Les Hazlewood wrote:

Just out of curiosity, where does this fit in versus, say, Selenium,  
MaxQ,

Canoo WebTest, and others?

There's nothing wrong if Windmill does the same stuff - I'm just  
curious

what it can do in comparison.

Cheers,

Les

On Thu, Aug 14, 2008 at 4:32 PM, Mikeal Rogers <[EMAIL PROTECTED] 
>wrote:



This is a proposal to enter the incubator.

See http://wiki.apache.org/incubator/WindmillProposal for the most
up-to-date version.

We look forward to comments and discussion.

= Abstract =

The goal of Windmill is to build the best tool for automated  
testing of

dynamic Web applications across all major browsers.

= Proposal =

Windmill provides a full-stack automation solution for dynamic
Web-application testing.

It accomplishes this by implementing an extensive test API in  
JavaScript,

and providing an intelligent proxy that can overcome the browser's
same-domain security policy. The test API allows a single test to  
run on

every major browser across all major operating systems.

Windmill boasts a wide range of debugging and test-authoring tools  
that

make test writing, debugging, and editing a more streamlined process.

= Background =

Windmill was created at the Open Source Applications Foundation by  
Mikeal

Rogers and Adam Christian to test the Chandler Server Web UI. It was
announced more broadly at OSCON 2007 and has since enjoyed a wide  
range of

use and contributions.

In January 2008, all the full-time, paid contributors from OSAF  
moved on to
other employment. The project has since retained steady  
contribution despite

having no full-time, paid contributors.

In July 2008, we proposed the project move its hosting away from OSAF
because of uncertainty about long term sustainability -- due to  
OSAF's

transition to a smaller-scale, mostly volunteer structure.

= Rationale =

Windmill was created to fulfill a need for a better dynamic Web- 
application
testing tool after much frustration with existing solutions. We  
believe it
has accomplished this goal and continues to improve, with ongoing,  
open

interaction with the community.

What the project currently lacks is clear direction, leadership, and
process. We believe the project would benefit greatly from Incubator
mentorship, which would allow it to see much wider adoption, and  
grow a

broader community.

= Current Status =

== Meritocracy ==

Since the project's inception, its development has been coordinated  
through
collaborative decision-making (e.g., "+1 voting") on the mailing  
list, and

open discussion on IRC.

== Community ==

Although the list of Core Developers has remained small we've  
welcomed

outside contributions. Along with a few small but good patches, we've
received some very good bugs and numerous features requests from the
community. Our wiki documentation is being continually improved by  
our

users.

We also have a very good reputation of providing support and  
resolving
problems on IRC (#windmill on irc.freenode.net).A number of our  
users have

stayed around to help others in need.

== Core Developers ==

Mikeal Rogers (Most of the Python code)
Adam Christian (Most of the JavaScript code)

== Alignment ==

Since Windmill was started at OSAF, it has enjoyed contributions  
from a
variety of paid staff at OSAF. All of those employees are now  
employed

elsewhere -- below are the ones that are still active.

* Mikeal Rogers (Mozillla)
* Adam Christian (Slide)
* Matthew Eernisse (Seesmic)

= Known Risks =

== Orphaned Products ==

The project