All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Talbot <chris@talbothome.com>
To: Wookey <wookey@wookware.org>,
	Marius Gripsgard <marius@ubports.com>,
	985893@bugs.debian.org
Cc: ofono@ofono.org, netdev@vger.kernel.org,
	debian-on-mobile-maintainers@alioth-lists.debian.net,
	librem-5-dev@lists.community.puri.sm, 982250@bugs.debian.org
Subject: Re: Bug#985893: Forking on MMSD
Date: Wed, 14 Apr 2021 20:12:21 -0400	[thread overview]
Message-ID: <0acefd2501e228328147911c7ba878b2fcd0cf3b.camel@talbothome.com> (raw)
In-Reply-To: <20210414220948.GL11215@mail.wookware.org>

Hello!

On Wed, 2021-04-14 at 23:09 +0100, Wookey wrote:
> On 2021-04-14 18:39 +0000, Marius Gripsgard wrote:
> 
> > I would really like to avoid a fork, it's not worth doing dual
> > work. Did you ping ofono devs at irc?  Also have you sent upstream
> > patches? If a fork is the way you want to go, you will need to
> > rename it as the existing packages need to follow upstream, we
> > can't
> > just rip an existing packages away from upstream.
> 
> Debian can package mmsd with whatever set of patches it sees fit. If
> the end result is ChrisT's version, with Modem Manager support, then
> I
> think that's reasonable. mmsd is not currently packaged in debian so
> I
> don't think a rename is required. Ultimately it's up to maintainers
> to
> choose which upstream is most appropriate. There used to be only one,
> but increasingly one gets a choice of varying degrees of active
> maintenance. (This can be a huge pain making life quite awkward for
> maintainers, and I find Debian is the only org trying to unify a
> diverse set of versions where a load of people have scratched their
> own itch and then just left it like that.)
> 

At this point, fork of mmsd should still work with ofono. I have not
disturbed anything ofono related, and have made several improvements to
the core that should benefit ofono too.

I would in addition welcome someone from ofono to work with me! I would
rather mmsd work with both stacks (as we all benefit from that). The
Mobian and PostmarketOS developers have welcomed me, and I am happy to
work with you all too. I joined the UBports matrix channel and
introduced myself (in addition to asking how you all contact the ofono
folks), you are free to reach out to me.

> Ultimately we want the best functionality for our users, and if the
> old upstream has been inactive for years then using this new,
> maintained version of mmsd may well be the best course. Efforts
> should
> continue to either give Chris access to the original repo or
> officially declare it 'under new management' so that there is a
> canonical place for the codebase, but in the meantime it's OK for
> debian to have a big patch.
> 

I admittedly do not know who to contact for repo access? I asked on the
Kernelnewbies IRC/Mailing list (as I am a bit of a kernel newbie), but
I did not hear anything back.

I am not trying to start a fork because I want to, and if you look at
Ofono's ML history, you can see that I have tried a lot to work with
upstream. I am starting a fork because I feel this is the only way I
can really move forward in getting MMS working. Without MMS,
unfortunately the Pinephone I have is little more than a toy with me,
and I put a lot of work into getting MMS working on the Modem Manager
stack.

> Versioning could be tricky in some situations, but SFACT the ofono
> mmsd is just 0.0 so the debian version can be 0.0.something and
> remain
> compatible with a shift back to that repo at some point.
> 
> Wookey

Thank you!

Respectfully,
Chris Talbot


  reply	other threads:[~2021-04-15  0:13 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-10 14:13 [PATCH 0/9] Updates for mmsd Chris Talbot
2021-04-10 14:13 ` Chris Talbot
2021-04-10 14:17 ` [PATCH 1/9] Fix mmsd to work with T-mobile Chris Talbot
2021-04-10 14:17   ` Chris Talbot
2021-04-10 14:20   ` [PATCH 2/9] Ensure Compatibility with Telus Canada Chris Talbot
2021-04-10 14:20     ` Chris Talbot
2021-04-10 14:20     ` [PATCH 3/9] Ensure Compatibility with AT&T Chris Talbot
2021-04-10 14:20       ` Chris Talbot
2021-04-10 14:21       ` [PATCH 4/9] Fix issue if there is an empty string in encoded text Chris Talbot
2021-04-10 14:21         ` Chris Talbot
2021-04-10 14:22         ` [PATCH 5/9] Allow for a user configurable maximum attachment size Chris Talbot
2021-04-10 14:22           ` Chris Talbot
2021-04-10 14:22           ` [PATCH 6/9] Update README Chris Talbot
2021-04-10 14:22             ` Chris Talbot
2021-04-10 14:23             ` [PATCH 7/9] Fix Draft and Sent Bugs Chris Talbot
2021-04-10 14:23               ` Chris Talbot
2021-04-10 14:23               ` [PATCH 8/9] Allow Maintainer mode to compile without -WError Chris Talbot
2021-04-10 14:23                 ` Chris Talbot
2021-04-10 14:24                 ` [PATCH 9/9] Enable support for Modem Manager Chris Talbot
2021-04-10 14:24                   ` Chris Talbot
2021-04-14 18:21 ` Forking on MMSD Chris Talbot
2021-04-14 18:21   ` Chris Talbot
2021-04-14 18:30   ` [Debian-on-mobile-maintainers] " Guido Günther
2021-04-14 18:46     ` Chris Talbot
2021-04-15  9:10       ` Guido Günther
2021-04-14 18:39   ` Marius Gripsgard
2021-04-14 18:39     ` Marius Gripsgard
2021-04-14 22:09     ` Bug#985893: " Wookey
2021-04-15  0:12       ` Chris Talbot [this message]
2021-04-14 19:29   ` Pavel Machek
2021-04-14 19:29     ` Pavel Machek
2021-04-14 21:11     ` Bug#985893: " Paul Wise
     [not found]     ` <c7ffd7e4d62e5d5ed397f69be180d81588a4cfd1.camel@talbothome.com>
2021-04-14 22:58       ` Pavel Machek
2021-04-14 22:58         ` Pavel Machek
2021-04-15  0:01         ` Chris Talbot
2021-04-27  9:15           ` Pavel Machek
2021-04-27  9:15             ` Pavel Machek
2021-04-29 14:49             ` Chris Talbot
2021-05-18  3:56             ` hoangnambohung

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=0acefd2501e228328147911c7ba878b2fcd0cf3b.camel@talbothome.com \
    --to=chris@talbothome.com \
    --cc=982250@bugs.debian.org \
    --cc=985893@bugs.debian.org \
    --cc=debian-on-mobile-maintainers@alioth-lists.debian.net \
    --cc=librem-5-dev@lists.community.puri.sm \
    --cc=marius@ubports.com \
    --cc=netdev@vger.kernel.org \
    --cc=ofono@ofono.org \
    --cc=wookey@wookware.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.