Let sleeping dogs lie
Here's the story in one (code) line:
find ./ -name *.* -type f -exec s -i "s/group/og/g" '{}' \;For the humans amongst us, I'll explain. As part of the rewrite of Organic groups to Drupal 7, I thought that the name also deserves a rename -- to follow Drupal's naming standards. Since there weren't enough votes in the poll in g.d.o I've decided not to go with the change. OG module will keep its name - although in the UI we will use "Group" (the same way as node is refereed to as content).
I'll commit all the changes that are currently in github back to OG's cvs, after Add entity key label will land.
Yet another advantage of #d7cx - decisions can be undone.
Comments
Never knew about the poll
I never knew of the "contributed module ideas" g.d.o group so I never even knew of the poll. I would have voted to completely change the name but can live with just the UI changing. Does changing the UI also mean changing the URLs that have typically been hard-coded into og?
As a side note... it may be worth creating a g.d.o group for the purpose of the groups module. A place to discuss possible add-on modules, etc. I'm a heavy user of og so I'm interested in its future. :-)
> Does changing the UI also
> Does changing the UI also mean changing the URLs that have typically been hard-coded into og?
Yes. Anyway the URL should change as it needs to include the entity-type as well (e.g. group/node/1/admin)
> it may be worth creating a g.d.o group for the purpose of the groups module
Sounds good.
Why a second poll?
I know of a poll on this site, but not on g.d.o.
Odd. There has been a broad consensus on the poll here, so I really don't understand the need for another one?
Post new comment