Debian Bug report logs - #861124
RFP: elpa-writeroom-mode -- distraction-free writing for Emacs

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupre <anarcat@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: RFP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Mon, 24 Apr 2017 16:09:13 -0400

Package: wnpp
Severity: wishlist

* Package name    : elpa-writeroom-mode
  Version         : 3.6.1
  Upstream Author : Joost Kremers <joostkremers@fastmail.fm>
* URL             : https://github.com/joostkremers/writeroom-mode
* License         : 3-clause BSD?
  Programming Lang: Elisp
  Description     : distraction-free writing for Emacs

writeroom-mode is a minor mode for Emacs that implements a
distraction-free writing mode similar to the famous Writeroom editor
for OS X. writeroom-mode is meant for GNU Emacs 24, lower versions are
not actively supported.

By default, writeroom-mode does the following things:

 * activate fullscreen
 * disable transparency
 * disable the menu bar
 * disable the tool bar
 * disable the scroll bar
 * enable a bottom window divider of 1 pixel
 * maximise the current window (i.e., delete all other windows in the
   frame)
 * place the fringes outside the margins
 * disable the mode line
 * add window margins to the current buffer so that the text is 80
   characters wide

The last three effects are buffer-local. The other effects apply to
the current frame. Because writeroom-mode is a minor mode, this isn't
entirely on the up and up, since minor modes aren't supposed to have
such global effects. But writeroom-mode is meant for distraction-free
writing, so these effects do make sense.

All these effects can be disabled or customised. In addition, there
are several more options that are disabled by default but can be
enabled in the customisation buffer.

----

I use this package to write long articles and things that need all my
focus. I don't think it has any other dependencies, and I use it
frequently - although I had to do some tweaks to make it work with
Xmonad.

There's another package called "darkroom-mode" that is similar, but
they didn't want to implement full-screen mode so I gave up on it.

I'd be happy to comaintain this with the elpa team if no one else
steps up.

Message #10 received at submit@bugs.debian.org (full text, mbox, reply):

From: Nicholas D Steeves <nsteeves@gmail.com>

To: Antoine Beaupre <anarcat@debian.org>, 861124@bugs.debian.org

Cc: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: Re: Bug#861124: RFP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Mon, 24 Apr 2017 20:37:20 -0400

[Message part 1 (text/plain, inline)]

control: owner -1
control: retitle -1 ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Hi Antoine,

I've been using a moderately customised local copy of writeroom-mode
forked from upstream many years ago, so of course I'd love to maintain
an official elpafied Debian package of it. :-)

How responsive is upstream to patches?  I find it really useful to
remove the fringes and margins when going from fullscreen to windowed,
and to have modeline enabled for fullscreen, for battery status,
clock, word count, etc, but to have these disabled for windowed.  One
of my other little personal projects is to change the font size when
going between windowed and fullscreen.  Do you know if tiling WMs
provide the necessary netwm hints for these to work properly?

Cheers,
Nicholas

[signature.asc (application/pgp-signature, inline)]

Message #24 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Nicholas D Steeves <nsteeves@gmail.com>

Cc: 861124@bugs.debian.org

Subject: Re: Bug#861124: RFP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Tue, 25 Apr 2017 08:04:56 -0400

On 2017-04-24 20:37:20, Nicholas D Steeves wrote:
> control: owner -1
> control: retitle -1 ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
>
> Hi Antoine,
>
> I've been using a moderately customised local copy of writeroom-mode
> forked from upstream many years ago, so of course I'd love to maintain
> an official elpafied Debian package of it. :-)

Well, the RFP was for the official version of course. :p But I guess it
would be fine if your improvements are packaged as well!

> How responsive is upstream to patches?

Pretty responsive, I'd say. If you look at the Github pull request list:

https://github.com/joostkremers/writeroom-mode/pulls?q=is%3Apr

... you'll see they have all been merged as is.

https://github.com/joostkremers/writeroom-mode/pulse/monthly

... although the project is not very active, but that's fine with me.

I have specifically requested two things, which got more or less
implemented completely:

https://github.com/joostkremers/writeroom-mode/issues/22
https://github.com/joostkremers/writeroom-mode/issues/24

> I find it really useful to remove the fringes and margins when going
> from fullscreen to windowed, and to have modeline enabled for
> fullscreen, for battery status, clock, word count, etc, but to have
> these disabled for windowed.

That seems completely counter-intuitive to me, but I guess if those are
made into separate modes, that should be fine. :)

> One of my other little personal projects is to change the font size
> when going between windowed and fullscreen.

That seems like a good idea - a separate effect too?

> Do you know if tiling WMs provide the necessary netwm hints for these
> to work properly?

Depends on the WMs. My experience with Xmonad so far has not been very
positive. I had to create a custom effect for fullscreen and the tiling
mode. I documented the sticky part here:

https://mail.haskell.org/pipermail/xmonad/2017-April/015260.html

The fullscreen part is better supported, but oddly a signal is missing
on writeroom's side, which is documented in issue #22 above...

Anwyays, this is all stuff that should be discussed in the upstream
trackers, and not necessarily here. I think we should try to follow
upstream as closely as possible here and get patches merged back
upstream.

So I encourage you to submit pull requests and issues for the things you
feel need to change in writeroom. So far, I have managed to use it
without patching it, and that is why I would like it to be packaged as
is in Debian.

I'd be happy to help you with the packaging if you need that or upload
if you need a sponsor or co-maintain if you're open to that. ;)
Otherwise, please go ahead and package this, it's great that someone is
stepping up so quickly to volunteer!

Thanks,

A.

PS: nice to see you here Nicholas :)

-- 
Wherever they's a fight so hungry people can eat, I'll be there.
Wherever they's a cop beatin' up a guy, I'll be there.
If Casy knowed, why, I'll be in the way guys yell when they're mad an'
I'll be in the way kids laugh when they're hungry an' they know
supper's ready. An' when our folks eat the stuff they raise an' live
in the house they build, why I'll be there.
                        - John Steinbeck, The Grapes of Wrath

Message #29 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Nicholas D Steeves <nsteeves@gmail.com>

To: Antoine Beaupré <anarcat@debian.org>

Cc: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Tue, 25 Apr 2017 11:05:57 -0400

control: pending -1

Hi Antoine,

On Tue, Apr 25, 2017 at 08:04:56AM -0400, Antoine Beaupré wrote:
> On 2017-04-24 20:37:20, Nicholas D Steeves wrote:
> > control: owner -1
> > control: retitle -1 ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
> >
> > Hi Antoine,
> >
> > I've been using a moderately customised local copy of writeroom-mode
> > forked from upstream many years ago, so of course I'd love to maintain
> > an official elpafied Debian package of it. :-)
> 
> Well, the RFP was for the official version of course. :p But I guess it
> would be fine if your improvements are packaged as well!
> 
> > How responsive is upstream to patches?
> 
> Pretty responsive, I'd say. If you look at the Github pull request list:
[...]
> I have specifically requested two things, which got more or less
> implemented completely:
> 
> https://github.com/joostkremers/writeroom-mode/issues/22
> https://github.com/joostkremers/writeroom-mode/issues/24

Nice!  Sorry I was unclear, I meant I'll package the official version
and send patches or pull requests to upstream.

> > I find it really useful to remove the fringes and margins when going
> > from fullscreen to windowed, and to have modeline enabled for
> > fullscreen, for battery status, clock, word count, etc, but to have
> > these disabled for windowed.
> 
> That seems completely counter-intuitive to me, but I guess if those are
> made into separate modes, that should be fine. :)

:-) Exactly.  My setup is a bit bizarre, but it basically evolved to
cope with the transition from a 17" 4:3 screen to a 10" 16:9 netbook,
and to get positive feedback from the word count and pressure from the
clock while typing way too forcefully while trying to meet deadlines.
It would be even more intense with a countdown timer...  The premise
being that you sit down to write, start writeroom, and the combo of
the carrot and stick helps with productivity: an interval of working
fast, then a relaxing and/or thinking/planning interval.

> > One of my other little personal projects is to change the font size
> > when going between windowed and fullscreen.
> 
> That seems like a good idea - a separate effect too?

I haven't actually done the work for it yet, but I've been wanting to
implement it "someday" for years.  I think the easiest thing to do,
for the purposes of writeroom, would probably be to configure a
scaling factor for 'text-scale-adjust as part of the fullscreen hook.

> > Do you know if tiling WMs provide the necessary netwm hints for these
> > to work properly?
> 
> Depends on the WMs. My experience with Xmonad so far has not been very
> positive. I had to create a custom effect for fullscreen and the tiling
> mode. I documented the sticky part here:
> 
> https://mail.haskell.org/pipermail/xmonad/2017-April/015260.html
> 
> The fullscreen part is better supported, but oddly a signal is missing
> on writeroom's side, which is documented in issue #22 above...
> 
> Anwyays, this is all stuff that should be discussed in the upstream
> trackers, and not necessarily here. I think we should try to follow
> upstream as closely as possible here and get patches merged back
> upstream.

Merged back, for sure.  Is the "discuss it on the BTS first" policy
for more users->BTS->maintainers->upstream?

> So I encourage you to submit pull requests and issues for the things you
> feel need to change in writeroom. So far, I have managed to use it
> without patching it, and that is why I would like it to be packaged as
> is in Debian.

Preliminary packaging is here:
ssh://git.debian.org/git/pkg-emacsen/pkg/writeroom-mode.git

I need to email to team to find out what the preferred way of managing
things in the VCS during a deep freeze (eg: push tags only, push an
experimental branch and keep master's changelog UNRELEASED, etc).
Also, I'm not sure what to license debian/* as wrt BSD-3-clause.

> I'd be happy to help you with the packaging if you need that or upload
> if you need a sponsor or co-maintain if you're open to that. ;)
> Otherwise, please go ahead and package this, it's great that someone is
> stepping up so quickly to volunteer!
> 
> Thanks,
> 
> A.
> 
> PS: nice to see you here Nicholas :)

Nice to see you too :-D  I'm highly motivated when people I know ask
for something, and it's also (finally) something I'm familiar with.
There's a part of me that feels "Aha!  I found my niche, my project to
prove I can be a DD...my selfish glory!" but that's overshadowed by
"It's way more fun and more meaningful to work as a team".

I'm thinking of something like an article and some streamlined
configurations for "Emacs for professional, technical, and creative
writing for everyone who didn't learn to use it as an IDE", plus
packaging all the bits that help boost focused productivity.  Maybe
mentioning ErgoEmacs...  Alternatively, it wouldn't be that hard to
make hitting the word-count target play a nice sound or do something
funny with nyan-mode :p

Take care,
Nicholas

Message #36 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Nicholas D Steeves <nsteeves@gmail.com>

Cc: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Tue, 25 Apr 2017 13:35:23 -0400

On 2017-04-25 11:05:57, Nicholas D Steeves wrote:
> control: pending -1

Just for the record - we usually mark bugs as "tags -1 +pending" when an
upload is ready in VCS or just uploaded to ftp-master. Not sure the
above does anything. :)

> Hi Antoine,
>
> On Tue, Apr 25, 2017 at 08:04:56AM -0400, Antoine Beaupré wrote:
>> On 2017-04-24 20:37:20, Nicholas D Steeves wrote:

[...]

>> > How responsive is upstream to patches?
>> 
>> Pretty responsive, I'd say. If you look at the Github pull request list:
> [...]
>> I have specifically requested two things, which got more or less
>> implemented completely:
>> 
>> https://github.com/joostkremers/writeroom-mode/issues/22
>> https://github.com/joostkremers/writeroom-mode/issues/24
>
> Nice!  Sorry I was unclear, I meant I'll package the official version
> and send patches or pull requests to upstream.

Excellent. :)

>> > I find it really useful to remove the fringes and margins when going
>> > from fullscreen to windowed, and to have modeline enabled for
>> > fullscreen, for battery status, clock, word count, etc, but to have
>> > these disabled for windowed.
>> 
>> That seems completely counter-intuitive to me, but I guess if those are
>> made into separate modes, that should be fine. :)
>
> :-) Exactly.  My setup is a bit bizarre, but it basically evolved to
> cope with the transition from a 17" 4:3 screen to a 10" 16:9 netbook,
> and to get positive feedback from the word count and pressure from the
> clock while typing way too forcefully while trying to meet deadlines.
> It would be even more intense with a countdown timer...  The premise
> being that you sit down to write, start writeroom, and the combo of
> the carrot and stick helps with productivity: an interval of working
> fast, then a relaxing and/or thinking/planning interval.

Is this similar to the pomodoro technique?

What do you use for the word count, by the way? I just M-x count-words
regularly, and since the message bar still shows, that just works...

>> > One of my other little personal projects is to change the font size
>> > when going between windowed and fullscreen.
>> 
>> That seems like a good idea - a separate effect too?
>
> I haven't actually done the work for it yet, but I've been wanting to
> implement it "someday" for years.  I think the easiest thing to do,
> for the purposes of writeroom, would probably be to configure a
> scaling factor for 'text-scale-adjust as part of the fullscreen hook.

I would make it a completely separate effect - but that's just me. I
encourage you to file an issue upstream, maybe the author already has
something in mind for this or even do the work for you. ;)

[...]

>> Anwyays, this is all stuff that should be discussed in the upstream
>> trackers, and not necessarily here. I think we should try to follow
>> upstream as closely as possible here and get patches merged back
>> upstream.
>
> Merged back, for sure.  Is the "discuss it on the BTS first" policy
> for more users->BTS->maintainers->upstream?

I'm not sure what you mean... In general, Debian welcomes upstream bugs
in the Debian bugtrackers because we want to support our users. Then
Debian package maintainers can sort through issues and forward some
upstream, sometimes fixing it with a patch in the Debian package...

But in general, I believe there is a consensus that we try to follow
upstream as much as possible.

>> So I encourage you to submit pull requests and issues for the things you
>> feel need to change in writeroom. So far, I have managed to use it
>> without patching it, and that is why I would like it to be packaged as
>> is in Debian.
>
> Preliminary packaging is here:
> ssh://git.debian.org/git/pkg-emacsen/pkg/writeroom-mode.git

Awesome! If you are not yet a Debian member, I encourage you to upload
a build to mentors.debian.net so that you can get better peer reviews as
well.

> I need to email to team to find out what the preferred way of managing
> things in the VCS during a deep freeze (eg: push tags only, push an
> experimental branch and keep master's changelog UNRELEASED, etc).

The freeze shouldn't matter in this case: it's a new package, so it
won't migrate to testing and there's no package in testing to update so
it's okay to upload to unstable. It's only when there's a version in
testing that you should avoid uploading to unstable unless it's to fix
RC bugs, and upload to experimental otherwise.

I use the UNRELEASED suite in the changelog when I upload signed
packages for public testing so that they don't get uploaded without my
explicit consent. Otherwise I generally don't use that feature, but
that's just me.

The emacsen team may indeed has its own peculiar ways of doing things
and it's good practice to join forces with them.

> Also, I'm not sure what to license debian/* as wrt BSD-3-clause.

I'm not sure what you mean. You need to specify the license of the
various writeroom-mode files in debian/copyright. Then you chose the
copyright you prefer for files in debian/* - I usually choose the same
license as the upstream files, but that's not absolutely mandatory. It
should be compatible, of course.

[...]

> Nice to see you too :-D  I'm highly motivated when people I know ask
> for something, and it's also (finally) something I'm familiar with.
> There's a part of me that feels "Aha!  I found my niche, my project to
> prove I can be a DD...my selfish glory!" but that's overshadowed by
> "It's way more fun and more meaningful to work as a team".

Hehe... well, we all started by scratching an itch. :)

> I'm thinking of something like an article and some streamlined
> configurations for "Emacs for professional, technical, and creative
> writing for everyone who didn't learn to use it as an IDE", plus
> packaging all the bits that help boost focused productivity.  Maybe
> mentioning ErgoEmacs...  Alternatively, it wouldn't be that hard to
> make hitting the word-count target play a nice sound or do something
> funny with nyan-mode :p

Fun stuff. :)

Good luck and thanks for packaging writeroom-mode!

A.
-- 
My passionate sense of social justice and social responsibility has
always contrasted oddly with my pronounced lack of need for direct
contact with other human beings and communities. I am truly a "lone
traveler" and have never belonged to my country, my home, my friends,
or even my immediate family, with my whole heart; in the face of all
these ties, I have never lost a sense of distance and a need for
solitude.
                       - Albert Einstein

Message #41 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Nicholas Steeves <nsteeves@gmail.com>

To: Antoine Beaupré <anarcat@debian.org>

Cc: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Wed, 26 Apr 2017 21:14:43 -0400

control: tags -1 -pending

On Tue, Apr 25, 2017 at 01:35:23PM -0400, Antoine Beaupré wrote:
> On 2017-04-25 11:05:57, Nicholas D Steeves wrote:
> > control: pending -1
>  
> Just for the record - we usually mark bugs as "tags -1 +pending" when an
> upload is ready in VCS or just uploaded to ftp-master. Not sure the
> above does anything. :)

Haha, yes, I received the failure notice and manually send an email to
control@d.  Now I see I need to remove the pending tag because I ran
into what I believe is an upstream issue with the info page (bug filed
upstream)

> > On Tue, Apr 25, 2017 at 08:04:56AM -0400, Antoine Beaupré wrote:
> >> On 2017-04-24 20:37:20, Nicholas D Steeves wrote:
>  
> >> > I find it really useful to remove the fringes and margins when going
> >> > from fullscreen to windowed, and to have modeline enabled for
> >> > fullscreen, for battery status, clock, word count, etc, but to have
> >> > these disabled for windowed.
> >>  
> >> That seems completely counter-intuitive to me, but I guess if those are
> >> made into separate modes, that should be fine. :)
> >
> > :-) Exactly.  My setup is a bit bizarre, but it basically evolved to
> > cope with the transition from a 17" 4:3 screen to a 10" 16:9 netbook,
> > and to get positive feedback from the word count and pressure from the
> > clock while typing way too forcefully while trying to meet deadlines.
> > It would be even more intense with a countdown timer...  The premise
> > being that you sit down to write, start writeroom, and the combo of
> > the carrot and stick helps with productivity: an interval of working
> > fast, then a relaxing and/or thinking/planning interval.
>  
> Is this similar to the pomodoro technique?

I had to look up pomodoro technique!  Yes, I believe it's similar,
especially.  From what I read, the original idea behind pomodoro is
different because it insists on the physicality of the timer, winding
the timer, a non-virtual alarm, checking off the intervals on the
piece of paper, etc.  I think the main difference is pomodoro rewards
compliance to structured time with breaks, where what I'm thinking
about is more like like gamification or a series of goals.  eg: write
X words in Y time, or more abstractly, maintain a rate of Z
words-per-hour by dividing X words by Y time-since-buffer-was-opened.

Everyone works differently but most of the people I know (including
myself) will finish a paper in less time, and to higher quality if the
composition stage is more sprint->break, stretch, do something active,
think about what to do next->loop until word count is met, and then
move on to editing.  To me, pomodoro would feel like working in one of
those offices from 1984 or the movie Brazil (1985).

> What do you use for the word count, by the way? I just M-x count-words
> regularly, and since the message bar still shows, that just works...

Traditionally I used wc.el bound to C-c C-c...pretty much the same as
you.  Wc in the modeline is now an option, and elpa-wc-mode in sid.
I'm planning to switch to smart-mode-line soon because it can justify
left, centre, or right, so I can finally retire custom modeline.
Elpa-wc-mode + smart-mode-line is a better way to put wc in the lower
right corner of a widescreen monitor where it is visually separate
from the narrow column of text, in dark grey on black where it is
unobtrusive.

If the motion of seeing it update is distracting I'm sure it would be
possible to configure wc-mode to update every N seconds

> >> > One of my other little personal projects is to change the font size
> >> > when going between windowed and fullscreen.
> >>  
> >> That seems like a good idea - a separate effect too?
> >
> > I haven't actually done the work for it yet, but I've been wanting to
> > implement it "someday" for years.  I think the easiest thing to do,
> > for the purposes of writeroom, would probably be to configure a
> > scaling factor for 'text-scale-adjust as part of the fullscreen hook.
>  
> I would make it a completely separate effect - but that's just me. I
> encourage you to file an issue upstream, maybe the author already has
> something in mind for this or even do the work for you. ;)

You can already scale the fonts with C-x C-+ and C-x C-- ;-) I just
want it to be modal.  Smaller fonts/larger viewport is better for
overview and editing, but a large font/small viewport helps keep ideas
compact when writing quickly--my preferred default.  What do you mean
by separate effect?  I think of it as large font for writing long
lines in text mode, and a smaller font with auto-indent enabled when
using a programming mode.

> >> Anwyays, this is all stuff that should be discussed in the upstream
> >> trackers, and not necessarily here. I think we should try to follow
> >> upstream as closely as possible here and get patches merged back
> >> upstream.
> >
> > Merged back, for sure.  Is the "discuss it on the BTS first" policy
> > for more users->BTS->maintainers->upstream?
>  
> I'm not sure what you mean... In general, Debian welcomes upstream bugs
> in the Debian bugtrackers because we want to support our users. Then
> Debian package maintainers can sort through issues and forward some
> upstream, sometimes fixing it with a patch in the Debian package...
>  
> But in general, I believe there is a consensus that we try to follow
> upstream as much as possible.

From what I can gather it's fairly open; however, for maintainers, I still
wonder where the bulk of discussions should happen.  And yes, total
agreement on how it's better to maintain a good relationships with
upstreams!

> > Preliminary packaging is here:
> > ssh://git.debian.org/git/pkg-emacsen/pkg/writeroom-mode.git
>  
> Awesome! If you are not yet a Debian member, I encourage you to upload
> a build to mentors.debian.net so that you can get better peer reviews as
> well.

I'm still a DM, so will need a sponsor for the initial upload, but
I'm holding off while I wait for upstream to respond.  If appropriate,
would you please take care of the forwarded tag?  Upstream url for the
issue can be found here:
https://github.com/joostkremers/writeroom-mode/issues/39

> > I need to email to team to find out what the preferred way of managing
> > things in the VCS during a deep freeze (eg: push tags only, push an
> > experimental branch and keep master's changelog UNRELEASED, etc).
>  
> The freeze shouldn't matter in this case: it's a new package, so it
> won't migrate to testing and there's no package in testing to update so
> it's okay to upload to unstable. It's only when there's a version in
> testing that you should avoid uploading to unstable unless it's to fix
> RC bugs, and upload to experimental otherwise.

Thank you for taking the time to explain this :-)

> I use the UNRELEASED suite in the changelog when I upload signed
> packages for public testing so that they don't get uploaded without my
> explicit consent. Otherwise I generally don't use that feature, but
> that's just me.
>  
> The emacsen team may indeed has its own peculiar ways of doing things
> and it's good practice to join forces with them.

+1 I got the ok from them to upload to unstable (when the package is
ready)  If you're curious about the info page issue the package is
available here:

https://mentors.debian.net/package/writeroom-mode
dget -x https://mentors.debian.net/debian/pool/main/w/writeroom-mode/writeroom-mode_3.6.1-1.dsc

> > Also, I'm not sure what to license debian/* as wrt BSD-3-clause.
>  
> I'm not sure what you mean. You need to specify the license of the
> various writeroom-mode files in debian/copyright. Then you chose the
> copyright you prefer for files in debian/* - I usually choose the same
> license as the upstream files, but that's not absolutely mandatory. It
> should be compatible, of course.

Might as well continue to stick with BSD-3-clause then.

Kind regards,
Nicholas

Message #48 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Nicholas Steeves <nsteeves@gmail.com>

Cc: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Wed, 26 Apr 2017 21:30:35 -0400

I won't have time to followup on this either sorry!

A.

-- 
Soyons réalistes, faisons l'impossible.
                        - Ernesto "Che" Guevara

Message #55 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Nicholas D Steeves <nsteeves@gmail.com>

To: Antoine Beaupré <anarcat@debian.org>

Cc: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Thu, 11 May 2017 11:04:21 -0400

[Message part 1 (text/plain, inline)]

Hi Antoine,

Elpa-writeroom-mode is ready to upload whenever you have the time.

It's available here:
    https://mentors.debian.net/package/writeroom-mode

Alternatively, one can download the package with dget using this command:

    dget -x https://mentors.debian.net/debian/pool/main/w/writeroom-mode/writeroom-mode_3.6.1-1.dsc

And here:

    ssh://git.debian.org/git/pkg-emacsen/pkg/writeroom-mode.git

Kind regards,
Nicholas

[signature.asc (application/pgp-signature, inline)]

Message #60 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Nicholas D Steeves <nsteeves@gmail.com>

To: Antoine Beaupré <anarcat@debian.org>

Cc: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Wed, 17 May 2017 10:57:00 -0400

[Message part 1 (text/plain, inline)]

Control: block -1 by 861772

Please do not upload this package yet.  I'm blocking this RFP with an
RFS I filed, and have tagged it moreinfo while I investigate the
severity of a possible trademark infringement issue.  I expect that to
be solved quickly, hopefully before you get back.

--N

[signature.asc (application/pgp-signature, inline)]

Message #67 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Nicholas D Steeves <nsteeves@gmail.com>

Cc: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Thu, 08 Jun 2017 17:23:02 -0400

On 2017-05-17 10:57:00, Nicholas D Steeves wrote:
> Control: block -1 by 861772
>
> Please do not upload this package yet.  I'm blocking this RFP with an
> RFS I filed, and have tagged it moreinfo while I investigate the
> severity of a possible trademark infringement issue.  I expect that to
> be solved quickly, hopefully before you get back.

Any news here?

-- 
fortune-to-signature. this means i have a bug in my emacs config. classic.

Message #72 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Nicholas D Steeves <nsteeves@gmail.com>

To: Antoine Beaupré <anarcat@debian.org>

Cc: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Thu, 8 Jun 2017 20:30:45 -0400

[Message part 1 (text/plain, inline)]

On Thu, Jun 08, 2017 at 05:23:02PM -0400, Antoine Beaupré wrote:
> On 2017-05-17 10:57:00, Nicholas D Steeves wrote:
> > Control: block -1 by 861772
> >
> > Please do not upload this package yet.  I'm blocking this RFP with an
> > RFS I filed, and have tagged it moreinfo while I investigate the
> > severity of a possible trademark infringement issue.  I expect that to
> > be solved quickly, hopefully before you get back.
> 
> Any news here?

My end of May and beginning of June were unexpectedly busy/fun, and I
was slow to get the process going.  At present I'm waiting to replies
to these inquiries.  On the upside, ivy-mode/swiper is progressing
nicely, which means find-file-in-project is also almost ready.

Other news: Sean is packaging a pomodoro mode-line timer, and
smart-mode-line is just about ready to upload--it provides easy
justify right support and "centre this thing in my modeline" support.
After everything has been uploaded I'll check to see if pomodoro has a
hook that can be used to make writeroom-mode show the modeline during
breaks, and then hide it again when resuming work.

Cheers,
Nicholas

[signature.asc (application/pgp-signature, inline)]

Message #77 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Nicholas D Steeves <nsteeves@gmail.com>

To: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Thu, 26 Oct 2017 14:57:36 -0400

[Message part 1 (text/plain, inline)]

On Thu, Jun 08, 2017 at 05:23:02PM -0400, Antoine Beaupré wrote:
> On 2017-05-17 10:57:00, Nicholas D Steeves wrote:
> > Control: block -1 by 861772
> >
> > Please do not upload this package yet.  I'm blocking this RFP with an
> > RFS I filed, and have tagged it moreinfo while I investigate the
> > severity of a possible trademark infringement issue.  I expect that to
> > be solved quickly, hopefully before you get back.
> 
> Any news here?

...still waiting for upstream.  I've packaged olivetti-mode in the
meantime, and have CCed you for the RFS bug.  The ITP bug is #879877
FIY.

Cheers,
Nicholas

[signature.asc (application/pgp-signature, inline)]

Message #87 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Nicholas D Steeves <nsteeves@gmail.com>

Cc: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Mon, 17 Sep 2018 15:17:05 -0400

On 2017-06-08 20:30:45, Nicholas D Steeves wrote:
> On Thu, Jun 08, 2017 at 05:23:02PM -0400, Antoine Beaupré wrote:
>> On 2017-05-17 10:57:00, Nicholas D Steeves wrote:
>> > Control: block -1 by 861772
>> >
>> > Please do not upload this package yet.  I'm blocking this RFP with an
>> > RFS I filed, and have tagged it moreinfo while I investigate the
>> > severity of a possible trademark infringement issue.  I expect that to
>> > be solved quickly, hopefully before you get back.
>> 
>> Any news here?
>
> My end of May and beginning of June were unexpectedly busy/fun, and I
> was slow to get the process going.  At present I'm waiting to replies
> to these inquiries.

On 2017-09-28 09:45:00, Nicholas D Steeves wrote:
> Yes, I asked a fairly generic question somewhere on OFTC, then
> privately contacted upstream, and got in contact with debian-legal
> with upstream's consent.  IIRC they recommended upstream rename as the
> easiest course of action (I forget if that was public or private), and
> provided an alternative that requires a bit of work (and less
> certainty).  What's at stake?  As I understand it, potential
> (American) lawyer fees, and/or headaches of needing to pull things
> offline in a hurry.
>
> Upstream recently send me an email, and is busy with IRL stuff.  I
> remain optimistic this will be resolved this fall.

Hi!

Pinging again here... Did you get any news from upstream?

You mentioned a discussion with debian-legal... I looked (briefly) in
the archives and didn't find a trace of this in the mailing list. Can we
get a better idea of what the legal issue is in general? You mention
trademark infringement, which trademark?

What's our next step here?

Or did you switch to olivetti mode? :)

A.
-- 
Either you're with us or you're with the terrorist state.

Message #92 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Nicholas D Steeves <nsteeves@gmail.com>

To: Antoine Beaupré <anarcat@debian.org>

Cc: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Mon, 17 Sep 2018 20:08:36 -0400

[Message part 1 (text/plain, inline)]

Control: forwarded -1 https://github.com/joostkremers/writeroom-mode/issues/45

Hi Antoine!

On Mon, Sep 17, 2018 at 03:17:05PM -0400, Antoine Beaupré wrote:
> 
> Hi!
> 
> Pinging again here... Did you get any news from upstream?
> 
> You mentioned a discussion with debian-legal... I looked (briefly) in
> the archives and didn't find a trace of this in the mailing list. Can we
> get a better idea of what the legal issue is in general? You mention
> trademark infringement, which trademark?
> 
> What's our next step here?
> 
> Or did you switch to olivetti mode? :)

I haven't yet heard back from upstream via PM, so I opened an issue
added a forwarded URL.  Hopefully the issue is sufficiently vague so
as not to be bothersome.

I check my archives and found that we quickly transitioned to using
CCed PM list of recipients.  The rationale being that websearching the
open mailing lists and bts could potentially provide a target for lazy
litigators (of two American companies).  How about this: if we don't
hear for upstream by the end of the month let's meet in person and
I'll summarise the issue.  Since those emails were PMs I don't think
it would be appropriate to forward them, even privately.

Cheers,
Nicholas

[signature.asc (application/pgp-signature, inline)]

Message #99 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Nicholas D Steeves <nsteeves@gmail.com>

Cc: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Mon, 17 Sep 2018 21:43:12 -0400

On 2018-09-17 20:08:36, Nicholas D Steeves wrote:
> I haven't yet heard back from upstream via PM, so I opened an issue
> added a forwarded URL.  Hopefully the issue is sufficiently vague so
> as not to be bothersome.
>
> I check my archives and found that we quickly transitioned to using
> CCed PM list of recipients.  The rationale being that websearching the
> open mailing lists and bts could potentially provide a target for lazy
> litigators (of two American companies).  How about this: if we don't
> hear for upstream by the end of the month let's meet in person and
> I'll summarise the issue.  Since those emails were PMs I don't think
> it would be appropriate to forward them, even privately.

Makes sense, thanks for the update.

A.
-- 
When I came back to the United States, I decided that if you could use
propaganda for war, you could certainly use it for peace. And
"propaganda" got to be a bad word because of the Germans using it, so
what I did was to try and find some other words so we found the words
"public relations".      - Edward Bernays

Message #104 received at 861124@bugs.debian.org (full text, mbox, reply):

From: Nicholas D Steeves <nsteeves@gmail.com>

To: 861124@bugs.debian.org

Subject: Re: Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs

Date: Wed, 04 Mar 2020 16:19:39 -0700

[Message part 1 (text/plain, inline)]

Control: retitle -1 RFP: elpa-writeroom-mode -- distraction-free writing for Emacs
Control: noowner -1 

Upstream is not longer considering a rename, so I am no longer
interested in uploading my work, because I do not want to be responsible
for dealing with potential correspondences with a litigious corporation
who distributes similarly named software in their app store.

Regards,
Nicholas

[signature.asc (application/pgp-signature, inline)]

Message #115 received at 861124-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 861124-close@bugs.debian.org

Subject: Bug#861124: fixed in writeroom-mode 3.11-1

Date: Wed, 03 Aug 2022 18:00:25 +0000

Source: writeroom-mode
Source-Version: 3.11-1
Done: Martin <debacle@debian.org>

We believe that the bug you reported is fixed in the latest version of
writeroom-mode, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 861124@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin <debacle@debian.org> (supplier of updated writeroom-mode package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 20 Jul 2022 10:03:08 +0000
Source: writeroom-mode
Binary: elpa-writeroom-mode
Architecture: source all
Version: 3.11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team <debian-emacsen@lists.debian.org>
Changed-By: Martin <debacle@debian.org>
Description:
 elpa-writeroom-mode - distraction-free writing for Emacs
Closes: 861124
Changes:
 writeroom-mode (3.11-1) unstable; urgency=medium
 .
   * Initial package (Closes: #861124)
Checksums-Sha1:
 91c14442bd9a04f96cbb961d23ed73eab1e4e51e 2010 writeroom-mode_3.11-1.dsc
 6fe76fd4eae1521197dff4593c66b8c88fc74047 190771 writeroom-mode_3.11.orig.tar.gz
 a010d05114152fa3a878e8f770415e5714d079ae 1884 writeroom-mode_3.11-1.debian.tar.xz
 af33efe1c0734c714f39e43b718a762dc9fc8875 14760 elpa-writeroom-mode_3.11-1_all.deb
 8eb1cf6d1b5755ab70cca532262b7edbd382376e 8100 writeroom-mode_3.11-1_amd64.buildinfo
Checksums-Sha256:
 f40c15c6a50a1cf536dd9b5423a36b68edef0a10c07663c1a28c7862b09fd8b3 2010 writeroom-mode_3.11-1.dsc
 28f1bdf839ce820e2f8a5f075d01f116032713ac6bee72cb3b5c0182d4d9898c 190771 writeroom-mode_3.11.orig.tar.gz
 4e13d63231374432e0d549351c8846ebef827d7e1da3301d5724ce10c9547e9f 1884 writeroom-mode_3.11-1.debian.tar.xz
 b7d86bf5fde5ab547403632fb1696c9207941add5e737b092af2949f75f7da31 14760 elpa-writeroom-mode_3.11-1_all.deb
 35179acb86470addb1d70a3336fe6b2d34830aef05579c14b879aeb83a6b8d66 8100 writeroom-mode_3.11-1_amd64.buildinfo
Files:
 8b9217573b72f4b82ee271562b56a7c9 2010 editors optional writeroom-mode_3.11-1.dsc
 36252380aab2a4a9bc999ae09d497c53 190771 editors optional writeroom-mode_3.11.orig.tar.gz
 4c3d56337852444981a1fe6c25a855ca 1884 editors optional writeroom-mode_3.11-1.debian.tar.xz
 4da1af57dabd0e499cf91ca2a1464bf5 14760 editors optional elpa-writeroom-mode_3.11-1_all.deb
 43628797f200f0406d1c0056f30e5584 8100 editors optional writeroom-mode_3.11-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAmLX3L0ACgkQ4+Chwoa5
Y+p0tBAAghYLQsxX92flFhmsh5pXdqbla05hysKnMlz4izHU2r2Rm9oBLKNDoG2G
HVYNYuJPBSq7SUiTVQ5vv3MMsFN0mfYy6JMeValXOeDyXaBk44wUpq86T8ATRiMs
lbHe+WoIOCVT+NxhoJCblb9MS+wD0YOjCwHGeyphkJpjsPhU+FnHcuPBcY3TlgLp
WEONzBXTzbhOp0Yo24bGzZO4R3aUYGLlbv09qfvA4SwtqvgneMrn/seoMrkcodUz
7fb8Xmxl/ameUsBkd3LEgbZTLNLusiwjSRpvFvpeXoeWR7uTQcm/UbLEsiKWBBLr
B9X5X0JgfuzFMBgHJLq7czmKkeoJuSZ23jdY0G68bLEnrm5pgXxUpufGn7LG/DeM
qZKbmjmneemmojr83zQnDIlQqyqSuQyS+gxhhN6Gwp8m4YPEAgHxKLaR5jinkkfR
rMDHWF8du2gZtqOrPJwqy3243HhKtmO2X+jSmHECawvs2hDCBQDE7UNljLMmsJQW
G488lUt4QPj9eIshgk59iEGtS3OssgC0qbC1DudgkXr4AYmZdfUtu/k5ezIoKrF4
AmxzLh2g3E4VXlMuhFBpwHVeWgCxx8hFEByB3Hf8G7pebLISfUP1KldiasS5XxGi
Fqxm4ONEJgEtIPB9Lz/X5uG/MbR/Nb2tM8M5XL1g3KRSXGWuqw0=
=52c9
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.