[mantisbt-dev] greetings, new here

[Brian Lamb]

Hi all,



I jumped in here in hopes to share off my tweaks that I have done working
with mantisbt over the course of the last 3 years, in corporate / enterprise
environments. I feel that this experience might be valuable to the
community. I did an overhaul to the css style, which was just minor, but
needed. I also did some tweaks on categories which disabled some, enabled
some new, and some other custom tweaks, including styles for a Kanban
plugin, and more.

It will take me some time to figure out how to use this technology here. I
mean it was a feat alone getting to the mailing lists, finding you guys
(took about an hour). So I think im in the right place. I need to get
ahold of the latest copy of mantisbt, and see whats changes first, and then
I will consider a pull request if I can get them applied nicely. I need to
know how this works, im fairly new to collaborating on github website
itself.



Regards,

Brian





Kind Regards,

Brian Lamb

Sr. Software Engineer
Full Stack Web Application Development
<http://www.linkedin.com/pub/brian-lamb/44/892/2b4/> LinkedIin

[Damien Regad]

Post by Brian Lamb
Hi all,

Hello Brian, and welcome.

I'm not sure why it took you so long to find us, after all if you type
"mantis" in Google, our website is the first link that pops up... from there
it's just 2 clicks on "Support" then "Mailing lists" to get here, not to
mention that a link to the website as well as this mailing list's address is
included in the header of every source file.

Anyway, glad to have you with us, your contributions would be welcome. The
best way to propose these is by submitting a Pull Request on our Github
repository https://github.com/mantisbt/mantisbt, preferably linked to a
corresponding issue in our tracker http://mantisbt.org/bugs

For anything that is not a bugfix, please make sure you base your patches
against the *master* branch. Also, kindly follow our coding guidelines. Our
wiki https://www.mantisbt.org/wiki/doku.php/mantisbt:developers_corner is a
useful reference.

If you need help, post here or try to ping us on our Gitter channel for a
chat https://gitter.im/mantisbt/mantisbt

Cheers
Damien





------------------------------------------------------------------------------

[Brian Lamb]

Hi Damien,

Thank you!

Not sure why it took me so long either, lol. Not knowing I was looking for
a mailing list, I went to git hub mantisbt, mantis site foot links, through
support, documentation, for any contact info, Docs for Developers, into both
Developers Corner and Developers Guide, read up a bit, from there clicked on
Contributing to MantisBT, read up a bit, then got kind of stuck-like-chuck.
I think I skipped the mantis connect, somehow I got to gmane and tried to
figure out its antiquities. Can you point out some resources in those
Developers Corner and Guide to the mailing list? Ya gotta know, I was
having fun, just browsin as they say!

Can you clarify this part please:
"For anything that is not a bugfix, please make sure you base your patches
against the *master* branch. Also, kindly follow our coding guidelines. Our
wiki https://www.mantisbt.org/wiki/doku.php/mantisbt:developers_corner is a
useful reference."

So if its not a bug fix, have fix applied to clean chekout of base master,
patch that right? And if it IS a big fix what? branch it, base the patch on
the branch fix?

brian

-----Original Message-----
From: Damien Regad [mailto:***@mantisbt.org]
Sent: Wednesday, October 28, 2015 12:59 AM
To: Mantisbt-***@lists.sourceforge.net
Subject: Re: [mantisbt-dev] greetings, new here

Post by Brian Lamb
Hi all,

Hello Brian, and welcome.

I'm not sure why it took you so long to find us, after all if you type
"mantis" in Google, our website is the first link that pops up... from there
it's just 2 clicks on "Support" then "Mailing lists" to get here, not to
mention that a link to the website as well as this mailing list's address is
included in the header of every source file.

Anyway, glad to have you with us, your contributions would be welcome. The
best way to propose these is by submitting a Pull Request on our Github
repository https://github.com/mantisbt/mantisbt, preferably linked to a
corresponding issue in our tracker http://mantisbt.org/bugs

For anything that is not a bugfix, please make sure you base your patches
against the *master* branch. Also, kindly follow our coding guidelines. Our
wiki https://www.mantisbt.org/wiki/doku.php/mantisbt:developers_corner is a
useful reference.

If you need help, post here or try to ping us on our Gitter channel for a
chat https://gitter.im/mantisbt/mantisbt

Cheers
Damien





----------------------------------------------------------------------------
--
_______________________________________________
mantisbt-dev mailing list
mantisbt-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-dev


------------------------------------------------------------------------------

[Damien Regad]

Post by Brian Lamb
"For anything that is not a bugfix, please make sure you base your
patches against the *master* branch. [...]
So if its not a bug fix, have fix applied to clean chekout of base
master, patch that right? And if it IS a big fix what? branch it,
base the patch on the branch fix?

My thinking was that you have been working with Mantis 1.2 since you
mentioned tweaks going back 3 years.

The reason for my comment is that 1.2 branch is in a feature freeze, we're
only applying bug fixes and security patches to it. The focus of
development is on release 1.3 (master branch).

Consequently, if you'd like to submit a new feature, you should indeed
fork our repo on Github, create a new branch based on master (git checkout
-b feature master) and send us a pull request with your changes.

To submit a bugfix for the current release, the process is the same,
except you'd be basing your branch off 1.2 (git checkout -b bugfix master-
1.2.x). This is independent from the size of the patch.

Hope this clarifies.




------------------------------------------------------------------------------