Recently I contacted the bio maintainers - I wondered if they are interested in joining efforts with drupal 6.x.
We 'd like to get input from the community, so I post my ideas here:
I've already a nodeprofile port in preparation - the nodefamily
dependency will be dropped. The subform element stays as I like this as
a clean abstraction for integration node forms elsewhere and so allows
one to easily integration into the user registration form or the user
edit categories.
I can think of three different ways to join forces:
1. completely merge the modules
This would be ok for me, as long as we go with the subform element
module. Don't know, if this would be ok for you?
+ a more widespread, probably better maintained and stable module
+ extensions can rely on one module + API
- users can't use choose their favourite solution any more
- installation requires one additonial module to drop in (subform
element)
or
2. build upon a small "core module"
We could provide a small "profile as nodes" core module, which allows
basically to select node types, which are profiles. No further
dependencies!
Perhaps we could start with bio 1.0 for that.
Then we could build extension modules that build upon that, but use the
same base. E.g. different user registration integration, views
integration, the user edit categories integration, nodefamily and so on.
+ Modules can build upon this!
or 3.
keep separate modules, but invent a common way, how node types are
marked as profile, e.g. a common variable. So profile as nodes
extensions can build on top of that and work with both too.
+ More simple installation, e.g. just drop in bio or nodeprofile and it
works with all its features.
- There would be no API on which the extensions can rely. So they would
have to invent basic but useful functions again and again..
or 4.
don't join forces