From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] drbdmanage and Python 3
Date: Tue, 14 Jul 2015 15:42:50 +0200 [thread overview]
Message-ID: <20150714134249.GA22235@rck.sh> (raw)
In-Reply-To: <55A50445.70205@mhtx.net>
On Tue, Jul 14, 2015 at 07:44:53AM -0500, Major Hayden wrote:
> Hello there,
>
> This is my first email to this list, so please let me know if this
> email is off-topic or belongs elsewhere! I've been a DRBD user for
> several years and I maintain the drbd packages for Fedora.
>
> I heard about drbdmanage and DRBD9 at a conference recently and I'm
> working to package drbdmanage on Fedora. However, it appears that
> drbdmanage isn't ready to be run with Python 3 quite yet. I found
> some print's without parentheses fairly quickly but I haven't taken a
> deep dive yet.
>
> Would Python 3 support and fixes be welcomed for drbdmanage? If so,
> would it make sense to send lots of patches to this list or send them
> somewhere else?
>
Hi and welcome to the list,
drbd-dev is for patch coordination and drbdmanage is also coordinated on
this list, so it is the right list.
You are right, drbdmanage is not yet ready for python3 and it is one of
the TODO items where help is highly appreciated!
Sending patches to this list is fine. If you can host your own repo, a
clone of our public repo with your own "for-upstream-py3" branch would
also be okay. Actually, I would prefer that plus mails to drbd-dev
whenever you are ready and we should merge your patches. Choose whatever
work flow you are most comfortable.
Currently, development on drbdmanage is mainly done by Robert, the
chief, and myself, his sidekick. For me it is perfectly fine to contact
me off-list if there are questions not appropriate for a broader
audience.
Regards, rck
prev parent reply other threads:[~2015-07-14 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 12:44 [Drbd-dev] drbdmanage and Python 3 Major Hayden
2015-07-14 13:42 ` Roland Kammerer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150714134249.GA22235@rck.sh \
--to=roland.kammerer@linbit.com \
--cc=drbd-dev@lists.linbit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox