From: Karim R. <kar...@gm...> - 2014-04-10 03:40:29
|
Hi Damien, Thanks for your reply. I've removed the erroneous mention of the MIT license in the language file, and added the GPL headers. Would it be possible for mantisbt-plugins to *fork* my repo instead of transferring ownership? I would prefer to retain control over the original repo and will be happy to maintain the fork. Thanks, Karim On Wed, Apr 9, 2014 at 3:51 PM, Damien Regad <dr...@ma...> wrote: > On 09.04.2014 20:08, Karim Ratib wrote: >> I've published my Slack integration plugin at >> https://github.com/infojunkie/MantisBT-Slack and I was wondering if it >> could be listed on the community plugins Github page at >> https://github.com/mantisbt-plugins. > > Hi Karim, > > I've created a team for you to transfer the repo to the plugins > organization; please follow the guidelines at > http://www.mantisbt.org/wiki/doku.php/mantisbt:mantis_plugins#hosting_a_new_plugin > > Kindly rename the repository by removing 'MantisBT'. You can call it for > example 'SlackIntegration'. > > I noticed you licensed your plugin under GPLv2 - you'll probably want to > add a header and copyright in each source file, and also remove the > reference to MIT license and the copyright by John Reese in the language > file. > > Cheers > Damien > > > --- > This email is free from viruses and malware because avast! Antivirus protection is active. > http://www.avast.com > > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |