Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
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 Description: PGP signature
Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
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
Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
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 Description: PGP signature
Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
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.
Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
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 Description: PGP signature
Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
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 Description: Digital signature
Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
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.
Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
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 Description: Digital signature
Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
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 Description: Digital signature
Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
I won't have time to followup on this either sorry! A. -- Soyons réalistes, faisons l'impossible. - Ernesto "Che" Guevara
Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
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
Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
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
Bug#861124: ITP: elpa-writeroom-mode -- distraction-free writing for Emacs
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
