[mantisbt-dev] Hi All - A change of direction for me.

[P Richards]

Hi All,



Just to let you know that I'm going to embark on a new project - "Mantis
Issue Tracker". This will be a fork from the Mantis Bug Tracker project with
a goal for being used for a helpdesk focus - this is the environment I
currently work in.



After 10 years spent working on Mantis Bug Tracker, it has become clear that
Victor's planned direction with moving towards a hosted MantisHub and trying
to make a financial return out of Mantis is not aligned with the goal's that
I set myself for involvement with an open source project. I'd like to wish
him success with those aims.



Myself, I'm keen to ensure that in todays hosted world with cloud services
etc, that it's possible to run a freely available issue tracker for all.



I'll post more details in a few days.



I still plan to continue to follow the project and submit any pull requests,
but I need to align my coding time with the needs for which I use Mantis -
which is as an issue checker in a MSSQL shop.



In the meantime, please let me know as soon as damien has fixed his email
address, as it's still broken and it would be good to do a joint security
release.



Paul

[P Richards]

And replying to my own post:



I've marked all my Pull requests on github as closed - some of them
contained ideas that may or may not be worth implementing, however where
everyone has seen them, whilst I'd be more than happy to help get them
merged, it does not make sense to me to live them open at this time.



Roland: Thanks for your support and advice and hopefully keep in touch.



Louis Bayle: I'll probably sent you a few patches over the coming months.



Victor: I suspect you've wanted to get rid of me for a while, so this should
make life easier for you. If you do want to discuss anything you know where
to find me.



Rombert: keep in touch. IT would be good to see you send your thoughts on
the SOAP API to the list one day



Damien: Come and find me on IRC and we can go through security patches for
1.2.18 and work out who is due credit where for finding vulnerabilities. I
believe I'm currently aware of 2 vulnerabilities that are not yet in bugs in
the bug tracker, as well as having fixes for the others. I *think* I may be
missing 1 patch across the known issues. To make life simple, we'll treat
the relationship for now as that of a security researcher and plan it as a
"joint disclosure" where proper credit and any announcements are released in
sync.



Paul



From: P Richards [mailto:***@mantisforge.org]
Sent: 20 October 2014 22:24
To: 'developer discussions'
Subject: [mantisbt-dev] Hi All - A change of direction for me.



Hi All,



Just to let you know that I'm going to embark on a new project - "Mantis
Issue Tracker". This will be a fork from the Mantis Bug Tracker project with
a goal for being used for a helpdesk focus - this is the environment I
currently work in.



After 10 years spent working on Mantis Bug Tracker, it has become clear that
Victor's planned direction with moving towards a hosted MantisHub and trying
to make a financial return out of Mantis is not aligned with the goal's that
I set myself for involvement with an open source project. I'd like to wish
him success with those aims.



Myself, I'm keen to ensure that in todays hosted world with cloud services
etc, that it's possible to run a freely available issue tracker for all.



I'll post more details in a few days.



I still plan to continue to follow the project and submit any pull requests,
but I need to align my coding time with the needs for which I use Mantis -
which is as an issue checker in a MSSQL shop.



In the meantime, please let me know as soon as damien has fixed his email
address, as it's still broken and it would be good to do a joint security
release.



Paul

[Damien Regad]

Paul

Despite our arguments, I valued your contributions to Mantis and
sincerely regret your decision to leave the team.

I wish you luck in your endeavor, but strongly suggest you pick a
different name and logo, to make sure you do not create any confusion in
the minds of users.

I also hope that your fork will remain close enough to Mantis that we
can benefit from each other, à la MySQL/MariaDB.

It also would be nice before you go, if you could release back to the
public all of the code you're currently holding in the mantisforge
archive, which you've been promising to do for nearly a year now (if not
more).

I’ve marked all my Pull requests on github as closed – some of them
contained ideas that may or may not be worth implementing, however where
everyone has seen them, whilst I’d be more than happy to help get them
merged, it does not make sense to me to live them open at this time.

I wish you hadn't done that - especially considering the recent "PR
spam" you generated, it will be more difficult and time-consuming to
retrieve them for an eventual merge.

Damien: Come and find me on IRC and we can go through security patches
for 1.2.18 and work out who is due credit where for finding
vulnerabilities.

Will do. Until then, do try and send the patches to me (with additional
relevant info as needed) - I assure you my email works just fine.

Damien

[Louis BAYLE]

Hi,

Of course it's always sad to see a teem split because it's often a waste of
energy. But forks are part of open-source project's life and sometime the
best thing to go forward. Also, I'm new to the Mantis community and I have
absolutely no judgement on this.

I just wanted to thank you for your interest to CodevTT, and I hope that
you will not too much change the database in your fork, so that CodevTT can
be compatible with both :-)

I'm looking forward to see your patches,
best regards
Louis

Louis BAYLE
Tel: [phone]

Post by Damien Regad
Paul
Despite our arguments, I valued your contributions to Mantis and
sincerely regret your decision to leave the team.
I wish you luck in your endeavor, but strongly suggest you pick a
different name and logo, to make sure you do not create any confusion in
the minds of users.
I also hope that your fork will remain close enough to Mantis that we
can benefit from each other, à la MySQL/MariaDB.
It also would be nice before you go, if you could release back to the
public all of the code you're currently holding in the mantisforge
archive, which you've been promising to do for nearly a year now (if not
more).

I’ve marked all my Pull requests on github as closed – some of them
contained ideas that may or may not be worth implementing, however where
everyone has seen them, whilst I’d be more than happy to help get them
merged, it does not make sense to me to live them open at this time.

I wish you hadn't done that - especially considering the recent "PR
spam" you generated, it will be more difficult and time-consuming to
retrieve them for an eventual merge.

Damien: Come and find me on IRC and we can go through security patches
for 1.2.18 and work out who is due credit where for finding
vulnerabilities.

Will do. Until then, do try and send the patches to me (with additional
relevant info as needed) - I assure you my email works just fine.
Damien
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
mantisbt-dev mailing list
https://lists.sourceforge.net/lists/listinfo/mantisbt-dev

[Robert Munteanu]

Hi Paul,

Let me start by acknowledging all the work you did on MantisBT - you
definitely contributed a lot and MantisBT is today better due to your
contributions, so a big thank you goes out for that.

I wish you good luck with your fork - and hope you don't mind if we
cherry-pick fixes that we find useful :-)

On a related note, I echo Damien's comment on naming - it would breed
confusion to name your project Mantis Issue Tracker ( MantisIT? ) so
please pick another name that

Cheers,

Robert

Post by P Richards
Hi All,
Just to let you know that I’m going to embark on a new project – “Mantis
Issue Tracker”. This will be a fork from the Mantis Bug Tracker project with
a goal for being used for a helpdesk focus – this is the environment I
currently work in.
After 10 years spent working on Mantis Bug Tracker, it has become clear that
Victor’s planned direction with moving towards a hosted MantisHub and trying
to make a financial return out of Mantis is not aligned with the goal’s that
I set myself for involvement with an open source project. I’d like to wish
him success with those aims.
Myself, I’m keen to ensure that in todays hosted world with cloud services
etc, that it’s possible to run a freely available issue tracker for all.
I’ll post more details in a few days.
I still plan to continue to follow the project and submit any pull requests,
but I need to align my coding time with the needs for which I use Mantis –
which is as an issue checker in a MSSQL shop.
In the meantime, please let me know as soon as damien has fixed his email
address, as it’s still broken and it would be good to do a joint security
release.
Paul
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
mantisbt-dev mailing list
https://lists.sourceforge.net/lists/listinfo/mantisbt-dev