On Tue, Jan 31, 2012 at 11:29 AM, Bruce Pieterse <address@hidden
<mailto:address@hidden>> wrote:
On Mon 30 Jan 2012 20:05:50 SAST, Bruce Pieterse wrote:
On Mon 30 Jan 2012 17:33:39 SAST, Kenneth Loafman wrote:
Yes, I am behind on getting things done, the bug tracker
is the most obvious. I could use some help on triage and
classification, although I do reserve the right to
withlist any request that does not fit into normal backup
parameters.
Right now, stability and robustness are the most important
things needed, followed by a rough roadmap of needed
improvements.
Some of the bugs have been around so long that I think
they have been fixed and overlooked. More testing is needed.
...Ken
On Mon, Jan 30, 2012 at 8:55 AM, <address@hidden
<mailto:address@hidden> <mailto:address@hidden
<mailto:address@hidden>>> wrote:
On 30.01.2012 12:21, Jan Niggemann wrote:
> Am 30.01.2012 11:32, schrieb address@hidden
<mailto:address@hidden>
<mailto:address@hidden <mailto:address@hidden>>:
>> the backlog simply shows that duplicity lacks
developers, that's a
>> fact and won't change just because the bugs are not
tagged as new
>> anymore.
> It's not the status of a bug that matters. As I see it,
developers could focus on the important stuff more easily
if the
simpler bugs were correctly triaged and classified. That way,
developers wouldn't need to do this task and could, well,
develop.
unfortunately the status quo is, nobody is really doing
either ;(
>
>> triaging would make sense if you'd also intend to fix
some or at
>> least try to reproduce them, do you?
> Unfortunately, I don't have the skills to fix bugs in
duplicity
and neither do I have a machine to test with in order to
reproduce
them...
are you using duplicity? if so, you have a machine on
which you
can. if not. set up a virtual machine (e.g. with virtualbox or
virtualpc) with linux.
>> let's wait what ken has to say.
> I wouldn't mind if you (as the group of developers) say
that I
can't be of much help :-)
> I just wanted to let you know that there's someone who
could do
some of the simpler tasks for you...
>
try to familiarize yourself with duplicity, python. don't be
afraid, hacking python is no brain surgery. answer
questions (on
launchpad, mailing list) in case you know the answer. can
it get
simpler? ;)
regards ede/duply.net <http://duply.net> <http://duply.net>
_________________________________________________
Duplicity-talk mailing list
address@hidden
<mailto:address@hidden>
<mailto:address@hidden
<mailto:address@hidden>>
https://lists.nongnu.org/__mailman/listinfo/duplicity-__talk
<https://lists.nongnu.org/mailman/listinfo/duplicity-talk>
_________________________________________________
Duplicity-talk mailing list
address@hidden <mailto:address@hidden>
https://lists.nongnu.org/__mailman/listinfo/duplicity-__talk
<https://lists.nongnu.org/mailman/listinfo/duplicity-talk>
Hi,
I have an hour or two spare this week, perhaps I can go
through the bugs and sort out the ones that are really old,
like this: https://bugs.launchpad.net/__duplicity/+bug/428323
<https://bugs.launchpad.net/duplicity/+bug/428323>
I'm currently going over (long overdue)
https://help.launchpad.net/ to get myself familiar with how
things work. If you have additional resources for me to look
at before I contribute, please let me know!
Funny thing, I really want to learn C and Python this year,
I'm currently a PHP developer, but have used Python following
Swaroop CH's tutorials:
http://www.swaroopch.com/__notes/Python
<http://www.swaroopch.com/notes/Python>. Hopefully I can
submit bug fixes in the near future!
Let me know!
Thanks
Bruce
Can I take the silence as yes? lol
Yes you can. Anyone can submit bug fixes. They are reviewed and
tested then released into the code. We appreciate your willingness to
help.
...Thanks,
...Ken
_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk