projects

Please help, you're my only hope...

Sorry if this is the wrong place to be posting this but it seemed like the easiest place to ask for some contact help short of creating a job posting.

In any case, I'm in a bit of an emergency situation and I need some help from someone with a few contracts I have at the moment. I've been working with Drupal for several years but I don't have a programming background.

Dear Sir,

Greeting from Riverstone Infotech,

I take this opportunity to introduce Riverstone Infotech, a Software Solution Corporation from San Francisco, US with the development center in Chennai, India. We have clients in U.S & Australia and been serving them for the last 10 years.

We are looking for a sustainable growth in Melbourne as we are progressing in our expertise in every domain, technology and software development. We have been providing cost effective IT solution to many industries and saved reasonable money to the company.

Hey just looking at a few sites and thinking about what should be on our projects list. Maybe themes could be one project. We could either take some from existing themes or maybe someone can develop a theme. I feel it might be good to have a couple of themes with the profile. Maybe a Basic Text Blue or an It Works Green theme. Of course the regions or areas can add their own, I just thought it would be good to have a few that would allow someone to have for default setup.

Back to project list:

<

ul>

Sorry, I was reading several of the conversations and posted this accidentally as a reply to a different question. I would welcome the input of the group.

Can anyone tell me how Storm conceives of the function of this field in a default Storm install? Does this field intend to capture the date a task or project was due? Or, does it intend to capture the date a task or project was actually completed?

If it captures the date a project was due, does storm then "watch" and time-stamp when we select a task/project's "Status" field and label it as "Completed."

Hello, this isn't really a "Job Post" since we don't have a specific job open right now, but we see some needs in the near future:

I work for a major Rochester, NY, non-profit organization (no mystery intended, it's WXXI) and we use Drupal for our primary web site. It's a fairly complex installation with appox 100 contributed modules installed, approx 40 content types, organic groups, panels, views, cck, media, and numerous "quirks" that require some explanation.

A lot of good things coming together as we're pressing forward with many of the objectives laid out in the Drupal Open Learning Initiative. We can use this post to tie everything together, keep tabs on progress, and discuss how to get involved!

One part of my GSoC is to add support (of some sort) to VersionControl API for having multiple branches within a project (like a drupal.org project) with different user permissions. The idea is to allow a more DVCS-like workflow, where people can work independently on their own branch and then request an admin user to pull their changes into the master repository. I won't be starting this for a few weeks, but I wanted to get a discussion going about what it should look like.

Well, if you can believe it, after all my hard work...the company I was doing this for decided to go with thier old HTML designer. Long story short, admidst me working on it, he marched back into the office on his own accord and bent the boss to his will to prove that he is better for the company because he has worked there before (unlike me). So now, I have no idea what kind of thing I can do with Drupal right now so that Im at least learning something. Any chance that there is a place online for Drupal newbs to get into a project for learning purposes?

Portland Community Media, in partnership with Denver Open Media, has created documents explaining the rules of scheduling Producer> Project> Programs. The document includes rules for series programs, scheduled on a quarterly basis, as well as individual programs that get scheduled on a first come, first served basis.

I have also included rules on how PCM schedules filler programs.

The focus of this discussion is:
- to communicate current scheduling rules and guidelines
- to discuss other methods of annual, quarterly or daily scheduling rules used by other media centers

One of the things we've been looking at out here in Portland is effective crewing management and tracking through the Open Media Project. At PCM we follow a policy of "if you don't use it you loose it" where producers need to keep active (at least once a year) in order to keep their certifications up-to-date. We also follow a policy of needing to work on productions before you can start your own.