This is a distribution for drupal6 which helps to maintain projects based on agile methodologie. It contains the following:

Content types:

Projects
Tasks
Files

Capable of:

Creating new Projects
Creating tasks for a particular project
Attach files for a particular project
Assign tasks to a particular user
Email notification when a user is assigned to a particular task

Project Page :
http://drupal.org/sandbox/nalan/1886534
GIT repository:
git clone --recursive --branch 6.x-2.x nalan@git.drupal.org:sandbox/nalan/1886534.git project_management_for_agile

My reviews for other projects:
http://drupal.org/node/1475048#comment-5826548
http://drupal.org/node/1475184#comment-5831278
http://drupal.org/node/1212602#comment-5831666
------------------------------------------------------------------------------------------
http://drupal.org/node/1475184#comment-5850086
http://drupal.org/node/1522378#comment-5855410
http://drupal.org/node/1522378#comment-5855904
http://drupal.org/node/1522378#comment-5861216
http://drupal.org/node/1522378#comment-5865560

CommentFileSizeAuthor
FireShot Screen Capture #028 - 'Project 2 I Project Management' - nalan_me_pmdrupal_node_7.png50.38 KBnalan

Comments

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented
Status: Active » Closed (duplicate)
Multiple Applications
It appears that there have been multiple project applications opened under your username:

Project 1: http://drupal.org/node/1666240
Project 2: http://drupal.org/node/1892212

As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).

If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.

nalan’s picture

nalan commented
Status: Closed (duplicate) » Needs review

I have closed the other project and re-opening this project for review.
By the way, I don't have access to "Create Full project", and for your info I have already contributed a project (http://drupal.org/project/neelambal)

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented
Status: Needs review » Needs work
Issue tags: -PAreview: review bonus

There is still a master branch, make sure to set the correct default branch: http://drupal.org/node/1659588 . Then remove the master branch, see also step 6 and 7 in http://drupal.org/node/1127732
Review of the 6.x-2.x branch:

This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.

manual review:

  1. No code in the repository, the installation profile code should live on drupal.org.

Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.

nalan’s picture

nalan commented
Status: Needs work » Needs review

Hi kalusi,

1) it is already in default branch of 6.x-2.x.
2) I'll soon add the README file.
3) How am I suppose to add profile code in drupal.org??? If i do so, then it will be sandbox project, then the verify-makefile will again ignore it. That is why, i added the profile, custom module & custom theme in the github!! I have also read the http://drupal.org/developing/distributions/drupalorg (step 5) regarding packaging the distribution but it is not at all clear for me. What is wrong in putting the files in github becasue after review it will all be once again packaged all together right??

Please let me know if i'm wrong.

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented

Just take a look at how other distributions do it:
http://drupal.org/project/recruiter
http://drupal.org/project/distributions

nalan’s picture

nalan commented

Hi klausi,

From the "Recruiter distribution" example, I found that the features module has been downloaded from "ssh://gitosis@git.epiqo.com:50022/recruiter_features.git" during MAKE process "recruiter.make" which is NOT a drupal.org. So is it ok if I put my features module and profile in github and called it directly by my overall-make file which is present in the drupal.org???

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented

No, the recruiter.make file does not contain such a reference: http://drupalcode.org/project/recruiter.git/blob/refs/heads/7.x-1.x:/rec...

The recruiter features module lives on drupal.org: http://drupal.org/project/recruiter_features

I think that old SSH URL was accidentally committed in some early stages of Recruiter a few years ago.

nalan’s picture

nalan commented

Thank you for your quick reply.

So, do i have to create separate projects for :
* features module
* custom theme
* profile
????

Or put all of them in separate folders like "modules/feature_madules", "themes/custom_theme ", "profile/pma.make " in drupal.org git along with the overall make file?

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented

No, you don't have to that. We did it because we wanted our features to be reusable outside of the distribution.

Yes, you can put them in a modules/themes folder. Note that there will be no "profile" folder, all make files should be in the repository root.

nalan’s picture

nalan commented

Hi klausi,

If I put the both the make files in the root, what is the path of the profile which i should suppose to give in the overall-make file??
I know that the features_module and custom theme could be just copied to the folder "sites/all/.... " because the custom profile depends on it and it will be demanded during the installation (I will also mention it in the README file). But the path of the profile to be included in the overall-make file.... I'm really confused here!

It is this single point which made me to confuse about the whole packaging concept!!

I again thank you for your quick reply :)

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented

all make files should be in the repository root.

feature modules do not have to be copied, they can live in the folder of a profile. Example for a fully built recruiter installation: all modules are in profiles/recruiter/modules.

The profile is not included in the profile make file: http://drupalcode.org/project/recruiter.git/blob/refs/heads/7.x-1.x:/dru...

It is only included in the build.make file that can build the whole Drupal installation: http://drupalcode.org/project/recruiter.git/blob/refs/heads/7.x-1.x:/bui...

nalan’s picture

nalan commented

Hi Klausi,
It is the build make file i'm talking about:
In your build make file, you have the profile getting downloaded from drupal.org git project!!

projects[recruiter][type] = profile
projects[recruiter][download][type] = git
projects[recruiter][download][url] = git://git.drupalcode.org/project/recruiter.git

In my build make file where should i suppose to retrieve the profile because it will be along with the root and it could not be in "github" or in "sandbox of drupal.org git". so what is that 3 lines of code (ie: the 3 lines of code mentioned above) i should suppose to put in my build make file??

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented

You can ignore the build.make file, we only use it to build a full drupal installation locally. Focus on drupal-org.make.

nalan’s picture

nalan commented

Without the build.make file how am i suppose to do the custom profile installation?

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented
Status: Needs review » Needs work

Sorry for the delay. Make sure to review more project applications and get a new review bonus and this will get finished faster.

The custom profile installation is handled by the Drupal installer. You select the custom installation profile when you install Drupal. Just checkout your repository to the profiles folder in a Drupal 7 checkout. Then let drush make download all the dependencies and you can install your profile.

drupal-org.make is still missing, so this needs work.

brycefisherfleig’s picture

brycefisherfleig commented
Title: Project Management for Agile » [D6] Project Management for Agile

Included drupal version in title for faster reviewer process.

marialewis520’s picture

marialewis520 commented

Friends you have given me important suggestions to me that how can i make my project working better. Appreciated. When i come to know about Drupal i was come to know that this tool makes your working much easier that other Apps. By using Drupal it is easier for me to make project management/plans for my projects.

PA robot’s picture

PA robot commented
Status: Needs work » Closed (won't fix)

Closing due to lack of activity. Feel free to reopen if you are still working on this application.

I'm a robot and this is an automated message from Project Applications Scraper.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Component: other » distribution/profile