Thread: Wiki CSS
Folks, Could whoever has the ability mark MediaWiki:Common.css in such a way as I can write to it? My username is dfetter. Thanks :) Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
On Tue, Sep 9, 2008 at 4:35 PM, David Fetter <david@fetter.org> wrote: > Folks, > > Could whoever has the ability mark MediaWiki:Common.css in such a way > as I can write to it? My username is dfetter. Why? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > Could whoever has the ability mark MediaWiki:Common.css in such a way > as I can write to it? My username is dfetter. Done. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200809091144 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkjGme4ACgkQvJuQZxSWSshDRgCg9qvzgR3mkkuLYqNjAPT4uItz PWEAn2vuVdIzNKwnEecDR/sAtWFAGvW+ =u4YL -----END PGP SIGNATURE-----
On Tue, Sep 09, 2008 at 04:43:28PM +0100, Dave Page wrote: > On Tue, Sep 9, 2008 at 4:35 PM, David Fetter <david@fetter.org> wrote: > > Folks, > > > > Could whoever has the ability mark MediaWiki:Common.css in such a > > way as I can write to it? My username is dfetter. > > Why? So I can fix up how it handles nested lists :) Anyhow, it's changed, and I'm fixing it up as I write this. Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
On Tue, Sep 9, 2008 at 4:51 PM, David Fetter <david@fetter.org> wrote: > On Tue, Sep 09, 2008 at 04:43:28PM +0100, Dave Page wrote: >> On Tue, Sep 9, 2008 at 4:35 PM, David Fetter <david@fetter.org> wrote: >> > Folks, >> > >> > Could whoever has the ability mark MediaWiki:Common.css in such a >> > way as I can write to it? My username is dfetter. >> >> Why? > > So I can fix up how it handles nested lists :) Why, what's wrong with them? They work fine for me. > Anyhow, it's changed, and I'm fixing it up as I write this. No, it's been changed back. We don't hand out sysop/root privs to anyone without good and justified reason. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Tue, Sep 9, 2008 at 4:49 PM, Greg Sabino Mullane <greg@turnstep.com> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > >> Could whoever has the ability mark MediaWiki:Common.css in such a way >> as I can write to it? My username is dfetter. > > Done. Err, hang on. why does David need to edit the css, and can it be done without handing out sysop privileges? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Tue, Sep 09, 2008 at 04:58:37PM +0100, Dave Page wrote: > On Tue, Sep 9, 2008 at 4:51 PM, David Fetter <david@fetter.org> wrote: > > On Tue, Sep 09, 2008 at 04:43:28PM +0100, Dave Page wrote: > >> On Tue, Sep 9, 2008 at 4:35 PM, David Fetter <david@fetter.org> wrote: > >> > Folks, > >> > > >> > Could whoever has the ability mark MediaWiki:Common.css in such > >> > a way as I can write to it? My username is dfetter. > >> > >> Why? > > > > So I can fix up how it handles nested lists :) > > Why, what's wrong with them? They work fine for me. > > > Anyhow, it's changed, and I'm fixing it up as I write this. > > No, it's been changed back. We don't hand out sysop/root privs to > anyone without good and justified reason. Slow down, there, cowboy. I'm trying to put up some of the SQL standard, and the usual markup won't work, as it involves lists nested 3 deep. How about reverting it again and not assuming I'm out to destroy the site? I've got plenty of accesses a lot more privileged than that, and I stand on my track record with same. Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
On Tue, 9 Sep 2008 09:03:24 -0700 David Fetter <david@fetter.org> wrote: > > No, it's been changed back. We don't hand out sysop/root privs to > > anyone without good and justified reason. > > Slow down, there, cowboy. I'm trying to put up some of the SQL > standard, and the usual markup won't work, as it involves lists nested > 3 deep. How about reverting it again and not assuming I'm out to > destroy the site? I've got plenty of accesses a lot more privileged > than that, and I stand on my track record with same. Slow down everyone :) Nobody is suggesting you are going to destroy the site David. Dave's point is valid. Root/Sysop should be reserved on all services. The fact that you have higher privs on other services isn't relevant. We all have varying level of privs on the boxen that doesn't mean we should all have root/sysop (insert favorite dangerous account here). Sincerely, Joshua D. Drake -- The PostgreSQL Company since 1997: http://www.commandprompt.com/ PostgreSQL Community Conference: http://www.postgresqlconference.org/ United States PostgreSQL Association: http://www.postgresql.us/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > No, it's been changed back. We don't hand out sysop/root privs to > anyone without good and justified reason. Dave, it's just the wiki, hardly equivalent to a 'root' priv; it just means he can edit a few of the more important pages on the wiki. Not seeing what the big deal is anyway, this is David Fetter, not some random Joe off the street. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200809091211 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkjGoFEACgkQvJuQZxSWSsh6JgCeOuA2oL0V1cAaHYAxRN2aVOGr o0YAn3LYYSDwRcEP/RHVOwHekZ5aFHuH =SYKj -----END PGP SIGNATURE-----
On Tue, Sep 9, 2008 at 5:03 PM, David Fetter <david@fetter.org> wrote: >> No, it's been changed back. We don't hand out sysop/root privs to >> anyone without good and justified reason. > > Slow down, there, cowboy. I'm trying to put up some of the SQL > standard, and the usual markup won't work, as it involves lists nested > 3 deep. How about reverting it again and not assuming I'm out to > destroy the site? I've got plenty of accesses a lot more privileged > than that, and I stand on my track record with same. With respect, that's not the point. I'm sure you agree that privileges on any system should only be given where they are justified, otherwise the security of the system can easily go to pot. On http://wiki.postgresql.org/wiki/User:Dpage I have lists going 4 levels deep with no problem. Please give an example of what doesn't work for you. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Tue, Sep 9, 2008 at 5:12 PM, Greg Sabino Mullane <greg@turnstep.com> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > >> No, it's been changed back. We don't hand out sysop/root privs to >> anyone without good and justified reason. > > Dave, it's just the wiki, hardly equivalent to a 'root' priv; it > just means he can edit a few of the more important pages on the > wiki. Not seeing what the big deal is anyway, this is David Fetter, > not some random Joe off the street. We take the security of the postgresql.org infrastructure seriously, and that includes giving privileged access to services only when required for a justified reason. David already knows full well that I trust him - I gave him root on git.postgresql.org. In that case though, there was a clear need. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Tue, Sep 09, 2008 at 05:12:54PM +0100, Dave Page wrote: > On Tue, Sep 9, 2008 at 5:03 PM, David Fetter <david@fetter.org> wrote: > > >> No, it's been changed back. We don't hand out sysop/root privs to > >> anyone without good and justified reason. > > > > Slow down, there, cowboy. I'm trying to put up some of the SQL > > standard, and the usual markup won't work, as it involves lists nested > > 3 deep. How about reverting it again and not assuming I'm out to > > destroy the site? I've got plenty of accesses a lot more privileged > > than that, and I stand on my track record with same. > > With respect, that's not the point. I'm sure you agree that privileges > on any system should only be given where they are justified, otherwise > the security of the system can easily go to pot. > > On http://wiki.postgresql.org/wiki/User:Dpage I have lists going 4 > levels deep with no problem. Please give an example of what doesn't > work for you. Very simple. The standard doesn't number them the way you're doing, and I need to be able to override it. Just to clarify, if somebody doesn't use actual HTML and the given classes for <li> tags, nothing will change. Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
On Tue, Sep 9, 2008 at 5:15 PM, David Fetter <david@fetter.org> wrote: > Very simple. The standard doesn't number them the way you're doing, > and I need to be able to override it. Just to clarify, if somebody > doesn't use actual HTML and the given classes for <li> tags, nothing > will change. OK, thanks. You should be able to edit it now. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Tue, Sep 09, 2008 at 05:21:33PM +0100, Dave Page wrote: > On Tue, Sep 9, 2008 at 5:15 PM, David Fetter <david@fetter.org> wrote: > > Very simple. The standard doesn't number them the way you're > > doing, and I need to be able to override it. Just to clarify, if > > somebody doesn't use actual HTML and the given classes for <li> > > tags, nothing will change. > > OK, thanks. You should be able to edit it now. Thanks :) Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
David Fetter <david@fetter.org> writes:
> Slow down, there, cowboy. I'm trying to put up some of the SQL
> standard, and the usual markup won't work,
Hmm, have you read the copyright notice on page 2 of the standard?
regards, tom lane
On Tue, Sep 09, 2008 at 04:19:29PM -0400, Tom Lane wrote: > David Fetter <david@fetter.org> writes: > > Slow down, there, cowboy. I'm trying to put up some of the SQL > > standard, and the usual markup won't work, > > Hmm, have you read the copyright notice on page 2 of the standard? It's fair use :) Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
On Tue, Sep 9, 2008 at 9:29 PM, David Fetter <david@fetter.org> wrote: > On Tue, Sep 09, 2008 at 04:19:29PM -0400, Tom Lane wrote: >> David Fetter <david@fetter.org> writes: >> > Slow down, there, cowboy. I'm trying to put up some of the SQL >> > standard, and the usual markup won't work, >> >> Hmm, have you read the copyright notice on page 2 of the standard? > > It's fair use :) Is there such a thing in France where the wiki lives? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Tuesday 09 September 2008 12:15:32 David Fetter wrote: > On Tue, Sep 09, 2008 at 05:12:54PM +0100, Dave Page wrote: > > On Tue, Sep 9, 2008 at 5:03 PM, David Fetter <david@fetter.org> wrote: > > >> No, it's been changed back. We don't hand out sysop/root privs to > > >> anyone without good and justified reason. > > > > > > Slow down, there, cowboy. I'm trying to put up some of the SQL > > > standard, and the usual markup won't work, as it involves lists nested > > > 3 deep. How about reverting it again and not assuming I'm out to > > > destroy the site? I've got plenty of accesses a lot more privileged > > > than that, and I stand on my track record with same. > > > > With respect, that's not the point. I'm sure you agree that privileges > > on any system should only be given where they are justified, otherwise > > the security of the system can easily go to pot. > > > > On http://wiki.postgresql.org/wiki/User:Dpage I have lists going 4 > > levels deep with no problem. Please give an example of what doesn't > > work for you. > > Very simple. The standard doesn't number them the way you're doing, > and I need to be able to override it. Just to clarify, if somebody > doesn't use actual HTML and the given classes for <li> tags, nothing > will change. > Isn't the right way to override css to use an inline style? -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
David Fetter <david@fetter.org> writes:
> On Tue, Sep 09, 2008 at 04:19:29PM -0400, Tom Lane wrote:
>> David Fetter <david@fetter.org> writes:
>>> Slow down, there, cowboy. I'm trying to put up some of the SQL
>>> standard, and the usual markup won't work,
>>
>> Hmm, have you read the copyright notice on page 2 of the standard?
> It's fair use :)
Have you gotten a lawyer to tell you so?
IMNLO it would depend largely on how much material you were quoting,
and if it's so much that you can't be bothered to adjust the markup,
I'm a bit nervous.
regards, tom lane
On Tue, Sep 09, 2008 at 05:23:18PM -0400, Tom Lane wrote: > David Fetter <david@fetter.org> writes: > > On Tue, Sep 09, 2008 at 04:19:29PM -0400, Tom Lane wrote: > >> David Fetter <david@fetter.org> writes: > >>> Slow down, there, cowboy. I'm trying to put up some of the SQL > >>> standard, and the usual markup won't work, > >> > >> Hmm, have you read the copyright notice on page 2 of the standard? > > > It's fair use :) > > Have you gotten a lawyer to tell you so? Nope. > IMNLO it would depend largely on how much material you were quoting, > and if it's so much that you can't be bothered to adjust the markup, > I'm a bit nervous. It's section 7.13 and 7.14 of the SQL standard, and "can't be bothered" doesn't even faintly describe what's going on, but thanks for your input :) Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
On Tue, 9 Sep 2008, David Fetter wrote: > The standard doesn't number them the way you're doing, and I need to be > able to override it. Just to clarify, if somebody doesn't use actual > HTML and the given classes for <li> tags, nothing will change. I'm not familiar enough with CSS to say whether that's true or not. I do suspect there was a way to accomplish this for a page without touching common.css like that. I would have certainly asked that question here and waited a while for feedback before touching anything. What I am uncomfortable with is the way this page was edited. The common.css file is cached by browsers for a long time. See http://en.wikipedia.org/wiki/Wikipedia:Catalogue_of_CSS_classes for comments about that. Looks like it was about three hours you experimented there to get that right. It really bothers me that changes that impact the whole site were made like that. Someone who happened to grab one of your intermediate files during that period is stuck with that one for the next month unless they know the proper reload trick. What if you'd have accidentally broken something? I personally would never touch common.css with an untested change on this Wiki. I have a private MediaWiki installation I use for experiments like that, and I'd only roll out a system-wide change on the PG Wiki that had been confirmed to work there first. In this case, I don't think you actually did any harm, but the way this all happened is not something I'd like to see repeated. -- * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
Greg, ( I believe that... ) You may avoid that caching by adding an expire date to the css http header so the browser will be forzed to perform the download. 2 cents. Gb. 2008/9/9, Greg Smith <gsmith@gregsmith.com>: > On Tue, 9 Sep 2008, David Fetter wrote: > >> The standard doesn't number them the way you're doing, and I need to be >> able to override it. Just to clarify, if somebody doesn't use actual >> HTML and the given classes for <li> tags, nothing will change. > > I'm not familiar enough with CSS to say whether that's true or not. I do > suspect there was a way to accomplish this for a page without touching > common.css like that. I would have certainly asked that question here and > waited a while for feedback before touching anything. > > What I am uncomfortable with is the way this page was edited. The > common.css file is cached by browsers for a long time. See > http://en.wikipedia.org/wiki/Wikipedia:Catalogue_of_CSS_classes for > comments about that. Looks like it was about three hours you experimented > there to get that right. It really bothers me that changes that impact > the whole site were made like that. Someone who happened to grab one of > your intermediate files during that period is stuck with that one for the > next month unless they know the proper reload trick. What if you'd have > accidentally broken something? > > I personally would never touch common.css with an untested change on this > Wiki. I have a private MediaWiki installation I use for experiments like > that, and I'd only roll out a system-wide change on the PG Wiki that had > been confirmed to work there first. In this case, I don't think you > actually did any harm, but the way this all happened is not something I'd > like to see repeated. > > -- > * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD > > -- > Sent via pgsql-www mailing list (pgsql-www@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-www > -- Guido Barosio ----------------------- http://www.globant.com guido.barosio@globant.com
David Fetter <david@fetter.org> writes:
> On Tue, Sep 09, 2008 at 05:23:18PM -0400, Tom Lane wrote:
>> IMNLO it would depend largely on how much material you were quoting,
>> and if it's so much that you can't be bothered to adjust the markup,
>> I'm a bit nervous.
> It's section 7.13 and 7.14 of the SQL standard,
Well, that's about 20 pages in the PDF I've got. I think if you think
that qualifies as fair use, you REALLY had better get confirmation from
a lawyer before putting the project at risk. My understanding of fair
use is that it probably stretches to a few paragraphs or so.
I think it would be a whole lot safer for you just to tell people
where to get the draft specs. They'd need it anyway in order to make
sense of all the terms that are referenced but not defined in these
two sections.
regards, tom lane
On Tue, Sep 09, 2008 at 08:37:04PM -0400, Tom Lane wrote: > Well, that's about 20 pages in the PDF I've got. I think if you think > that qualifies as fair use, you REALLY had better get confirmation from > a lawyer before putting the project at risk. My understanding of fair > use is that it probably stretches to a few paragraphs or so. It may well stretch beyond that, but I'm willing to bet that large corporation-sponsored committees with itchy lawyer fingers and a strong interest in keeping control of their publications are willing to swat a small ill-funded project or two in order to protect that interest. I think this effort is borrowing trouble, and we shouldn't do it. I support Tom's call for references rather than excerpts. I have to echo, as well, the concerns about testing things on a production site. Not cool, that. A -- Andrew Sullivan ajs@commandprompt.com +1 503 667 4564 x104 http://www.commandprompt.com/
On Tue, 9 Sep 2008 22:58:25 -0400 Andrew Sullivan <ajs@commandprompt.com> wrote: > On Tue, Sep 09, 2008 at 08:37:04PM -0400, Tom Lane wrote: > > > Well, that's about 20 pages in the PDF I've got. I think if you > > think that qualifies as fair use, you REALLY had better get > > confirmation from a lawyer before putting the project at risk. My > > understanding of fair use is that it probably stretches to a few > > paragraphs or so. > > It may well stretch beyond that, but I'm willing to bet that large > corporation-sponsored committees with itchy lawyer fingers and a > strong interest in keeping control of their publications are willing > to swat a small ill-funded project or two in order to protect that > interest. I think this effort is borrowing trouble, and we shouldn't > do it. I support Tom's call for references rather than excerpts. In short... there is a reason more "fair use" versions of the SPEC haven't shown up on the web. +1 remove. Joshua D. Drake -- The PostgreSQL Company since 1997: http://www.commandprompt.com/ PostgreSQL Community Conference: http://www.postgresqlconference.org/ United States PostgreSQL Association: http://www.postgresql.us/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
Dave Page wrote: > David already knows full well that I trust him - I gave him root on > git.postgresql.org. In that case though, there was a clear need. David, do you actually do anything on git.p.o that requires root access? As far as I can tell, you do everything under yourown user account, and you are not part of the admin alias.
On Thu, Sep 11, 2008 at 10:00 AM, Peter Eisentraut <peter_e@gmx.net> wrote: > Dave Page wrote: >> >> David already knows full well that I trust him - I gave him root on >> git.postgresql.org. In that case though, there was a clear need. > > David, do you actually do anything on git.p.o that requires root access? As > far as I can tell, you do everything under your own user account, and you > are not part of the admin alias. > David has sudo access to do anything, via the PGGITADMIN alias, along with you and Greg. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Dave Page wrote: > On Thu, Sep 11, 2008 at 10:00 AM, Peter Eisentraut <peter_e@gmx.net> wrote: >> Dave Page wrote: >>> David already knows full well that I trust him - I gave him root on >>> git.postgresql.org. In that case though, there was a clear need. >> David, do you actually do anything on git.p.o that requires root access? As >> far as I can tell, you do everything under your own user account, and you >> are not part of the admin alias. >> > > David has sudo access to do anything, via the PGGITADMIN alias, along > with you and Greg. Sorry, I meant the email alias, used for user requests for things possibly needing root access.