Refactoring of other Drupal 6 module which is not on d.o

Events happening in the community are now at Drupal community events on www.drupal.org.
misc's picture

How do we do with this kind of application: http://drupal.org/node/1426462
As it says it is built upon another module (for D6, this is D7), but it is not on drupal.org. So how do we handle the collaboration issue in this case?

Comments

"The collaboration issue" being... ?

beanluc's picture

Is "the collaboration issue" the one which is addressed here? Are you concerned about attribution to previous contributors after forking this from the github repo?

Or would you have some other concern in mind?

Hmm

jthorson's picture

I'd probably post a comment asking if they've been in contact with the original authors, as it would be good to include both versions under a single d.o project page ... but if the existing module hasn't been posted to drupal.org, and the original is GPL licensed, then I don't see any issues from the 'module duplication' point of view for the application itself.

easy peasy - it's gpl

greggles's picture

and the original is GPL licensed,

  • A drupal module
  • That is distributed
  • Must be GPL

http://drupal.org/licensing/faq

In this case, it's also explicitly GPL https://github.com/jakob-stoeck/drupal-biblio-mendeley/blob/master/LICEN...

Thanks, no I know.

misc's picture

Thanks, now I know.

/* Mikke Schirén, https://digitalist/ */

Code review for security advisory coverage applications

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week