groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcin Erdmann <>
Subject Re: [PROPOSAL]About creating open collective for Groovy programming language in the name of Groovy Community
Date Wed, 09 Jan 2019 21:01:32 GMT
Great initiative, Daniel, thanks.

I know of at least one situation where a company wanted to contribute to
Groovy development in a monetary way but it was somewhat unclear of how to
actually implement it and it fell through the cracks. Having something like
the collective you're proposing would definitely make it easier and would
not require a company to sponsor a specific contributor. It would allow
multiple companies to put money into a pot which could then be used by
contributors who have the capacity and whenever their personal
circumstances allow them to work on development of the language.


On Tue, Jan 8, 2019 at 2:56 AM 孙 岚 <> wrote:

> Hi all,
>       As we all know, Groovy is lack of sponsorship and slows down its
> steps since Pivotal stopped sponsoring in 2014. Groovy needs more
> resources to complete big features and fix hard issues, e.g. MOP2,
> async/await, Refining generics of STC, Supporting Java11+ fully without
> warnings, etc.
>       I propose to create open collective for Groovy programming language,
> which can help Groovy Community to collect money to sponsor developing
> Groovy. Even if the collected money is very few every year, something is
> better than nothing!
>       Here are 2 steps to create open collective for Groovy(as the
> following snapshots show).  "*OSC will assist in managing the funds of
> the Fund*; it will collect the income and will pay and disburse the net
> income and principal for purposes of the Project as specifically set forth
> in the Protocols."(SEE the details in attachment 1)
>       As *groovy/groovy-core* is not my personal project, so I am
> requesting permission from you before I create open collective. To be
> frank, I am not sure whether it conforms to the Apache policy, so I send
> the email as a *Groovy enthusiast*(not a Apache committer) via my own
> hotmail(not the apache mail). I wish we could create open collective for *Groovy
> programming language* in the name of *Groovy Community*.
>       FYI, many open source projects have created open collective, e.g.
> 1,  babel:
> 2,  asciidoctor:
> 3,  jhipster:
> 4,  vuejs:
> 5,  mochajs:
>       Any thoughts?
> Cheers,
> Daniel.Sun
> *Steps to create open collective for Groovy*
> (*Terms & Conditions* details can be found in the attachments of this
> email)

View raw message