[Bug 504068] New: Update task lists
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Update task lists
https://bugzilla.redhat.com/show_bug.cgi?id=504068
Summary: Update task lists
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: project-tracking
AssignedTo: kwade(a)redhat.com
ReportedBy: mel(a)redhat.com
QAContact: kwade(a)redhat.com
CC: fedora-docs-list(a)redhat.com
Classification: Fedora
ke4qqq helping with new contributor tasks, quaid working on all lists; IG and
relnotes moved to hosted Trac. (Note that this ticket is part of an experiment
by mchua to keep tasks in BZ.)
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years, 8 months
Project Start: New Updated Deployment Guide for the Upcoming Fedora 12!
by Douglas Silas
Greetings Fedora users and system administrators,
I meant to announce this last week on fedora-docs-list, but the CC
slipped my mind. Here's copy of the announcement I sent to
deployment-guide-list(a)redhat.com. See the Deployment Guide wiki:
https://fedorahosted.org/deploymentguide/wiki
...for details on joining this list. All are welcome.
ORIGINAL ANNOUNCEMENT
I'm proud to announce that I'll be heading a new project to update a
new guide, the Fedora Deployment Guide, for the upcoming Fedora 12
release! The Fedora Deployment Guide covers system administration
tasks such as package maintenance, user administration, printing,
and setting up networks, printers, and services such as Apache,
LDAP, OpenSSH, Samba, etc.
You can see what's in it and the most current state of the upcoming
Fedora 12 Deployment Guide here:
http://dsilas.fedorapeople.org/Deployment_Guide/en-US/
The target for completion of this project is before Nov. 1, ahead of
the GA target date for Fedora 12, which is currently Nov. 3.
The project page for the Deployment Guide, which also tells you
where to obtain the source files (which are in DocBook XML), is here:
https://fedorahosted.org/deploymentguide/wiki
We will definitely be accepting contributors; please contact me if
you are able to help out. There is a Deployment Guide mailing list.
To gain access to it, please send an email to the project
maintainers (of whom I am one) with a brief introduction:
https://www.redhat.com/mailman/listinfo/deployment-guide-list
The Fedora Deployment Guide is written in DocBook XML and is
published using the open source Publican build tool:
https://fedorahosted.org/publican/
More details will follow next week (such as additions to the TOC).
I hope to hear suggestions and opinions from you!
Cheers,
--
Douglas Silas
Technical Writer | Red Hat, Inc.
Purkyňova 99 | Brno, Czech Republic
Office Direct Dial—62116
Brno Office—(+420) 532 294 111 ext. 10718
dhensley(a)redhat.com
14 years, 8 months
Need Feedback on HOWTO wiki created by /me.
by Kishan Goyal
Hi,
Last week I made a wiki page on HOWTO Install Fedora 11. The page is
an effort to help users with the installation of Fedora 11.
I used VirtualBox to install Fedora 11 virtually on my laptop, and, in
the process, took screenshots of every step that I encountered and
wrote down the installation procedure in steps. The wiki page is
available here [1].
This is the first time I have created such a HOWTO or guide and I may
have missed out on something. I would be glad to receive any comments,
criticism, etc. which would help me to improve this wiki and in my
future ventures.
[1] http://www.burntomlette.in/index.php?title=Installing_fedora11
Thanks,
Regards,
Kishan Goyal.
14 years, 8 months
Reviewed: [[Welcome_Message_To_New_Ambassadors]]
by Karsten Wade
Susmit:
Sorry to break the threading, I accidentally deleted your original
email. Your welcome message made a nice review over lunch today:
https://fedoraproject.org/wiki/Welcome_Message_To_New_Ambassadors
I made changes directly because I didn't see anything substantive that
I changed. That is, I don't think I changed any meaning, just did
some grammar adjustments and clarifications. Please read my changes
carefully -- I'm not as familiar with the updated mentoring guidelines
as I should be. :)
There is one issue in the instructions -- it directs the new potential
Ambassador to get aggregated on Fedora Planet. However, that requires
being in a FAS group already (plus having signed the CLA.) If the
Ambassador-to-be is not already in the 'ambassadors' group, they have
to belong to another group, too.
Maybe that was the intention? I note the mandatory-in-India step of
contributing to another group. Is that the secret solution?
One concern is that we'll get an influx of people to low-barrier
groups, such as 'docs', who are just interested in getting their FAS
group to get aggregated and fulfill Ambassador requirements. I could
foresee a chain-reaction of people raising barriers in groups to block
against that. Also, it is possible to contribute to various projects
without joining the group. One could write wiki documentation or be
involved in QA test days without belonging to the 'docs' or 'qa'
groups.
Would it be possible to have the candidate bring proof of that instead
of being required to have joined another group? In other words, if
they are going to join e.g. 'docs' just to get in to 'ambassadors',
they are less likely to sustain contributions to the Docs Team. (It's
OK if people don't want to remain a Docs contributor, we just need to
set the expectations all around.)
cheers - Karsten
--
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41
14 years, 8 months
Fedora Desktop Guide Update
by Matthew Daniels
At last week's FDSCo meeting, I blabbered along for a few minutes concerning
where I wanted to go with the User Guide (and, subsequently, that I thought
we should rename it).
I've put together a mock table of contents and a few sample paragraphs of
the sort of style I envisioned in the rewritten guide. I'd appreciate any
comments on other ways to address the audience, better topics to choose, or
anything else that you feel would make it better.
Please note that it's neither properly formatted nor spell/grammar-checked
nor comprehensive in scope. I'm just looking for ideas before we get too
far instead of after we've done half the guide.
Links:
http://danielsmw.fedorapeople.org/Guide.pdf
http://danielsmw.fedorapeople.org/Guide.odt
Also, because of the way this has been
restyled, I think it could be easier for people to contribute; instead
of delving into the full document and pulling out a scalpel to
existing, messy content, people could just send me a paragraph or two
on a particular question they care about or think is relevant.
Cheers!
- - -- --- ----- -------- ------------- ---------------------
Matthew Daniels
Fedora Project
+ danielsmw(a)gmail.com
Clemson University
+ mdaniel(a)clemson.edu
Home Page / Blog
+ people.clemson.edu/~mdaniel
+ danielsmw.wordpress.com
14 years, 8 months
how can I help?
by Niko Yoshio
Hi everyone,
how can I contribute?
where do I start?
thanks
14 years, 8 months
Re: Errors while syncing bugzilla with owners.list
by Piotr Drąg
W dniu 03.08.2009 20:20, accounts(a)fedoraproject.org pisze:
> The following errors were encountered while updating bugzilla with information
> from owners.list files. Please have the problem taken care of:
>
> ({'product': u'Fedora Documentation', 'component': u'readme-burning-isos', 'initialowner': u'oglesbyzm(a)gmail.com'}, 51, "There is no user named 'oglesbyzm(a)gmail.com'.\n Either you mis-typed the name or that user has not yet registered\n for a Red Hat Bugzilla account.")
>
I think someone should do something with this.
--
Piotr Drąg
http://raven.pmail.pl
14 years, 8 months
