Search results

{{header|docs}} [[Category:Docs Project process]]

{{header|docs}} ...s use an online application called Transifex to help track the translation process and to interface with the documentation repositories.

{{header|docs}} <!-- {{:DocsProject/ReleaseNotes/Process,, from="^## INCLUDERELNOTESPROCESSSTART$", to="^## INCLUDERELNOTESPROCESSEN

{{header|docs}} ...collection of languages being processed. doc-publican-rpm automates this process.

|style="background: #ffcc00; color: black" | All current modules in Docs CVS already follow these policies. The information in this page needs to b {{Admon/caution | This page describes the package preparation process for FDP only. If you are interested in packaging for Fedora Extras, refer

...DocBook, the file format used by the DocsProject for master copies of all Project documents. ...vely easy for other contributors when it's time to add the document to the Project CVS.

...t. Karsten agreed. There's going to probably be some changes for what a "project" is and clean up some of the outdated information. * New package submission process - Warren and Dave are scheduled to meet on Friday to discuss this. Outcome

...maintained by the [[Fedora Documentation Project]] and published on http://docs.fedoraproject.org. Guides range from detailed manuals hundreds of pages lon Your guide might be an entirely new piece of writing or a project that you are migrating to Fedora from elsewhere, for example, a Red Hat Ent

...|| [[Extras| Extras]] ||[[Ambassadors| Ambassadors & Marketing ]] || [[docs| Documentation]] || [[kadischi| Kadischi]] || [[l10n| Translation]] * Information on The Fedora Project Board can be found at http://fedoraproject.org/wiki/Board

= Fedora Release Notes Process = export CVSROOT=:pserver:anonymous@cvs.fedoraproject.org:/cvs/docs

* Getting people interested in Docs project, to feel confident with the tools used, getting an useful product finished * Getting more and more qualified people into the real for Docs Team.

[[Category:Docs Project process]]

...enting a fully automated publishing process for the [[Fedora Documentation Project]]. ...tool, [[Publican]]. Publican also maintains the Fedora documentation site (docs.fedoraproject.org) and automatically generates and updates the navigation m

Docs Project lead: [[User:laubersm|Susan Lauber]] ...ee]] -> [[:Category:Packaging guidelines]] is for the Packaging: namespace docs.

...the docs list signup page] . The primary purpose of this is to begin the process of building trust by learning about the writer/editor, and downloading thei ...on/important|Personal Information|Fedora is a very visible and transparent project, which means that its mailing lists are archived and mirrored in many place

[[Category:Docs Project process]]

{{header|docs}} Before beginning this process, be sure you have been through the [[Preparing the Release Notes for final

{{lang|en|es|page=Reporting problems with Docs}} {{header|docs}}

...the [[DocsProject|Docs Project]] Karsten "quaid" Wade about their joining process (30-40mins)

Items for the [[Release_announcements#Process|Release announcement process]] need to be moved over to here. ...t excite you. Note, some Beats are committed to git://git.fedorahosted.org/docs/release-notes.git as they are written.