note

cp -r feature_ax feature_press
cd feature_press
rename 's/feature_ax/feature_press/' *.*

Just created a new sandbox project, and try to push it to d.o:
git push origin master

error: src refspec master does not match any.

When you are putting a new project on Drupal.org means you haven't committed anything yet!

git init is not enough, heh.

(Yes, i googled this before figuring thisout, so if that's how you got here, you are not alone)

when renaming something, leave off slashes to be safe

when moving something into another folder, have no slash on the folder you are moving but include the slash on the folder you are moving it to.

For instance:

git mv admin_menu contrib/

drupal 7 programmatically create node in installation profile
http://www.group42.ca/creating_and_updating_nodes_programmatically_in_drupal_7

I have spent the day discovering that you cannot populate with content the content type created in a Feature module using the .install file of that Feature module.

We may want to do this for a present project, and in any case i wanted to flag one of the coolest things in Drupal 7,
Adding new contextual links: http://drupal.org/node/1089922

See also http://deglos.com/blog/2011/02/06/hacking-contextual-links-drupal-7

Found some great clues in a test

http://api.drupal.org/api/drupal/modules--simpletest--drupal_web_test_case.php/7/source

Putting that to work in our installation profile's .install file, shown beneath a modification of standard.install's role creation to create an additional 'content manager' role and to name the 'administrator' role more appropriately, as 'developer':

Thanks in part to
http://sachachua.com/blog/2008/07/eclipse-to-emacs-navigating-your-source-tree/

Set-up:

(If not already installed: sudo apt-get install exuberant-ctags)

ctags -R -f ctagstags --languages=php --langmap=php:.module.php.inc.engine.profile .

In .vimrc,

set tags=ctagstags;/

In .bashrc

capital letters in module names shouldn't be allowed.

http://drupal.org/node/1189292

update: it exists, http://drupal.org/sandbox/mlncn/1204336

it should be a drush script that puts files in sites/all/modules/devel
keeps them up-to-date with git
and then enables them

http://drupal.org/project/environment

is just too much overhead.

Basically all the reasonable approaches are here: