It would be good if we can have a bugzilla "product" configured which
holds the "contrib" issues.
And of course the components should reflect the projects with default
assignees to the project maintainers.
Fabian Jakobs schrieb:
> Hello List,
>
> in the last few days we have been working hard
Hi,
Is it possible to have the qooxdoo-contrib mailinglist available in Nabble ?
http://www.nabble.com/qooxdoo-f3821.html
regards.
frederic
Sebastian Werner wrote:
>
> Fabian Jakobs schrieb:
>> Siarhei Barysiuk schrieb:
>>> Hello Fabian!
>>>
>>> I like very much idea about incubator. :) Great
Fabian Jakobs schrieb:
> Siarhei Barysiuk schrieb:
>> Hello Fabian!
>>
>> I like very much idea about incubator. :) Great to have all related
>> projects in one place.
>>
>> But I seem it's hard to organize. Each project has own sources,
>> developers, needs.
>> How will it be managed? For example
Siarhei Barysiuk schrieb:
> Hello Fabian!
>
> I like very much idea about incubator. :) Great to have all related
> projects in one place.
>
> But I seem it's hard to organize. Each project has own sources,
> developers, needs.
> How will it be managed? For example permissions of developers. What a
Hello Fabian!
I like very much idea about incubator. :) Great to have all related
projects in one place.
But I seem it's hard to organize. Each project has own sources,
developers, needs.
How will it be managed? For example permissions of developers. What about
approval of application/new project
Hello List,
in the last few days we have been working hard to set up
qooxdoo-contrib. qooxdoo-contrib will be a central place to host qooxdoo
related projects like
* New backends
* Example applications
* New widgets
* New qooxdoo classes
* ...
Its main purpose is to give anyo
