In http://wiki.audean.com/g2/choosing the last column is titled Refactoring. While it might be obvious to others, I'm not sure I understand what it means and why it is on a column by itself.

I'm assuming that it means on-going G2 Refactoring of such features... is it?

Comments

fgm’s picture

You are assuming correctly. It is on a column by itself since it will not be G2 as we know it, but (hopefully), a combination of most (if not all) features in all the modules on the other columns.

Do you want to take part in that work ? Or have specific questions/requests about G2 or glossaries in general ?

BenK’s picture

I also took a look at the comparison chart and G2 Refactoring sounds great. Where are you and others in the process of developing this? I see that there was a Developer Days meetup... what was the result of that?

I'm looking for a Drupal 7 version of a glossary-type module and just wondering if G2 Refactoring is something likely to be available in the next couple of months. Are any issue threads dedicated to this development?

Thanks,
Ben

fgm’s picture

Alas, the sprint at DDDB had to be canceled, to allow for my finishing my Views 3 presentation there.

There will most likely be a D7 version of G2 in the next couple of months, but I have absolutely zero certainty as to whether it will be production-ready. The best way to take part in the development or follow up on it is to follow and/or contribute to the issue queue here, and register on the audean wiki to help with the documentation part, especially the modules comparison page, so I can have more complete details on what can/should/should not be merged in from other modules, This will also make it easier for users looking for such a module if that page gets to be really polished and then copied on d.o. in replacement for the current obsolete page.

bensnyder’s picture

@fgm - Howdy!

Thanks for the work you've done with getting node-based glossary functionality in Drupal! I'm wondering if you have any current projects or engagements in the near future that might warrant you spending time with the D7 branch of this module?

Perhaps you can create an issue with itemized tasks/objectives/issues, given that you are intimately familiar with the code. That way, other aspiring devs (like myself) can jump in and contribute more effectively. I think what we need here is a little more leadership/direction (not that there already isn't!) so that we can collectively develop this module.

Node-based glossary functionality is a killer feature for D7. I can think of several sites that I run that would benefit tremendously just from the added meshing/SEO.

Please advise, thanks! Everything you've done so far is much, much appreciated!

fgm’s picture

Issue summary: View changes
Status: Active » Fixed

Answered OP's question, so marking fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.