Watching the ebb and flow of the list is actually interesting. Today almost
seems like the list was holding its breath. Yesterday, there was activity,
today it was quiet.

Folks, I'm not Moses. You are very much allowed to talk; I'm not issuing
commandments from on high :)

Now, on to the weekly update:

*What got done?*
This was actually a fairly productive week I'm pleased with the overall
results:

   - We've started using a new tool to help with planning:
   http://turbogears.flow.io/ It's a very simple, easy to use tool, and
   helps us keep some sort of focus on what's being done now, and what's coming
   up next. If you want to join that board, please speak with me. We can get
   you set up fairly easily.
   - I've managed to implement a fix for trac ticket #2336 and upload it to
   git. It's visible on SF.net right now. It's also visible on github, where
   I'm keeping my fork of the repository. As I complete tickets, I'll upload
   the resulting repository to SF.
   - We've run into some significant hiccups with the current SF offerings
   for hosting. More details below.
   - We've heard from Shining Panda, a company that is working on providing
   a continuous integration offering for Python developers. Hopefully, we can
   use their service when it comes out.

*Where are we now?*
I'm thinking we're at a crossroads with SF. Under the pylonsproject
umbrella, we're running into noticeable issues. Hosted Trac is downlevel,
importing tickets into hosted Trac is far from easy, git sometimes gives
permissions issues when I try to upload to there, and getting a useable
front page that won't step on the Pyramid developers toes has to wait until
they can create a front page, and then we can take a subdirectory under
there (or two, one for TG1 and TG2).

We need to migrate away from the current setup, as we're using resources
that were supposed to be temporarily granted, but we're not making moves to
stop using them. SF looks like it will, eventually, be the right home for
us, but I don't think we can wait. I'm thinking we need to get a new VPS
setup and working, and migrate there. Once the systems are all in place for
us to make a smooth migration to SF, we can do so. Right now, though, I
think we need to look at switching VPSes. I want to be off of Webfaction
(not because I don't like them, I do, I just don't want to abuse their
generosity) before the middle of March.

It's also time to look at the Google Summer of Code. The deadline for the
application is March 7, and I can think of a *bunch* of projects to put on
the list. Chris Perkins has already expressed a willingess to mentor. I'm
definitely going to volunteer. Do we have any other volunteers? And any
project ideas? I'll list mine below.

*What will be done this coming week?*
I'm trying to avoid doing too much code type work while we try to get
through the migration. As such, my main focus this week will be on GSoC. I'm
going to get the application, get the projects and mentors listed, and get
things moving there. Hopefully we get accepted, and get some students who
want to work with us. I'd like that, anyway.

My project ideas? A user management extension, a git repository extension, a
config extension, a CMS, a blog extension, possibly a replacement for
repoze.who/repose.what, too. Oh, a new "reference" application, too,
something to help show off what TG can really do. In my case, the idea is
for a program to handle *all* media types: text, video, and picture, and do
so in one unified interface. I think that would be something useful that
even I would use.

That's just off the top of my head. What other ideas abound? And who will
mentor?

That's the wrapup for now. The gears are turning again: Don't let them stop!

-- 
Michael J. Pedersen
My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171
          Yahoo/pedermj2002, MSN/[email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/turbogears-trunk?hl=en.

Reply via email to