Re: [dev] Some suckless hackathon 2017 preparation

2017-09-02 Thread Anselm R Garbe
Hi Michael, On 1 September 2017 at 19:55, Michael Forney wrote: > I hope the wayland-related work at the hackathon won't just be > duplicates of my efforts. We will make sure to avoid duplicate efforts. BR, Anselm

Re: [dev] Some suckless hackathon 2017 preparation

2017-09-01 Thread Michael Forney
On 2017-09-01, Silvan Jegen wrote: > On Fri, Sep 01, 2017 at 08:40:34AM -0400, Carlos Torres wrote: >> > On Aug 30, 2017, at 2:07 PM, Silvan Jegen wrote: >> > >> > * Wayland dwm prototype? >> > * Suckless Wayland client library prototype? >> >> I think Michael Forney has already addressed these i

Re: [dev] Some suckless hackathon 2017 preparation

2017-09-01 Thread Lee Fallat
I don't know if it's possible, but a suckless issue tracker would be a god-send. On Fri, Sep 1, 2017 at 12:06 PM, Silvan Jegen wrote: > On Fri, Sep 01, 2017 at 08:40:34AM -0400, Carlos Torres wrote: >> > On Aug 30, 2017, at 2:07 PM, Silvan Jegen wrote: >> > >> > * Wayland dwm prototype? >> > *

Re: [dev] Some suckless hackathon 2017 preparation

2017-09-01 Thread Silvan Jegen
On Fri, Sep 01, 2017 at 08:40:34AM -0400, Carlos Torres wrote: > > On Aug 30, 2017, at 2:07 PM, Silvan Jegen wrote: > > > > * Wayland dwm prototype? > > * Suckless Wayland client library prototype? > > I think Michael Forney has already addressed these issues. Yes, I am aware of those. I assu

Re: [dev] Some suckless hackathon 2017 preparation

2017-09-01 Thread Carlos Torres
Hello, > On Aug 30, 2017, at 2:07 PM, Silvan Jegen wrote: > > * Wayland dwm prototype? > * Suckless Wayland client library prototype? I think Michael Forney has already addressed these issues. And many others. —Carlos

Re: [dev] Some suckless hackathon 2017 preparation

2017-07-26 Thread Silvan Jegen
On Wed, Jul 26, 2017 at 12:05:01PM -0500, Joshua Haase wrote: > Anselm R Garbe writes: > > > IMHO this view is short sighted. The point of an _issue_ tracker (not > > every issue is a bug) is not the possibility to flood the developer > > with random bug reports, but to provide a simple infrastru

Re: [dev] Some suckless hackathon 2017 preparation

2017-07-26 Thread Joshua Haase
Anselm R Garbe writes: > IMHO this view is short sighted. The point of an _issue_ tracker (not > every issue is a bug) is not the possibility to flood the developer > with random bug reports, but to provide a simple infrastructure to > organize and priotize a TODO list for the development of a ce

Re: [dev] Some suckless hackathon 2017 preparation

2017-07-26 Thread Anselm R Garbe
On 25 July 2017 at 11:59, Laslo Hunhold wrote: > On Mon, 24 Jul 2017 22:13:36 -0500 > Joshua Haase wrote: >> I do think a good issue tracker is needed and would be willing to >> contribute on september 2-3 (although maybe in a different time zone: >> [UTC-6]). >> >> As for useless bug reports, a

Re: [dev] Some suckless hackathon 2017 preparation

2017-07-25 Thread Laslo Hunhold
On Tue, 25 Jul 2017 11:59:59 +0200 Laslo Hunhold wrote: > [...] In my opinion, a bug report on how "Uselessfont stops working > under dwm" is helpful, [...] correction: is _not_ helpful -- Laslo Hunhold

Re: [dev] Some suckless hackathon 2017 preparation

2017-07-25 Thread Laslo Hunhold
On Mon, 24 Jul 2017 22:13:36 -0500 Joshua Haase wrote: Hey Joshua, > I do think a good issue tracker is needed and would be willing to > contribute on september 2-3 (although maybe in a different time zone: > [UTC-6]). > > As for useless bug reports, a good cure would be to give access only > t

Re: [dev] Some suckless hackathon 2017 preparation

2017-07-24 Thread Joshua Haase
Hiltjo Posthuma writes: >> > iii) focus on totally new stuff like the issue tracking, Silvans >> > patchwork idea or mail archiver > > I don't think we should use an issue tracker. I can see there will be > endless useless bug reports with fontconfig issues already. Instead > user expectations s

Re: [dev] Some suckless hackathon 2017 preparation

2017-07-24 Thread Hiltjo Posthuma
On Sun, Jul 23, 2017 at 03:57:42PM +0200, Laslo Hunhold wrote: > On Sun, 23 Jul 2017 15:30:05 +0200 > Anselm R Garbe wrote: > > Hey Anselm, > > > Second, one goal of the slackathon is also to streamline the project > > landscape of suckless.org, which also means we should presumably > > define 3

Re: [dev] Some suckless hackathon 2017 preparation

2017-07-23 Thread Silvan Jegen
Hi Anselm On Sun, Jul 23, 2017 at 03:30:05PM +0200, Anselm R Garbe wrote: > Second, one goal of the slackathon is also to streamline the project > landscape of suckless.org, which also means we should presumably > define 3-4 clusters that will be addressed during the event and > identify all areas

Re: [dev] Some suckless hackathon 2017 preparation

2017-07-23 Thread Laslo Hunhold
On Sun, 23 Jul 2017 15:30:05 +0200 Anselm R Garbe wrote: Hey Anselm, > Second, one goal of the slackathon is also to streamline the project > landscape of suckless.org, which also means we should presumably > define 3-4 clusters that will be addressed during the event and > identify all areas th

Re: [dev] Some suckless hackathon 2017 preparation

2017-07-23 Thread Anselm R Garbe
Hi there, thanks for your suggestion to prepare the content we could work on during slackathon 2017. Let me chime in with some thoughts: First of all -- for all of you who can't attend slackathon in person, but still would like to support the outcome somehow, I encourage you to adjust your sched

[dev] Some suckless hackathon 2017 preparation

2017-07-23 Thread Silvan Jegen
Heyho! I thought we could try to organize people into interest groups around suckless projects and think of goals within them to reach for the suckless hackathon 2017. That way we can save some organisation time at the hackathon itself since then people should already know what start with and they