Looks awesome.
One thing: we should setup something like bugzilla so we can track
features/bugs easily. This is more organized than just people working on
the features they want.
Shuhao
On 11/22/2013 12:21 AM, D M German wrote:
Hi Everybody,
I had a brief discussion with Denis yesterday
Is there anything wrong with using Github's issues tracker?
On Fri, Nov 22, 2013 at 1:57 PM, Shuhao Wu shu...@shuhaowu.com wrote:
Looks awesome.
One thing: we should setup something like bugzilla so we can track
features/bugs easily. This is more organized than just people working on
the
Is that where we want to put things? I'm usually okay with it, but for
certain projects bugzilla would be better as it is larger and more
complicated.
Github is also a bad place for people to report bugs as only those that
have a github account can. Something like bugzilla that allows persona
On 11/22/2013 10:58 AM, Wilson Brenna wrote:
Is there anything wrong with using Github's issues tracker?
There's also issues trackers (for bugs, feature-requests, and patches
separately) on sourceforge.net.
Those have the advantage of already being in place; but presumably they
are more
Hi Everybody,
I had a brief discussion with Denis yesterday and we agreed to clarify
the process of accepting contributions to Xournal. I have tried to
document it here:
HTTP://github.com/dmgerman/xournal/blob/master/README.org
this file will also appear at the bottom of:
Hi,
I think the readme description might benefit from to a step 0.
” New ideas for a feature for xournal, should be posted as a short proposal in
the mailing list. Thus, Xournal developers will be able to comment whether the
idea fits within the scope of xournals development strategies. They
On Fri, Nov 22, 2013 at 2:51 PM, Torsten Wagner
torsten.wag...@gmail.com wrote:
Hi,
I think the readme description might benefit from to a step 0.
” New ideas for a feature for xournal, should be posted as a short proposal
in the mailing list. Thus, Xournal developers will be able to comment
