TwTools, a new home for ToscaWidgets

[percious]

hello out there!

I just wanted to let everyone know that I am currently under the
process of taking over maintenance of all of the ToscaWidgets projects
which currently reside at:

http://svn.turbogears.org/projects/

My plan is to move all of these projects over to:

http://twtools.googlecode.com/svn/projects/

If you are an owner/maintainer of one of these projects, and have a
compelling reason to leave it in the Turbogears trunk let me know! I
think for the time being ToscaWidgets and ToscaWidgetsForms are going
to stay, but anything with a "tw" is getting moved.

each project will be getting its own trunk/tags/branches directory.
Those of you who are still actively maintaining their projects will be
given access to twtools.

If the package is not registered with pypi, I will be registering it.
If the package *is* registered with PyPI, I would appreciate it if you
could add the user twtools to the project roles as an owner.

If you have a private tw project that you want to publicise, and need
to find it a good home, TwTools is here for you. Please just email me
or Mark Ramm and one of us will give you access to the twtools repo
and a project folder complete with trunk/tags/branches for your
project. The only thing we ask in return is that you either allow us
to register your project, or add twtools as a "owner" to your pypi
account.

Why should share my ownership? The fact is that tw projects are small
and are often times abandoned, because they hold little value by
themselves. However, collectively the ToscaWidgets libraries are
pretty valuable to the WSGI community. They save developers time and
provide a place to put your work if you move from company to company.
We want the ability to pass maintenance from one developer to the
next, especially as JS libraries move pretty quickly and there is a
need to stay up-to-date.

Finally, I am going to propose a "tw." pypi namespace. This will
allow a clean slate for projects that are abandoned and goes along
with the "z3c.blah" and "zope.blah" way of doing things (which I
rather like). Vote here to keep it twBlah or tw.blah. (I also think
getting rid of capitals is more PEP8 compliant)

This email is going to be duplicated somewhere in the TG
documentation.

cheers.
-chris

[iain duncan]

> Finally, I am going to propose a "tw." pypi namespace. This will
> allow a clean slate for projects that are abandoned and goes along
> with the "z3c.blah" and "zope.blah" way of doing things (which I
> rather like). Vote here to keep it twBlah or tw.blah. (I also think
> getting rid of capitals is more PEP8 compliant)

+1 from me, and thanks for taking over maintenance.

Iain

[Florent Aide]

On Fri, Mar 28, 2008 at 10:34 PM, percious <ch...@percious.com> wrote:

> Finally, I am going to propose a "tw." pypi namespace. This will
> allow a clean slate for projects that are abandoned and goes along
> with the "z3c.blah" and "zope.blah" way of doing things (which I
> rather like). Vote here to keep it twBlah or tw.blah. (I also think
> getting rid of capitals is more PEP8 compliant)

+1 on tw.blah (PEP8 & namespace)

[Alice McGregor]

> Finally, I am going to propose a "tw." pypi namespace.  This will
> allow a clean slate for projects that are abandoned and goes along
> with the "z3c.blah" and "zope.blah" way of doing things (which I
> rather like).  Vote here to keep it twBlah or tw.blah.  (I also think
> getting rid of capitals is more PEP8 compliant)

+1 here too. There's nothing wrong with namespaces! I'm glad to
finally see some forward progress with tw.

- Alice.

[Alberto Valverde]

>
> percious schrieb:

>> I just wanted to let everyone know that I am currently under the
>> process of taking over maintenance of all of the ToscaWidgets projects
>>

>> I think for the time being ToscaWidgets and ToscaWidgetsForms are going
>> to stay, but anything with a "tw" is getting moved.
>

> Hi Chris,
>
> that is good news! Just to clarify: are you the new maintainer also for
> ToscaWidgets proper or just for tw* projects?
>
> If you are the maintainer for ToscaWidgets also, what are your plans for
> toscawidgets.org and beta.toscawidgets.org? Will they be merged with
> your code.google.com site also? Or should we host them on the
> turbogears.org server (the domain name should stay, IMHO)?
>
> Since we decided to replace TG widgets with TW in TG 1.1 (see
> 1.1/DevPlans on the wiki), it would be important for us (us being the
> 1.1 release team), to have some form of influence over the TW release
> process and documentation.
>
> I'd appreciate your thoughts on this.

Chris and I have been discussing this yesterday in this thread [1] in TW's
mailing list. The gist of it is that we're both going to be maintainers of
TW with full access to the cheeseshop and toscawidgets.org.
toscawidgets.org will act as the hub of the TW ecosystem hosting
repositories, docs, tracs, widget browser and other goodies.

toscawidgets.org is currently hosted in a VPS I own. However, I'm quite
amiable to the idea of moving it over to the VPS turbogears.org is hosted
at to have a larger pool of backup admins.

Alberto

[1]
http://groups.google.com/group/toscawidgets-discuss/browse_thread/thread/a2700123b7f0b9e0