Re: [Savannah-hackers-public] Modifying Savannah website
Zeus and I applied some of the changes, in particular more links are
underlined.
--
Sylvain
On Mon, May 25, 2009 at 07:13:18PM -0500, Karl Berry wrote:
karl for me, the brown color for
links used on savannah is quite hard to distinguish from normal text.
(My vision is not the best.) If we let people have their own normal
link color, they would stand out a lot more.
beuc This one is here:
http://git.savannah.gnu.org/cgit/savane-cleanup.git/tree/frontend/php/css/Savannah.css
Thanks. I have two changes to propose, though it's all certainly open
to debate and personal choices. FWIW, I played around with this by
saving web page - complete in a browser on the texinfo project page
and the home page, then changing the Savannah.css in the resulting
*_files subdir.
1) This change switches to plain old blue for links. If that seems too
drastic, the commented-out hex color is a less-vibrant blue that
might suit.
-a { text-decoration: none; color: #641212;}
+a { text-decoration: none; color: #ff;} /* #0022aa */
a:hover { text-decoration: underline; color: #c40f0f; }
Another change that would help, and more or less obviate the need for
a color change, is if the underlines were kept in the main text, and
text decoration was only turned off in the navbar. I didn't see an
easy way to do that.
For that matter, there could be underlines in the navbar too as far
as I'm concerned (just remove text-decoration: none), but I suspect
that there would be no consensus for that.
2) I noticed in the css that #33 is apparently used for the body
text, which is, I guess, kind of a dark gray. Personally my eyes
like just plain black better.
Wdyt?
--- /u/karl/tmp/ORIG/Savannah.css 2009-05-24 17:53:04.0 -0700
+++ /u/karl/tmp/Savannah.css 2009-05-25 17:08:52.0 -0700
@@ -42,3 +42,3 @@
font-family: arial,helvetica;
- color: #33;
+ color: black;
/* background-color: #ffe4b7; */
@@ -61,3 +61,3 @@
.footer {
- color: #33;
+ color: black;
/* background-color: #CCBB88; */
@@ -100,3 +100,3 @@
border-bottom: thin dotted #e0c080;
- color: #33;
+ color: black;
}
@@ -116,5 +116,5 @@
background-color: #ff;
-/* border-bottom: thin solid #33; */
-/* border-top: thin solid #33; */
-/* border-right: thin solid #33; */
+/* border-bottom: thin solid black; */
+/* border-top: thin solid black; */
+/* border-right: thin solid black; */
padding-top: 10px;
@@ -188,3 +188,3 @@
text-align: left;
- color: #33;
+ color: black;
border-bottom: thin dotted #e0c080;
@@ -195,3 +195,3 @@
text-align: right;
- color: #33;
+ color: black;
border-bottom: thin dotted #e0c080;
@@ -258,3 +258,3 @@
border-bottom: thin dotted #e0c080;
- color: #33;
+ color: black;
padding: 1%;
@@ -267,3 +267,3 @@
border-bottom: thin dotted #e0c080;
- color: #33;
+ color: black;
padding: 1%;
@@ -276,3 +276,3 @@
border-bottom: thin dotted #e0c080;
- color: #33;
+ color: black;
}
@@ -282,3 +282,3 @@
border: thin dotted #e0c080;
- color: #33;
+ color: black;
}
Re: [Savannah-hackers-public] Modifying Savannah website
karl for me, the brown color for
links used on savannah is quite hard to distinguish from normal text.
(My vision is not the best.) If we let people have their own normal
link color, they would stand out a lot more.
beuc This one is here:
http://git.savannah.gnu.org/cgit/savane-cleanup.git/tree/frontend/php/css/Savannah.css
Thanks. I have two changes to propose, though it's all certainly open
to debate and personal choices. FWIW, I played around with this by
saving web page - complete in a browser on the texinfo project page
and the home page, then changing the Savannah.css in the resulting
*_files subdir.
1) This change switches to plain old blue for links. If that seems too
drastic, the commented-out hex color is a less-vibrant blue that
might suit.
-a { text-decoration: none; color: #641212;}
+a { text-decoration: none; color: #ff;} /* #0022aa */
a:hover { text-decoration: underline; color: #c40f0f; }
Another change that would help, and more or less obviate the need for
a color change, is if the underlines were kept in the main text, and
text decoration was only turned off in the navbar. I didn't see an
easy way to do that.
For that matter, there could be underlines in the navbar too as far
as I'm concerned (just remove text-decoration: none), but I suspect
that there would be no consensus for that.
2) I noticed in the css that #33 is apparently used for the body
text, which is, I guess, kind of a dark gray. Personally my eyes
like just plain black better.
Wdyt?
--- /u/karl/tmp/ORIG/Savannah.css 2009-05-24 17:53:04.0 -0700
+++ /u/karl/tmp/Savannah.css2009-05-25 17:08:52.0 -0700
@@ -42,3 +42,3 @@
font-family: arial,helvetica;
- color: #33;
+ color: black;
/* background-color: #ffe4b7; */
@@ -61,3 +61,3 @@
.footer {
- color: #33;
+ color: black;
/* background-color: #CCBB88; */
@@ -100,3 +100,3 @@
border-bottom: thin dotted #e0c080;
- color: #33;
+ color: black;
}
@@ -116,5 +116,5 @@
background-color: #ff;
-/* border-bottom: thin solid #33; */
-/* border-top: thin solid #33; */
-/* border-right: thin solid #33; */
+/* border-bottom: thin solid black; */
+/* border-top: thin solid black; */
+/* border-right: thin solid black; */
padding-top: 10px;
@@ -188,3 +188,3 @@
text-align: left;
- color: #33;
+ color: black;
border-bottom: thin dotted #e0c080;
@@ -195,3 +195,3 @@
text-align: right;
- color: #33;
+ color: black;
border-bottom: thin dotted #e0c080;
@@ -258,3 +258,3 @@
border-bottom: thin dotted #e0c080;
- color: #33;
+ color: black;
padding: 1%;
@@ -267,3 +267,3 @@
border-bottom: thin dotted #e0c080;
- color: #33;
+ color: black;
padding: 1%;
@@ -276,3 +276,3 @@
border-bottom: thin dotted #e0c080;
- color: #33;
+ color: black;
}
@@ -282,3 +282,3 @@
border: thin dotted #e0c080;
- color: #33;
+ color: black;
}
Re: [Savannah-hackers-public] Modifying Savannah website
Hi, http://savannah.gnu.org/register/requirements.php This one is here: http://web.cvs.savannah.gnu.org/viewvc/administration/content/gnu-content/register/?root=administration To modify it: cvs -d:pserver:anonym...@cvs.sv.gnu.org:/web/administration co administration/content/gnu-content/register The checklist on the registration page is a good start but I think it will need additional information. So I want to modify this page in a way that I hope will make it more clear that: It's here, but it's raw PHP code: http://git.savannah.gnu.org/cgit/savane-cleanup.git/tree/frontend/php/register2/index.php Better send a patch. You might want to place strong (bold), big, and emphasis html tags on text that link to the requirements. Different issue, but since it came up ... for me, the brown color for links used on savannah is quite hard to distinguish from normal text. (My vision is not the best.) If we let people have their own normal link color, they would stand out a lot more. This one is here: http://git.savannah.gnu.org/cgit/savane-cleanup.git/tree/frontend/php/css/Savannah.css Please send me a patch :) a) The project will be denied approval until all mandatory requirements are met. Submissions that obviously ignore these points are disapproved without further comment. That doesn't sound good. Always justify. However closing a submission immediately in such case instead of keeping it open for 2 weeks sounds acceptable. -- Sylvain
Re: [Savannah-hackers-public] Modifying Savannah website
On Wed, 2009-05-13 at 10:44 +0200, Sylvain Beucler wrote: This one is here: http://web.cvs.savannah.gnu.org/viewvc/administration/content/gnu-content/register/?root=administration Great, I will merge the other requirements with this page. a) The project will be denied approval until all mandatory requirements are met. Submissions that obviously ignore these points are disapproved without further comment. That doesn't sound good. Always justify. Well, I have never known how to politely justify the disapproval of projects like this one: https://savannah.gnu.org/task/?9347 I am out of words, so to speak :)
Re: [Savannah-hackers-public] Modifying Savannah website
a) The project will be denied approval until all mandatory requirements are met. Submissions that obviously ignore these points are disapproved without further comment. That doesn't sound good. Always justify. Well, I have never known how to politely justify the disapproval of projects like this one: https://savannah.gnu.org/task/?9347 I am out of words, so to speak :) We don't offer test accounts ? ;) -- Sylvain
Re: [Savannah-hackers-public] Modifying Savannah website
as it is required to be authenticated to view the /register/ location. Really? I am able to see https://savannah.gnu.org/register/requirements.php without being logged in. (The ssl cert thing is likely rather off-putting, but of course that's a different issue.) I think that the best source of information is already linked from https://savannah.gnu.org/maintenance/HowToGetYourProjectApprovedQuickly is the most comprehensive list I know of -- despite not being the official policy, everything on there is officially required as far as I know. I didn't see it linked from requirements.php. In any case, I agree with both of you that the above non-wiki requirements.php page could be considerably more specific. By the way, I have been in awe of both your efforts at taking care of incoming registrations! You might want to place strong (bold), big, and emphasis html tags on text that link to the requirements. Different issue, but since it came up ... for me, the brown color for links used on savannah is quite hard to distinguish from normal text. (My vision is not the best.) If we let people have their own normal link color, they would stand out a lot more. Best, Karl
Re: [Savannah-hackers-public] Modifying Savannah website
Hello Silvain, I can't keep pace with the project submissions. Many of them block too long because of the same issues again and again and I blame this to the fact that Savannah's hosting requirements are somewhat scattered around all over GNU and Savannah. The checklist on the registration page is a good start but I think it will need additional information. So I want to modify this page in a way that I hope will make it more clear that: a) The project will be denied approval until all mandatory requirements are met. Submissions that obviously ignore these points are disapproved without further comment. b) All these hard requirements are listed in one place together. If I remember correctly, we have at least three different places for this as of now. I hope this will make the approval process more predictable to the author and more effective for us. Regards Sebastian On Sat, 2009-05-09 at 17:47 +0200, Sylvain Beucler wrote: On Sat, May 09, 2009 at 01:48:14PM +0200, Sebastian Gerhardt wrote: Hello, how can I edit the text on this webpage? https://savannah.gnu.org/register/ Is there some option to edit it from within the browser like in a Wiki or do I have to join the Savane clean-up project team for this? The technical means is less important than what you want to modify. So what do you wish to change on this page?
Re: [Savannah-hackers-public] Modifying Savannah website
On 5/11/09, Sebastian Gerhardt sebgerha...@gmx.net wrote: Hello Silvain, I can't keep pace with the project submissions. Many of them block too long because of the same issues again and again and I blame this to the fact that Savannah's hosting requirements are somewhat scattered around all over GNU and Savannah. The checklist on the registration page is a good start but I think it will need additional information. So I want to modify this page in a way that I hope will make it more clear that: a) The project will be denied approval until all mandatory requirements are met. Submissions that obviously ignore these points are disapproved without further comment. b) All these hard requirements are listed in one place together. If I remember correctly, we have at least three different places for this as of now. I hope this will make the approval process more predictable to the author and more effective for us. I think that the best source of information is already linked from that page you wish to edit. I agree with that the requirments are dispersed in different directions. I do not even see the number one issue addressed in the requirements: copyright and license notices. http://savannah.gnu.org/register/requirements.php I think if we wanted to have less people apply with projects that do not meet the requirements, then at least a link to the requirements should be placed on the front page. New users have little to go on before they create a log in, as it is required to be authenticated to view the /register/ location. For a new user to go through the process and then find out about the requirements, might be pretty discouraging and therefore taken less seriously. You might want to place strong (bold), big, and emphasis html tags on text that link to the requirements. Perhaps, you may even go as far as to provide example projects that fit the bill. -- Nicodemo
Re: [Savannah-hackers-public] Modifying Savannah website
On Sat, May 09, 2009 at 01:48:14PM +0200, Sebastian Gerhardt wrote: Hello, how can I edit the text on this webpage? https://savannah.gnu.org/register/ Is there some option to edit it from within the browser like in a Wiki or do I have to join the Savane clean-up project team for this? The technical means is less important than what you want to modify. So what do you wish to change on this page? -- Sylvain
