Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

Quoting James Clarke (2017-05-22 16:25:38) > But I notice that for the sbuild path, schroot is completely missing, Maybe I should also point out that schroot is just the *default* sbuild chroot backend. It also supports the "sudo" mode (which essentially just uses "sudo chroot") and the

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

Ian Jackson writes: > Use [dgit] to publish your git history, by doing your uploads with > dgit push. > > The root goal is this: Debian should publish the source for all our > packages, as git branches, in a format that is directly useable by > ordinary people.

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On 22.05.2017 16:25, James Clarke wrote: > You say that, but this is incredibly biased. Even he admits that in the > colour choice. Disclaimer: as the cowbuilder maintainer (which comes > from the cow*dancer* source package, for historical reasons, despite > what the diagram may tell you) I am of

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

Ben Finney writes ("Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)"): > Ian Jackson <ijack...@chiark.greenend.org.uk> writes: > > I want every maintainer who is using git to be able to use dgit. > > Use it

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Tue, May 23, 2017 at 06:34:09PM +0100, Sean Whitton wrote: > On Tue, May 23, 2017 at 06:38:29PM +0200, Emilio Pozuelo Monfort wrote: > > I have to deal with packages in svn, git-bp and plain git, and have started > > to > > write a set of (ugly) scripts that perform common actions in each of

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

Ian Jackson writes: > I want every maintainer who is using git to be able to use dgit. Use it to do what, though? The package description is currently: git interoperability with the Debian archive dgit (with the associated infrastructure) makes it

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Tue, May 23, 2017 at 06:38:29PM +0200, Emilio Pozuelo Monfort wrote: > I have to deal with packages in svn, git-bp and plain git, and have started to > write a set of (ugly) scripts that perform common actions in each of those > formats, and a generic wrapper that calls the right one depending

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Tue, May 23, 2017 at 10:21:27AM +0100, Jonathan Dowland wrote: > On Mon, May 22, 2017 at 10:07:20PM +0100, James Clarke wrote: > > There already effectively is a semi-"primary" implementation given that > > sbuild is used on the buildds. > > Yes that is a very strong fact in favour of sbuild.

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

Jonathan Dowland writes: > Fair enough, cowbuilder was one of the ones in my hazy peripheral vision > as "another", along with some tools to use things like docker that I am > aware of but couldn't remember the names. None of them have the same > traction as pbuilder or sbuild.

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

Emilio Pozuelo Monfort writes ("Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)"): > Besides, the sbuild/pbuilder duplicity is the least of your problems > in terms of multiple workflows, because once you choose one of those

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On 22/05/17 16:25, James Clarke wrote: > On Mon, May 22, 2017 at 03:06:48PM +0100, Jonathan Dowland wrote: >> On Mon, May 22, 2017 at 12:47:51PM +0100, Sean Whitton wrote: >>> Someone else already had this idea: >>> >>> https://people.debian.org/~stapelberg//2016/11/25/build-tools.html >> >>

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

Sean Whitton writes ("Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)"): > A way to set the version during the build, as you suggest, would be > sufficient to cover this. It is hard to see how we could relieve the &g

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

Sean Whitton writes ("Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)"): > On Mon, May 22, 2017 at 09:22:00PM +0100, Sean Whitton wrote: > > On Mon, May 22, 2017 at 01:42:54PM -0400, Jeremy Bicha wrote: > > > Of

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 10:07:20PM +0100, James Clarke wrote: > There already effectively is a semi-"primary" implementation given that > sbuild is used on the buildds. Yes that is a very strong fact in favour of sbuild. > And as for making these "secondary" implementations not geared for real >

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 09:22:00PM +0100, Sean Whitton wrote: > On Mon, May 22, 2017 at 01:42:54PM -0400, Jeremy Bicha wrote: > > Of course, dgit is yet another workflow and my understanding is that > > git-buildpackage (without dgit) is far more commonly used in Debian. > > This isn't fair to

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, 22 May 2017 22:20:29 +0200, Andreas Tille wrote: >On Mon, May 22, 2017 at 10:46:59PM +0500, Andrey Rahmatullin wrote: >> On Mon, May 22, 2017 at 09:07:52AM +, Holger Levsen wrote: >> > there's just a hundred Debian workflows to maintain a package and 200 >> > manuals

Re: Moving away from (unsupportable) FusionForge on Alioth?

Hi Andreas, On Thu, May 18, 2017 at 09:07:53AM +0200, Andreas Tille wrote: > > I think that in the mid-term (probably even in short term) you'll *save* > > developer time by switching to git, > And your thinking is based on what arguments? a.) git is a lot faster than svn on most operations,

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 05:10:26PM +0100, Jonathan Dowland wrote: > On Mon, May 22, 2017 at 03:25:38PM +0100, James Clarke wrote: > > On Mon, May 22, 2017 at 03:06:48PM +0100, Jonathan Dowland wrote: > > > Excellent, this is a great start, and seeing "Michael Stapelberg" for me > > > is an >

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 03:07:42PM +0100, Ian Jackson wrote: > Areas of work that could do with attention from people with relevant > expertise and effort: > > * Getting rid of the need to mess with the changelog. That might >involve changes to Debian changelog practice, or better tooling

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 01:42:54PM -0400, Jeremy Bicha wrote: > Of course, dgit is yet another workflow and my understanding is that > git-buildpackage (without dgit) is far more commonly used in Debian. This isn't fair to dgit. While it does impose some minimal requirements upon git trees, it

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 10:46:59PM +0500, Andrey Rahmatullin wrote: > On Mon, May 22, 2017 at 09:07:52AM +, Holger Levsen wrote: > > there's just a hundred Debian workflows to maintain a package and 200 > > manuals for that. > No, no, there are more workflows than manuals for them. For

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On 05/22/2017 07:42 PM, Jeremy Bicha wrote: > On Mon, May 22, 2017 at 10:07 AM, Ian Jackson > <ijack...@chiark.greenend.org.uk> wrote: >> Holger Levsen writes ("infinite number of Debian workflows (Re: Moving away >> from (unsupportable) FusionForge on Alioth?)&q

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 09:07:52AM +, Holger Levsen wrote: > there's just a hundred Debian workflows to maintain a package and 200 > manuals for that. No, no, there are more workflows than manuals for them. -- WBR, wRAR signature.asc Description: PGP signature

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 10:07 AM, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote: > Holger Levsen writes ("infinite number of Debian workflows (Re: Moving away > from (unsupportable) FusionForge on Alioth?)"): > I would encourage anyone who has effort to work on this

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 03:25:38PM +0100, James Clarke wrote: > On Mon, May 22, 2017 at 03:06:48PM +0100, Jonathan Dowland wrote: > > Excellent, this is a great start, and seeing "Michael Stapelberg" for me is > > an ^^^ > > indication of quality. emphasis on

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 03:06:48PM +0100, Jonathan Dowland wrote: > On Mon, May 22, 2017 at 12:47:51PM +0100, Sean Whitton wrote: > > Someone else already had this idea: > > > > https://people.debian.org/~stapelberg//2016/11/25/build-tools.html > > Excellent, this is a great start, and seeing

infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

Holger Levsen writes ("infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)"): > I can totally confirm this. When people ask me how to get foo fixed in Debian > and I start explaining the above, people role their eyes and poi

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 12:47:51PM +0100, Sean Whitton wrote: > Someone else already had this idea: > > https://people.debian.org/~stapelberg//2016/11/25/build-tools.html Excellent, this is a great start, and seeing "Michael Stapelberg" for me is an indication of quality. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 12:28:01PM +0200, Emilio Pozuelo Monfort wrote: > Do you mean cdbs rather than cmake? I'm struggling to make a connection > between > dh and cmake. Yes, I do; thanks for the correction. (although it does remind me that this issue of more-than-one-way-to-do-it extends up

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 10:29:24AM +0100, Jonathan Dowland wrote: > I often think about this problem, and I start to wonder if step 0 is to try > and > enumerate it properly. That is: I picture in my mind some kind of huge diagram > (perhaps generated from more structured data, I dunno, something

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On 22/05/17 11:29, Jonathan Dowland wrote: > I often think about this problem, and I start to wonder if step 0 is to try > and > enumerate it properly. That is: I picture in my mind some kind of huge diagram > (perhaps generated from more structured data, I dunno, something into a > graphviz) >

Re: infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

I often think about this problem, and I start to wonder if step 0 is to try and enumerate it properly. That is: I picture in my mind some kind of huge diagram (perhaps generated from more structured data, I dunno, something into a graphviz) of a landscape of debian developer tools, grouped by

infinite number of Debian workflows (Re: Moving away from (unsupportable) FusionForge on Alioth?)

On Mon, May 22, 2017 at 07:52:34AM +, Riku Voipio wrote: > Right now, if you have a minor change - such fixing Homepage: or typo on > definition, it's not as straitforward as submitting a pull request. And > it gets much worse if you want to patch against upstream or build a new > upstream

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Fri, May 19, 2017 at 01:56:17PM +0200, Andreas Tille wrote: > If (and only if) there would be some momentum for a move to Git neither > I nor any other member of the Debian Med team will block this. But for > the moment I keep on failing to see an advantage only out of the fact > that "it is

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On 05/21/2017 09:17 AM, Wouter Verhelst wrote: > On Mon, May 15, 2017 at 09:45:46PM +0200, Zlatan Todoric wrote: >> >> On 05/15/2017 02:02 PM, Lars Wirzenius wrote: >>> On Mon, May 15, 2017 at 01:42:09PM +0200, Arturo Borrero Gonzalez wrote: On 15 May 2017 at 13:30, Paul Wise

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On Mon, May 15, 2017 at 09:45:46PM +0200, Zlatan Todoric wrote: > > > On 05/15/2017 02:02 PM, Lars Wirzenius wrote: > > On Mon, May 15, 2017 at 01:42:09PM +0200, Arturo Borrero Gonzalez wrote: > >> On 15 May 2017 at 13:30, Paul Wise wrote: > >>> TBH if I was confronted with the

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Hello Paul, On Fri, May 19, 2017 at 01:25:06PM -0400, Paul Tagliamonte wrote: > I, frankly, don't even pretend to care what our developer community > thinks of the site -- the site isn't just for you. I agree that it would be great to have data from usability testing of our site. I disagree

Re: LXDE web page bashing thread Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

The website is on GitHub so anyone can suggest things by throwing me issues or PRs at https://github.com/lxde/lxde.org The hamburger menu requiring JavaScript is something that I don't have good alternative with right now. Also, welcome back, Martin :) Yao Wei On Fri, 19 May 2017 at 21:18

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

[loads of bikeshedding and grandstanding] So this thread is a shitshow. Has anyone thought about taking the website (or really, anything we put out), going and talking with **our users** and see what they have to say? What they think of the site? Record them finding and creating an install

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Hi there, please remember: it is not the design, that makes a website interesting, but the content! So maybe we should first discuss, and maybe confirm, what might people interest on the debian site. I suggest just to collect ideas, and make a ranking (i.e. freedom was named 1563 times,

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Thu, May 18, 2017 at 01:40:03PM +0200, Andreas Tille wrote: > In last GSoC the student was not comfortable with SVN. I have converted > lots of packages at request of the student. So I'm perfectly following > your reasoning if (and only if) there are potential packaging > contributors at

LXDE web page bashing thread Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2017-05-19 15:00, Zlatan Todoric wrote: > Well Debian on its page doesn't mention it is Linux based > or has Linux kernel or at all word Linux. We have Linux, HURD and the FreeBSD kernel, though. I suspect the thought was

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On 05/18/2017 12:32 PM, Sean Whitton wrote: > Hello Zlatan, > [...] > > The community consensus seems to be that we want to promote ourselves, > but we care more about providing quality information than do the people > who designed sites like lxde.org (sorry to keep using that example). > This

Re: Moving away from (unsupportable) FusionForge on Alioth?

Hi Guido, On Fri, May 19, 2017 at 01:35:58PM +0200, Guido Günther wrote: > > Keeping only debian/ in git is supported by gbp as well (see > --git-overlay). Thanks for the hint - I've seen this and I'm aware of it. > AFAIK It's not that commonly used so there might be bugs > lurking and

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Wed, May 17, 2017 at 10:19:24PM +0200, Andreas Tille wrote: > Hi, > > On Mon, May 15, 2017 at 02:43:56PM +0200, Johannes Schauer wrote: > > > > The top 10 teams with packages in SVN are: > > > > 347 Debian Med Packaging Team > > > > This

Re: Moving away from (unsupportable) FusionForge on Alioth?

在 2017年5月14日星期日 +08 下午2:33:19，Pirate Praveen 写道： > On ഞായര്‍ 14 മെയ് 2017 02:23 വൈകു, Boyuan Yang wrote: > > As a result, I'm writing to suggest we find an answer to such a problem > > soon. Migration to Jessie or Stretch with new FusionForge version might > > be possible. Or we should just drop

Re: Moving away from (unsupportable) FusionForge on Alioth?

Hi Mattia, On Wed, May 17, 2017 at 10:38:41PM +0200, Mattia Rizzolo wrote: > I wonder... > The problem here is about fusionforge only, in fact. > If we were to move git (i.e. the vast majority of its usage) to another > place, and took down fusionforge (i.e. no more guest user management), I > do

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

One local team of BSP Debian paris ask me to propose a new webiste. i did :) If it fit to any use you need, i'm happy, if not, i'm happy to help in fit it better :) Elisa 2017-05-18 16:54 GMT+02:00 Sean Whitton : > Hello Elisa, > > On Thu, May 18, 2017 at 03:14:49PM

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Hello Elisa, On Thu, May 18, 2017 at 03:14:49PM +0200, Elisa Godoy de Castro Guerra wrote: > To finish this website we need : > - the text to present stretch to news user to debian (who do ?) Are you suggesting this as a "Get Stretch" website, similar to ? This thread has been about replacing

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Thanks, To finish this website we need : - the text to present stretch to news user to debian (who do ?) - more ilustration to be more firendly and attractive (i can do) - official publication after official approval from community :) - a available deadline to help in organization ^^' 2017-05-18

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On Thu, May 18, 2017 at 02:37:33PM +0200, Elisa Godoy de Castro Guerra wrote: > I participate to the BSP debian meeting in paris last week end. > I propose a little webpage. > https://gitlab.com/yemanjalisa/debianstretchwebsite > > I would love finish this work to fit for your need. > I dit it

When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Hi, My name is elisa, Sorry for my english... I participate to the BSP debian meeting in paris last week end. I propose a little webpage. https://gitlab.com/yemanjalisa/debianstretchwebsite I would love finish this work to fit for your need. I dit it very quickly on last sunday in collaboration

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Thu, May 18, 2017 at 10:43:44AM +0100, Jonathan Dowland wrote: > > developer time simply to switch lots of packages from an old VCS to a > > modern one has zero effect on users desktops and has no high priority. > > Absolutely; the impact is on potential packaging contributors. In last GSoC

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Hello Zlatan, On Tue, May 16, 2017 at 02:58:14AM +0200, Zlatan Todoric wrote: > Improving things doesn't mean destroying identity. We add and remove > archs, we added graphical installer, we don't configure graphics > manually anymore - did we loose identity? Social Contract and DFSG > ensure our

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On Tue, May 16, 2017 at 11:13:38AM +0100, Wookey wrote: > I will observe that the debian wiki is a lot more up-to-date than the > website because it is much easier to update (much as I admire wml as > a tool/language). A relevant read is

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Thu, May 18, 2017 at 09:07:53AM +0200, Andreas Tille wrote: > > And probably we should all just use git. > > If we really could agree upon a common workflow I will definitely adapt. > But there is no such agreement as far as I can see. This is basically the problem. It's not that we have to

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Wed, May 17, 2017 at 10:38:41PM +0200, Mattia Rizzolo wrote: > I wonder... > The problem here is about fusionforge only, in fact. > If we were to move git (i.e. the vast majority of its usage) to another > place, and took down fusionforge (i.e. no more guest user management), I > do not think

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On Wed, May 17, 2017 at 11:49:26AM +0200, Steffen Möller wrote: > We should vividly demonstrate on our home page that we are just that - > alive and developing. If we could have users contribute success stories > like "I switched my Granny from Windows to Debian and she likes it" or > "We

Re: Moving away from (unsupportable) FusionForge on Alioth?

Andreas Tille writes: > I do not see a good reason to spent time into a migration from SVN to > Git. Isn't EOL of the hosting platform FusionForge a good reason? Cheers Ole

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Wed, May 17, 2017 at 11:12:53PM +, Holger Levsen wrote: > git clone https://src.fedoraproject.org/cgit/rpms/${srcpkg}.git is really > awesome and works for every package in Fedora! (*) I haven't looked at it much yet but I though Ian Jackson's dgit was a pretty neat solution to this

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Wed, May 17, 2017 at 10:19:24PM +0200, Andreas Tille wrote: > In short: There is no doubt that Git is the better VCS but spending > developer time simply to switch lots of packages from an old VCS to a > modern one has zero effect on users desktops and has no high priority. Absolutely; the

Re: Moving away from (unsupportable) FusionForge on Alioth?

Hi Holger, On Wed, May 17, 2017 at 11:12:53PM +, Holger Levsen wrote: > On Wed, May 17, 2017 at 10:19:24PM +0200, Andreas Tille wrote: > > In short: There is no doubt that Git is the better VCS but spending > > developer time simply to switch lots of packages from an old VCS to a > > modern

Re: Moving away from (unsupportable) FusionForge on Alioth?

Hi Tzafir, On Thu, May 18, 2017 at 06:04:09AM +0200, Tzafrir Cohen wrote: > > > The top 10 teams with packages in SVN are: > > > > > > 347 Debian Med Packaging Team > > > > > > > This number contains possibly 150 packages that *could* be

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

But responsive design does not only matters for mobile, it also matters on bigger screen, like high resolution or hi dpi screen, which is what Debian lack of. Like what I said the website is bizarre on a bigger screen. You can try reading the website with the window maximized on 1920x1080 screen.

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Wed, May 17, 2017 at 10:19:24PM +0200, Andreas Tille wrote: > In short: There is no doubt that Git is the better VCS but spending > developer time simply to switch lots of packages from an old VCS to a > modern one has zero effect on users desktops and has no high priority. I think that in

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Wed, May 17, 2017 at 10:19:24PM +0200, Andreas Tille wrote: > In short: There is no doubt that Git is the better VCS but spending > developer time simply to switch lots of packages from an old VCS to a > modern one has zero effect on users desktops and has no high priority. I wonder... The

Re: Moving away from (unsupportable) FusionForge on Alioth?

Hi, On Mon, May 15, 2017 at 02:43:56PM +0200, Johannes Schauer wrote: > > The top 10 teams with packages in SVN are: > > 347 Debian Med Packaging Team > This number contains possibly 150 packages that *could* be migrated - provided somebody

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Simon McVittie writes ("Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)"): > On Wed, 17 May 2017 at 13:33:06 +0100, Ian Jackson wrote: > > * Websites which reorganise themselves through CSS and/or JavS

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On Wed, 17 May 2017 at 13:33:06 +0100, Ian Jackson wrote: > * Websites which reorganise themselves through CSS and/or JavScript >to try to produce a better selection of visibloe bits depending on >the screen size. > >I find these mildly annoying, but I don't use a smartphone and >

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Steffen Möller writes ("Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)"): > And there is a confusion over "dynamic web sites" (maybe problematic) > with "non-static content" (must have).

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On 16/05/2017 07:07, Mechtilde wrote: > these two questions come into my mind: > > What does a "newcomer" expect from > such a website? > what do we expect from a newcomer? > > To go from user to dev is a gliding way. > > "Want To Become Debian Developer" is the last step for a dev not

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Arturo Borrero Gonzalez dijo [Mon, May 15, 2017 at 01:42:09PM +0200]: > Hi Paul, > > I believe that what we are actually looking for is a bit of > improvement in the marketing side. > Modern and fancy things. > > The LXDE example is good on that. Is a good example on how to craft content-void

Re: Moving away from (unsupportable) FusionForge on Alioth?

Hello Boyuan, On Tue, May 16, 2017 at 09:11:07PM +0800, Boyuan Yang wrote: > I've got some different ideas. While it makes sense that packaging-only > projects on the new VCS hosting system should not enable the issue tracking > system (people should use Debian BTS instead. Pull Requests should

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Tue, May 16, 2017 at 10:25:54AM +0800, Paul Wise wrote: > On Tue, May 16, 2017 at 12:39 AM, Antonio Terceiro wrote: > > > Right. IIRC that was said to me at Debconf16 about Debian-specific > > services (such as ci.debian.net which was the context of my question). > > Yeah, for codebases

Re: Moving away from (unsupportable) FusionForge on Alioth?

在 2017年5月16日星期二 +08 下午3:15:31，Mattia Rizzolo 写道： > On Tue, May 16, 2017 at 09:11:07PM +0800, Boyuan Yang wrote: > > For example, there are documentation projects like debian-reference and > > debian-handbook, native packages like dpkg, apt and reportbug. In that > > case, the issue tracking

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Tue, May 16, 2017 at 09:11:07PM +0800, Boyuan Yang wrote: > For example, there are documentation projects like debian-reference and > debian-handbook, native packages like dpkg, apt and reportbug. In that case, > the issue tracking *should* be enabled and used. Issue tracking here will act >

Re: Moving away from (unsupportable) FusionForge on Alioth?

在 2017年5月16日星期二 +08 下午2:51:16，Benjamin Drung 写道： > Am Dienstag, den 16.05.2017, 13:47 +0530 schrieb Pirate Praveen: > > On ചൊവ്വ 16 മെയ് 2017 05:20 രാവിലെ, Sean Whitton wrote: > > > Thank you for updating us, Alex. > > > > > > On Mon, May 15, 2017 at 09:13:11AM +0200, Alexander Wirt wrote: > > >

Re: Moving away from (unsupportable) FusionForge on Alioth?

Am Dienstag, den 16.05.2017, 13:47 +0530 schrieb Pirate Praveen: > On ചൊവ്വ 16 മെയ് 2017 05:20 രാവിലെ, Sean Whitton wrote: > > Thank you for updating us, Alex. > > > > On Mon, May 15, 2017 at 09:13:11AM +0200, Alexander Wirt wrote: > > > - Git Hosting - we want to give pagure [1] a try, which

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On 2017-05-15 13:42 +0200, Hans wrote: > Maybe other things, that people do not know yet, which show the power of > debian, should be mentioned (I think of biggest community, best documentation, 'Best documentation' is a strong claim that I don't think many would agree with :-) Debian is many

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On 05/16/2017 04:56 AM, lumin wrote: >> I'll take any day a sort animations that explains things rather then >> going through forest of information to figure out what is it, but I >> guess these all are personal opinions. > A tiny bit of animations should be enough for our homepage. The style >

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

2017-05-15 13:12 GMT+03:00 lumin : > Especially look at the homepage of Gentoo It's ugly, seriously.

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On Mon, 15 May 2017, Adrian Bunk wrote: > The contents of the Gentoo homepage is similar to what Debian has but > presented with a different CSS - something like that would be a good > improvement. I took a look at the Gentoo website and there's more than just better CSS. I find it much better

Re: Moving away from (unsupportable) FusionForge on Alioth?

On ചൊവ്വ 16 മെയ് 2017 05:20 രാവിലെ, Sean Whitton wrote: > Thank you for updating us, Alex. > > On Mon, May 15, 2017 at 09:13:11AM +0200, Alexander Wirt wrote: >> - Git Hosting - we want to give pagure [1] a try, which uses gitolite, which >> is a >> nice git solution. > > Ah, that's nice. >

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Le 16/05/2017 03:47, Nicholas D Steeves a écrit : On Tue, May 16, 2017 at 02:17:40AM +0200, Stéphane Aulery wrote: Yes, Debian is a community like another, and a community is build with shared principles. Design isn't principle, it is just a shameful exploitation of the idea of beauty, serving

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Mon, May 15, 2017 at 08:39:11AM +, Riku Voipio wrote: > OTOH it might just not be worth to convert all project histories into > git. Linus didn't do it for upstream kernel either. Convert the easy > cases automatically and leave the rest ones for maintainers as an > opportunity to do a

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Hello, Am 15.05.2017 um 21:45 schrieb Zlatan Todoric: > > > On 05/15/2017 02:02 PM, Lars Wirzenius wrote: >> On Mon, May 15, 2017 at 01:42:09PM +0200, Arturo Borrero Gonzalez wrote: >>> On 15 May 2017 at 13:30, Paul Wise wrote: TBH if I was confronted with the new LXDE

Re: Moving away from (unsupportable) FusionForge on Alioth?

Jonathan Dowland dijo [Mon, May 15, 2017 at 09:27:27AM +0100]: > On Mon, May 15, 2017 at 09:13:11AM +0200, Alexander Wirt wrote: > > Nice to have: > (snip) > > - Mailinglists > > I've always thought it a bit weird, unfortunate (and possibly a historical > accident) > that we have

Re: Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

> I'll take any day a sort animations that explains things rather then > going through forest of information to figure out what is it, but I > guess these all are personal opinions. A tiny bit of animations should be enough for our homepage. The style of lxde.org does not fit Debian's style and I

Re: Moving away from (unsupportable) FusionForge on Alioth?

On Tue, May 16, 2017 at 12:39 AM, Antonio Terceiro wrote: > Right. IIRC that was said to me at Debconf16 about Debian-specific > services (such as ci.debian.net which was the context of my question). Yeah, for codebases maintained by the service maintainer not having packages seems reasonable

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Let's begin with a sin of big screen users. Say, I am using 2560x1440 display, and the website is painful to view. Adding a max-width to the container can help. Secondly, I think the fonts can be larger and be less crowded (by increasing line-height). I think there are much more we can do even

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On May 15 2017, Adam Borowski wrote: >> https://www.debian.org/ > > Not that different from Gentoo's. What's the problem you're seeing? I think this is one of the those situations where if you don't see it yourself right away, you'll just have to take other people's word

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On Tue, May 16, 2017 at 02:17:40AM +0200, Stéphane Aulery wrote: > > Yes, Debian is a community like another, and a community is build > with shared principles. Design isn't principle, it is just a shameful > exploitation of the idea of beauty, serving a precise purpose which > is not a shared

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Hi, On 05/16/2017 01:48 AM, Sean Whitton wrote: > > More generally, while I agree that we should be flexible in the pursuit > of new contributors and users, we mustn't lose our identity in that > process. Improving things doesn't mean destroying identity. We add and remove archs, we added

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Le 16/05/2017 02:27, Ben Hutchings a écrit : On Tue, 2017-05-16 at 02:17 +0200, Stéphane Aulery wrote: [...] Yes, Debian is a community like another, and a community is build with shared principles. Design isn't principle, it is just a shameful exploitation of the idea of beauty, serving a

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On Tue, 2017-05-16 at 02:17 +0200, Stéphane Aulery wrote: [...] > Yes, Debian is a community like another, and a community is build > with shared principles. Design isn't principle, it is just a shameful > exploitation of the idea of beauty, serving a precise purpose which > is not a shared

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Le 16/05/2017 01:48, Sean Whitton a écrit : Hello Zlatan, On Mon, May 15, 2017 at 09:45:46PM +0200, Zlatan Todoric wrote: Then lets forget about getting newcomers (fresh blood) to Debian as you're so close minded to modern/new things - the same way they probably close the window when they

Re: Moving away from (unsupportable) FusionForge on Alioth?

Thank you for updating us, Alex. On Mon, May 15, 2017 at 09:13:11AM +0200, Alexander Wirt wrote: > - Git Hosting - we want to give pagure [1] a try, which uses gitolite, which > is a > nice git solution. Ah, that's nice. > Pagure also has issue tracking. Is it possible to turn this off? I

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

Hello Zlatan, On Mon, May 15, 2017 at 09:45:46PM +0200, Zlatan Todoric wrote: > Then lets forget about getting newcomers (fresh blood) to Debian as > you're so close minded to modern/new things - the same way they probably > close the window when they see '90 style with a lot of text that >

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On 2017-05-15.15:02, Lars Wirzenius wrote: > http://lxde.org/ seems to be the site in question. I agree with Paul, > I don't like it, and when I encounter pages in that style, I tend to > close the window. > > * It's not nearly information-dense enough. www.debian.org is too > dense, but the

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On 05/15/2017 08:01 PM, Adam Borowski wrote: > On Mon, May 15, 2017 at 10:12:26AM +, lumin wrote: >> On Mon, 2017-05-15 at 11:19 +0200, Arturo Borrero Gonzalez wrote: >>> Our users are really complaining about our look in the web and we >>> should address it. >> I'm looking forward to a new

  1   2   >