vcs and tickets and so on for toscawidgets related project
iain duncan
will likely use Rum aswell down the road. It's a framework for building
custom CMS's, principally for TG2, but like rum/tosca, I intend to make
it so that a fairly simple set of adapters will allow it to be used on
other python web frameworks. I would like to make this available to
others as well and have it possibly contribute to more popularity for
toscawidgets and rum.
Sooo, I'm trying to figure out what the heck to do for version control,
wiki, docs, tickets. TG was svn+trac and is now using sphinx, which i
like. Do we know if TG2 is staying on svn? I think toscawidgets and rum
will be the closest and most foundational related projects, so it makes
sense to share as much of that as possible. What are tosca/rum using,
and why where those choices made?
thanks
Iain
Jorge Vargas
>
> I am working on a new project that uses toscawidgets extensively, and
> will likely use Rum aswell down the road. It's a framework for building
> custom CMS's, principally for TG2, but like rum/tosca, I intend to make
> it so that a fairly simple set of adapters will allow it to be used on
> other python web frameworks. I would like to make this available to
> others as well and have it possibly contribute to more popularity for
> toscawidgets and rum.
>
> Sooo, I'm trying to figure out what the heck to do for version control,
> wiki, docs, tickets. TG was svn+trac and is now using sphinx, which i
> like.
> Do we know if TG2 is staying on svn?
chances are no, there is a big discussion on the tg list about this
and almost everyone agrees that moving to mercurial is a good idea, so
it's a question of when rather than if.
The long time plan seems to be using the same code base that runs
toscawidgets.org but on a different server.
I'm working on said codebase to replace my companies svn+trac
installation, which I hope will help out the greater goal, maybe even
make a "project" out of it, who knows.
> I think toscawidgets and rum
> will be the closest and most foundational related projects, so it makes
> sense to share as much of that as possible. What are tosca/rum using,
> and why where those choices made?
everything is hosted on mercurial+trac, and it works great. As to why
I guess it was just Alberto's choice but to me they are the best
solutions to said problems at the moment.
tw.org infraestructure will be a good place to host your project, as
it was build so all things TW will have a place to live, in fact you
can create the project right now. But since I don't own the machine I
guess a good-to-go from Alberto will be good.
>
> thanks
> Iain
>
>
>
>
> >
>
iain duncan
Thanks Jorge, that properly confirms my hunches.
I guess I will keep my documentation efforts to sphinx docs only and
work on a local hg repository and not worry about the website stuff
until I talk to you and Alberto later then. Does that sound like a good
approach? ( I'm terribly new to actually coding with other humans! )
When I have a running proof of concept layer that is documented and does
something useful I will be hassling y'all for sure. ;-)
Iain
Jorge Vargas
milestone, for a project.
iain duncan
> > Thanks Jorge, that properly confirms my hunches.
> >
> > I guess I will keep my documentation efforts to sphinx docs only and
> > work on a local hg repository and not worry about the website stuff
> > until I talk to you and Alberto later then. Does that sound like a good
> > approach? ( I'm terribly new to actually coding with other humans! )
> >
> That is exactly what I'm doing. I consider push to the server as a
> milestone, for a project.
>
Thank you for your input Jorge. Hopefully this comes out as useful!
Iain