planning

A well-known, "very" high-tech university is considering OA for its extranet knowledge-base. This decision came after looking at TWiki. What I'm attempting to plan for is how to manage UI for 200+ "Spaces," as OA provides. And also if this goes beyond what OA intends for. But I think it's rather ideal still. What do you think?

Hey all. This is a repost of my blog at
http://blog.onsavvy.com/post/52578909727/5-gotchas-in-open-source-projec...

I'm still climbing up the ladder of estimation proficiency so I'd really learn from you guys! Here are some of my experiences and thoughts - what do you think?

=======================

"So how much will this project cost and how long will it take?"

The million dollar question every freelancer and agency faces. Nothing moves before the client gets a satisfactory answer to this question, and signs it off.

Everyone,

There are 144 days left until the social event of the season called BADCamp. We have 0 people signed up for the event and 12,000ドル in sponsorship money raised. It will be all happening, of course, but plenty of work to do. The high level goals are to chat website things and help build the larger team of volunteers.

NOTE - This meeting is before the SFDUG social event at the C3 office. We will only be meeting for one hour, so come prepared to BADCamp.

Logistics:
* Schedule - Monday at 5pm
* In person - 300 Beale Street, Suite 101 (Chapter Three Office)

I've recently finished a big video project, hoping to be the next big YouTube. I'm hoping they are too. In the process I encountered a host of different challenges as you do with any new project. I thought I'd share some of the critical success variables back with the community. Hopefully, I'll help you avoid some of the growing pains I suffered through.

Does anybody have experience creating route planning tools using any location/gmap/openlayer modules? Basically, my goal is to input an arbitrary amount of locations (with a fixed start/end point) and find the shortest route between all the points.

Hi all, I promised a while ago to provide a rough roadmap for development of the SMS Framework suite of modules. Here is what I have so far.

I have been through the enormous issue queue and have collected a list of requests (bugs, features, etc) to factor in. I also had a meeting with Will White in January about this, and I am doing my best to include his ideas and intentions, as with derhasi's previous group post about 6.x-2.0.

So I am late in getting this posted, but there was a very productive BoF at DrupalCon DC about Handlers that has somewhat changed the intended approach. I will try to summarize what we decided here.

It seems the variety of options to create some sort of distro or feature set or pattern or template or whatever are broad, but one thing that is united under all of them is the need to collect a list of what sort of features should be included in this. So what features do you think every or most church websites should have. Let's stay away from modules, how it would be accomplished.

This is a question about defining the problem. We can figure out how to solve it later.

We now have a testing framework in Drupal core. What we need to move forward is some structure that makes writing tests easy and efficient so that we can go towards our 100% code coverage goal without wasting development resources.

What would you like to see happen for a 'first' step? Some additional postings/discussions here on the group? A live chat of some kind? An actual in-person meeting? If so, would it just be to get to know each other or perhaps some kind of show-and-tell? What do you think we should do?