Hi everyone,
I'd like to maintain whatever momentum and excitement we have for working on a new website.
Project name and logo
---------------------
This is a big discussion which we don't necessarily have time or energy
to have right now. I think we all pretty much agree that updating
the website (regardless of the name/logo used) is the thing to focus on. With that in mind, I'd suggest that -- at least for now -- we use the name "Webware" with subtitle "Python Web Application Toolkit" and this version of Jacob Hanson's logo, which people generally seemed to like:
http://www.alphamotion.com/jacob_hanson-logo_03.gif
Python Web Application Toolkit sounds good to me. I think we have enough to move forward on this.
Hosting ------- Shane McChesney made a generous offer to pay for a virtual server from tummy.com for two years. Shane, does this offer still stand? If so, I think we should go ahead with it. I'd be happy to configure the server and set up access for those who will need it.
Yes, this would be great, and much thanks to Shane.
Domain
------
I would be happy to register a domain for the project for at least 2 years.
Unfortunately, it appears the squatter currently holding webware.org decided to renew it for another year. *sigh*
Here are some domains which are available: webware-project.org webware-python.org webware-toolkit.org
Any thoughts?
webware-python.org seems the most natural to me. We should have webware.sf.net point to the server either way. I'm pretty sure it's not a big deal to change that virtual domain.
Or webware-py.org, or as Shane suggested webware4python.org. As long as we decide on something -- webware.sf.net isn't bad or anything, but not being top-level makes Webware seem smaller, and there's so many dead SF projects that the sf.net name isn't great. But it's not bad either.
I kind of like webware-py.org -- short enough to type easily. (e.g., cheetahtemplate.org is too long for me)
If anyone registers a name, they should be sure to use an account where they can share the information. Then if something happens or they drift away, the group can continue to manage the domain.
Volunteers to work on website
-----------------------------
Eric Radman volunteered to contribute to the new website. I take that to
mean he doesn't have time to be the primary author/designer.
I would be happy to donate a few cycles of my own time, but my strengths are more with programming than with the visual aspect of web design. Also, I would prefer to help coordinate the effort, and spend my time on other Webware maintenance, too (fixing bugs, applying patches, working towards a new release).
Any other volunteers?
I can move the Wiki content over. I'd rather not keep Twiki, though I'm not sure what should replace it. MoinMoin? Whatever, as long as we can write reST text. (Zwiki? too hard to maintain?)
If anyone is interested in a Subversion repository, I can set that up as well. I like Subversion. Maybe we could put the Sandbox into Subversion...
If someone wants to take on the responsibility, I think we should empower them to make changes directly to the site without group approval (in part because "group approval" is really vague). I'd rather have a wonky design up for a little while, rather than lose momentum while we over-discuss possible designs.
Ian
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
