From Fedora Project Wiki

Page title matches

Page text matches

  • ...Each page should also be in a separate sub-category for the specific sub-process. [[Category:Docs Project]]
    56 members (0 subcategories, 0 files) - 16:49, 19 February 2009
  • * [[Docs Project tasks| Schedule of tasks]] to implement the goals * [[Improving_the_Docs_Project_workflow| Ideas on Improving the Documentation Process Workflow]]
    675 bytes (85 words) - 13:43, 13 August 2012
  • #REDIRECT [[Archive:Docs Project Steering Committee process]]
    61 bytes (7 words) - 15:13, 15 June 2010
  • #REDIRECT [[Archive:Docs Project Steering Committee elections process]]
    71 bytes (8 words) - 18:25, 1 April 2009
  • {{header|docs}} [[Category:Docs Project process]]
    297 bytes (36 words) - 02:31, 22 February 2009
  • = Fedora Docs Project CVS Usage Guidelines = ...edora Project. Users receive access to CVS, when appropriate, through the process located at [[Extras/CvsAccess| the Extras CVS access page]] .
    3 KB (458 words) - 02:43, 26 July 2009
  • This page covers several aspects of projects that are hosted for the [[Docs Project]]: ...the Trac wiki, except for the front page. Instead make pages on the main project wiki and refer back to there.
    1 KB (145 words) - 22:26, 14 June 2010
  • {{header|docs}} ...raVersionNumber|next}}-docs-tasks.html Fedora {{FedoraVersionNumber|next}} Docs schedule]
    1 KB (146 words) - 13:54, 6 May 2013
  • * Subscription to the [https://admin.fedoraproject.org/mailman/listinfo/docs docs] mailing list. ** This is the primary forum used for discussions about the docs: we use it for everything, from developing new ideas to refining old ones.
    2 KB (357 words) - 23:56, 14 June 2010
  • {{header|docs}} Проект Fedora Documentation ("Docs Project") снабжен 100% свободной открытым содержан�
    4 KB (182 words) - 13:49, 22 November 2010
  • [[Category:Docs Project]][[Category:Wiki gardening]] The [[DocsProject]] oversees the wiki gardening process.
    654 bytes (86 words) - 02:01, 6 December 2008
  • [[Docs_Project|Fedora Docs Project]] # Smoothing out the translation process and removing barriers. What do Docs people need to be successful? Translators?
    1 KB (171 words) - 13:56, 11 September 2011
  • = Fixing fedora-docs Bugs in Bugzilla = ...lly, this resolution will only be for FDP members to file bugs against CVS docs. If the fix is for a document that has ''already'' been published, wait to
    2 KB (276 words) - 18:51, 22 February 2009
  • {{header|docs}} = Release Notes Process =
    7 KB (1,108 words) - 03:48, 24 February 2009
  • = Making it Easier to Join the Fedora Project = Formerly entitled: "Simplifying the Onboarding Process for the Fedora Project"
    4 KB (552 words) - 16:30, 24 May 2008
  • {{header|docs}} ...guide are stored in Git repositories on [https://pagure.io/projects/fedora-docs/%2A Pagure], and each repository has its own "issues" section where you can
    2 KB (259 words) - 17:13, 7 April 2021
  • {{header|docs}} {{admon/note | This page is obsolete | Come back to [[Docs Project]] }}
    1 KB (205 words) - 19:10, 6 June 2019
  • {{header|docs}} .../%2A Pagure], and others in Git repositories on [https://gitlab.com/fedora/docs Gitlab]. Each repository has its own "issues" section where you can report
    2 KB (316 words) - 05:59, 1 June 2022
  • Stable: http://docs.fedoraproject.org/selinux-user-guide/f10/en-US/ The existing [http://selinuxproject.org/page/Documentation_TODO SELinux project documentation todo list].
    3 KB (428 words) - 20:35, 19 September 2016
  • The Feature Process has proven itself to be clunky. We need to think about changes to it now t == One process, two audiences ==
    2 KB (376 words) - 17:18, 22 March 2011
  • {{header|docs}} [[Category:Docs Project process]]
    1,015 bytes (165 words) - 14:38, 8 April 2011
  • {{header|docs}} ...s use an online application called Transifex to help track the translation process and to interface with the documentation repositories.
    1 KB (225 words) - 14:34, 16 August 2011
  • {{header|docs}} <!-- {{:DocsProject/ReleaseNotes/Process,, from="^## INCLUDERELNOTESPROCESSSTART$", to="^## INCLUDERELNOTESPROCESSEN
    8 KB (1,222 words) - 01:14, 25 February 2009
  • {{header|docs}} ...collection of languages being processed. doc-publican-rpm automates this process.
    2 KB (328 words) - 15:20, 8 April 2011
  • |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
    5 KB (818 words) - 18:34, 22 February 2009
  • ...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.
    3 KB (461 words) - 18:38, 22 February 2009
  • ...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
    2 KB (368 words) - 16:34, 24 May 2008
  • ...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
    7 KB (1,094 words) - 20:46, 21 March 2014
  • ...|| [[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
    6 KB (710 words) - 19:19, 28 April 2015
  • = Fedora Release Notes Process = export CVSROOT=:pserver:anonymous@cvs.fedoraproject.org:/cvs/docs
    8 KB (1,200 words) - 16:36, 24 May 2008
  • * 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.
    5 KB (728 words) - 05:53, 20 January 2011
  • [[Category:Docs Project process]]
    1 KB (203 words) - 19:58, 11 January 2009
  • ...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
    6 KB (989 words) - 00:29, 4 February 2014
  • Docs Project lead: [[User:laubersm|Susan Lauber]] ...ee]] -> [[:Category:Packaging guidelines]] is for the Packaging: namespace docs.
    5 KB (771 words) - 17:53, 5 March 2009
  • ...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
    3 KB (488 words) - 18:56, 5 April 2016
  • [[Category:Docs Project process]]
    1 KB (186 words) - 21:41, 1 July 2010
  • {{header|docs}} Before beginning this process, be sure you have been through the [[Preparing the Release Notes for final
    2 KB (386 words) - 15:08, 4 December 2012
  • {{lang|en|es|page=Reporting problems with Docs}} {{header|docs}}
    1 KB (235 words) - 21:33, 19 September 2016
  • ...the [[DocsProject|Docs Project]] Karsten "quaid" Wade about their joining process (30-40mins)
    1 KB (187 words) - 17:29, 4 January 2009
  • 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.
    3 KB (408 words) - 20:49, 19 September 2016
  • The contributor podcast is a project designed to give Fedora project contributors the chance to meet fellow contributors who they would not talk * To give project members a chance to interact with a contributor they normally would not tal
    4 KB (648 words) - 20:45, 19 April 2010
  • {{header|docs}} More information on the process is available at
    2 KB (338 words) - 15:14, 18 September 2016
  • A wiki is a community documentation space. The Fedora Documentation Project is the set of Master Gardeners with the role of helping to train all the ot ...re two major types of pages -- a content-focused page (Content_Area) and a project-focused page (Project_Name). Example namespaces are:
    7 KB (863 words) - 01:52, 17 October 2016
  • ...s and then translated into the many languages that the Fedora Localization Project supports. One unfortunate side effect of this process is that because the XML files must be complete before translators start wor
    2 KB (242 words) - 15:39, 11 November 2010
  • {{header|docs}} == Ideas on Improving the Fedora Docs Workflow ==
    6 KB (833 words) - 21:54, 22 May 2009
  • ...leaseNotes/Process| the Process page]] for details and start editing at [[Docs/Beats| ]] today.}} ...ty participation in the [[DocsProject/ReleaseNotes/Process | release notes process]].
    7 KB (1,000 words) - 04:24, 26 February 2009
  • ...ugh the [[Transifex]] interface, so they need to request the Documentation Project to add a new language to a particular document. ...he current release cycle -- https://translate.fedoraproject.org/projects/p/docs-release-notes/
    2 KB (247 words) - 02:03, 15 June 2010
  • {{header|docs}} [[Category:Docs Project process]]
    2 KB (270 words) - 14:48, 8 March 2018
  • {{header|docs}} == Docs Projects ==
    15 KB (2,236 words) - 20:02, 27 October 2010
  • ...ratively work on a set of files, such as in a development or documentation project. You can use [http://cvs.fedoraproject.org/viewcvs/?root=docs ViewCVS] to browse the Fedora Documentation CVS repository.
    12 KB (1,939 words) - 17:15, 21 November 2009
View (previous 50 | ) (20 | 50 | 100 | 250 | 500)