TwTools debut and Toscawidget release party
percious
moving tg/projects over to twtools/projects.
I also released the following widgets (some of which have never seen
the likes of pypi before)
tw.forms (probably the most important one)
js libraries
========
tw.extjs
tw.mootools (New!)
tw.mochikit
tw.jquery (now includes tw.jquery.flot!)
one-offs
======
tw.tabber (never before released)
tw.recaptcha (new as of last week)
tw.rating (not released before)
tw.tinymce
Here is the list of outstanding widgets to convert over the namespace
of. These are projects which are twXXX but don't live in the TG
repository. If you are an owner of one of these projects, please give
me your blessing by pointing me at your source repository. Those
libraries which are licensed appropriately will be assimilated if the
author does not respond in a reasonable amount of time. I may even do
prototype as a new widget with the current release of the JS.
twPrototype
twMaps (google maps)
Also, if you are an owner of a twXXX in pypi, consider removing your
entry if your project is now in twtools. I will be emailing those
authors personally if they do not remove their packages within a
reasonable time. This will avoid a heck of a lot of confusion later
on.
Need removal:
===========
twExtJS
twExt
twJQuery
twForms
twTinyMCE
tw.jquery.flot : luke, would you verify that the moved-around code
works right?
All you GSoC now have no reason not to start crackin'. Email me and
I'll give you commit access.
Again, if anyone out there has a TW they would like to share, but
don't want the hassle of having an svn repository, dealing with an
issue tracking system, or managing releases, twtools is here for you.
Just email me and we will find an appropriate home for your code.
cheers.
-chris
percious
widgets that are moved over in svn, but yet to be released:
===========================================================
tw.ajaxtools
tw.grids
tw.flashmp3
ajaxtools is being phased-out in favor of tw.jquery.activeform (the
original was based on jquery)
the other two I dont know what they do, so if you are the author, pipe
up or I'm not going to release them.
tg widgets that still need tw-izing
====================================
tgcurvycorners (in TG repo)
TGFKLookup 0.1a0.dev-r1287
TGYUI 2.5.0
Scriptaculous 1.8.1.1
TGBooleanFormWidget 0.1
TGExpandingFormWidget 0.1.3
dynwidgets 1.1
TGFirebugLite 1.0b
TurboFeeds 0.1b
these widgets represent a significant opportunity for someone with tw
experience to get in on the ground-floor open source participation.
Why not take a few of these widgets and convert them at our next
sprint at the end of april!?
cheers.
-chris
Alberto Valverde
> I made the proposed namespace change and spent most of my evening
> moving tg/projects over to twtools/projects.
Sorry for being so late to the party (and disappearing for so long, but
that's another story...)
I'm the owner of some of the packages mentioned and I'd would rather
like them to live at toscawidgets.org as I had mentioned a couple of
months ago and http://beta.toscawidgets.org/hg hints.
Daniel Haus has made a great job with the new design which I would hate
to see unused. Besides that, the VPS where it's hosted is much more
flexible than google code and can host WSGI apps, such as the widget
browser I'm working on.
Could we please agree on something to prevent what would effectively
turn into an eventual fork?
Alberto
Florent Aide
>
> percious wrote:
> > I made the proposed namespace change and spent most of my evening
> > moving tg/projects over to twtools/projects.
[...]
> Could we please agree on something to prevent what would effectively
> turn into an eventual fork?
We don't want no fork. As you already proposed somewhere else, Chris
could have access to your server and to the pypi pages. This would
solve most of our issues and ensure we are not stuck if you go
undercover again :)
A tools project like the one Chris is working on could even be hosted
on your server. We could then have a good platform to host an
ecosystem of TW widgets and begin promoting it over tg1 widgets and
_way_ beyond :)
What do you think Chris ?
Florent.
percious
You are of course welcome to host the code which you own wherever you
like. Every widget I moved over was MIT or LGPL licensed, so I
thought it was legally reasonable to move them over. I like the idea
of a centralized repository, I just don't know if hg is appropriate
for the average developer. SVN seems more widely accepted by the
community, and provides yet one less barrier to contribution.
The fact is that we have been struggling to get a reasonable release
for TG2 going because twForms was quite out of date in pypi. We have
asked you a number of times to do a release. This made our tutorial
session at pycon especially unpleasant. One person with that much
control over a technology which is so essential to the TG and greater
WSGI community needs to either be very active, or share ownership
(preferably both). People were seriously considering dropping TW
altogether. If I hadn't stepped up to say we need to keep it (mainly
because dbsprockets carries a heavy dependency) it would have perished
for sure.
I want to keep the tw. namespace going. All the packages in pypi
which carry the tw. namespace are owned by myself and the twtools
user, which Mark and I both have the password to. I spent a
considerable amount of time re-releasing and releasing packages which
had been collecting dust. I sent messages to the board to get
feedback from the community and received a positive response from
them.
I don't want this to be a fork of tw.forms/tw.alberto_owned_projects,
but I think twtools needs to live, and it needs to be on googlecode.
The toscawidgets beta site has been so for over 6 months now, and
google offers so much hosting for absolutely no cost. Plus, google
indexes the page into their own searches so we would get better
publicity for the widgets that are available. Also, google handles
all of the password/user management which makes it easier for us. We
also don't have to babysit a server anywhere. I am happy to give you
co-ownership with Mark and myself of twtools. Everything I have done
ensures transfer of ownership should I not be available. TwTools also
gives a consistent way of managing our tw library, and encourages
developers to participate by taking the burden of release and
maintenance away.
Basically we got a little tired of waiting and something needed to be
done. I believe twtools is the right solution, but I encourage your
feedback.
cheers.
-chris
Alberto Valverde
percious wrote:
> Alberto,
>
> You are of course welcome to host the code which you own wherever you
> like. Every widget I moved over was MIT or LGPL licensed, so I
> thought it was legally reasonable to move them over. I like the idea
> of a centralized repository, I just don't know if hg is appropriate
> for the average developer. SVN seems more widely accepted by the
> community, and provides yet one less barrier to contribution.
I like the idea of a central repository, trac and wiki too and it is
exactly what I have in mind for toscawidgets.org.
Out of curiosity, why do you think Mercurial is not appropriate? Many
open-source projects are using it, including Pylons, and seem quite
happy with it.
> The fact is that we have been struggling to get a reasonable release
> for TG2 going because twForms was quite out of date in pypi.
I can't see how a lack of a twForms release has been holding a TG2
release back. AFAIK, TG2 depends on a version of Pylons which is not
release yet either!
> We have asked you a number of times to do a release.
Sorry, but I can't seem to find an email in my personal mailbox (ie: not
from a mailing list which get filtered to separate folders which I've
ignored for the past 2 months) where I was asked for a release. The only
personal email I've received was Florent's last Thursday which I
promptly replied informing Florent, Mark and you that I wanted to
continue co-managing and co-developing TW with you.
> This made our tutorial session at pycon especially unpleasant.
Again, why? Doesn't pylons-dev pose the same problems?
> One person with that much
> control over a technology which is so essential to the TG and greater
> WSGI community needs to either be very active, or share ownership
> (preferably both).
I perfectly understand. This is the reason we're talking about this
right now. I'm gladly accepting your offer to share the effort of
releasing and maintaining TW.
> People were seriously considering dropping TW
> altogether. If I hadn't stepped up to say we need to keep it (mainly
> because dbsprockets carries a heavy dependency) it would have perished
> for sure.
Thanks for stepping up. However, I also depend on TW for many projects
and many people outside TG2 use it too so the assertion that (if TW was
dropped from TG2 it) "would have perished for sure" is a bit exaggerated
IMHO.
> I want to keep the tw. namespace going. All the packages in pypi
> which carry the tw. namespace are owned by myself and the twtools
> user, which Mark and I both have the password to. I spent a
> considerable amount of time re-releasing and releasing packages which
> had been collecting dust. I sent messages to the board to get
> feedback from the community and received a positive response from
> them.
Fine. I have no problems with a "tw" namespace, in fact, if you search
the archives, you will find that I even suggested a similar change
months ago: not chamging the distributions names but the python package
names (to change "from toscawidgets.widgets import forms" to the nicer
"from tw import forms").
However, I still want to move TW and twForms to toscawidgets.org as I
was planning to do and announced. Quite some work has already gone into
beta.toscawidgets.org (both design and programming-wise) and google code
just can't support some of the features I want to provide (eg: an
interacive widget browser and a "tw" cogbin leveraging the toscawidgets
trove index)
I see that twForms has already been forked inside twTools. I'd like to
ask you to please reconsider this move. Fragmenting efforts is the
almost the worst thing that could happen to TW (besides me being run by
a goat-carrying truck ;)
> I don't want this to be a fork of tw.forms/tw.alberto_owned_projects,
> but I think twtools needs to live, and it needs to be on googlecode.
Again, fine by me as long as neither TW or twForms is forked. But I
still think though that toscawidgets.org would better serve as a central
repository. Both for technical reasons (can run python) and "branding"
(Daniel's design, "toscawidgets.org", ...)
> The toscawidgets beta site has been so for over 6 months now,
This is 300% exaggerated. The mailing list archive and
http://beta.toscawidgets.org/hg/twWebSite/ proves it ;)
and
> google offers so much hosting for absolutely no cost. Plus, google
> indexes the page into their own searches so we would get better
> publicity for the widgets that are available. Also, google handles
> all of the password/user management which makes it easier for us. We
> also don't have to babysit a server anywhere. I am happy to give you
> co-ownership with Mark and myself of twtools. Everything I have done
> ensures transfer of ownership should I not be available.
> TwTools also
> gives a consistent way of managing our tw library, and encourages
> developers to participate by taking the burden of release and
> maintenance away.
Agree. A central repository is more convenient for developers to just
drop their widgets there. But couldn't toscawidgets.org be a better fit?
This are some the things that are possible on the VPS toscawidgets.org
is hosted at (and not on google code) that I was and I'm willing to
implement:
1) Automatic API docs generation with Apydia for all projects living in
the tree, along with a live preview of each Widget instance (this needs
patching Apydia)
2) Available widgets can be seen *live* and interacted with to see how
params affect display, input widgets can be submitted to see how the
validators coerces the POST/GET vars...
3) A "Cogbin" clone that periodically queries PyPI to list all
registered widgets.
4) Trac is available with all it's goodies
5) Mercurial kicks SVN's ass :P
> Basically we got a little tired of waiting and something needed to be
> done. I believe twtools is the right solution, but I encourage your
> feedback.
There was my lengthy feedback ;)
Regards,
Alberto
percious
>
> I can't see how a lack of a twForms release has been holding a TG2
> release back. AFAIK, TG2 depends on a version of Pylons which is not
> release yet either!
TW required <0.9, which made for some interesting scrambling...
>
> > We have asked you a number of times to do a release.
>
> Sorry, but I can't seem to find an email in my personal mailbox (ie: not
> from a mailing list which get filtered to separate folders which I've
> ignored for the past 2 months) where I was asked for a release. The only
> personal email I've received was Florent's last Thursday which I
> promptly replied informing Florent, Mark and you that I wanted to
> continue co-managing and co-developing TW with you.
>
formencode issues, and perhaps pokes from other TG developers (as I
was told).
http://groups.google.com/group/turbogears-trunk/browse_thread/thread/92f049cf27b68dfd/d4873eebfe56e5a3?lnk=gst&q=formencode#d4873eebfe56e5a3
http://groups.google.com/group/turbogears-trunk/browse_thread/thread/65ae2566773da57b/b28f79a76d15464d?lnk=gst&q=formencode#b28f79a76d15464d
http://groups.google.com/group/toscawidgets-discuss/browse_thread/thread/18d43033db4ffbe0/5a9d01727cdf8ef7?lnk=gst&q=iain#5a9d01727cdf8ef7
>
> Again, why? Doesn't pylons-dev pose the same problems?
>
we have stuff working in the current setup. And pylons-dev is a huge
change. The fixes to twForms were minor and could have resulted in a
quick release. Mostly just the test code had to be changed. Adding
all these trunk dependencies gets us into dangerous waters with would-
be TG2 adopters. So, no, pylons-dev is has not the same issues.
> > People were seriously considering dropping TW
> > altogether. If I hadn't stepped up to say we need to keep it (mainly
> > because dbsprockets carries a heavy dependency) it would have perished
> > for sure.
>
> Thanks for stepping up. However, I also depend on TW for many projects
> and many people outside TG2 use it too so the assertion that (if TW was
> dropped from TG2 it) "would have perished for sure" is a bit exaggerated
> IMHO.
http://groups.google.com/group/turbogears-trunk/browse_thread/thread/2fcbd97911b85cbd
You will notice me championing TW in there...
>
> > I want to keep the tw. namespace going. All the packages in pypi
> > which carry the tw. namespace are owned by myself and the twtools
> > user, which Mark and I both have the password to. I spent a
> > considerable amount of time re-releasing and releasing packages which
> > had been collecting dust. I sent messages to the board to get
> > feedback from the community and received a positive response from
> > them.
>
> Fine. I have no problems with a "tw" namespace, in fact, if you search
> the archives, you will find that I even suggested a similar change
> months ago: not chamging the distributions names but the python package
> names (to change "from toscawidgets.widgets import forms" to the nicer
> "from tw import forms").
>
existing tw packages.
> However, I still want to move TW and twForms to toscawidgets.org as I
> was planning to do and announced. Quite some work has already gone into
> beta.toscawidgets.org (both design and programming-wise) and google code
> just can't support some of the features I want to provide (eg: an
> interacive widget browser and a "tw" cogbin leveraging the toscawidgets
> trove index)
>
> I see that twForms has already been forked inside twTools. I'd like to
> ask you to please reconsider this move. Fragmenting efforts is the
> almost the worst thing that could happen to TW (besides me being run by
> a goat-carrying truck ;)
>
on maintaining tw.forms in parallel with twForms. I just want
tw.forms to have a home that we can access when the author is not
available (like to fix formencode for instance).
> > I don't want this to be a fork of tw.forms/tw.alberto_owned_projects,
> > but I think twtools needs to live, and it needs to be on googlecode.
>
> Again, fine by me as long as neither TW or twForms is forked. But I
> still think though that toscawidgets.org would better serve as a central
> repository. Both for technical reasons (can run python) and "branding"
> (Daniel's design, "toscawidgets.org", ...)
>
> > The toscawidgets beta site has been so for over 6 months now,
>
> This is 300% exaggerated. The mailing list archive andhttp://beta.toscawidgets.org/hg/twWebSite/proves it ;)
well. oy. I hate to have to go through what I did last night a
second time. Let's make a deal. Lets get 2,4,5 above working and
help me transfer everything over when we are done. Provide me with
access to toscawidgets.org and I will happily help in maintaining it,
and directing new users on Hg. Right now my GSoC students need a
place for their widgets, and tw.forms needed a new release. TwTools
might be nothing more than a nice hold-over until tw.org gets up-to-
snuff.
Thanks for all your feedback. Hopefully the end-result is
constructive. :)
cheers.
-chris
percious
Provide an easy way for people to sign up with an account for
toscawidgets.org and get a commit-bit on mecurial.
Also, does mecurial support directory-based permissions? It would be
nice to limit permissions on a per-project basis.
-chris
On Apr 1, 12:17 pm, percious <ch...@percious.com> wrote:
> Thanks for the feedback Alberto.
>
>
>
> > I can't see how a lack of a twForms release has been holding a TG2
> > release back. AFAIK, TG2 depends on a version of Pylons which is not
> > release yet either!
>
> Right, but the current release of pylons requires formencode>0.9 and
> TW required <0.9, which made for some interesting scrambling...
>
>
>
> > > We have asked you a number of times to do a release.
>
> > Sorry, but I can't seem to find an email in my personal mailbox (ie: not
> > from a mailing list which get filtered to separate folders which I've
> > ignored for the past 2 months) where I was asked for a release. The only
> > personal email I've received was Florent's last Thursday which I
> > promptly replied informing Florent, Mark and you that I wanted to
> > continue co-managing and co-developing TW with you.
>
> Not made by me personally, but mentioned on the ML about the
> formencode issues, and perhaps pokes from other TG developers (as I
>
>
> > Again, why? Doesn't pylons-dev pose the same problems?
>
> I agree, but Ben Bangert has been working closely with us to make sure
> we have stuff working in the current setup. And pylons-dev is a huge
> change. The fixes to twForms were minor and could have resulted in a
> quick release. Mostly just the test code had to be changed. Adding
> all these trunk dependencies gets us into dangerous waters with would-
> be TG2 adopters. So, no, pylons-dev is has not the same issues.
>
> > > People were seriously considering dropping TW
> > > altogether. If I hadn't stepped up to say we need to keep it (mainly
> > > because dbsprockets carries a heavy dependency) it would have perished
> > > for sure.
>
> > Thanks for stepping up. However, I also depend on TW for many projects
> > and many people outside TG2 use it too so the assertion that (if TW was
> > dropped from TG2 it) "would have perished for sure" is a bit exaggerated
> > IMHO.
>
percious
projects from pypi as we can so that we don't confuse users with the
namespace issues?
>
>
>
> > I can't see how a lack of a twForms release has been holding a TG2
> > release back. AFAIK, TG2 depends on a version of Pylons which is not
> > release yet either!
>
> Right, but the current release of pylons requires formencode>0.9 and
> TW required <0.9, which made for some interesting scrambling...
>
>
>
> > > We have asked you a number of times to do a release.
>
> > Sorry, but I can't seem to find an email in my personal mailbox (ie: not
> > from a mailing list which get filtered to separate folders which I've
> > ignored for the past 2 months) where I was asked for a release. The only
> > personal email I've received was Florent's last Thursday which I
> > promptly replied informing Florent, Mark and you that I wanted to
> > continue co-managing and co-developing TW with you.
>
> Not made by me personally, but mentioned on the ML about the
> formencode issues, and perhaps pokes from other TG developers (as I
>
>
> > Again, why? Doesn't pylons-dev pose the same problems?
>
> I agree, but Ben Bangert has been working closely with us to make sure
> we have stuff working in the current setup. And pylons-dev is a huge
> change. The fixes to twForms were minor and could have resulted in a
> quick release. Mostly just the test code had to be changed. Adding
> all these trunk dependencies gets us into dangerous waters with would-
> be TG2 adopters. So, no, pylons-dev is has not the same issues.
>
> > > People were seriously considering dropping TW
> > > altogether. If I hadn't stepped up to say we need to keep it (mainly
> > > because dbsprockets carries a heavy dependency) it would have perished
> > > for sure.
>
> > Thanks for stepping up. However, I also depend on TW for many projects
> > and many people outside TG2 use it too so the assertion that (if TW was
> > dropped from TG2 it) "would have perished for sure" is a bit exaggerated
> > IMHO.
>
iain duncan
> One final thing, I swear. Can we agree to remove as many twXXX
> projects from pypi as we can so that we don't confuse users with the
> namespace issues?
May I also request a meta package maybe ( or something ) so that it's
possible for a new user to do *one* easy_install of something and get
all that is needed to be up and running?
I found it confusing that toscawidgets and twforms were both needed and
still find the separation confusing when I have to hunt for something in
the internals.
Maybe tw.common or tw.core or something?
Thanks
Iain
Alberto Valverde
Ok, I really need to set better filters on my mailbox, I hope I'm still
the only "Alberto" in TG-land since that'll make it trivial. :)
I've missed all this at the time and just got to read it, I hope to have
time to chime in those threads soon. Thanks for the support.
Ok, so we should better have only one package then. tw.forms is fine by
me, farewell twForms.
>>> I don't want this to be a fork of tw.forms/tw.alberto_owned_projects,
>>> but I think twtools needs to live, and it needs to be on googlecode.
>> Again, fine by me as long as neither TW or twForms is forked. But I
>> still think though that toscawidgets.org would better serve as a central
>> repository. Both for technical reasons (can run python) and "branding"
>> (Daniel's design, "toscawidgets.org", ...)
>>
>>> The toscawidgets beta site has been so for over 6 months now,
>> This is 300% exaggerated. The mailing list archive andhttp://beta.toscawidgets.org/hg/twWebSite/proves it ;)
>
>
> touche, but I might add that TW documentation is long overdue.
Hmm, errr, mmmm... next question please. ;)
Great! 4 and 5 are almost ready. 4 needs some tweaks on the config. side
and 5) just needs projects to be moved there (hgpull makes it easy).
Site-wide authentication just needs wiring to a DB and a registration
form (tw.recaptcha couldn't be more timely!).
I have several prototypes for 2 which I need to consolidate into a
usable and clean piece of code.
I believe that if I do some home-work during the week to finish the
auth/registration stuff and we could virtually sprint over the weekend
to set you up your shell account, move the projects from tg.org and
code.google write an intro text for the front page (the current one is
very outdated and verbose) beta.tw.org can finally be tw.org. What d you
think?
Provide me with
> access to toscawidgets.org and I will happily help in maintaining it,
> and directing new users on Hg. Right now my GSoC students need a
> place for their widgets, and tw.forms needed a new release. TwTools
> might be nothing more than a nice hold-over until tw.org gets up-to-
> snuff.
(...)
percious wrote:
> Oh and can we add a #6?
>
> Provide an easy way for people to sign up with an account for
> toscawidgets.org and get a commit-bit on mecurial.
Sure. A registration form and site-wide auth was already planned :)
>
> Also, does mecurial support directory-based permissions? It would be
> nice to limit permissions on a per-project basis.
Sort of. It supports per repository permissions. Given that in mercurial
each branch or project is a repository in practice it is the same
effect. What you're seeing in beta.toscawidgets.org/hg is not one but
two repositories actually.
percious wrote:
> One final thing, I swear. Can we agree to remove as many twXXX
> projects from pypi as we can so that we don't confuse users with the
> namespace issues?
All of them that are under my control, but please add me as an owner too
;). However, renaming packages needs proper announcement and support
since all projects that list twX as a dependency in their setup.py will
need to be updated. Maybe leaving "legacy" packages full of
DeprecationWarnings on import and in the metadata description would be a
good idea to ease transitioning. Ivo already had troubles with twJQuery
from suddenly being removed from TG's SVN...
Glad we're finally agreeing on something. I'm sure this whole
opening-up-toscawidgets will be a great thing :)
Regards,
Alberto
P.S: I need to get offline now. I'll get back in this thread tomorrow
(just in case I'm pronounced dead too early :P)
percious
> Ok, I really need to set better filters on my mailbox, I hope I'm still
> the only "Alberto" in TG-land since that'll make it trivial. :)
> I believe that if I do some home-work during the week to finish the
> auth/registration stuff and we could virtually sprint over the weekend
> to set you up your shell account, move the projects from tg.org and
> code.google write an intro text for the front page (the current one is
> very outdated and verbose) beta.tw.org can finally be tw.org. What d you
> think?
each evening after 8pm MDT. I usually work throughout the week during
the evenings. Just make a list of things for me to do and some hg
access and I'll help out. I agree the front page needs work, there is
too much on it, and there are some spelling errors. If you can give
me some access that is something I can happily work on. Lets target
May 1 for the release of tw.org. TwTools will bridge that gap, and
allow us to release some kick ass widgets/docs with the new site. It
will also give the marketing group time to get up to speed, because
they are just getting ramped up.
> All of them that are under my control, but please add me as an owner too
> ;). However, renaming packages needs proper announcement and support
> since all projects that list twX as a dependency in their setup.py will
> need to be updated. Maybe leaving "legacy" packages full of
> DeprecationWarnings on import and in the metadata description would be a
> good idea to ease transitioning. Ivo already had troubles with twJQuery
> from suddenly being removed from TG's SVN...
>
goes prime-time, I'd want to see those packages gone.
> Glad we're finally agreeing on something. I'm sure this whole
> opening-up-toscawidgets will be a great thing :)
>
to coordinate. We both want Tosca to be a success. I think we both
want to see community interaction as well. twJQuery should go right
away because it doesn't even work right now.
> P.S: I need to get offline now. I'll get back in this thread tomorrow
> (just in case I'm pronounced dead too early :P)
cheers.
-chris
Alberto Valverde
> (...)
>
>> I believe that if I do some home-work during the week to finish the
>> auth/registration stuff and we could virtually sprint over the weekend
>> to set you up your shell account, move the projects from tg.org and
>> code.google write an intro text for the front page (the current one is
>> very outdated and verbose) beta.tw.org can finally be tw.org. What d you
>> think?
>
> I can't sprint this weekend, but I might be able to spare a few hours
> each evening after 8pm MDT. I usually work throughout the week during
> the evenings. Just make a list of things for me to do and some hg
> access and I'll help out. I agree the front page needs work, there is
> too much on it, and there are some spelling errors. If you can give
> me some access that is something I can happily work on. Lets target
> May 1 for the release of tw.org. TwTools will bridge that gap, and
> allow us to release some kick ass widgets/docs with the new site. It
> will also give the marketing group time to get up to speed, because
> they are just getting ramped up.
Sounds great, so let it be May 1st the great day :). I'll try finish the
auth. stuff this weekend then so I can give write access to the repo.
and use the Trac for coordination ASAP.
For the meantime: Any progress on the docs you guys have been working on
in docs.tg.org will be beneficial. Since it's written in
restructuredtext it can be later moved to the trac at tw.org easily. If
you'd like to give a shot at improving the front page, the source is
inside the tw distribution in docs/index.txt. Feel free to commit any
changes to TG's SVN since I'm syncing it periodically with my Hg sandbox
until we finally move it to tw.org.
Alberto
percious
> the archives, you will find that I even suggested a similar change
> months ago: not chamging the distributions names but the python package
> names (to change "from toscawidgets.widgets import forms" to the nicer
> "from tw import forms").
see it happen before too many new people adopt toscawidgets. Can we
shoot for May 1 on this as well? It would make my wrist hurt less to
type tw instead of toscawidgets.widgets in all the documentation. :-P
Seriously though, I really like this and I think there is considerable
support from the rest of the community.
-chris
percious
what I am doing? I mean, I'm good, but im not "that" good. Perhaps I
should just check out a local copy... what do you recommend?
-chris
Alberto Valverde
Yeah, this should go along the tw.X distribution name change too.
Alberto
Alberto Valverde
> Is there a way that I can change the beta.tw site "live" so I can see
> what I am doing? I mean, I'm good, but im not "that" good. Perhaps I
> should just check out a local copy... what do you recommend?
I'm working on a local copy myself and the push changes to beta when
ready. There's a README.txt inside the twWebSite egg which explains how
it can be installed. setup.py is also configured to pull all "pullable"
dependencies. If you have any troubles just let me know.
You can also work on beta directly if you prefer that.
Regardless of which method you choose, please mail me a SSH public key
so I can give you access to the server.
Alberto
P.S: Would you (or anyone reading this) like to help out with the ML's
new users moderation? Right now I'm the only one who can moderate which
has been a problem when I've been away last months. I'd really
appreciate some help with this.
iain duncan
I can do that. Is it a google group? I work from home so I'm at my usual
email all the time and probably working different hours than most being
on the west coast of Canada here.
Iain
Roger Demetrescu
> P.S: Would you (or anyone reading this) like to help out with the ML's
> new users moderation? Right now I'm the only one who can moderate which
> has been a problem when I've been away last months. I'd really
> appreciate some help with this.
Hi Alberto !
I can do it too...
Cheers
Roger
Alberto Valverde
> (...)
> Hi Alberto !
>
> I can do it too...
iain duncan wrote:
> (...)
>
> I can do that. Is it a google group? I work from home so I'm at my usual
> email all the time and probably working different hours than most being
> on the west coast of Canada here.
Iain, Roger,
You're both managers now. Thanks!
Alberto
percious
percious
for now. I'll send you an SHA in private.
cheers.
-chris
percious
I'm going to change the TG2 dependency to point at tw.forms. Let mw
know if this is a problem. People are still having problems in this
area:
http://groups.google.com/group/turbogears-trunk/browse_thread/thread/1765dda5b9bd1c49
cheers.
-chris