9:48 a.m.
First, I'd like to welcome you all to the new Fedora Websites mailing
list. The purpose of this list is discussion related to the formal
Fedora websites (fedoraproject.org and fedora.redhat.com) and to allow a
forum for communication between the contributors and maintainers of
these sites and the maintainers of third-party Fedora-related websites.
To start off, we have a few items to address. Consider these the early
agenda for this list and the group it represents. Additions and
suggestions are welcome.
1. The List of Fedora Community Websites
Scott Glaser has begun working on a list [1] of Fedora Community
Websites that will be added to the Communicate page [2] of the wiki. If
you have any suggestions for this list, please contact him. He will
also need assistance in deciding what sorts of sites should be
included. If you have any remarks to that end, he will be happy to hear
them in #fedora-docs on freenode. Look for Sonar_Guy.
2. Deprecation of fedora.redhat.com
Ongoing efforts have been underway to place all critical content on the
fedoraproject.org wiki and to prepare the wiki to supplant the current
fedora.redhat.com website as the primary site for the Project. Much of
the content from f.r.c has already been duplicated on the wiki, but
there are still many pieces that have yet to be moved. One of the
bigger concerns is publishing the documentation produced by the Docs
Project on the wiki. Another key concern is tightening security and
establishing policies for key wiki pages, such as those which are
highest traffic or contain legal information.
3. Technical contacts and maintainers for wiki pages
The idea of marking pages on the wiki using comments to list technical
contacts/maintainers for those pages has been discussed on
fedora-docs-list. The idea is simple: have a maintainer assigned to
each page, who is responsible for keeping that page up-to-date and
generally taking care of it. For more details, please see the
fedora-docs-list archives [3].
4. Wiki translation
Yuan Yijun has jumped ahead of the rest of us and begun working on a
zh_CN translation of the wiki. So far, his work has not been in line
with the translation ideas discussed so far. We need to decide just how
we want to handle the wiki translation, including what kind of structure
we want to use, policies regarding translation of sensitive materials,
and what parts of the wiki should (not) be translated. Obviously, there
is interest in getting this done. We have had individuals interested
specifically in Japanese, Chinese, Brazilian Portuguese and French
translations all try to get things moving. It's time to figure out how
this is going to be done.
5. Usability improvements on the wiki
There have been several good suggestions for improvements to the wiki.
First, there was the idea of making a more general-purpose FrontPage to
better serve visitors. Then, assorted improvements for the wiki's
themes. A lot of progress has been made, lets see what else needs to be
done. The latest idea, courtesy of Rahul Sundaram, is the restoration
of the 'Parent' links provided by MoinMoin's default themes. These
links, which allow a visitor to quickly browse to any page's parent in
the hierarchy, disappeared during the creation of the
kindofblue/sinorca4moin theme.
On a final note, if you have not already done so, you might want to
consider signing up for the 'web' group in the Fedora Account System and
adding yourself to the list on the wiki [4] of people
interested in working on the Fedora websites. Elliot Lee was kind
enough to start that page as a first step in coordinating work on the
Fedora websites. He had an excellent point, and one that is served well
by this new mailing list: it is time that all the various efforts to
improve Fedora on the web be coordinated so that they may move forward
more efficiently. Lets do it!
[1] http://fedoraproject.org/wiki/ScottGlaser - See the bottom of the page
[2] http://fedoraproject.org/wiki/Communicate
[3]
https://www.redhat.com/archives/fedora-docs-list/2005-October/msg00111.html
[4] http://fedoraproject.org/wiki/Websites
--
Patrick "The N-Man" Barnes
nman64(a)n-man.com
www.n-man.com
--
1:47 p.m.
New subject: Interim plan for fedora.redhat.com
OK, so. There's a bunch of changes that need to happen on
fedora.redhat.com, because it's been decaying for far too long -- and
we're going to make these changes in the next two weeks. Basically,
here's our plan:
1. Rework all the content, bearing in mind that at some point (soon) we'll
move it to fp.o. Most of the new content will be repurposed from the
great content that has been written at fp.o recently. For the first few
days of next week, Alex and I will be barricading ourselves in a room and
writing/editing/checking in new content. That's all we'll be doing.
2. Begin translation efforts in-house for this static content. I expect
it'll be mostly Red Hat folks, but this is a decision for Sarah Wang, who
runs our translation efforts. The goal will be to have key f.r.c content
translated into several of the most popular languages within the next
month.
This way, once we've worked out the infrastructure issues for the static
content on fp.o (drupal? zope? YAcms?), the work of sorting the content
*itself* will be mostly done. And it no longer makes sense (and never
did, really) to delay this content rewrite until we've got a "better"
website to put it on.
--g
_____________________ ____________________________________________
Greg DeKoenigsberg ] [ the future masters of technology will have
Community Relations ] [ to be lighthearted and intelligent. the
Red Hat ] [ machine easily masters the grim and the
] [ dumb. --mcluhan
On Tue, 8 Nov 2005, Patrick Barnes wrote:
First, I'd like to welcome you all to the new Fedora Websites
mailing
list. The purpose of this list is discussion related to the formal
Fedora websites (fedoraproject.org and fedora.redhat.com) and to allow a
forum for communication between the contributors and maintainers of
these sites and the maintainers of third-party Fedora-related websites.
To start off, we have a few items to address. Consider these the early
agenda for this list and the group it represents. Additions and
suggestions are welcome.
1. The List of Fedora Community Websites
Scott Glaser has begun working on a list [1] of Fedora Community
Websites that will be added to the Communicate page [2] of the wiki. If
you have any suggestions for this list, please contact him. He will
also need assistance in deciding what sorts of sites should be
included. If you have any remarks to that end, he will be happy to hear
them in #fedora-docs on freenode. Look for Sonar_Guy.
2. Deprecation of fedora.redhat.com
Ongoing efforts have been underway to place all critical content on the
fedoraproject.org wiki and to prepare the wiki to supplant the current
fedora.redhat.com website as the primary site for the Project. Much of
the content from f.r.c has already been duplicated on the wiki, but
there are still many pieces that have yet to be moved. One of the
bigger concerns is publishing the documentation produced by the Docs
Project on the wiki. Another key concern is tightening security and
establishing policies for key wiki pages, such as those which are
highest traffic or contain legal information.
3. Technical contacts and maintainers for wiki pages
The idea of marking pages on the wiki using comments to list technical
contacts/maintainers for those pages has been discussed on
fedora-docs-list. The idea is simple: have a maintainer assigned to
each page, who is responsible for keeping that page up-to-date and
generally taking care of it. For more details, please see the
fedora-docs-list archives [3].
4. Wiki translation
Yuan Yijun has jumped ahead of the rest of us and begun working on a
zh_CN translation of the wiki. So far, his work has not been in line
with the translation ideas discussed so far. We need to decide just how
we want to handle the wiki translation, including what kind of structure
we want to use, policies regarding translation of sensitive materials,
and what parts of the wiki should (not) be translated. Obviously, there
is interest in getting this done. We have had individuals interested
specifically in Japanese, Chinese, Brazilian Portuguese and French
translations all try to get things moving. It's time to figure out how
this is going to be done.
5. Usability improvements on the wiki
There have been several good suggestions for improvements to the wiki.
First, there was the idea of making a more general-purpose FrontPage to
better serve visitors. Then, assorted improvements for the wiki's
themes. A lot of progress has been made, lets see what else needs to be
done. The latest idea, courtesy of Rahul Sundaram, is the restoration
of the 'Parent' links provided by MoinMoin's default themes. These
links, which allow a visitor to quickly browse to any page's parent in
the hierarchy, disappeared during the creation of the
kindofblue/sinorca4moin theme.
On a final note, if you have not already done so, you might want to
consider signing up for the 'web' group in the Fedora Account System and
adding yourself to the list on the wiki [4] of people
interested in working on the Fedora websites. Elliot Lee was kind
enough to start that page as a first step in coordinating work on the
Fedora websites. He had an excellent point, and one that is served well
by this new mailing list: it is time that all the various efforts to
improve Fedora on the web be coordinated so that they may move forward
more efficiently. Lets do it!
[1] http://fedoraproject.org/wiki/ScottGlaser - See the bottom of the page
[2] http://fedoraproject.org/wiki/Communicate
[3]
https://www.redhat.com/archives/fedora-docs-list/2005-October/msg00111.html
[4] http://fedoraproject.org/wiki/Websites
--
Patrick "The N-Man" Barnes
nman64(a)n-man.com
www.n-man.com
--
3:52 p.m.
New subject: Interim plan for fedora.redhat.com
On Fri, 11 Nov 2005 14:47:44 -0500 (EST), Greg DeKoenigsberg wrote
OK, so. There's a bunch of changes that need to happen on
fedora.redhat.com, because it's been decaying for far too long -- and
we're going to make these changes in the next two weeks. Basically,
here's our plan:
1. Rework all the content, bearing in mind that at some point (soon) we'll
move it to fp.o. Most of the new content will be repurposed from the
great content that has been written at fp.o recently. For the first few
days of next week, Alex and I will be barricading ourselves in a room and
writing/editing/checking in new content. That's all we'll be doing.
2. Begin translation efforts in-house for this static content. I expect
it'll be mostly Red Hat folks, but this is a decision for Sarah Wang, who
runs our translation efforts. The goal will be to have key f.r.c content
translated into several of the most popular languages within the next
month.
This way, once we've worked out the infrastructure issues for the static
content on fp.o (drupal? zope? YAcms?), the work of sorting the content
*itself* will be mostly done. And it no longer makes sense (and never
did, really) to delay this content rewrite until we've got a "better"
website to put it on.
--g
_____________________ ____________________________________________
Greg DeKoenigsberg ] [ the future masters of technology will have
Community Relations ] [ to be lighthearted and intelligent. the
Red Hat ] [ machine easily masters the grim and the
] [ dumb. --mcluhan
Hi All,
I just joined Fedora "web" group officially approved by Warren Togami. (Thank
you again
Warren.)
Here is my first question as a member.
Who's going to decide which CMS will be installed on fedoraproject.org?
I understand Seth Vidal prefers Python based CMS and I'm sure everyone has their own
favorite CMS. Recently I've been testing Drupal CMS (http://drupal.org) on my own
server
(http://fedoranews.org/cms) and I must admit I'm very impressed with its features and
capabilities.
Please let me know if I misunderstood the plan. Otherwise, I hope there is some sort of
voting process for us.
Regards,
--
Thomas Chung
FedoraNEWS.ORG (http://fedoranews.org)
"..where you can free your knowledge for your free community!"
2:42 p.m.
New subject: Interim plan for fedora.redhat.com
I just joined Fedora "web" group officially approved by
Warren Togami. (Thank you again
Warren.)
Here is my first question as a member.
Who's going to decide which CMS will be installed on fedoraproject.org?
Please let me know if I misunderstood the plan. Otherwise, I hope
there is some sort of
voting process for us.
voting process on security of the systems we use.
<sarcasm>That sounds like a fantastic idea</sarcasm>
-sv
7:16 a.m.
New subject: Interim plan for fedora.redhat.com
On Fri, 2005-11-11 at 13:52 -0800, Thomas Chung wrote:
I just joined Fedora "web" group officially approved by
Warren Togami. (Thank you again
Warren.)
Welcome. I'm glad to see participation from active community site
administrators. We may not be able to match all of our expectations or
needs, but it's good that we have a chance and a place to work out our
common understanding and goals.
Here is my first question as a member.
Who's going to decide which CMS will be installed on fedoraproject.org?
It will be decided on this list. The decision, as all are in Fedora,
comes from the project leaders. Ideas drift to the top based on merit.
This is why PHP-based solutions are non-starters. They can never drift
to the top because the merit of features-over-security is not the Fedora
way.
Please let me know if I misunderstood the plan. Otherwise, I hope
there is some sort of
voting process for us.
As Seth has caustically put it, this is not a democracy. However, your
voice has weight in the decision. Please keep thinking of solutions,
given the limitations and parameters that the project leadership puts in
place.
We cannot endlessly debate what is the right solution. We need to pick
one that best matches our values and capabilities, and push forward with
it. It is better to take our time adding functionality to a good-enough
but lacking solution, than to get ourselves stuck with a really-great
security nightmare.
The two people who have 1000x more merit than the rest of us when it
comes to the Fedora infrastructure have put their feet down against PHP
and for Python. AFAIC, the decision is made about language, now we just
need to decide which Python-based solution to use.
- Karsten
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Red Hat SELinux Guide
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
7:26 a.m.
New subject: Interim plan for fedora.redhat.com
On Mon, 2005-11-14 at 05:16 -0800, Karsten Wade wrote:
AFAIC, the decision is made about language, now we just
need to decide which Python-based solution to use.
We have both Plone and Zope in Extras, so those are certainly decent
options.
--
Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net>
http://fedora.ivazquez.net/
gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72
7:22 a.m.
On Tue, 2005-11-08 at 09:48 -0600, Patrick Barnes wrote:
One of the
bigger concerns is publishing the documentation produced by the Docs
Project on the wiki.
This should be relatively easy. The content is checked into CVS as PHP-
wrapped globs of HTML. We can replace this with Python-based wrapping,
right?
The pages are all statically generated from the PHP pages, using
includes to pull in headers, footers, navigation elements, and styling.
If we cannot change this to Python in the short-term, perhaps a simple
solution is to have the PHP conversion done on the back-end inside of a
private network, then rsync'd out to fp.org/docs.
Another key concern is tightening security and
establishing policies for key wiki pages, such as those which are
highest traffic or contain legal information.
+1 for page owners.
- Karsten
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Red Hat SELinux Guide
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
7:33 a.m.
On Mon, 2005-11-14 at 05:22 -0800, Karsten Wade wrote:
This should be relatively easy. The content is checked into CVS as
PHP-
wrapped globs of HTML. We can replace this with Python-based wrapping,
right?
There are multiple Python-based templating engines in Extras.
--
Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net>
http://fedora.ivazquez.net/
gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72
7:35 a.m.
Ignacio Vazquez-Abrams wrote:
On Mon, 2005-11-14 at 05:22 -0800, Karsten Wade wrote:
>This should be relatively easy. The content is checked into CVS as PHP-
>wrapped globs of HTML. We can replace this with Python-based wrapping,
>right?
>
>
There are multiple Python-based templating engines in Extras.
Can you provide a list that would serve the purpose defined above?
regards
Rahul
7:46 a.m.
On Mon, 2005-11-14 at 19:05 +0530, Rahul Sundaram wrote:
Ignacio Vazquez-Abrams wrote:
>On Mon, 2005-11-14 at 05:22 -0800, Karsten Wade wrote:
>
>
>>This should be relatively easy. The content is checked into CVS as PHP-
>>wrapped globs of HTML. We can replace this with Python-based wrapping,
>>right?
>>
>>
>
>There are multiple Python-based templating engines in Extras.
>
>
>
Can you provide a list that would serve the purpose defined above?
Off the top of my head I believe that Kid (http://kid.lesscode.org/) can
do it. I'd need to actually look at the others in order to know about
them, and unfortunately I don't have the time right this minute to do
so.
--
Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net>
http://fedora.ivazquez.net/
gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72
6747
days inactive
6753
days old
websites@lists.fedoraproject.org
9 comments
7 participants
participants (7)
-
Greg DeKoenigsberg -
Ignacio Vazquez-Abrams -
Karsten Wade -
Patrick W. Barnes -
Rahul Sundaram -
Seth Vidal -
Thomas Chung