roadmap

I need to create a kind of intranet
as a website for a subsidiary company of a university where
users who own projects can upload their progress (pdf files) and can be reviewed by departments responsible for the revision and thus advance their project in a roadmap or a series of booths evaluating their project

any ideas?
someone who wants to support me and needs support for some tasks?

Đối với người bắt đầu làm học Drupal thì việc học cái gì bắt đầu như thế nào là một điều rất khó khăn. Hồi trước mình và một bạn nữa cùng thảo luận và đưa ra một bản Roadmap dành cho Self Drupal Training. Anh em tham khảo xem. Hy vọng có ích dành cho người bắt đầu.

Xem file đính kèm :)

Hey fellow docs enthusiasts!

As some of you may have seen, there is going to be a big Docs Sprint in Vancouver in December (come join us if you're nearby!) The other part of what's going on that weekend, is that the core Docs Team members traveling here, as well as a few core devs (webchick, chx, and dmitrig01) will be gathering on Friday to discuss the Docs Team structure and initiatives in a dedicated retreat style afternoon.

We'll be discussing and brainstorming about things like:

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.

I wanted to post my ideas and what I thought would be a good roadmap for Pathauto as we're getting closer to a Drupal 7 release and what could be a big effort to have Pathauto in core for Drupal 8. I'd love to hear your feedback on these ideas!

After a good discussion with others, I cam up with a roadmap of the SSL support in Aegir which is of course up for discussion, but I think it's pretty neat and allows for targeting the problem one chunk at a time. All patches welcome from here on!

Based on an email conversation I had with Darren, Evgeny, Aron Novak and Walkah I pulled together this roadmap for advanced OpenID features (attribute exchange, provider, etc).

The goal is to reduce the overall number of modules involved in deploying OpenID attribute exchange features, to expand on existing content profile integration, to remove dependencies on modules that are not used in all use cases and to push changes into OpenID and OpenID Provider where it makes sense.

What about implementing a roadmap as a wiki based on Drupal 6 battle plans? Or now we might want to shift to Drupal 7.

It would group the features/bugs by categories and include a list of contributors willing to work on each item. No item can be listed without having at least one volunteer interested in working on it. That way we won't waste time with items that no one is interested in, but people can get a better idea of what is planned in the future.

Let's plan an informal roadmap for Pdfview.

I posted a recent flexinode update on my blog. Please read that, to see where we are now and where we are heading.

The most important part from that post is:

1. First we must clean out all the code and remove broken fields.
2. Then fix all critical bugs.
3. Then fix the upgrade path from 4.6 to 4.7.
4. Once stable, a 4.7-2.0 release will be brought out. and a 5.0 branch is opened.
5. Then I will start committing patches to prepare for a 5.0 release.
6. Once stable, a 5.0-1.0 release will be brought out.
7. Then new features make a chance o